Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
To: intel-wired-lan@lists.osuosl.org
Cc: mustafa.ismail@intel.com, benjamin.mikailenko@intel.com,
	jesse.brandeburg@intel.com, leszek.kaliszczuk@intel.com,
	przemyslaw.kitszel@intel.com, shiraz.saleem@intel.com
Subject: [Intel-wired-lan] [PATCH net-next v3 05/10] ice: stop hard coding the ICE_VSI_CTRL location
Date: Wed, 21 Dec 2022 12:38:17 +0100	[thread overview]
Message-ID: <20221221113822.12858-6-michal.swiatkowski@linux.intel.com> (raw)
In-Reply-To: <20221221113822.12858-1-michal.swiatkowski@linux.intel.com>

From: Jacob Keller <jacob.e.keller@intel.com>

When allocating the ICE_VSI_CTRL, the allocated struct ice_vsi pointer is
stored into the PF's pf->vsi array at a fixed location. This was
historically done on the basis that it could provide an O(1) lookup for the
special control VSI.

Since we store the ctrl_vsi_idx, we already have O(1) lookup regardless of
where in the array we store this VSI.

Simplify the logic in ice_vsi_alloc by using the same method of storing the
control VSI as other types of VSIs.

Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
Signed-off-by: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
---
 drivers/net/ethernet/intel/ice/ice_lib.c | 34 +++++++++++-------------
 1 file changed, 15 insertions(+), 19 deletions(-)

diff --git a/drivers/net/ethernet/intel/ice/ice_lib.c b/drivers/net/ethernet/intel/ice/ice_lib.c
index 709e58820937..4751092e02ef 100644
--- a/drivers/net/ethernet/intel/ice/ice_lib.c
+++ b/drivers/net/ethernet/intel/ice/ice_lib.c
@@ -479,10 +479,7 @@ int ice_vsi_free(struct ice_vsi *vsi)
 	/* updates the PF for this cleared VSI */
 
 	pf->vsi[vsi->idx] = NULL;
-	if (vsi->idx < pf->next_vsi && vsi->type != ICE_VSI_CTRL)
-		pf->next_vsi = vsi->idx;
-	if (vsi->idx < pf->next_vsi && vsi->type == ICE_VSI_CTRL && vsi->vf)
-		pf->next_vsi = vsi->idx;
+	pf->next_vsi = vsi->idx;
 
 	ice_vsi_free_stats(vsi);
 	ice_vsi_free_arrays(vsi);
@@ -690,23 +687,22 @@ ice_vsi_alloc(struct ice_pf *pf, struct ice_port_info *pi,
 	vsi->vf = vf;
 	set_bit(ICE_VSI_DOWN, vsi->state);
 
-	if (vsi->type == ICE_VSI_CTRL && !vf) {
-		/* Use the last VSI slot as the index for PF control VSI */
-		vsi->idx = pf->num_alloc_vsi - 1;
-		pf->ctrl_vsi_idx = vsi->idx;
-		pf->vsi[vsi->idx] = vsi;
-	} else {
-		/* fill slot and make note of the index */
-		vsi->idx = pf->next_vsi;
-		pf->vsi[pf->next_vsi] = vsi;
+	/* fill slot and make note of the index */
+	vsi->idx = pf->next_vsi;
+	pf->vsi[pf->next_vsi] = vsi;
 
-		/* prepare pf->next_vsi for next use */
-		pf->next_vsi = ice_get_free_slot(pf->vsi, pf->num_alloc_vsi,
-						 pf->next_vsi);
-	}
+	/* prepare pf->next_vsi for next use */
+	pf->next_vsi = ice_get_free_slot(pf->vsi, pf->num_alloc_vsi,
+					 pf->next_vsi);
 
-	if (vsi->type == ICE_VSI_CTRL && vf)
-		vf->ctrl_vsi_idx = vsi->idx;
+	if (vsi->type == ICE_VSI_CTRL) {
+		if (vf) {
+			vf->ctrl_vsi_idx = vsi->idx;
+		} else {
+			WARN_ON(pf->ctrl_vsi_idx != ICE_NO_VSI);
+			pf->ctrl_vsi_idx = vsi->idx;
+		}
+	}
 
 unlock_pf:
 	mutex_unlock(&pf->sw_mutex);
-- 
2.36.1

_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

  parent reply	other threads:[~2022-12-21 11:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-21 11:38 [Intel-wired-lan] [PATCH net-next v3 00/10] implement devlink reload in ice Michal Swiatkowski
2022-12-21 11:38 ` [Intel-wired-lan] [PATCH net-next v3 01/10] ice: move RDMA init to ice_idc.c Michal Swiatkowski
2022-12-21 11:38 ` [Intel-wired-lan] [PATCH net-next v3 02/10] ice: alloc id for RDMA using xa_array Michal Swiatkowski
2022-12-21 11:38 ` [Intel-wired-lan] [PATCH net-next v3 03/10] ice: cleanup in VSI config/deconfig code Michal Swiatkowski
2023-01-06  6:31   ` G, GurucharanX
2022-12-21 11:38 ` [Intel-wired-lan] [PATCH net-next v3 04/10] ice: split ice_vsi_setup into smaller functions Michal Swiatkowski
2023-01-06  6:32   ` G, GurucharanX
2022-12-21 11:38 ` Michal Swiatkowski [this message]
2023-01-06  6:33   ` [Intel-wired-lan] [PATCH net-next v3 05/10] ice: stop hard coding the ICE_VSI_CTRL location G, GurucharanX
2022-12-21 11:38 ` [Intel-wired-lan] [PATCH net-next v3 06/10] ice: split probe into smaller functions Michal Swiatkowski
2023-01-06  6:34   ` G, GurucharanX
2022-12-21 11:38 ` [Intel-wired-lan] [PATCH net-next v3 07/10] ice: sync netdev filters after clearing VSI Michal Swiatkowski
2023-01-06  6:35   ` G, GurucharanX
2022-12-21 11:38 ` [Intel-wired-lan] [PATCH net-next v3 08/10] ice: move VSI delete outside deconfig Michal Swiatkowski
2023-01-06  6:36   ` G, GurucharanX
2022-12-21 11:38 ` [Intel-wired-lan] [PATCH net-next v3 09/10] ice: update VSI instead of init in some case Michal Swiatkowski
2023-01-06  6:36   ` G, GurucharanX
2022-12-21 11:38 ` [Intel-wired-lan] [PATCH net-next v3 10/10] ice: implement devlink reinit action Michal Swiatkowski
2023-01-06  6:37   ` G, GurucharanX

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=20221221113822.12858-6-michal.swiatkowski@linux.intel.com \
    --to=michal.swiatkowski@linux.intel.com \
    --cc=benjamin.mikailenko@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jesse.brandeburg@intel.com \
    --cc=leszek.kaliszczuk@intel.com \
    --cc=mustafa.ismail@intel.com \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=shiraz.saleem@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