patacongo commented on PR #12802: URL: https://github.com/apache/nuttx/pull/12802#issuecomment-2259107726
> I'm on the fence a bit here. Despite most of other RTOSes have event groups I think Linux always was going in paradigm of using file descriptors + select to implement "wait for multiple events" and that it why timerfd, signalfd and other file descriptor extensions exist. I do not think that POSIX has a good solution for that. @patacongo I would appreciate your vision/comment here. This appears to be new OS internal functionality and not available to applications. Hence, there are no file descriptors. It uses internal OS naming (nxevent_ prefix) and does not support any system call interface for applications. I only skimmed the functionality, but it seems to be functionally similar to pthread barriers. Do I understand that correctly? If so, why are there two implementations of such similar functionality. Shouldn't there correctly be only one, with logic like this providing the common backend functionality for pthread barriers? -- 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: commits-unsubscr...@nuttx.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
