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
| ||
|
Message-ID: <PH0PR11MB5013728221A46185F0032B6496679@PH0PR11MB5013.namprd11.prod.outlook.com> Date: Mon, 24 Apr 2023 06:35:11 +0000 From: "Buvaneswaran, Sujai" <sujai.buvaneswaran@...el.com> To: Michal Swiatkowski <michal.swiatkowski@...ux.intel.com>, "intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org> CC: "pmenzel@...gen.mpg.de" <pmenzel@...gen.mpg.de>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>, Simon Horman <simon.horman@...igine.com> Subject: RE: [Intel-wired-lan] [PATCH net-next v4 5/5] ice: use src VSI instead of src MAC in slow-path > -----Original Message----- > From: Intel-wired-lan <intel-wired-lan-bounces@...osl.org> On Behalf Of > Michal Swiatkowski > Sent: Friday, April 7, 2023 10:22 PM > To: intel-wired-lan@...ts.osuosl.org > Cc: pmenzel@...gen.mpg.de; netdev@...r.kernel.org; Simon Horman > <simon.horman@...igine.com> > Subject: [Intel-wired-lan] [PATCH net-next v4 5/5] ice: use src VSI instead of > src MAC in slow-path > > The use of a source MAC to direct packets from the VF to the corresponding > port representor is only ok if there is only one MAC on a VF. To support this > functionality when the number of MACs on a VF is greater, it is necessary to > match a source VSI instead of a source MAC. > > Let's use the new switch API that allows matching on metadata. > > If MAC isn't used in match criteria there is no need to handle adding rule > after virtchnl command. Instead add new rule while port representor is being > configured. > > Remove rule_added field, checking for sp_rule can be used instead. > Remove also checking for switchdev running in deleting rule as it can be > called from unroll context when running flag isn't set. Checking for sp_rule > covers both context (with and without running flag). > > Rules are added in eswitch configuration flow, so there is no need to have > replay function. > > Signed-off-by: Michal Swiatkowski <michal.swiatkowski@...ux.intel.com> > Reviewed-by: Piotr Raczynski <piotr.raczynski@...el.com> > Reviewed-by: Simon Horman <simon.horman@...igine.com> > --- > drivers/net/ethernet/intel/ice/ice_eswitch.c | 83 ++++++------------- > drivers/net/ethernet/intel/ice/ice_eswitch.h | 14 ---- > .../ethernet/intel/ice/ice_protocol_type.h | 5 +- > drivers/net/ethernet/intel/ice/ice_repr.c | 17 ---- > drivers/net/ethernet/intel/ice/ice_repr.h | 5 +- > drivers/net/ethernet/intel/ice/ice_switch.c | 6 ++ > drivers/net/ethernet/intel/ice/ice_switch.h | 1 + > drivers/net/ethernet/intel/ice/ice_vf_lib.c | 3 - > drivers/net/ethernet/intel/ice/ice_virtchnl.c | 8 -- > 9 files changed, 40 insertions(+), 102 deletions(-) > Tested-by: Sujai Buvaneswaran <sujai.buvaneswaran@...el.com>
Powered by blists - more mailing lists