From: Brett Creeley <bcreeley@amd.com>
To: Dave Ertman <david.m.ertman@intel.com>, intel-wired-lan@lists.osuosl.org
Cc: daniel.machon@microchip.com, simon.horman@corigine.com,
netdev@vger.kernel.org
Subject: Re: [PATCH iwl-next v4 05/10] ice: process events created by lag netdev event handler
Date: Wed, 14 Jun 2023 14:24:23 -0700 [thread overview]
Message-ID: <887cbcd2-d01c-2736-d0de-660de80ef4d6@amd.com> (raw)
In-Reply-To: <20230609211626.621968-6-david.m.ertman@intel.com>
On 6/9/2023 2:16 PM, Dave Ertman wrote:
> Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
>
>
> Add in the function framework for the processing of LAG events. Also add
> in helper function to perform common tasks.
>
> Add the basis of the process of linking a lower netdev to an upper netdev.
>
> Reviewed-by: Daniel Machon <daniel.machon@microchip.com>
> Signed-off-by: Dave Ertman <david.m.ertman@intel.com>
> ---
> drivers/net/ethernet/intel/ice/ice_lag.c | 535 +++++++++++++++---
> drivers/net/ethernet/intel/ice/ice_lag.h | 1 +
> drivers/net/ethernet/intel/ice/ice_switch.c | 10 +-
> drivers/net/ethernet/intel/ice/ice_switch.h | 3 +
> drivers/net/ethernet/intel/ice/ice_virtchnl.c | 2 +
> 5 files changed, 478 insertions(+), 73 deletions(-)
>
[...]
> +/**
> + * ice_lag_reclaim_vf_nodes - When interface leaving bond primary reclaims nodes
> + * @lag: primary interface lag struct
> + * @src_hw: HW struct for current node location
> + */
> +static void
> +ice_lag_reclaim_vf_nodes(struct ice_lag *lag, struct ice_hw *src_hw)
> +{
> + struct ice_pf *pf;
> + int i, tc;
> +
> + if (!lag->primary || !src_hw)
> + return;
> +
> + pf = lag->pf;
> + ice_for_each_vsi(pf, i)
> + if (pf->vsi[i] && (pf->vsi[i]->type == ICE_VSI_VF ||
> + pf->vsi[i]->type == ICE_VSI_SWITCHDEV_CTRL))
> + ice_for_each_traffic_class(tc)
> + ice_lag_reclaim_vf_tc(lag, src_hw, i, tc);
Seems like indentation got messed up here for ice_lag_reclaim_vf_tc()?
Is this supposed to be under the if block?
> +}
> +
[...]
next prev parent reply other threads:[~2023-06-14 21:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 21:16 [PATCH iwl-next v4 00/10] Implement support for SRIOV + LAG Dave Ertman
2023-06-09 21:16 ` [PATCH iwl-next v4 01/10] ice: Correctly initialize queue context values Dave Ertman
2023-06-14 11:12 ` Simon Horman
2023-06-09 21:16 ` [PATCH iwl-next v4 02/10] ice: Add driver support for firmware changes for LAG Dave Ertman
2023-06-14 11:17 ` Simon Horman
2023-06-14 16:56 ` Ertman, David M
2023-06-14 19:44 ` Simon Horman
2023-06-14 21:23 ` Brett Creeley
2023-06-14 22:42 ` Ertman, David M
2023-06-09 21:16 ` [PATCH iwl-next v4 03/10] ice: changes to the interface with the HW and FW for SRIOV_VF+LAG Dave Ertman
2023-06-09 21:16 ` [PATCH iwl-next v4 04/10] ice: implement lag netdev event handler Dave Ertman
2023-06-14 21:24 ` Brett Creeley
2023-06-14 22:58 ` Ertman, David M
2023-06-14 23:18 ` Brett Creeley
2023-06-09 21:16 ` [PATCH iwl-next v4 05/10] ice: process events created by " Dave Ertman
2023-06-14 21:24 ` Brett Creeley [this message]
2023-06-14 23:19 ` Ertman, David M
2023-06-14 23:24 ` Brett Creeley
2023-06-09 21:16 ` [PATCH iwl-next v4 06/10] ice: Flesh out implementation of support for SRIOV on bonded interface Dave Ertman
2023-06-14 21:24 ` Brett Creeley
2023-06-14 23:34 ` Ertman, David M
2023-06-09 21:16 ` [PATCH iwl-next v4 07/10] ice: support non-standard teardown of bond interface Dave Ertman
2023-06-09 21:16 ` [PATCH iwl-next v4 08/10] ice: enforce interface eligibility and add messaging for SRIOV LAG Dave Ertman
2023-06-09 21:16 ` [PATCH iwl-next v4 09/10] ice: enforce no DCB config changing when in bond Dave Ertman
2023-06-09 21:16 ` [PATCH iwl-next v4 10/10] ice: update reset path for SRIOV LAG support Dave Ertman
2023-06-11 17:41 ` [PATCH iwl-next v4 00/10] Implement support for SRIOV + LAG Daniel Machon
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=887cbcd2-d01c-2736-d0de-660de80ef4d6@amd.com \
--to=bcreeley@amd.com \
--cc=daniel.machon@microchip.com \
--cc=david.m.ertman@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=netdev@vger.kernel.org \
--cc=simon.horman@corigine.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).