From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ciara Loftus <ciara.loftus@intel.com>, <dev@dpdk.org>
Cc: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/af_xdp: use bpf link for XDP programs
Date: Tue, 2 Nov 2021 16:50:10 +0000 [thread overview]
Message-ID: <55d9029e-59e4-83e5-fa12-5bb690b74bd4@intel.com> (raw)
In-Reply-To: <20211022104253.31999-1-ciara.loftus@intel.com>
On 10/22/2021 11:42 AM, Ciara Loftus wrote:
> Since v0.4.0, if the underlying kernel supports it, libbpf uses 'bpf link'
> to manage the programs on the interfaces of the xsks. This has two
> repercussions for the PMD.
>
> 1. In the case where the PMD asks libbpf to load the default XDP program,
> the PMD no longer needs to remove it on teardown. This is because bpf link
> handles the unloading under the hood.
> 2. In the case where the PMD loads a custom program, libbpf expects this
> program to be linked via bpf link prior to creating the socket.
>
> This patch introduces probes for the libbpf version and kernel support
> for bpf link and orchestrates the loading and unloading of
> programs according to the capabilities of the kernel and libbpf. The
> libbpf version is checked with meson and pkg-config. The probe for
> kernel support mirrors how it is implemented in libbpf. A bpf_link is
> created and looked up on loopback device. If successful, bpf_link will be
> used for the AF_XDP netdev.
>
> Signed-off-by: Ciara Loftus <ciara.loftus@intel.com>
> Signed-off-by: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2021-11-02 17:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 9:50 [dpdk-dev] [PATCH] " Ciara Loftus
2021-10-19 13:14 ` Ferruh Yigit
2021-10-22 10:29 ` Loftus, Ciara
2021-10-22 10:42 ` [dpdk-dev] [PATCH v2] " Ciara Loftus
2021-11-02 16:50 ` Ferruh Yigit [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=55d9029e-59e4-83e5-fa12-5bb690b74bd4@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ciara.loftus@intel.com \
--cc=dev@dpdk.org \
--cc=maciej.fijalkowski@intel.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).