From: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: maciej.fijalkowski@intel.com, netdev@vger.kernel.org,
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 10/15] ice: create port representor for SF
Date: Tue, 13 Feb 2024 10:55:05 +0100 [thread overview]
Message-ID: <Zcs8eSp0R98Ejrce@mev-dev> (raw)
In-Reply-To: <ZcsvpByD9n9BR-6D@nanopsycho>
On Tue, Feb 13, 2024 at 10:00:20AM +0100, Jiri Pirko wrote:
> Tue, Feb 13, 2024 at 08:27:19AM CET, michal.swiatkowski@linux.intel.com wrote:
> >Store subfunction and VF pointer in port representor structure as an
> >union. Add port representor type to distinguish between each of them.
> >
> >Keep the same flow of port representor creation, but instead of general
> >attach function create helpers for VF and subfunction attach function.
> >
> >Type of port representor can be also known based on VSI type, but it
> >is more clean to have it directly saved in port representor structure.
> >
> >Create port representor when subfunction port is activated.
> >
> >Add devlink lock for whole VF port representor creationi and destruction.
> >It is done to be symmetric with what happens in case of SF port
> >representor. SF port representor is always added or removed with devlink
> >lock taken. Doing the same with VF port representor simplify logic.
> >
> >Reviewed-by: Wojciech Drewek <wojciech.drewek@intel.com>
> >Signed-off-by: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
> >---
> > .../intel/ice/devlink/ice_devlink_port.c | 4 +-
> > .../intel/ice/devlink/ice_devlink_port.h | 1 +
> > drivers/net/ethernet/intel/ice/ice_eswitch.c | 82 ++++++++++---
> > drivers/net/ethernet/intel/ice/ice_eswitch.h | 22 +++-
> > drivers/net/ethernet/intel/ice/ice_repr.c | 110 +++++++++++-------
> > drivers/net/ethernet/intel/ice/ice_repr.h | 21 +++-
> > drivers/net/ethernet/intel/ice/ice_sf_eth.c | 11 ++
> > drivers/net/ethernet/intel/ice/ice_sriov.c | 4 +-
> > drivers/net/ethernet/intel/ice/ice_txrx.c | 2 +-
> > drivers/net/ethernet/intel/ice/ice_vf_lib.c | 4 +-
> > 10 files changed, 184 insertions(+), 77 deletions(-)
>
> Again, please split.
Ok
WARNING: multiple messages have this Message-ID (diff)
From: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
To: Jiri Pirko <jiri@resnulli.us>
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
Subject: Re: [iwl-next v1 10/15] ice: create port representor for SF
Date: Tue, 13 Feb 2024 10:55:05 +0100 [thread overview]
Message-ID: <Zcs8eSp0R98Ejrce@mev-dev> (raw)
In-Reply-To: <ZcsvpByD9n9BR-6D@nanopsycho>
On Tue, Feb 13, 2024 at 10:00:20AM +0100, Jiri Pirko wrote:
> Tue, Feb 13, 2024 at 08:27:19AM CET, michal.swiatkowski@linux.intel.com wrote:
> >Store subfunction and VF pointer in port representor structure as an
> >union. Add port representor type to distinguish between each of them.
> >
> >Keep the same flow of port representor creation, but instead of general
> >attach function create helpers for VF and subfunction attach function.
> >
> >Type of port representor can be also known based on VSI type, but it
> >is more clean to have it directly saved in port representor structure.
> >
> >Create port representor when subfunction port is activated.
> >
> >Add devlink lock for whole VF port representor creationi and destruction.
> >It is done to be symmetric with what happens in case of SF port
> >representor. SF port representor is always added or removed with devlink
> >lock taken. Doing the same with VF port representor simplify logic.
> >
> >Reviewed-by: Wojciech Drewek <wojciech.drewek@intel.com>
> >Signed-off-by: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
> >---
> > .../intel/ice/devlink/ice_devlink_port.c | 4 +-
> > .../intel/ice/devlink/ice_devlink_port.h | 1 +
> > drivers/net/ethernet/intel/ice/ice_eswitch.c | 82 ++++++++++---
> > drivers/net/ethernet/intel/ice/ice_eswitch.h | 22 +++-
> > drivers/net/ethernet/intel/ice/ice_repr.c | 110 +++++++++++-------
> > drivers/net/ethernet/intel/ice/ice_repr.h | 21 +++-
> > drivers/net/ethernet/intel/ice/ice_sf_eth.c | 11 ++
> > drivers/net/ethernet/intel/ice/ice_sriov.c | 4 +-
> > drivers/net/ethernet/intel/ice/ice_txrx.c | 2 +-
> > drivers/net/ethernet/intel/ice/ice_vf_lib.c | 4 +-
> > 10 files changed, 184 insertions(+), 77 deletions(-)
>
> Again, please split.
Ok
next prev parent reply other threads:[~2024-02-13 9:55 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 7:27 [Intel-wired-lan] [iwl-next v1 00/15] ice: support devlink subfunctions Michal Swiatkowski
2024-02-13 7:27 ` Michal Swiatkowski
2024-02-13 7:27 ` [Intel-wired-lan] [iwl-next v1 01/15] ice: move devlink port code to a separate file Michal Swiatkowski
2024-02-13 7:27 ` Michal Swiatkowski
2024-02-13 7:27 ` [Intel-wired-lan] [iwl-next v1 02/15] ice: add new VSI type for subfunctions Michal Swiatkowski
2024-02-13 7:27 ` Michal Swiatkowski
2024-02-13 7:27 ` [Intel-wired-lan] [iwl-next v1 03/15] ice: export ice ndo_ops functions Michal Swiatkowski
2024-02-13 7:27 ` Michal Swiatkowski
2024-02-13 7:27 ` [Intel-wired-lan] [iwl-next v1 04/15] ice: add basic devlink subfunctions support Michal Swiatkowski
2024-02-13 7:27 ` Michal Swiatkowski
2024-02-13 8:55 ` [Intel-wired-lan] " Jiri Pirko
2024-02-13 8:55 ` Jiri Pirko
2024-02-13 9:39 ` [Intel-wired-lan] " Michal Swiatkowski
2024-02-13 9:39 ` Michal Swiatkowski
2024-02-13 11:27 ` Jiri Pirko
2024-02-13 11:27 ` Jiri Pirko
2024-02-13 12:02 ` Michal Swiatkowski
2024-02-13 12:02 ` Michal Swiatkowski
2024-02-13 14:57 ` Jiri Pirko
2024-02-13 14:57 ` Jiri Pirko
2024-02-14 6:26 ` Michal Swiatkowski
2024-02-14 6:26 ` Michal Swiatkowski
2024-02-14 19:45 ` Jacob Keller
2024-02-14 19:45 ` Jacob Keller
2024-02-13 7:27 ` [Intel-wired-lan] [iwl-next v1 05/15] ice: add subfunctions ethtool ops Michal Swiatkowski
2024-02-13 7:27 ` Michal Swiatkowski
2024-02-13 7:27 ` [Intel-wired-lan] [iwl-next v1 06/15] ice: add subfunction aux driver support Michal Swiatkowski
2024-02-13 7:27 ` Michal Swiatkowski
2024-02-13 8:57 ` [Intel-wired-lan] " Jiri Pirko
2024-02-13 8:57 ` Jiri Pirko
2024-02-13 9:43 ` [Intel-wired-lan] " Michal Swiatkowski
2024-02-13 9:43 ` Michal Swiatkowski
2024-02-13 11:28 ` [Intel-wired-lan] " Jiri Pirko
2024-02-13 11:28 ` Jiri Pirko
2024-02-13 12:03 ` [Intel-wired-lan] " Michal Swiatkowski
2024-02-13 12:03 ` Michal Swiatkowski
2024-02-13 7:27 ` [Intel-wired-lan] [iwl-next v1 07/15] ice: add auxiliary device sfnum attribute Michal Swiatkowski
2024-02-13 7:27 ` Michal Swiatkowski
2024-02-13 8:59 ` [Intel-wired-lan] " Jiri Pirko
2024-02-13 8:59 ` Jiri Pirko
2024-02-13 9:53 ` [Intel-wired-lan] " Michal Swiatkowski
2024-02-13 9:53 ` Michal Swiatkowski
2024-02-13 11:29 ` [Intel-wired-lan] " Jiri Pirko
2024-02-13 11:29 ` Jiri Pirko
2024-02-13 11:55 ` [Intel-wired-lan] " Michal Swiatkowski
2024-02-13 11:55 ` Michal Swiatkowski
2024-02-13 22:04 ` [Intel-wired-lan] " Jacob Keller
2024-02-13 22:04 ` Jacob Keller
2024-02-14 8:45 ` [Intel-wired-lan] " Jiri Pirko
2024-02-14 8:45 ` Jiri Pirko
2024-02-14 19:41 ` [Intel-wired-lan] " Keller, Jacob E
2024-02-14 19:41 ` Keller, Jacob E
2024-02-13 7:27 ` [Intel-wired-lan] [iwl-next v1 08/15] ice: store SF data in VSI struct Michal Swiatkowski
2024-02-13 7:27 ` Michal Swiatkowski
2024-02-13 7:27 ` [Intel-wired-lan] [iwl-next v1 09/15] ice: store representor ID in bridge port Michal Swiatkowski
2024-02-13 7:27 ` Michal Swiatkowski
2024-02-13 7:27 ` [Intel-wired-lan] [iwl-next v1 10/15] ice: create port representor for SF Michal Swiatkowski
2024-02-13 7:27 ` Michal Swiatkowski
2024-02-13 9:00 ` [Intel-wired-lan] " Jiri Pirko
2024-02-13 9:00 ` Jiri Pirko
2024-02-13 9:55 ` Michal Swiatkowski [this message]
2024-02-13 9:55 ` Michal Swiatkowski
2024-02-13 7:27 ` [Intel-wired-lan] [iwl-next v1 11/15] ice: check if SF is ready in ethtool ops Michal Swiatkowski
2024-02-13 7:27 ` Michal Swiatkowski
2024-02-13 7:27 ` [Intel-wired-lan] [iwl-next v1 12/15] ice: netdevice ops for SF representor Michal Swiatkowski
2024-02-13 7:27 ` Michal Swiatkowski
2024-02-13 7:27 ` [Intel-wired-lan] [iwl-next v1 13/15] ice: support subfunction devlink Tx topology Michal Swiatkowski
2024-02-13 7:27 ` Michal Swiatkowski
2024-02-13 7:27 ` [Intel-wired-lan] [iwl-next v1 14/15] ice: basic support for VLAN in subfunctions Michal Swiatkowski
2024-02-13 7:27 ` Michal Swiatkowski
2024-02-13 7:27 ` [Intel-wired-lan] [iwl-next v1 15/15] ice: move ice_devlink.[ch] to devlink folder Michal Swiatkowski
2024-02-13 7:27 ` Michal Swiatkowski
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=Zcs8eSp0R98Ejrce@mev-dev \
--to=michal.swiatkowski@linux.intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=jiri@resnulli.us \
--cc=maciej.fijalkowski@intel.com \
--cc=michal.kubiak@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pio.raczynski@gmail.com \
--cc=przemyslaw.kitszel@intel.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.