From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Shibin Koikkara Reeny <shibin.koikkara.reeny@intel.com>,
dev@dpdk.org, qi.z.zhang@intel.com, anatoly.burakov@intel.com,
bruce.richardson@intel.com, john.mcnamara@intel.com
Cc: ciara.loftus@intel.com
Subject: Re: [PATCH v4] net/af_xdp: AF_XDP PMD CNI Integration
Date: Fri, 10 Feb 2023 13:41:51 +0000 [thread overview]
Message-ID: <fe181999-f4bf-0029-92ff-b97104616a5d@amd.com> (raw)
In-Reply-To: <20230209120549.388318-1-shibin.koikkara.reeny@intel.com>
On 2/9/2023 12:05 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.
>
> Patch include howto doc explain how to configure AF_XDP CNI to
> working with DPDK.
>
> [1]: https://github.com/intel/afxdp-plugins-for-kubernetes
>
> Signed-off-by: Shibin Koikkara Reeny <shibin.koikkara.reeny@intel.com>
btw, it is just a detail but if you will send a new version, can you
please fix the patch title to remove the duplicated "af_xdp", it can be
something like:
net/af_xdp: support CNI integration
next prev parent reply other threads:[~2023-02-10 13:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <to=20221214154102.1521489-1-shibin.koikkara.reeny@intel.com>
2023-02-02 16:55 ` [PATCH v3] " Shibin Koikkara Reeny
2023-02-03 9:46 ` Mcnamara, John
2023-02-08 8:23 ` Zhang, Qi Z
2023-02-08 18:30 ` Ferruh Yigit
2023-02-09 11:49 ` Koikkara Reeny, Shibin
2023-02-09 12:05 ` [PATCH v4] " Shibin Koikkara Reeny
2023-02-10 13:04 ` Ferruh Yigit
2023-02-10 15:38 ` Koikkara Reeny, Shibin
2023-02-10 20:50 ` Ferruh Yigit
2023-02-10 13:41 ` Ferruh Yigit [this message]
2023-02-10 15:48 ` [PATCH v5] net/af_xdp: support " Shibin Koikkara Reeny
2023-02-14 14:50 ` Mcnamara, John
2023-02-15 16:30 ` [PATCH v6] " Shibin Koikkara Reeny
2023-02-16 13:50 ` Ferruh Yigit
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=fe181999-f4bf-0029-92ff-b97104616a5d@amd.com \
--to=ferruh.yigit@amd.com \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=ciara.loftus@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--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).