Re: epoll oddities following setup/teardown optimizations

er 19, 2023 3:21:34 PM > To: dev@nuttx.apache.org > Subject: Re: epoll oddities following setup/teardown optimizations > > Hi, Marten > > I found some information about the epoll problem with the nonblocking local > socket. > From https://man7.org/linux/man-pages/man2/connect.2.

Re: epoll oddities following setup/teardown optimizations

te changes in > the underlying driver/module will never be detected and pollsetup not > re-ran when needed. > > > Regards > > Marten Svanfeldt > > > From: 汪博文 > Sent: Tuesday, September 19, 2023 12:11:27 PM > To: Mårten Svanfel

Re: epoll oddities following setup/teardown optimizations

r/module will never be detected and pollsetup not > re-ran when needed. > > > Regards > > Marten Svanfeldt > > > From: 汪博文 > Sent: Tuesday, September 19, 2023 12:11:27 PM > To: Mårten Svanfeldt > Cc: dev@nuttx.apache.org > Subject: RE

Re: epoll oddities following setup/teardown optimizations

ollsetup not re-ran when needed. Regards Marten Svanfeldt From: 汪博文 Sent: Tuesday, September 19, 2023 12:11:27 PM To: Mårten Svanfeldt Cc: dev@nuttx.apache.org Subject: RE: epoll oddities following setup/teardown optimizations Hi, I has a fix fs_epoll: add critical section for teardown process an

RE: epoll oddities following setup/teardown optimizations

Hi, I has a fix fs_epoll: add critical section for teardown process and reset the eph… by CV-Bowen ・ Pull Request #10706 ・ apache/nuttx (github.com) about this problem. But I couldn’t find your GitHub ID, so I’m notifying you through email. Could you

Re: epoll oddities following setup/teardown optimizations

Hi Wang Bowen and Marten, Is it possible to include an ostest with this code to avoid similar regression in the future? BR, Alan On 9/18/23, 汪博文 wrote: > Hi, > > I did the epoll optimization last year. And your analysis is right. The new > epoll implementation has BUG and I has reproduced

RE: epoll oddities following setup/teardown optimizations

Hi, I did the epoll optimization last year. And your analysis is right. The new epoll implementation has BUG and I has reproduced this issue locally based on your description. I’m very sorry that this issue has affected your nuttx upgrade. I will fix this issue as soon as possible. Thanks.

epoll oddities following setup/teardown optimizations

Hi, Our software heavily relies on epoll based wait/event loops, using mixes of "real" FDs (mostly sockets), eventfd and timerfds, and after upgrading to Nuttx 12.2.1 I have some oddities in behaviour that I think can be traced to the optimizations in