From: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
To: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
jacob.e.keller@intel.com, michal.kubiak@intel.com,
sridhar.samudrala@intel.com, przemyslaw.kitszel@intel.com,
wojciech.drewek@intel.com, pio.raczynski@gmail.com,
jiri@nvidia.com, mateusz.polchlopek@intel.com, shayd@nvidia.com,
kalesh-anakkur.purayil@broadcom.com, horms@kernel.org
Subject: Re: [iwl-next v5 04/15] ice: treat subfunction VSI the same as PF VSI
Date: Thu, 27 Jun 2024 14:31:14 +0200 [thread overview]
Message-ID: <Zn1bkhZ1lF1w96AA@mev-dev> (raw)
In-Reply-To: <Zn1H6hmr4Y7ZFvT6@boxer>
On Thu, Jun 27, 2024 at 01:07:22PM +0200, Maciej Fijalkowski wrote:
> On Thu, Jun 06, 2024 at 01:24:52PM +0200, Michal Swiatkowski wrote:
> > When subfunction VSI is open the same code as for PF VSI should be
> > executed. Also when up is complete. Reflect that in code by adding
> > subfunction VSI to consideration.
> >
> > In case of stopping, PF doesn't have additional tasks, so the same
> > is with subfunction VSI.
> >
> > Reviewed-by: Simon Horman <horms@kernel.org>
> > Signed-off-by: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
> > ---
> > drivers/net/ethernet/intel/ice/ice_main.c | 5 +++--
> > 1 file changed, 3 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/net/ethernet/intel/ice/ice_main.c b/drivers/net/ethernet/intel/ice/ice_main.c
> > index e76e19036593..ddc348371841 100644
> > --- a/drivers/net/ethernet/intel/ice/ice_main.c
> > +++ b/drivers/net/ethernet/intel/ice/ice_main.c
> > @@ -6726,7 +6726,8 @@ static int ice_up_complete(struct ice_vsi *vsi)
> >
> > if (vsi->port_info &&
> > (vsi->port_info->phy.link_info.link_info & ICE_AQ_LINK_UP) &&
> > - vsi->netdev && vsi->type == ICE_VSI_PF) {
> > + ((vsi->netdev && vsi->type == ICE_VSI_PF) ||
> > + (vsi->netdev && vsi->type == ICE_VSI_SF))) {
>
> patch 1 has:
>
> if (vsi->netdev && (vsi->type == ICE_VSI_PF ||
> vsi->type == ICE_VSI_SF)) {
>
> so maybe stay consistent and do the same here?
>
> nit: also seems that a really small helper would make the code easier to
> read and wrap...something like:
>
> bool ice_is_vsi_pf_sf(struct ice_vsi* vsi)
> {
> return (vsi->type == ICE_VSI_PF || vsi->type == ICE_VSI_SF);
> }
Make sense, hope you are ok, with changing it on the occasion (for
example adding multibuffer support).
Thanks,
Michal
>
> > ice_print_link_msg(vsi, true);
> > netif_tx_start_all_queues(vsi->netdev);
> > netif_carrier_on(vsi->netdev);
> > @@ -7427,7 +7428,7 @@ int ice_vsi_open(struct ice_vsi *vsi)
> >
> > ice_vsi_cfg_netdev_tc(vsi, vsi->tc_cfg.ena_tc);
> >
> > - if (vsi->type == ICE_VSI_PF) {
> > + if (vsi->type == ICE_VSI_PF || vsi->type == ICE_VSI_SF) {
> > /* Notify the stack of the actual queue counts. */
> > err = netif_set_real_num_tx_queues(vsi->netdev, vsi->num_txq);
> > if (err)
> > --
> > 2.42.0
> >
next prev parent reply other threads:[~2024-06-27 12:32 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 11:24 [iwl-next v5 00/15] ice: support devlink subfunction Michal Swiatkowski
2024-06-06 11:24 ` [iwl-next v5 01/15] ice: add new VSI type for subfunctions Michal Swiatkowski
2024-07-23 11:06 ` [Intel-wired-lan] " Romanowski, Rafal
2024-06-06 11:24 ` [iwl-next v5 02/15] ice: export ice ndo_ops functions Michal Swiatkowski
2024-07-23 11:13 ` [Intel-wired-lan] " Romanowski, Rafal
2024-06-06 11:24 ` [iwl-next v5 03/15] ice: add basic devlink subfunctions support Michal Swiatkowski
2024-07-23 11:13 ` [Intel-wired-lan] " Romanowski, Rafal
2024-06-06 11:24 ` [iwl-next v5 04/15] ice: treat subfunction VSI the same as PF VSI Michal Swiatkowski
2024-06-27 11:07 ` Maciej Fijalkowski
2024-06-27 12:31 ` Michal Swiatkowski [this message]
2024-07-23 11:14 ` [Intel-wired-lan] " Romanowski, Rafal
2024-06-06 11:24 ` [iwl-next v5 05/15] ice: allocate devlink for subfunction Michal Swiatkowski
2024-06-14 10:55 ` Simon Horman
2024-07-23 11:15 ` [Intel-wired-lan] " Romanowski, Rafal
2024-06-06 11:24 ` [iwl-next v5 06/15] ice: base subfunction aux driver Michal Swiatkowski
2024-07-23 11:16 ` [Intel-wired-lan] " Romanowski, Rafal
2024-06-06 11:24 ` [iwl-next v5 07/15] ice: implement netdev for subfunction Michal Swiatkowski
2024-06-27 11:13 ` Maciej Fijalkowski
2024-06-27 12:32 ` Michal Swiatkowski
2024-07-23 11:20 ` [Intel-wired-lan] " Romanowski, Rafal
2024-06-06 11:24 ` [iwl-next v5 08/15] ice: make representor code generic Michal Swiatkowski
2024-07-23 11:21 ` [Intel-wired-lan] " Romanowski, Rafal
2024-06-06 11:24 ` [iwl-next v5 09/15] ice: create port representor for SF Michal Swiatkowski
2024-07-23 11:21 ` [Intel-wired-lan] " Romanowski, Rafal
2024-06-06 11:24 ` [iwl-next v5 10/15] ice: don't set target VSI for subfunction Michal Swiatkowski
2024-07-23 11:23 ` [Intel-wired-lan] " Romanowski, Rafal
2024-06-06 11:24 ` [iwl-next v5 11/15] ice: check if SF is ready in ethtool ops Michal Swiatkowski
2024-07-23 11:24 ` [Intel-wired-lan] " Romanowski, Rafal
2024-06-06 11:25 ` [iwl-next v5 12/15] ice: implement netdevice ops for SF representor Michal Swiatkowski
2024-06-14 11:02 ` Simon Horman
2024-07-23 11:24 ` [Intel-wired-lan] " Romanowski, Rafal
2024-06-06 11:25 ` [iwl-next v5 13/15] ice: support subfunction devlink Tx topology Michal Swiatkowski
2024-07-23 11:25 ` [Intel-wired-lan] " Romanowski, Rafal
2024-06-06 11:25 ` [iwl-next v5 14/15] ice: basic support for VLAN in subfunctions Michal Swiatkowski
2024-07-23 11:25 ` [Intel-wired-lan] " Romanowski, Rafal
2024-06-06 11:25 ` [iwl-next v5 15/15] ice: allow to activate and deactivate subfunction Michal Swiatkowski
2024-07-23 11:26 ` [Intel-wired-lan] " Romanowski, Rafal
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=Zn1bkhZ1lF1w96AA@mev-dev \
--to=michal.swiatkowski@linux.intel.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=jiri@nvidia.com \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=maciej.fijalkowski@intel.com \
--cc=mateusz.polchlopek@intel.com \
--cc=michal.kubiak@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pio.raczynski@gmail.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=shayd@nvidia.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).