Raslan, Ferruh In these patches (merged in mlx5 tree) just the commit messages are updated: http://patchwork.dpdk.org/patch/64831/ http://patchwork.dpdk.org/patch/64832/ http://patchwork.dpdk.org/patch/64852/
With best regards, Slava > -----Original Message----- > From: Ferruh Yigit <ferruh.yi...@intel.com> > Sent: Wednesday, January 8, 2020 16:47 > To: Slava Ovsiienko <viachesl...@mellanox.com>; dev@dpdk.org > Cc: Matan Azrad <ma...@mellanox.com>; Raslan Darawsheh > <rasl...@mellanox.com>; Ori Kam <or...@mellanox.com>; sta...@dpdk.org > Subject: Re: [dpdk-stable] [PATCH] net/mlx5: fix matcher metadata register c0 > field setup > > On 12/20/2019 7:48 AM, Viacheslav Ovsiienko wrote: > > The metadata register c0 field in the matcher might be split into two > > independent fields - the source vport index and META item value. These > > fields have no permanent assigned bits, the configuration is queried > > from the kernel drivers. > > > > MLX5_SET configures the specified 32-bit field as whole entity. > > For metadata register c0 we should take into account the provided mask > > in order to configure the specified subfield bits only. > > Hi Slava, > > Is there a more human friendly name for the field instead of "C0"? > > I don't know what "matcher metadata register" is, what is the impact of the > fix? > Which functionality was broken now fixed? Does it make sense to reflect it in > the patch title / commit log? > > Same comment for the related patches: > net/mlx5: fix register c0 usage for metadata entities > net/mlx5: fix metadata item endianness conversion
