# \[NET+OS\] Which Thread executes the naEthBypassTransmit Callback Function ?

**URL:** <https://forums.digi.com/t/net-os-which-thread-executes-the-naethbypasstransmit-callback-function/20980>\
**Category:** Embedded Devices\
**Tags:** net, thread, os, callback\
**Created:** [December 12, 2019, 10:37am UTC](https://forums.digi.com/t/net-os-which-thread-executes-the-naethbypasstransmit-callback-function/20980 "2019-12-12T10:37:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pierre\_Audenard](https://avatars.discourse-cdn.com/v4/letter/p/8491ac/32.png) [@Pierre\_Audenard](https://forums.digi.com/u/Pierre_Audenard)\
**Post date:** [December 12, 2019, 10:37am UTC](https://forums.digi.com/t/net-os-which-thread-executes-the-naethbypasstransmit-callback-function/20980/1 "2019-12-12T10:37:13Z")

</div>

The naEthBypassTransmit functions transmits an Ethernet bypass Packet.  
Once transmitted, The driver frees the packet but not the data buffer.  
A txCompleteFn callback is used to free the data buffer.

I would like to execute more code in this callback.

The question is : Which Thread executes this callback ?

---

<div class="post-metadata">

**Author:** ![LeonidM](https://avatars.discourse-cdn.com/v4/letter/l/d26b3c/32.png) [@LeonidM](https://forums.digi.com/u/LeonidM)\
**Post date:** [December 15, 2019, 8:46am UTC](https://forums.digi.com/t/net-os-which-thread-executes-the-naethbypasstransmit-callback-function/20980/2 "2019-12-15T08:46:06Z")

</div>

just put a breakpoint in that function and once you stop there, look at the call stack. You will see in what thread you are.

---

<div class="post-metadata">

**Author:** ![Pierre\_Audenard](https://avatars.discourse-cdn.com/v4/letter/p/8491ac/32.png) [@Pierre\_Audenard](https://forums.digi.com/u/Pierre_Audenard)\
**Post date:** [December 19, 2019, 10:59am UTC](https://forums.digi.com/t/net-os-which-thread-executes-the-naethbypasstransmit-callback-function/20980/3 "2019-12-19T10:59:04Z")

</div>

Thanks for your answer.

Unfortunaly I work without JTAG Emulator (connectcore module embedded in device).

tx\_thread\_identify returns a non null pointer.  
But tx\_thread\_info\_get (to get thread name) returns TX\_THREAD\_ERROR.

OK.  
I retrieve the name with -\>tx\_thread\_name.  
“ByPass Send Comlete”.  
Now I can see in eth\_api.c that one thread is especially created for this callback