Hi,
I need to design the receiving and sending task threads to consume as less as possible from the system (DSP/BIOS) resources.
Is there a mechanism implemented in the NDK to achieve this goals?
Anatoly.
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi,
I need to design the receiving and sending task threads to consume as less as possible from the system (DSP/BIOS) resources.
Is there a mechanism implemented in the NDK to achieve this goals?
Anatoly.
Anatoly,
It's not clear what "DSP/BIOS" resources you are referring to. Do you mean task stack memory? Or do you mean that you want the task threads to take as little as possible of the CPU cycles relative to your application threads? Or something else?
Also, what version of the NDK and BIOS are you using? And on what device and platform?
Hi,
The DSP/BIOS is 5.41.10.36, NDK2.20.04.26. The board is OMAP -L138 C6748 DSP, no ARM.
I want the transmitting/receiving task threads to take as little as possible of the CPU cycles so I have more "time" for other application threads. I need the transceiving task threads not to block others, and release all the time when the TCP stack has no activity.
Anatoly,
You can try making your send/receive tasks have lower priority than the other tasks in your system. I would suggest experimenting with different priorities and see if that gives you the desired effects.
Steve
I'm using NDK 2 for ethernet application.
Is it possible to make these threads active only on data transmit/receive events or interrupts coming from the lower layers of the NDK?