Hi Ferruh & Thomas, > -----Original Message----- > From: Ferruh Yigit <ferruh.yi...@intel.com> > Sent: Thursday, May 6, 2021 2:21 AM > To: Bing Zhao <bi...@nvidia.com>; Slava Ovsiienko > <viachesl...@nvidia.com>; Matan Azrad <ma...@nvidia.com>; NBU- > Contact-Thomas Monjalon <tho...@monjalon.net> > Cc: dev@dpdk.org; Ori Kam <or...@nvidia.com>; Raslan Darawsheh > <rasl...@nvidia.com> > Subject: Re: [dpdk-dev] [PATCH v7 17/17] doc: update mlx5 support > for conntrack > > External email: Use caution opening links or attachments > > > On 5/5/2021 1:23 PM, Bing Zhao wrote: > > In the release notes and mlx5 NIC document, the support and > limitation > > of connection tracking are added. > > > > A new NIC feature seems added, better to be acked beyond the mlx5 > scope. > > > Signed-off-by: Bing Zhao <bi...@nvidia.com> > > Acked-by: Viacheslav Ovsiienko <viachesl...@nvidia.com> > > --- > > doc/guides/nics/features/default.ini | 1 + > > doc/guides/nics/features/mlx5.ini | 1 + > > doc/guides/nics/mlx5.rst | 14 ++++++++++++++ > > doc/guides/rel_notes/release_21_05.rst | 2 ++ > > 4 files changed, 18 insertions(+) > > > > diff --git a/doc/guides/nics/features/default.ini > > b/doc/guides/nics/features/default.ini > > index 8046bd121e..0deb4ef547 100644 > > --- a/doc/guides/nics/features/default.ini > > +++ b/doc/guides/nics/features/default.ini > > @@ -66,6 +66,7 @@ Module EEPROM dump = > > Registers dump = > > LED = > > Multiprocess aware = > > +Connection tracking = > > FreeBSD = > > Linux = > > Windows = > > Need to update 'doc/guides/nics/features.rst' too, to describe new > feature. > > I will drop new feature part in next-net, it can be sent as separate > patch later. Will keep driver and release notes documentation.
http://patches.dpdk.org/project/dpdk/patch/20210518125235.90185-1-bi...@nvidia.com/ A new patch with the updated description is in the link below. I checked the file of the "features.rst" again, it seems that only the API for ethdev are described. Even if conntrack is a new feature and provided by new HW, but the only way to operate on it is to use rte_flow API now. So I am not quite sure if it is possible and proper to list the feature in the driver feature lists table. What do you think? BR. Bing
