Hi Saeed,
Thanks for the review.

> -----Original Message-----
> From: Saeed Mahameed <[email protected]>
> Sent: Friday, November 13, 2020 1:27 AM
> To: Naveen Mamindlapalli <[email protected]>; [email protected];
> [email protected]
> Cc: [email protected]; [email protected]; Sunil Kovvuri Goutham
> <[email protected]>; Linu Cherian <[email protected]>;
> Geethasowjanya Akula <[email protected]>; Jerin Jacob Kollanukkaran
> <[email protected]>; Subbaraya Sundeep Bhatta <[email protected]>;
> Hariprasad Kelam <[email protected]>
> Subject: [EXT] Re: [PATCH v3 net-next 01/13] octeontx2-af: Modify default KEX
> profile to extract TX packet fields
> 
> External Email
> 
> ----------------------------------------------------------------------
> On Wed, 2020-11-11 at 12:43 +0530, Naveen Mamindlapalli wrote:
> > From: Stanislaw Kardach <[email protected]>
> >
> > The current default Key Extraction(KEX) profile can only use RX packet
> > fields while generating the MCAM search key. The profile can't be used
> > for matching TX packet fields. This patch modifies the default KEX
> > profile to add support for extracting TX packet fields into MCAM
> > search key. Enabled Tx KPU packet parsing by configuring TX PKIND in
> > tx_parse_cfg.
> >
> > Also modified the default KEX profile to extract VLAN TCI from the
> > LB_PTR and exact byte offset of VLAN header. The NPC KPU parser was
> > modified to point LB_PTR to the starting byte offset of VLAN header
> > which points to the tpid field.
> >
> > Signed-off-by: Stanislaw Kardach <[email protected]>
> > Signed-off-by: Sunil Goutham <[email protected]>
> > Signed-off-by: Naveen Mamindlapalli <[email protected]>
> >
> 
> Reviewed-by: Saeed Mahameed <[email protected]>
> 

Reply via email to