From: Simon Horman <horms@kernel.org>
To: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
marcin.szycik@intel.com, wojciech.drewek@intel.com,
sridhar.samudrala@intel.com, przemyslaw.kitszel@intel.com,
Marcin Szycik <marcin.szycik@linux.intel.com>
Subject: Re: [iwl-next v1 4/8] ice: control default Tx rule in lag
Date: Fri, 2 Feb 2024 18:18:05 +0100 [thread overview]
Message-ID: <20240202171805.GS530335@kernel.org> (raw)
In-Reply-To: <ZbtCom/grznFpesc@mev-dev>
On Thu, Feb 01, 2024 at 08:05:06AM +0100, Michal Swiatkowski wrote:
> 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,
I think that might be a good idea.
But my question was a bit different: I'm asking if this patch addresses
a regression introduced earlier in the series. Sorry for not being clearer
the first time around.
next prev parent reply other threads:[~2024-02-02 17:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 12:53 [iwl-next v1 0/8] ice: use less resources in switchdev Michal Swiatkowski
2024-01-25 12:53 ` [iwl-next v1 1/8] ice: remove eswitch changing queues algorithm Michal Swiatkowski
2024-01-25 12:53 ` [iwl-next v1 2/8] ice: do Tx through PF netdev in slow-path Michal Swiatkowski
2024-01-25 12:53 ` [iwl-next v1 3/8] ice: default Tx rule instead of to queue Michal Swiatkowski
2024-01-25 12:53 ` [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
2024-02-02 17:18 ` Simon Horman [this message]
2024-01-25 12:53 ` [iwl-next v1 5/8] ice: remove switchdev control plane VSI Michal Swiatkowski
2024-01-25 12:53 ` [iwl-next v1 6/8] ice: change repr::id values Michal Swiatkowski
2024-01-25 12:53 ` [iwl-next v1 7/8] ice: do switchdev slow-path Rx using PF VSI Michal Swiatkowski
2024-01-25 12:53 ` [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=20240202171805.GS530335@kernel.org \
--to=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=marcin.szycik@intel.com \
--cc=marcin.szycik@linux.intel.com \
--cc=michal.swiatkowski@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;
as well as URLs for NNTP newsgroup(s).