From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Shibin Koikkara Reeny <shibin.koikkara.reeny@intel.com>,
<dev@dpdk.org>, <bruce.richardson@intel.com>
Cc: <ciara.loftus@intel.com>, <qi.z.zhang@intel.com>
Subject: Re: [PATCH v2] net/af_xdp: AF_XDP PMD CNI Integration
Date: Wed, 25 Jan 2023 16:43:20 +0000 [thread overview]
Message-ID: <bfec7393-d048-442a-bd35-6e448e396e51@intel.com> (raw)
In-Reply-To: <20221214154102.1521489-1-shibin.koikkara.reeny@intel.com>
On 12/14/2022 3:41 PM, Shibin Koikkara Reeny wrote:
> Integrate support for the AF_XDP CNI and device plugin [1] so that the
> DPDK AF_XDP PMD can work in an unprivileged container environment.
> Part of the AF_XDP PMD initialization process involves loading
> an eBPF program onto the given netdev. This operation requires
> privileges, which prevents the PMD from being able to work in an
> unprivileged container (without root access). The plugin CNI handles
> the program loading. CNI open Unix Domain Socket (UDS) and waits
> listening for a client to make requests over that UDS. The client(DPDK)
> connects and a "handshake" occurs, then the File Descriptor which points
> to the XSKMAP associated with the loaded eBPF program is handed over
> to the client. The client can then proceed with creating an AF_XDP
> socket and inserting the socket into the XSKMAP pointed to by the
> FD received on the UDS.
>
> A new vdev arg "use_cni" is created to indicate user wishes to run
> the PMD in unprivileged mode and to receive the XSKMAP FD from the CNI.
> When this flag is set, the XSK_LIBBPF_FLAGS__INHIBIT_PROG_LOAD libbpf flag
> should be used when creating the socket, which tells libbpf not to load the
> default libbpf program on the netdev. We tell libbpf not to do this because
> the loading is handled by the CNI in this scenario.
>
> [1]: https://github.com/intel/afxdp-plugins-for-kubernetes
>
> Signed-off-by: Shibin Koikkara Reeny <shibin.koikkara.reeny@intel.com>
> ---
Tested-by: Anatoly Burakov <anatoly.burakov@intel.com>
The testing setup is a bit involved, but everything seems to work once
all the pieces fall into place.
--
Thanks,
Anatoly
next prev parent reply other threads:[~2023-01-25 16:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <to=20221213104746.805221-1-shibin.koikkara.reeny@intel.com>
2022-12-14 15:41 ` Shibin Koikkara Reeny
2023-01-18 12:10 ` Zhang, Qi Z
2023-01-19 15:10 ` Koikkara Reeny, Shibin
2023-02-02 14:49 ` Zhang, Qi Z
2023-02-02 15:18 ` Bruce Richardson
2023-02-02 17:02 ` Koikkara Reeny, Shibin
2023-01-25 16:43 ` Burakov, Anatoly [this message]
2022-12-14 15:34 Shibin Koikkara Reeny
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=bfec7393-d048-442a-bd35-6e448e396e51@intel.com \
--to=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=ciara.loftus@intel.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.com \
--cc=shibin.koikkara.reeny@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).