From: Magnus Karlsson <magnus.karlsson@gmail.com>
To: Dan Siemon <dan@coverfire.com>
Cc: Xdp <xdp-newbies@vger.kernel.org>
Subject: Re: AF_XDP (i40e) behavior change in 5.11?
Date: Fri, 26 Mar 2021 08:37:34 +0100 [thread overview]
Message-ID: <CAJ8uoz1OTAW36rM4An1ZtO4M_0HTGjps5FKWfYwAuTGCQoHVmg@mail.gmail.com> (raw)
In-Reply-To: <eb19b630c087ba6497f2a0a627c232d45a5af22f.camel@coverfire.com>
On Thu, Mar 25, 2021 at 11:17 PM Dan Siemon <dan@coverfire.com> wrote:
>
> On Wed, 2021-03-24 at 11:00 +0100, Magnus Karlsson wrote:
> > On Wed, Mar 24, 2021 at 10:22 AM Dan Siemon <dan@coverfire.com>
> > wrote:
> > >
> > > ./xsk_fwd -i ens1f0 -q 2 -i ens1f1 -q 2 -c 5 -i ens1f0 -q 3 -i
> > > ens1f1 -
> > > q 3 -c 6
> > >
> > > On 5.10, the cores (2,3) assigned interrupts for the queues (2,3)
> > > are
> > > idle when there is no traffic.
> > >
> > > On 5.11, the cores immediately go to 100% system time when the
> > > program
> > > starts (as viewed in htop). There is no network traffic.
> > >
> > > Intel 710/i40e.
> > >
> > > I tried this with xsk_fwd built from 5.10 and 5.11 trees with the
> > > same
> > > result.
> > >
> > > Is this behavior change expected?
> >
> > Thanks for reporting this. No, this is not intentional. I did send up
> > a fix for a bug in the i40e driver that was introduced in 5.11. It
> > might be the culprit. Could you please try the patch below and see if
> > it works? It is not yet in net.
> >
> > https://www.spinics.net/lists/netdev/msg729128.htm
>
> Hi Magnus,
>
> It appears (quick testing) that the patch fixes the problem.
Perfect! I will send a mail and try to get it through the internal
testing as soon as possible so we can get it up on the list and
merged.
Thank you: Magnus
> Thanks.
>
prev parent reply other threads:[~2021-03-26 7:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 2:30 AF_XDP (i40e) behavior change in 5.11? Dan Siemon
2021-03-24 10:00 ` Magnus Karlsson
2021-03-25 22:17 ` Dan Siemon
2021-03-26 7:37 ` Magnus Karlsson [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=CAJ8uoz1OTAW36rM4An1ZtO4M_0HTGjps5FKWfYwAuTGCQoHVmg@mail.gmail.com \
--to=magnus.karlsson@gmail.com \
--cc=dan@coverfire.com \
--cc=xdp-newbies@vger.kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).