From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Maryam Tahhan <mtahhan@redhat.com>,
stephen@networkplumber.org, lihuisong@huawei.com,
fengchengwen@huawei.com, liuyonglong@huawei.com,
shibin.koikkara.reeny@intel.com, ciara.loftus@intel.com
Cc: dev@dpdk.org
Subject: Re: [v1] doc/rel-notes: Add AF_XDP DP integration
Date: Fri, 15 Dec 2023 12:24:50 +0000 [thread overview]
Message-ID: <8f67e865-0dc5-4a28-8fb4-de54e501eb79@amd.com> (raw)
In-Reply-To: <20231215111528.950508-1-mtahhan@redhat.com>
On 12/15/2023 11:15 AM, Maryam Tahhan wrote:
> Add a new feature item that references the AF_XDP
> DP integration.
>
> Signed-off-by: Maryam Tahhan <mtahhan@redhat.com>
>
Hi Maryam,
Better to have documentation (including release note update) and code in
same patch.
If there will be a new version please combine both patches into one,
otherwise I can squash them together while merging.
> ---
> doc/guides/rel_notes/release_24_03.rst | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/doc/guides/rel_notes/release_24_03.rst b/doc/guides/rel_notes/release_24_03.rst
> index 6f8ad27808..606cdf6316 100644
> --- a/doc/guides/rel_notes/release_24_03.rst
> +++ b/doc/guides/rel_notes/release_24_03.rst
> @@ -55,6 +55,13 @@ New Features
> Also, make sure to start the actual text at the margin.
> =======================================================
>
> +* **Integration of AF_XDP PMD with AF_XDP Device Plugin**
> +
> + The EAL vdev argument for the AF_XDP PMD ``uds_path`` was added
> + to allow Kubernetes Pods that which to use AF_XDP with DPDK to run
> + with limited privileges. This flag indicates that the AF_XDP PMD
> + will be used in unprivileged mode and will receive the XSKMAP FD from
> + the AF_XDP Device Plugin.
>
Does it make sense to mentioned that 'use_cni' device argument is
removed? If there are some users of it, they may like to know that it is
removed/replaced.
Btw, I am not aware of any process on consistency of PMD device args,
but that is definitely something that can impact end user experience,
better to help them as much as possible.
next prev parent reply other threads:[~2023-12-15 12:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 11:15 Maryam Tahhan
2023-12-15 12:24 ` Ferruh Yigit [this message]
2023-12-15 15:38 ` Maryam Tahhan
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=8f67e865-0dc5-4a28-8fb4-de54e501eb79@amd.com \
--to=ferruh.yigit@amd.com \
--cc=ciara.loftus@intel.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=lihuisong@huawei.com \
--cc=liuyonglong@huawei.com \
--cc=mtahhan@redhat.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).