Mesh application threading

[mneber]

Hi Nordic,

I have a general question about kernel threads in the mesh stack. From memory, Bluetooth has its own thread in the stack I think. At some point in the stack the Bluetooth thread would pass off a received message to another thread (application thread?) which delivers the received bytes to the model and is accessible by the application code. Is that assumption correct?

my question comes from processing the received message and then transmitting out over uart. I want to balance thread workloads so that we don’t miss any messages from uart or mesh. 

thanks!

[Edvin]

Hello,

Are you currently struggling with packet loss? Or is this some hypothetical scenario that you want to avoid?

The handling of the messages coming from thread are already handled in a different thread than the parts that receives the messages themselves, so I would be surprised if you are seeing issues like that.

Best regards,

Edvin

[mneber]

Thanks Edvin. We are still authoring. The question came up as how to balance processing in the different parts of the application. 

with some digging I could see where the handoff happens in the mesh stack. I also noted where the messages are handled as stack variables and followed that method in our application processing.