From: Jiri Pirko <jiri@resnulli.us>
To: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
Cc: shayd@nvidia.com, maciej.fijalkowski@intel.com,
mateusz.polchlopek@intel.com, netdev@vger.kernel.org,
jiri@nvidia.com, michal.kubiak@intel.com,
intel-wired-lan@lists.osuosl.org, pio.raczynski@gmail.com,
sridhar.samudrala@intel.com, jacob.e.keller@intel.com,
wojciech.drewek@intel.com, przemyslaw.kitszel@intel.com
Subject: Re: [Intel-wired-lan] [iwl-next v1 0/4] ice: prepare representor for SF support
Date: Mon, 22 Apr 2024 15:02:10 +0200 [thread overview]
Message-ID: <ZiZf0k-38srn486H@nanopsycho> (raw)
In-Reply-To: <20240419171336.11617-1-michal.swiatkowski@linux.intel.com>
Fri, Apr 19, 2024 at 07:13:32PM CEST, michal.swiatkowski@linux.intel.com wrote:
>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].
>
>[1] https://lore.kernel.org/netdev/20240213072724.77275-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
FWIW, looks fine to me.
>
> .../net/ethernet/intel/ice/devlink/devlink.c | 2 -
> .../ethernet/intel/ice/devlink/devlink_port.c | 4 +-
> drivers/net/ethernet/intel/ice/ice_eswitch.c | 83 +++++++++++++------
> 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, 88 insertions(+), 39 deletions(-)
>
>--
>2.42.0
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Jiri Pirko <jiri@resnulli.us>
To: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
jacob.e.keller@intel.com, michal.kubiak@intel.com,
maciej.fijalkowski@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
Subject: Re: [iwl-next v1 0/4] ice: prepare representor for SF support
Date: Mon, 22 Apr 2024 15:02:10 +0200 [thread overview]
Message-ID: <ZiZf0k-38srn486H@nanopsycho> (raw)
In-Reply-To: <20240419171336.11617-1-michal.swiatkowski@linux.intel.com>
Fri, Apr 19, 2024 at 07:13:32PM CEST, michal.swiatkowski@linux.intel.com wrote:
>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].
>
>[1] https://lore.kernel.org/netdev/20240213072724.77275-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
FWIW, looks fine to me.
>
> .../net/ethernet/intel/ice/devlink/devlink.c | 2 -
> .../ethernet/intel/ice/devlink/devlink_port.c | 4 +-
> drivers/net/ethernet/intel/ice/ice_eswitch.c | 83 +++++++++++++------
> 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, 88 insertions(+), 39 deletions(-)
>
>--
>2.42.0
>
>
next prev parent reply other threads:[~2024-04-22 13:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 17:13 [Intel-wired-lan] [iwl-next v1 0/4] ice: prepare representor for SF support Michal Swiatkowski
2024-04-19 17:13 ` Michal Swiatkowski
2024-04-19 17:13 ` [Intel-wired-lan] [iwl-next v1 1/4] ice: store representor ID in bridge port Michal Swiatkowski
2024-04-19 17:13 ` Michal Swiatkowski
2024-04-19 17:13 ` [Intel-wired-lan] [iwl-next v1 2/4] ice: move devlink locking outside the port creation Michal Swiatkowski
2024-04-19 17:13 ` Michal Swiatkowski
2024-04-19 17:13 ` [Intel-wired-lan] [iwl-next v1 3/4] ice: move VSI configuration outside repr setup Michal Swiatkowski
2024-04-19 17:13 ` Michal Swiatkowski
2024-04-24 21:08 ` [Intel-wired-lan] " Tony Nguyen
2024-04-24 21:08 ` Tony Nguyen
2024-05-06 8:50 ` [Intel-wired-lan] " Michal Swiatkowski
2024-05-06 8:50 ` Michal Swiatkowski
2024-04-19 17:13 ` [Intel-wired-lan] [iwl-next v1 4/4] ice: update representor when VSI is ready Michal Swiatkowski
2024-04-19 17:13 ` Michal Swiatkowski
2024-04-22 13:02 ` Jiri Pirko [this message]
2024-04-22 13:02 ` [iwl-next v1 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=ZiZf0k-38srn486H@nanopsycho \
--to=jiri@resnulli.us \
--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=michal.swiatkowski@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.