Re: epoll oddities following setup/teardown optimizations

2023-09-19 Thread 汪博文
Hi, I understood your meaning. You are right. You mean the taskB should also get the POLLIN event when taskA send some data event if taskB do not check the socket connected event. I will take a look about this. Regards Wang Bowen Mårten Svanfeldt 于2023年9月19日周二 21:41写道: > Hi, > > > I know a POL

Re: epoll oddities following setup/teardown optimizations

2023-09-19 Thread Mårten Svanfeldt
Hi, I know a POLLOUT would be the right thing if I am interested in knowing when the connection is complete, but I don't care :) I _could_ add a POLLOUT just to "work around" this error however I prefer not. We only care about when there is data available, so POLLIN is correct, and it works

Re: epoll oddities following setup/teardown optimizations

2023-09-19 Thread 汪博文
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.html, we can see: EINPROGRESS The socket is nonblocking and the connection cannot be completed immediately. (UNIX domai

Re: epoll oddities following setup/teardown optimizations

2023-09-19 Thread Mårten Svanfeldt
Hello, I did some quick checking and it does indeed solve my problem. Do you want me to give a review/ack on the github PR? I do have an account there with id "thebolt" (but it is not yet linked to my current employers email from which I am writing this) I do however still have some epoll pr

RE: epoll oddities following setup/teardown optimizations

2023-09-19 Thread 汪博文
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: [EXT] Re: CTU CAN FD driver multi-licence for Nuttx

2023-09-19 Thread Pavel Pisa
Hello Greg and others, On Thursday 14 of September 2023 17:19:16 Gregory Nutt wrote: > On 9/14/2023 8:52 AM, Alan C. Assis wrote: > > I think the authors of the driver can release the source code using > > two or more licenses. > > cd c > > We already have an example of it in NuttX: SocketCAN > >