[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BY3PR18MB470718017D6B5513C87883E3A0959@BY3PR18MB4707.namprd18.prod.outlook.com>
Date: Mon, 10 Apr 2023 08:43:51 +0000
From: Sai Krishna Gajula <saikrishnag@...vell.com>
To: Simon Horman <simon.horman@...igine.com>
CC: "davem@...emloft.net" <davem@...emloft.net>,
"edumazet@...gle.com" <edumazet@...gle.com>,
"kuba@...nel.org" <kuba@...nel.org>,
"pabeni@...hat.com" <pabeni@...hat.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Sunil Kovvuri Goutham <sgoutham@...vell.com>,
Geethasowjanya Akula <gakula@...vell.com>,
"richardcochran@...il.com" <richardcochran@...il.com>,
Linu Cherian <lcherian@...vell.com>,
Jerin Jacob Kollanukkaran <jerinj@...vell.com>,
Hariprasad Kelam <hkelam@...vell.com>,
Subbaraya Sundeep Bhatta <sbhatta@...vell.com>,
Ratheesh Kannoth <rkannoth@...vell.com>
Subject: Re: [net PATCH v2 5/7] octeontx2-af: Fix issues with NPC field hash
extract
Please see inline,
> -----Original Message-----
> From: Simon Horman <simon.horman@...igine.com>
> Sent: Saturday, April 8, 2023 8:51 PM
> To: Sai Krishna Gajula <saikrishnag@...vell.com>
> Cc: davem@...emloft.net; edumazet@...gle.com; kuba@...nel.org;
> pabeni@...hat.com; netdev@...r.kernel.org; linux-
> kernel@...r.kernel.org; Sunil Kovvuri Goutham <sgoutham@...vell.com>;
> Geethasowjanya Akula <gakula@...vell.com>; richardcochran@...il.com;
> Linu Cherian <lcherian@...vell.com>; Jerin Jacob Kollanukkaran
> <jerinj@...vell.com>; Hariprasad Kelam <hkelam@...vell.com>;
> Subbaraya Sundeep Bhatta <sbhatta@...vell.com>; Ratheesh Kannoth
> <rkannoth@...vell.com>
> Subject: Re: [net PATCH v2 5/7] octeontx2-af: Fix issues with NPC field
> hash extract
>
> On Fri, Apr 07, 2023 at 05:53:42PM +0530, Sai Krishna wrote:
> > From: Ratheesh Kannoth <rkannoth@...vell.com>
> >
> > 1. As per previous implementation, mask and control parameter to
> > generate the field hash value was not passed to the caller program.
> > Updated the secret key mbox to share that information as well, as a
> > part of the fix.
> > 2. Earlier implementation did not consider hash reduction of both
> > source and destination IPv6 addresses. Only source IPv6 address was
> > considered. This fix solves that and provides option to hash reduce
> > both source and destination IPv6 addresses.
> > 3. Fix endianness issue during hash reduction while storing the IPv6
> > source/destination address as hash keys.
> > 4. Configure hardware parser based on hash extract feature enable flag
> > for IPv6.
>
> Hi Sai and Ratheesh,
>
> there is a lot going on here.
> Could you consider breaking this up into more than one patch?
We will break this patch into multiple patches and submit v3.
Thanks,
Sai
Powered by blists - more mailing lists