On Wed, Sep 1, 2021 at 9:33 PM Cong Wang <xiyou.wangcong@xxxxxxxxx> wrote: > > On Tue, Aug 31, 2021 at 12:33 PM Cong Wang <xiyou.wangcong@xxxxxxxxx> wrote: > > Like I mentioned before, I suspect there is some delay in one of > > the queues on the way or there is a worker wakeup latency. > > I will try adding some tracepoints to see if I can capture it. > > > > I tried to revert this patch locally to reproduce the EAGAIN > failure, but even after repeating the sockmap_listen test hundreds > of times, I didn't see any failure here. > > If you are still interested in this issue, I'd suggest you adding some > tracepoints to see what happens to kworker or the packet queues. > > It does not look like a sockmap bug, otherwise I would be able to > reproduce it here. > Cong, the issue is not that read() sometimes returns EAGAIN. It is that when using select on the redirected socket, it will hang forever. > Thanks.
