DPDK patches and discussions
 help / color / mirror / Atom feed
From: Matan Azrad <matan@nvidia.com>
To: David Marchand <david.marchand@redhat.com>,
	Michael Baum <michaelba@nvidia.com>
Cc: "NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
	"dev@dpdk.org" <dev@dpdk.org>,
	Raslan Darawsheh <rasland@nvidia.com>,
	Slava Ovsiienko <viacheslavo@nvidia.com>,
	dpdk stable <stable@dpdk.org>
Subject: RE: [PATCH] net/mlx5: fix FD configuration for Rx interrupt
Date: Mon, 14 Mar 2022 10:49:08 +0000	[thread overview]
Message-ID: <DM4PR12MB538938769E464AA60DC9663DDF0F9@DM4PR12MB5389.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8w8Uw4OkokvFCbkYTE2NT1hKAU5+5tcDY4qAMh29XQWEA@mail.gmail.com>



From: David Marchand
> On Thu, Mar 10, 2022 at 6:04 PM Michael Baum <michaelba@nvidia.com>
> wrote:
> > > > # strace -r -f ./dpdk-dir/v21.11/examples/dpdk-l3fwd-power
> > > > --lcores
> > > > 0@3,1@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.

+1



 
> 
> --
> David Marchand


      reply	other threads:[~2022-03-14 10:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10 13:19 Michael Baum
2022-03-10 15:12 ` David Marchand
2022-03-10 16:16   ` Thomas Monjalon
2022-03-10 17:04     ` Michael Baum
2022-03-14  9:31       ` David Marchand
2022-03-14 10:49         ` Matan Azrad [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DM4PR12MB538938769E464AA60DC9663DDF0F9@DM4PR12MB5389.namprd12.prod.outlook.com \
    --to=matan@nvidia.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=michaelba@nvidia.com \
    --cc=rasland@nvidia.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=viacheslavo@nvidia.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).