All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net-next v2 00/12] Add switchdev driver model for ice driver
Date: Wed, 23 Jun 2021 07:48:29 +0200	[thread overview]
Message-ID: <c2378b90-a307-aa00-471b-247a15423527@molgen.mpg.de> (raw)
In-Reply-To: <20210622212134.341728-1-michal.swiatkowski@linux.intel.com>

Dear Michal,


Am 22.06.21 um 23:21 schrieb Michal Swiatkowski:
> The following patch series introduces basic switchdev model
> support in ice driver. Implement the following blocks of
> switchdev framework:
> - VF port representors creation
> - control plane VSI definition
> - exception path (a. k. a. "slow-path") - to allow a virtual
> switch or linux bridge to receive any packet that doesn't match
> any hw filter
> - link state management of virtual ports
> - query virtual port statistics
> 
> Hardware offload support in switchdev mode is out of scope of
> this patchset. Devlink interface is used to toggle between
> switchdev and legacy (the default) modes of the driver.

These are great news. Could you please elaborate in the summary how to 
switch to the new mode of the driver? What are the benefits of switchdev 
in this case? Less maintenance or better performance?

Should the switchdev folks be involved in review?

> Changelog:
>   v2:
>    * fix build issue in ice: setting and releasing switchdev environment
>    by moving call of ice_vsi_setup to next patch which have definition
>    for switchdev VSI
> 
> Grzegorz Nitka (5):
>    ice: setting and releasing switchdev environment

It?d be great if you could use verbs in imperative mood.


Kind regards,

Paul


>    ice: introduce new type of VSI for switchdev
>    ice: enable/disable switchdev when managing VFs
>    ice: rebuild switchdev when resetting all VFs
>    ice: switchdev slow path
> 
> Michal Swiatkowski (5):
>    ice: basic support for eswitch mode management
>    ice: introduce VF port representor
>    ice: allow process vf opcodes in different ways
>    ice: manage VSI antispoof and destination override
>    ice: allow changing lan_en and lb_en on dflt rules
> 
> Wojciech Drewek (2):
>    ice: Move devlink port to PF/VF struct
>    ice: add port representor ethtool ops and stats
> 
>   drivers/net/ethernet/intel/Kconfig            |  10 +
>   drivers/net/ethernet/intel/ice/Makefile       |   4 +-
>   drivers/net/ethernet/intel/ice/ice.h          |  48 +-
>   drivers/net/ethernet/intel/ice/ice_base.c     |  37 +-
>   drivers/net/ethernet/intel/ice/ice_devlink.c  | 109 ++-
>   drivers/net/ethernet/intel/ice/ice_devlink.h  |   6 +-
>   drivers/net/ethernet/intel/ice/ice_eswitch.c  | 656 ++++++++++++++++++
>   drivers/net/ethernet/intel/ice/ice_eswitch.h  |  82 +++
>   drivers/net/ethernet/intel/ice/ice_ethtool.c  |  32 +-
>   drivers/net/ethernet/intel/ice/ice_fltr.c     |  80 +++
>   drivers/net/ethernet/intel/ice/ice_fltr.h     |   7 +
>   .../net/ethernet/intel/ice/ice_lan_tx_rx.h    |  43 ++
>   drivers/net/ethernet/intel/ice/ice_lib.c      | 112 ++-
>   drivers/net/ethernet/intel/ice/ice_lib.h      |  11 +
>   drivers/net/ethernet/intel/ice/ice_main.c     |  47 +-
>   drivers/net/ethernet/intel/ice/ice_repr.c     | 329 +++++++++
>   drivers/net/ethernet/intel/ice/ice_repr.h     |  27 +
>   drivers/net/ethernet/intel/ice/ice_switch.c   |   2 +-
>   drivers/net/ethernet/intel/ice/ice_switch.h   |   6 +
>   drivers/net/ethernet/intel/ice/ice_txrx.c     |   3 +
>   drivers/net/ethernet/intel/ice/ice_txrx_lib.c |   4 +-
>   drivers/net/ethernet/intel/ice/ice_type.h     |   1 +
>   .../net/ethernet/intel/ice/ice_virtchnl_pf.c  | 196 +++++-
>   .../net/ethernet/intel/ice/ice_virtchnl_pf.h  |  45 ++
>   24 files changed, 1817 insertions(+), 80 deletions(-)
>   create mode 100644 drivers/net/ethernet/intel/ice/ice_eswitch.c
>   create mode 100644 drivers/net/ethernet/intel/ice/ice_eswitch.h
>   create mode 100644 drivers/net/ethernet/intel/ice/ice_repr.c
>   create mode 100644 drivers/net/ethernet/intel/ice/ice_repr.h
> 

  parent reply	other threads:[~2021-06-23  5:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-22 21:21 [Intel-wired-lan] [PATCH net-next v2 00/12] Add switchdev driver model for ice driver Michal Swiatkowski
2021-06-22 21:21 ` [Intel-wired-lan] [PATCH net-next v2 01/12] ice: basic support for eswitch mode management Michal Swiatkowski
2021-06-23  5:58   ` Paul Menzel
2021-06-23  3:41     ` Michal Swiatkowski
2021-07-05 10:22       ` Paul Menzel
2021-06-22 21:21 ` [Intel-wired-lan] [PATCH net-next v2 02/12] ice: Move devlink port to PF/VF struct Michal Swiatkowski
2021-06-22 21:21 ` [Intel-wired-lan] [PATCH net-next v2 03/12] ice: introduce VF port representor Michal Swiatkowski
2021-06-22 21:21 ` [Intel-wired-lan] [PATCH net-next v2 04/12] ice: allow process vf opcodes in different ways Michal Swiatkowski
2021-06-22 21:21 ` [Intel-wired-lan] [PATCH net-next v2 05/12] ice: manage VSI antispoof and destination override Michal Swiatkowski
2021-06-22 21:21 ` [Intel-wired-lan] [PATCH net-next v2 06/12] ice: allow changing lan_en and lb_en on dflt rules Michal Swiatkowski
2021-06-22 21:21 ` [Intel-wired-lan] [PATCH net-next v2 07/12] ice: setting and releasing switchdev environment Michal Swiatkowski
2021-06-22 21:21 ` [Intel-wired-lan] [PATCH net-next v2 08/12] ice: introduce new type of VSI for switchdev Michal Swiatkowski
2021-06-22 21:21 ` [Intel-wired-lan] [PATCH net-next v2 09/12] ice: enable/disable switchdev when managing VFs Michal Swiatkowski
2021-06-22 21:21 ` [Intel-wired-lan] [PATCH net-next v2 10/12] ice: rebuild switchdev when resetting all VFs Michal Swiatkowski
2021-06-22 21:21 ` [Intel-wired-lan] [PATCH net-next v2 11/12] ice: switchdev slow path Michal Swiatkowski
2021-06-22 21:21 ` [Intel-wired-lan] [PATCH net-next v2 12/12] ice: add port representor ethtool ops and stats Michal Swiatkowski
2021-06-23  5:48 ` Paul Menzel [this message]
2021-06-23  7:50   ` [Intel-wired-lan] [PATCH net-next v2 00/12] Add switchdev driver model for ice driver 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=c2378b90-a307-aa00-471b-247a15423527@molgen.mpg.de \
    --to=pmenzel@molgen.mpg.de \
    --cc=intel-wired-lan@osuosl.org \
    /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.