hujun260 commented on PR #17468: URL: https://github.com/apache/nuttx/pull/17468#issuecomment-3832851817
> One more update for you all: > > 1. In the process of promoting NuttX right now, most business stakeholders have extremely high requirements for kernel performance and will opt for Zephyr as their first choice. Developers also have numerous doubts about the stability and performance of the NuttX kernel. > 2. When working on your internal solutions, you’d better research how other companies have implemented their corresponding solutions. Even Bestechnic, your Tier 1 supplier, does not recommend using your framework for headphone and Wi-Fi/BT module solutions. > 3. The next-generation OS will be built on the first principles rather than being based on excessive assumptions. Any business implementations with poor performance or flaws should be phased out and optimized, instead of having the operating system do a great deal of unnecessary fallback work for them. It just means we are encountering different usage scenarios. While enter_critical_section might work for very simple cases, But, nuttX needs to evolve. Memory safety issues are not imaginary. Let's take the function nxsched_foreach as an example. We cannot guarantee that the tcb parameter passed to the handler is always valid. Neither enter_critical_section nor sched_lock can solve this problem. If the handler performs a wait operation, it will invalidate the entire critical section and the scheduling lock. <img width="506" height="443" alt="image" src="https://github.com/user-attachments/assets/1c4f4e45-b4e6-4601-8392-5904b928f45e"; /> -- 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]
