lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 12 Nov 2020 11:57:16 -0800 From: Saeed Mahameed <saeed@...nel.org> To: Naveen Mamindlapalli <naveenm@...vell.com>, netdev@...r.kernel.org, linux-kernel@...r.kernel.org Cc: kuba@...nel.org, davem@...emloft.net, sgoutham@...vell.com, lcherian@...vell.com, gakula@...vell.com, jerinj@...vell.com, sbhatta@...vell.com, hkelam@...vell.com Subject: Re: [PATCH v3 net-next 01/13] octeontx2-af: Modify default KEX profile to extract TX packet fields On Wed, 2020-11-11 at 12:43 +0530, Naveen Mamindlapalli wrote: > From: Stanislaw Kardach <skardach@...vell.com> > > 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 <skardach@...vell.com> > Signed-off-by: Sunil Goutham <sgoutham@...vell.com> > Signed-off-by: Naveen Mamindlapalli <naveenm@...vell.com> > Reviewed-by: Saeed Mahameed <saeedm@...dia.com>
Powered by blists - more mailing lists