patacongo commented on PR #13018: URL: https://github.com/apache/nuttx/pull/13018#issuecomment-2302149425
> To improve the real-time performance of the system, we prefer to perform as few operations as possible within the interrupt function. We have designed an interrupt thread for each interrupt, where all the operations that are not necessary to be handled in the interrupt function are delegated to be processed by the interrupt thread. This description is the same as the description of the original intent of the high priority worker thread. The high priority worker thread is only a single thread and, hence, has bandwidth/latency limitations. https://cwiki.apache.org/confluence/display/NUTTX/Porting+Guide#hpwork > This makes me feel like we are going into the Nucleus LISR+HISR model Yes, the Nucleus model was the original intent. The high priority work queue was intended to be the bottom half of an interrupt handler. There may be multiple low priority threads retained in a thread pool. Multiple high priority threads could be implemented as will without bandwidth/latency issues. I'm not opposed to an alternative model. But we need to be careful with resource utilization. There is a trade-off between resource utilization and low latency interrupt performance. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
