From: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
To: intel-wired-lan@lists.osuosl.org
Cc: shayd@nvidia.com, maciej.fijalkowski@intel.com,
sridhar.samudrala@intel.com, mateusz.polchlopek@intel.com,
netdev@vger.kernel.org, jiri@nvidia.com, michal.kubiak@intel.com,
pio.raczynski@gmail.com, przemyslaw.kitszel@intel.com,
jacob.e.keller@intel.com, wojciech.drewek@intel.com
Subject: [Intel-wired-lan] [iwl-next v2 0/4] ice: prepare representor for SF support
Date: Mon, 6 May 2024 10:46:49 +0200 [thread overview]
Message-ID: <20240506084653.532111-1-michal.swiatkowski@linux.intel.com> (raw)
Hi,
This is a series to prepare port representor for supporting also
subfunctions. We need correct devlink locking and the possibility to
update parent VSI after port representor is created.
Refactor how devlink lock is taken to suite the subfunction use case.
VSI configuration needs to be done after port representor is created.
Port representor needs only allocated VSI. It doesn't need to be
configured before.
VSI needs to be reconfigured when update function is called.
The code for this patchset was split from (too big) patchset [1].
v1 --> v2 [2]:
* add returns for kdoc in ice_eswitch_cfg_vsi
[1] https://lore.kernel.org/netdev/20240213072724.77275-1-michal.swiatkowski@linux.intel.com/
[2] https://lore.kernel.org/netdev/20240419171336.11617-1-michal.swiatkowski@linux.intel.com/
Michal Swiatkowski (4):
ice: store representor ID in bridge port
ice: move devlink locking outside the port creation
ice: move VSI configuration outside repr setup
ice: update representor when VSI is ready
.../net/ethernet/intel/ice/devlink/devlink.c | 2 -
.../ethernet/intel/ice/devlink/devlink_port.c | 4 +-
drivers/net/ethernet/intel/ice/ice_eswitch.c | 85 +++++++++++++------
drivers/net/ethernet/intel/ice/ice_eswitch.h | 14 ++-
.../net/ethernet/intel/ice/ice_eswitch_br.c | 4 +-
.../net/ethernet/intel/ice/ice_eswitch_br.h | 1 +
drivers/net/ethernet/intel/ice/ice_repr.c | 16 ++--
drivers/net/ethernet/intel/ice/ice_repr.h | 1 +
drivers/net/ethernet/intel/ice/ice_vf_lib.c | 2 +-
9 files changed, 90 insertions(+), 39 deletions(-)
--
2.42.0
next reply other threads:[~2024-05-06 8:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 8:46 Michal Swiatkowski [this message]
2024-05-06 8:46 ` [Intel-wired-lan] [iwl-next v2 1/4] ice: store representor ID in bridge port Michal Swiatkowski
2024-05-14 7:28 ` Buvaneswaran, Sujai
2024-05-06 8:46 ` [Intel-wired-lan] [iwl-next v2 2/4] ice: move devlink locking outside the port creation Michal Swiatkowski
2024-05-14 7:29 ` Buvaneswaran, Sujai
2024-05-06 8:46 ` [Intel-wired-lan] [iwl-next v2 3/4] ice: move VSI configuration outside repr setup Michal Swiatkowski
2024-05-14 7:31 ` Buvaneswaran, Sujai
2024-05-06 8:46 ` [Intel-wired-lan] [iwl-next v2 4/4] ice: update representor when VSI is ready Michal Swiatkowski
2024-05-14 7:32 ` Buvaneswaran, Sujai
2024-05-06 10:59 ` [Intel-wired-lan] [iwl-next v2 0/4] ice: prepare representor for SF support 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=20240506084653.532111-1-michal.swiatkowski@linux.intel.com \
--to=michal.swiatkowski@linux.intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=jiri@nvidia.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 read-only IMAP folder(s) and NNTP newsgroup(s).