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 <mtah...@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.
