On Wed, Nov 4, 2015 at 12:14 PM, will sanfilippo <[email protected]> wrote: > I dont have an answer but I would like to add something using the BLE stack > as an example. The BLE stack wants to create tasks or a task and it wants the > highest priority task. How do we let people know that the BLE stack must have > the highest priority task? Through documentation? If we let people define > task priorities there is a risk that they give the BLE task an incorrect > priority. This would be an issue with either approach btw. >
I think this is documentation. You may want it to be the highest priority task, but what if somebody has two interfaces, and doesn't care if they miss packets or data on the BLE link? I think it should just be clearly spelled out in documentation that it's a good thing for BLE to be highest priority task, and the latency requirement from when an interrupt occurs to when the task is swapped in (and count a statistic/log a message when that happens.) Sterling
