From: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: wojciech.drewek@intel.com, marcin.szycik@intel.com,
netdev@vger.kernel.org, jesse.brandeburg@intel.com,
intel-wired-lan@lists.osuosl.org, przemyslaw.kitszel@intel.com,
jacob.e.keller@intel.com, piotr.raczynski@intel.com
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v1 00/15] one by one port representors creation
Date: Tue, 24 Oct 2023 15:10:46 +0200 [thread overview]
Message-ID: <ZTfCVsYtbwSg9nZ/@wasp> (raw)
In-Reply-To: <ZTeveEZ1W/zejDuM@nanopsycho>
On Tue, Oct 24, 2023 at 01:50:16PM +0200, Jiri Pirko wrote:
> Tue, Oct 24, 2023 at 01:09:14PM CEST, michal.swiatkowski@linux.intel.com wrote:
> >Hi,
> >
> >Currently ice supports creating port representors only for VFs. For that
> >use case they can be created and removed in one step.
> >
> >This patchset is refactoring current flow to support port representor
> >creation also for subfunctions and SIOV. In this case port representors
> >need to be createad and removed one by one. Also, they can be added and
> >removed while other port representors are running.
> >
> >To achieve that we need to change the switchdev configuration flow.
> >Three first patches are only cosmetic (renaming, removing not used code).
> >Next few ones are preparation for new flow. The most important one
> >is "add VF representor one by one". It fully implements new flow.
> >
> >New type of port representor (for subfunction) will be introduced in
> >follow up patchset.
>
> Examples please. Show new outputs of devlink commands.
>
> Thanks!
>
If you mean outputs after refactor to one by one solution nothing
has changed:
# devlink port show (after creating 4 VFs in switchdev mode)
pci/0000:18:00.0/0: type eth netdev ens785f0np0 flavour physical port 0 splittable true lanes 8
pci/0000:18:00.0/2: type eth netdev ens785f0np0_0 flavour pcivf controller 0 pfnum 0 vfnum 0 external false splittable false
pci/0000:18:00.0/4: type eth netdev ens785f0np0_3 flavour pcivf controller 0 pfnum 0 vfnum 3 external false splittable false
pci/0000:18:00.0/5: type eth netdev ens785f0np0_1 flavour pcivf controller 0 pfnum 0 vfnum 1 external false splittable false
pci/0000:18:00.0/6: type eth netdev ens785f0np0_2 flavour pcivf controller 0 pfnum 0 vfnum 2 external false splittable false
According subfunction, it will also be in cover latter for patchset that
is implementing subfunction.
Commands:
# devlink dev eswitch set pci/0000:18:00.0 mode switchdev
# devlink port add pci/0000:18:00.0 flavour pcisf pfnum 0 sfnum 1000
# devlink port function set pci/0000:18:00.0/3 state active
Outputs:
Don't have it saved, will send it here after rebasing subfunction of top
of this one.
Thanks,
Michal
> >
> >Michal Swiatkowski (15):
> > ice: rename switchdev to eswitch
> > ice: remove redundant max_vsi_num variable
> > ice: remove unused control VSI parameter
> > ice: track q_id in representor
> > ice: use repr instead of vf->repr
> > ice: track port representors in xarray
> > ice: remove VF pointer reference in eswitch code
> > ice: make representor code generic
> > ice: return pointer to representor
> > ice: allow changing SWITCHDEV_CTRL VSI queues
> > ice: set Tx topology every time new repr is added
> > ice: realloc VSI stats arrays
> > ice: add VF representors one by one
> > ice: adjust switchdev rebuild path
> > ice: reserve number of CP queues
> >
> > drivers/net/ethernet/intel/ice/ice.h | 13 +-
> > drivers/net/ethernet/intel/ice/ice_devlink.c | 29 +
> > drivers/net/ethernet/intel/ice/ice_devlink.h | 1 +
> > drivers/net/ethernet/intel/ice/ice_eswitch.c | 562 ++++++++++--------
> > drivers/net/ethernet/intel/ice/ice_eswitch.h | 22 +-
> > .../net/ethernet/intel/ice/ice_eswitch_br.c | 22 +-
> > drivers/net/ethernet/intel/ice/ice_lib.c | 81 ++-
> > drivers/net/ethernet/intel/ice/ice_main.c | 6 +-
> > drivers/net/ethernet/intel/ice/ice_repr.c | 195 +++---
> > drivers/net/ethernet/intel/ice/ice_repr.h | 9 +-
> > drivers/net/ethernet/intel/ice/ice_sriov.c | 20 +-
> > drivers/net/ethernet/intel/ice/ice_tc_lib.c | 4 +-
> > drivers/net/ethernet/intel/ice/ice_vf_lib.c | 9 +-
> > drivers/net/ethernet/intel/ice/ice_vf_lib.h | 2 +-
> > 14 files changed, 553 insertions(+), 422 deletions(-)
> >
> >--
> >2.41.0
> >
> >
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2023-10-24 13:36 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 11:09 [Intel-wired-lan] [PATCH iwl-next v1 00/15] one by one port representors creation Michal Swiatkowski
2023-10-24 11:09 ` [Intel-wired-lan] [PATCH iwl-next v1 01/15] ice: rename switchdev to eswitch Michal Swiatkowski
2023-10-24 11:09 ` [Intel-wired-lan] [PATCH iwl-next v1 02/15] ice: remove redundant max_vsi_num variable Michal Swiatkowski
2023-10-24 11:09 ` [Intel-wired-lan] [PATCH iwl-next v1 03/15] ice: remove unused control VSI parameter Michal Swiatkowski
2023-10-24 11:09 ` [Intel-wired-lan] [PATCH iwl-next v1 04/15] ice: track q_id in representor Michal Swiatkowski
2023-11-09 10:19 ` Buvaneswaran, Sujai
2023-10-24 11:09 ` [Intel-wired-lan] [PATCH iwl-next v1 05/15] ice: use repr instead of vf->repr Michal Swiatkowski
2023-10-24 11:09 ` [Intel-wired-lan] [PATCH iwl-next v1 06/15] ice: track port representors in xarray Michal Swiatkowski
2023-11-09 10:20 ` Buvaneswaran, Sujai
2023-10-24 11:09 ` [Intel-wired-lan] [PATCH iwl-next v1 07/15] ice: remove VF pointer reference in eswitch code Michal Swiatkowski
2023-11-09 10:21 ` Buvaneswaran, Sujai
2023-10-24 11:09 ` [Intel-wired-lan] [PATCH iwl-next v1 08/15] ice: make representor code generic Michal Swiatkowski
2023-11-09 10:22 ` Buvaneswaran, Sujai
2023-10-24 11:09 ` [Intel-wired-lan] [PATCH iwl-next v1 09/15] ice: return pointer to representor Michal Swiatkowski
2023-11-09 10:23 ` Buvaneswaran, Sujai
2023-11-09 10:25 ` Buvaneswaran, Sujai
2023-10-24 11:09 ` [Intel-wired-lan] [PATCH iwl-next v1 10/15] ice: allow changing SWITCHDEV_CTRL VSI queues Michal Swiatkowski
2023-11-09 10:25 ` Buvaneswaran, Sujai
2023-10-24 11:09 ` [Intel-wired-lan] [PATCH iwl-next v1 11/15] ice: set Tx topology every time new repr is added Michal Swiatkowski
2023-11-09 10:26 ` Buvaneswaran, Sujai
2023-10-24 11:09 ` [Intel-wired-lan] [PATCH iwl-next v1 12/15] ice: realloc VSI stats arrays Michal Swiatkowski
2023-11-09 10:30 ` Buvaneswaran, Sujai
2023-10-24 11:09 ` [Intel-wired-lan] [PATCH iwl-next v1 13/15] ice: add VF representors one by one Michal Swiatkowski
2023-11-09 10:31 ` Buvaneswaran, Sujai
2023-10-24 11:09 ` [Intel-wired-lan] [PATCH iwl-next v1 14/15] ice: adjust switchdev rebuild path Michal Swiatkowski
2023-11-09 10:31 ` Buvaneswaran, Sujai
2023-10-24 11:09 ` [Intel-wired-lan] [PATCH iwl-next v1 15/15] ice: reserve number of CP queues Michal Swiatkowski
2023-11-09 10:32 ` Buvaneswaran, Sujai
2023-10-24 11:50 ` [Intel-wired-lan] [PATCH iwl-next v1 00/15] one by one port representors creation Jiri Pirko
2023-10-24 13:10 ` Michal Swiatkowski [this message]
2023-10-24 13:59 ` Jiri Pirko
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=ZTfCVsYtbwSg9nZ/@wasp \
--to=michal.swiatkowski@linux.intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=jiri@resnulli.us \
--cc=marcin.szycik@intel.com \
--cc=netdev@vger.kernel.org \
--cc=piotr.raczynski@intel.com \
--cc=przemyslaw.kitszel@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