All of lore.kernel.org
 help / color / mirror / Atom feed
From: Penigalapati, Sandeep <sandeep.penigalapati@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net-next v3 04/12] ice: allow process vf opcodes in different ways
Date: Wed, 11 Aug 2021 05:24:35 +0000	[thread overview]
Message-ID: <MW3PR11MB4554CD4703D59F012C57AE4D9CF89@MW3PR11MB4554.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210625024501.6126-5-michal.swiatkowski@linux.intel.com>

>-----Original Message-----
>From: Intel-wired-lan <intel-wired-lan-bounces@osuosl.org> On Behalf Of
>Michal Swiatkowski
>Sent: Friday, June 25, 2021 8:15 AM
To: intel-wired-lan@lists.osuosl.org
>Subject: [Intel-wired-lan] [PATCH net-next v3 04/12] ice: allow process vf
>opcodes in different ways
>
>In switchdev driver shouldn't add MAC, VLAN and promisc filters on iavf
>demand but should return success to not break normal iavf flow.
>
>Achieve that by creating table of functions pointer with default functions used
>to parse iavf command. While parse iavf command, call correct function from
>table instead of calling function direct.
>
>When port representors are being created change functions in table to new
>one that behaves correctly for switchdev puprose (ignoring new filters).
>
>Change back to default ops when representors are being removed.
>
>Co-developed-by: Wojciech Drewek <wojciech.drewek@intel.com>
>Signed-off-by: Wojciech Drewek <wojciech.drewek@intel.com>
>Signed-off-by: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
>---
> drivers/net/ethernet/intel/ice/ice_repr.c     |  23 ++-
> .../net/ethernet/intel/ice/ice_virtchnl_pf.c  | 170 +++++++++++++++---
>.../net/ethernet/intel/ice/ice_virtchnl_pf.h  |  32 ++++
> 3 files changed, 198 insertions(+), 27 deletions(-)
>
Tested-by: Sandeep Penigalapati <sandeep.penigalapati@intel.com>

  reply	other threads:[~2021-08-11  5:24 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-25  2:44 [Intel-wired-lan] [PATCH net-next v3 00/12] Add switchdev driver model for ice driver Michal Swiatkowski
2021-06-25  2:44 ` [Intel-wired-lan] [PATCH net-next v3 01/12] ice: support basic E-Switch mode control Michal Swiatkowski
2021-08-03  9:11   ` Penigalapati, Sandeep
2021-06-25  2:44 ` [Intel-wired-lan] [PATCH net-next v3 02/12] ice: Move devlink port to PF/VF struct Michal Swiatkowski
2021-08-06  9:51   ` Penigalapati, Sandeep
2021-06-25  2:44 ` [Intel-wired-lan] [PATCH net-next v3 03/12] ice: introduce VF port representor Michal Swiatkowski
2021-08-06  9:50   ` Penigalapati, Sandeep
2021-06-25  2:44 ` [Intel-wired-lan] [PATCH net-next v3 04/12] ice: allow process vf opcodes in different ways Michal Swiatkowski
2021-08-11  5:24   ` Penigalapati, Sandeep [this message]
2021-06-25  2:44 ` [Intel-wired-lan] [PATCH net-next v3 05/12] ice: manage VSI antispoof and destination override Michal Swiatkowski
2021-08-11  5:27   ` Penigalapati, Sandeep
2021-06-25  2:44 ` [Intel-wired-lan] [PATCH net-next v3 06/12] ice: allow changing lan_en and lb_en on dflt rules Michal Swiatkowski
2021-08-06 10:08   ` Penigalapati, Sandeep
2021-06-25  2:44 ` [Intel-wired-lan] [PATCH net-next v3 07/12] ice: set and release switchdev environment Michal Swiatkowski
2021-08-18  3:39   ` Penigalapati, Sandeep
2021-06-25  2:44 ` [Intel-wired-lan] [PATCH net-next v3 08/12] ice: introduce new type of VSI for switchdev Michal Swiatkowski
2021-08-11  5:25   ` Penigalapati, Sandeep
2021-06-25  2:44 ` [Intel-wired-lan] [PATCH net-next v3 09/12] ice: enable/disable switchdev when managing VFs Michal Swiatkowski
2021-08-03  8:59   ` Penigalapati, Sandeep
2021-06-25  2:44 ` [Intel-wired-lan] [PATCH net-next v3 10/12] ice: rebuild switchdev when resetting all VFs Michal Swiatkowski
2021-08-11  5:25   ` Penigalapati, Sandeep
2021-06-25  2:45 ` [Intel-wired-lan] [PATCH net-next v3 11/12] ice: switchdev slow path Michal Swiatkowski
2021-08-06 10:55   ` Penigalapati, Sandeep
2021-06-25  2:45 ` [Intel-wired-lan] [PATCH net-next v3 12/12] ice: add port representor ethtool ops and stats Michal Swiatkowski
2021-08-06 10:46   ` Penigalapati, Sandeep

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=MW3PR11MB4554CD4703D59F012C57AE4D9CF89@MW3PR11MB4554.namprd11.prod.outlook.com \
    --to=sandeep.penigalapati@intel.com \
    --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.