Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
To: Dave Ertman <david.m.ertman@intel.com>,
	<intel-wired-lan@lists.osuosl.org>
Subject: Re: [Intel-wired-lan] [PATCH iwl-net] ice: Fix VF Reset paths when interface in a failed over aggregate
Date: Wed, 8 Nov 2023 12:28:36 +0100	[thread overview]
Message-ID: <bb27edad-077f-85ba-89b8-f8d9faaecf57@intel.com> (raw)
In-Reply-To: <20231107173825.1853492-1-david.m.ertman@intel.com>

On 11/7/23 18:38, Dave Ertman wrote:
> There is an error when an interface has the following conditions:
> - PF is in an aggregate (bond)
> - PF has VFs created on it
> - bond is in a state where it is failed-over to the secondary interface
> - A VF reset is issued on one or more of those VFs
> 
> The issue is generated by the originating PF trying to rebuild or
> reconfigure the VF resources.  Since the bond is failed over to the
> secondary interface the queue contexts are in a modified state.
> 
> To fix this issue, have the originating interface reclaim its resources
> prior to the tear-down and rebuild or reconfigure.  Then after the process
> is complete, move the resources back to the currently active interface.
> 
> There are multiple paths that can be used depending on what triggered the
> event, so create a helper function to move the queues and use paired calls
> to the helper (back to origin, process, then move back to active interface)
> under the same lag_mutex lock.
> 
> Fixes: 1e0f9881ef79 ("ice: Flesh out implementation of support for SRIOV on bonded interface")
> Signed-off-by: Dave Ertman <david.m.ertman@intel.com>
> ---
>   drivers/net/ethernet/intel/ice/ice_lag.c      | 42 +++++++++++++++++++
>   drivers/net/ethernet/intel/ice/ice_lag.h      |  1 +
>   drivers/net/ethernet/intel/ice/ice_vf_lib.c   | 20 +++++++++
>   drivers/net/ethernet/intel/ice/ice_virtchnl.c | 25 +++++++++++
>   4 files changed, 88 insertions(+)

you should carry Reviewed-by (and Tested-by if provided) tags from
earlier versions and from our e1000 ML too,
Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>

in the future you have to also CC netdev ML and main LKML for ice
contributions
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

  reply	other threads:[~2023-11-08 11:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-07 17:38 [Intel-wired-lan] [PATCH iwl-net] ice: Fix VF Reset paths when interface in a failed over aggregate Dave Ertman
2023-11-08 11:28 ` Przemek Kitszel [this message]
2023-11-15  6:43 ` Buvaneswaran, Sujai

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=bb27edad-077f-85ba-89b8-f8d9faaecf57@intel.com \
    --to=przemyslaw.kitszel@intel.com \
    --cc=david.m.ertman@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    /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