From: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
To: Simon Horman <horms@kernel.org>
Cc: wojciech.drewek@intel.com, marcin.szycik@intel.com,
Marcin Szycik <marcin.szycik@linux.intel.com>,
netdev@vger.kernel.org, sridhar.samudrala@intel.com,
intel-wired-lan@lists.osuosl.org, przemyslaw.kitszel@intel.com
Subject: Re: [Intel-wired-lan] [iwl-next v1 4/8] ice: control default Tx rule in lag
Date: Thu, 1 Feb 2024 08:05:06 +0100 [thread overview]
Message-ID: <ZbtCom/grznFpesc@mev-dev> (raw)
In-Reply-To: <20240129105541.GH401354@kernel.org>
On Mon, Jan 29, 2024 at 10:55:41AM +0000, Simon Horman wrote:
> On Thu, Jan 25, 2024 at 01:53:10PM +0100, Michal Swiatkowski wrote:
> > Tx rule in switchdev was changed to use PF instead of additional control
> > plane VSI. Because of that during lag we should control it. Control
> > means to add and remove the default Tx rule during lag active/inactive
> > switching.
> >
> > It can be done the same way as default Rx rule.
>
> Hi Michal,
>
> Can I confirm that LAG TX/RX works both before and after this patch?
>
Hi Simon,
This part of LAG code is related to the LAG + switchdev feature (it
isn't chaning LAG core code). Hope that normal LAG also works well. This
is the scenario when you have PF in switchdev, bond created of two PFs
connected to the bridge with representors. Switching between interfaces
from bond needs to add default Rx rule, and after my changes also
default Tx rule.
Do you think I should add this description to commit message?
Thanks,
Michal
> >
> > Reviewed-by: Wojciech Drewek <wojciech.drewek@intel.com>
> > Reviewed-by: Marcin Szycik <marcin.szycik@linux.intel.com>
> > Signed-off-by: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
> > ---
> > drivers/net/ethernet/intel/ice/ice_lag.c | 39 ++++++++++++++++++------
> > drivers/net/ethernet/intel/ice/ice_lag.h | 3 +-
> > 2 files changed, 32 insertions(+), 10 deletions(-)
> >
> > diff --git a/drivers/net/ethernet/intel/ice/ice_lag.c b/drivers/net/ethernet/intel/ice/ice_lag.c
>
> ...
>
> > @@ -266,9 +274,22 @@ ice_lag_cfg_dflt_fltr(struct ice_lag *lag, bool add)
> > {
> > u32 act = ICE_SINGLE_ACT_VSI_FORWARDING |
> > ICE_SINGLE_ACT_VALID_BIT | ICE_SINGLE_ACT_LAN_ENABLE;
> > + int err;
> > +
> > + err = ice_lag_cfg_fltr(lag, act, lag->pf_recipe, &lag->pf_rx_rule_id,
> > + ICE_FLTR_RX, add);
> > + if (err)
> > + return err;
> > +
> > + err = ice_lag_cfg_fltr(lag, act, lag->pf_recipe, &lag->pf_tx_rule_id,
> > + ICE_FLTR_TX, add);
> > + if (err) {
> > + ice_lag_cfg_fltr(lag, act, lag->pf_recipe, &lag->pf_rx_rule_id,
> > + ICE_FLTR_RX, !add);
> > + return err;
> > + }
> >
> > - return ice_lag_cfg_fltr(lag, act, lag->pf_recipe,
> > - &lag->pf_rule_id, add);
> > + return 0;
> > }
>
> nit: perhaps this could be more idiomatically written using a
> goto to unwind on error.
>
Thanks, I will rewrite it.
> ...
next prev parent reply other threads:[~2024-02-01 7:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 12:53 [Intel-wired-lan] [iwl-next v1 0/8] ice: use less resources in switchdev Michal Swiatkowski
2024-01-25 12:53 ` [Intel-wired-lan] [iwl-next v1 1/8] ice: remove eswitch changing queues algorithm Michal Swiatkowski
2024-01-25 12:53 ` [Intel-wired-lan] [iwl-next v1 2/8] ice: do Tx through PF netdev in slow-path Michal Swiatkowski
2024-01-25 12:53 ` [Intel-wired-lan] [iwl-next v1 3/8] ice: default Tx rule instead of to queue Michal Swiatkowski
2024-01-25 12:53 ` [Intel-wired-lan] [iwl-next v1 4/8] ice: control default Tx rule in lag Michal Swiatkowski
2024-01-29 10:55 ` Simon Horman
2024-02-01 7:05 ` Michal Swiatkowski [this message]
2024-02-02 17:18 ` Simon Horman
2024-01-25 12:53 ` [Intel-wired-lan] [iwl-next v1 5/8] ice: remove switchdev control plane VSI Michal Swiatkowski
2024-01-25 12:53 ` [Intel-wired-lan] [iwl-next v1 6/8] ice: change repr::id values Michal Swiatkowski
2024-01-25 12:53 ` [Intel-wired-lan] [iwl-next v1 7/8] ice: do switchdev slow-path Rx using PF VSI Michal Swiatkowski
2024-01-25 12:53 ` [Intel-wired-lan] [iwl-next v1 8/8] ice: count representor stats Michal Swiatkowski
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=ZbtCom/grznFpesc@mev-dev \
--to=michal.swiatkowski@linux.intel.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=marcin.szycik@intel.com \
--cc=marcin.szycik@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@intel.com \
--cc=sridhar.samudrala@intel.com \
--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