gustavonihei commented on PR #8971:
URL: https://github.com/apache/nuttx/pull/8971#issuecomment-1499123554

   > > which are more efficient than the standard critical section APIs in 
regards to protecting the HR Timer resources
   > 
   > @gustavonihei Just curious of the above statement. How so?
   
   I haven't actually measured to present quantitative data, it is just a 
perception based on a simple comparison of the work executed by each API. The 
spinlock-based API just disables interrupts and spins in a lock, while the 
`[enter|leave]_critical_section` API performs a more complex logic, including 
the processing of inter-cpu pause requests.
   Besides, the usage of a device-local spinlock copes with defining a critical 
section of finer granularity on SMP-enabled systems, preventing false CPU 
locking.


-- 
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]

Reply via email to