netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>,
	<intel-wired-lan@lists.osuosl.org>
Cc: <netdev@vger.kernel.org>, <david.m.ertman@intel.com>,
	<wojciech.drewek@intel.com>,
	Marcin Szycik <marcin.szycik@intel.com>
Subject: Re: [PATCH iwl-next v1] ice: add drop rule matching on not active lport
Date: Thu, 24 Aug 2023 13:40:14 -0700	[thread overview]
Message-ID: <2181fe8c-44d3-acdd-b474-0faf7a78d69a@intel.com> (raw)
In-Reply-To: <20230823035755.777005-1-michal.swiatkowski@linux.intel.com>



On 8/22/2023 8:57 PM, Michal Swiatkowski wrote:
> Inactive LAG port should not receive any packets, as it can cause adding
> invalid FDBs (bridge offload). Add a drop rule matching on inactive lport
> in LAG.
> 
> Co-developed-by: Marcin Szycik <marcin.szycik@intel.com>
> Signed-off-by: Marcin Szycik <marcin.szycik@intel.com>
> Signed-off-by: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
> ---
>   .../net/ethernet/intel/ice/ice_eswitch_br.c   |  6 +-
>   drivers/net/ethernet/intel/ice/ice_lag.c      | 80 ++++++++++++++++---
>   drivers/net/ethernet/intel/ice/ice_lag.h      |  2 +
>   3 files changed, 72 insertions(+), 16 deletions(-)
> 
> diff --git a/drivers/net/ethernet/intel/ice/ice_eswitch_br.c b/drivers/net/ethernet/intel/ice/ice_eswitch_br.c
> index 67bfd1f61cdd..6ae0269bdf73 100644
> --- a/drivers/net/ethernet/intel/ice/ice_eswitch_br.c
> +++ b/drivers/net/ethernet/intel/ice/ice_eswitch_br.c
> @@ -73,7 +73,7 @@ ice_eswitch_br_ingress_rule_setup(struct ice_adv_rule_info *rule_info,
>   	rule_info->sw_act.vsi_handle = vf_vsi_idx;
>   	rule_info->sw_act.flag |= ICE_FLTR_RX;
>   	rule_info->sw_act.src = pf_id;
> -	rule_info->priority = 5;
> +	rule_info->priority = 2;

I'm not seeing anything in the commit message about changing priority. 
Would be nice to see why this is needed for review and posterity.

>   }
>   
>   static void
> @@ -84,7 +84,7 @@ ice_eswitch_br_egress_rule_setup(struct ice_adv_rule_info *rule_info,
>   	rule_info->sw_act.flag |= ICE_FLTR_TX;
>   	rule_info->flags_info.act = ICE_SINGLE_ACT_LAN_ENABLE;
>   	rule_info->flags_info.act_valid = true;
> -	rule_info->priority = 5;
> +	rule_info->priority = 2;
>   }
>   
>   static int
> @@ -207,7 +207,7 @@ ice_eswitch_br_guard_rule_create(struct ice_hw *hw, u16 vsi_idx,
>   	rule_info.allow_pass_l2 = true;
>   	rule_info.sw_act.vsi_handle = vsi_idx;
>   	rule_info.sw_act.fltr_act = ICE_NOP;
> -	rule_info.priority = 5;
> +	rule_info.priority = 2;
>   
>   	err = ice_add_adv_rule(hw, list, lkups_cnt, &rule_info, rule);
>   	if (err)


      parent reply	other threads:[~2023-08-24 20:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-23  3:57 [PATCH iwl-next v1] ice: add drop rule matching on not active lport Michal Swiatkowski
2023-08-24  8:56 ` Simon Horman
2023-08-24 20:40 ` Tony Nguyen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2181fe8c-44d3-acdd-b474-0faf7a78d69a@intel.com \
    --to=anthony.l.nguyen@intel.com \
    --cc=david.m.ertman@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=marcin.szycik@intel.com \
    --cc=michal.swiatkowski@linux.intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=wojciech.drewek@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).