From: Maryam Tahhan <mtahhan@redhat.com>
To: ferruh.yigit@amd.com, stephen@networkplumber.org,
lihuisong@huawei.com, fengchengwen@huawei.com,
liuyonglong@huawei.com, david.marchand@redhat.com,
shibin.koikkara.reeny@intel.com, ciara.loftus@intel.com
Cc: dev@dpdk.org
Subject: Re: [v8 0/3] net/af_xdp: fix multi interface support for K8s
Date: Wed, 14 Feb 2024 16:18:56 +0000 [thread overview]
Message-ID: <cc8638f2-008e-4c6b-a479-ee6e10a5b853@redhat.com> (raw)
In-Reply-To: <20240214160716.2391286-1-mtahhan@redhat.com>
Sorry folks
Just spotted the checkpatch warnings :( I will fix these now.
BR
Maryam
On 14/02/2024 16:06, Maryam Tahhan wrote:
> The original `use_cni` implementation was limited to
> supporting only a single netdev in a DPDK pod. This patchset
> aims to fix this limitation transparently to the end user.
> It will also enable compatibility with the latest AF_XDP
> Device Plugin.
>
> Signed-off-by: Maryam Tahhan <mtahhan@redhat.com>
> ---
> v8:
> * Go back to using `use_cni` vdev argument
> * Introduce `use_map_pinning` vdev param.
> * Rename `uds_path` to `dp_path` so that it can be used
> with map pinning as well as `use_cni`.
> * Set `dp_path` internally in the AF_XDP PMD if it's
> not configured by the user.
> * Clean up the original `use_cni` documentation separately
> to coding changes.
>
> v7:
> * Give a more descriptive commit msg headline.
> * Fixup typos in documentation.
>
> v6:
> * Add link to PR 81 in commit message
> * Add release notes changes to this patchset
>
> v5:
> * Fix alignment for ETH_AF_XDP_USE_DP_UDS_PATH_ARG
> * Remove use_cni references in af_xdp.rst
>
> v4:
> * Rename af_xdp_cni.rst to af_xdp_dp.rst
> * Removed all incorrect references to CNI throughout af_xdp
> PMD file.
> * Fixed Typos in af_xdp_dp.rst
>
> v3:
> * Remove `use_cni` vdev argument as it's no longer needed.
> * Update incorrect CNI references for the AF_XDP DP in the
> documentation.
> * Update the documentation to run a simple example with the
> AF_XDP DP plugin in K8s.
>
> v2:
> * Rename sock_path to uds_path.
> * Update documentation to reflect when CAP_BPF is needed.
> * Fix testpmd arguments in the provided example for Pods.
> * Use AF_XDP API to update the xskmap entry.
> ---
> Maryam Tahhan (3):
> docs: AF_XDP Device Plugin
> net/af_xdp: fix multi interface support for K8s
> net/af_xdp: support AF_XDP DP pinned maps
>
> doc/guides/howto/af_xdp_cni.rst | 253 ------------------
> doc/guides/howto/af_xdp_dp.rst | 349 +++++++++++++++++++++++++
> doc/guides/howto/index.rst | 2 +-
> doc/guides/nics/af_xdp.rst | 44 +++-
> doc/guides/rel_notes/release_24_03.rst | 17 ++
> drivers/net/af_xdp/rte_eth_af_xdp.c | 162 ++++++++----
> 6 files changed, 527 insertions(+), 300 deletions(-)
> delete mode 100644 doc/guides/howto/af_xdp_cni.rst
> create mode 100644 doc/guides/howto/af_xdp_dp.rst
>
prev parent reply other threads:[~2024-02-14 16:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 16:06 Maryam Tahhan
2024-02-14 16:06 ` [v8 1/3] docs: AF_XDP Device Plugin Maryam Tahhan
2024-02-14 16:06 ` [v8 2/3] net/af_xdp: fix multi interface support for K8s Maryam Tahhan
2024-02-14 16:06 ` [v8 3/3] net/af_xdp: support AF_XDP DP pinned maps Maryam Tahhan
2024-02-14 16:18 ` Maryam Tahhan [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=cc8638f2-008e-4c6b-a479-ee6e10a5b853@redhat.com \
--to=mtahhan@redhat.com \
--cc=ciara.loftus@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=ferruh.yigit@amd.com \
--cc=lihuisong@huawei.com \
--cc=liuyonglong@huawei.com \
--cc=shibin.koikkara.reeny@intel.com \
--cc=stephen@networkplumber.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).