From: Piotr Raczynski <piotr.raczynski@intel.com>
To: Rafael Vargas <vargas@khomp.com>
Cc: xdp-newbies@vger.kernel.org
Subject: Re: Kernel Panic when loading XDP on i40e driver
Date: Wed, 19 Aug 2020 12:16:15 -0400 [thread overview]
Message-ID: <20200819161615.GA13798@kpll.igk.intel.com> (raw)
In-Reply-To: <CAEaYocZ6Px5Jyt96TDrqyJNXbYps-GTrrSeGFm9nZeUPO-9U2Q@mail.gmail.com>
On Wed, Aug 19, 2020 at 11:08:31AM -0300, Rafael Vargas wrote:
> Em sex., 7 de ago. de 2020 às 12:51, Rafael Vargas <vargas@khomp.com> escreveu:
> > [...]
> > Using kernel 5.8 (mainline from kernel.org) and a Lenovo Intel X722
> > controller (using the i40e driver). Loading any XDP program to this
> > driver will immediately crash with a Kernel Panic.
> >[...]
>
Hi Rafael,
> I've tested with the net-next kernel and there is no Kernel Panic
> there, but looks like native XDP support is not working on i40e, as
> iproute2 reports it as xdpgeneric. Is this correct or am I missing
> something in the way I load my programs (libbpf's
> bpf_set_link_xdp_fd)?
>
We're aware of the issue with X722 and have the fix cooking,
in general native mode works on i40e, but you'll see issues
with X722. We'll submit a patch ASAP.
If it's reported as xdpgeneric, are you sure you set
XDP_FLAGS_DRV_MODE flag when calling bpf_set_link_xdp_fd?
> Also the driver that is currently supplied by Intel and the one
> supplied in the kernel sources seems to have diverged...
Out of tree driver does not have AF_XDP in place as of now,
however XDP is supposed to work fine, again, not with X722.
prev parent reply other threads:[~2020-08-19 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 15:51 Kernel Panic when loading XDP on i40e driver Rafael Vargas
2020-08-07 17:01 ` Jesse Brandeburg
2020-08-19 14:08 ` Rafael Vargas
2020-08-19 16:16 ` Piotr Raczynski [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=20200819161615.GA13798@kpll.igk.intel.com \
--to=piotr.raczynski@intel.com \
--cc=vargas@khomp.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 NNTP newsgroup(s).