From: Jesper Dangaard Brouer <jbrouer@redhat.com>
To: David Ahern <dsahern@gmail.com>
Cc: Cameron Elliott <cameron@cameronelliott.com>,
Xdp <xdp-newbies@vger.kernel.org>,
Magnus Karlsson <magnus.karlsson@gmail.com>
Subject: Re: xdpsock ... -N -z and AF_XDP XDP_ZEROCOPY not working: RESOLVED!
Date: Thu, 30 Jan 2020 09:02:03 +0100 [thread overview]
Message-ID: <20200130090203.71b475a0@carbon> (raw)
In-Reply-To: <c45f64a7-ffff-a123-818c-4dc127cd3ff4@gmail.com>
On Wed, 29 Jan 2020 21:41:57 -0700
David Ahern <dsahern@gmail.com> wrote:
> On 1/29/20 6:02 PM, Cameron Elliott wrote:
> > With this command:
> > git clone git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git
> > More info: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/
> >
> > I built the kernel using these directions:
> > https://wiki.ubuntu.com/KernelTeam/GitKernelBuild
> >
> > And after rebooting and running on the 5.5 bpf-next kernel, -z and
> > XDP_ZEROCOPY were working fine!
>
> since this is literally bleeding edge, is there a wiki/doc/other for
> kernel versions and supported features? Something similar to what MLX
> does for switchdev [1] would be really helpful.
>
> [1] https://github.com/Mellanox/mlxsw/wiki
The IOvisor BCC project tries to keep track of kernel version and BPF +
XDP features, here[2]:
[2] https://github.com/iovisor/bcc/blob/master/docs/kernel-versions.md
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
prev parent reply other threads:[~2020-01-30 8:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-30 1:02 xdpsock ... -N -z and AF_XDP XDP_ZEROCOPY not working: RESOLVED! Cameron Elliott
2020-01-30 4:41 ` David Ahern
2020-01-30 8:02 ` Jesper Dangaard Brouer [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=20200130090203.71b475a0@carbon \
--to=jbrouer@redhat.com \
--cc=cameron@cameronelliott.com \
--cc=dsahern@gmail.com \
--cc=magnus.karlsson@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.