[PATCH] net/mlx5: fix FD configuration for Rx interrupt

[David Marchand]

On Thu, Mar 10, 2022 at 6:04 PM Michael Baum <michaelba at nvidia.com> wrote:
> > > # strace -r -f ./dpdk-dir/v21.11/examples/dpdk-l3fwd-power --lcores
> > > 0 at 3,1 at 5 -a 0000:82:00.0 --in-memory -- -p 0x1 -P --config '(0,0,1)'
> > > ...
> > > [pid 534983]      0.000348 epoll_wait(26, [], 1, 10) = 0
> > > [pid 534983]      0.010082 read(24,
> > >
> > > For some reason, there is an event available for fd 18 right away
> > > (which is the issue in the first place).
>
> I don't understand who is FD 18, I cannot see it in your log

I had refreshed the trace before sending, but did not update the mail,
I meant fd 24.


Now, looking from scratch (rather than my one month old mail),
epoll_wait() returning 0 is normal since it's returning on a 10ms
timeout.
The mlx5 rx fd should be left in non blocking mode.


-- 
David Marchand