From: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
To: intel-wired-lan@lists.osuosl.org
Cc: netdev@vger.kernel.org, wojciech.drewek@intel.com,
piotr.raczynski@intel.com,
Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
Subject: [PATCH net-next v2 0/4] ice: allow matching on meta data
Date: Tue, 4 Apr 2023 09:28:29 +0200 [thread overview]
Message-ID: <20230404072833.3676891-1-michal.swiatkowski@linux.intel.com> (raw)
Hi,
This patchset is intended to improve the usability of the switchdev
slow path. Without matching on a meta data values slow path works
based on VF's MAC addresses. It causes a problem when the VF wants
to use more than one MAC address (e.g. when it is in trusted mode).
Parse all meta data in the same place where protocol type fields are
parsed. Add description for the currently implemented meta data. It is
important to note that depending on DDP not all described meta data can
be available. Using not available meta data leads to error returned by
function which is looking for correct words in profiles read from DDP.
There is also one small improvement, remove of rx field in rule info
structure (patch 2). It is redundant.
v1 --> v2:
* fix spell issues
* use GENMASK to define source VSI mask
Michal Swiatkowski (4):
ice: define meta data to match in switch
ice: remove redundant Rx field from rule info
ice: allow matching on meta data
ice: use src VSI instead of src MAC in slow-path
drivers/net/ethernet/intel/ice/ice_eswitch.c | 76 +++----
drivers/net/ethernet/intel/ice/ice_eswitch.h | 14 --
.../ethernet/intel/ice/ice_protocol_type.h | 196 +++++++++++++++++-
drivers/net/ethernet/intel/ice/ice_repr.c | 17 --
drivers/net/ethernet/intel/ice/ice_repr.h | 5 +-
drivers/net/ethernet/intel/ice/ice_switch.c | 182 +++++++---------
drivers/net/ethernet/intel/ice/ice_switch.h | 9 +-
drivers/net/ethernet/intel/ice/ice_tc_lib.c | 34 ++-
drivers/net/ethernet/intel/ice/ice_tc_lib.h | 1 +
drivers/net/ethernet/intel/ice/ice_vf_lib.c | 3 -
drivers/net/ethernet/intel/ice/ice_virtchnl.c | 8 -
.../net/ethernet/intel/ice/ice_vlan_mode.c | 2 +-
12 files changed, 319 insertions(+), 228 deletions(-)
--
2.39.2
next reply other threads:[~2023-04-04 7:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 7:28 Michal Swiatkowski [this message]
2023-04-04 7:28 ` [PATCH net-next v2 1/4] ice: define meta data to match in switch Michal Swiatkowski
2023-04-04 7:28 ` [PATCH net-next v2 2/4] ice: remove redundant Rx field from rule info Michal Swiatkowski
2023-04-04 10:07 ` [Intel-wired-lan] " Alexander Lobakin
2023-04-04 11:40 ` Michal Swiatkowski
2023-04-04 7:28 ` [PATCH net-next v2 3/4] ice: allow matching on meta data Michal Swiatkowski
2023-04-04 10:22 ` [Intel-wired-lan] " Alexander Lobakin
2023-04-04 11:43 ` Michal Swiatkowski
2023-04-04 7:28 ` [PATCH net-next v2 4/4] ice: use src VSI instead of src MAC in slow-path Michal Swiatkowski
2023-04-04 10:30 ` [Intel-wired-lan] " Alexander Lobakin
2023-04-04 11:44 ` Michal Swiatkowski
2023-04-04 11:38 ` Paul Menzel
2023-04-05 8:07 ` 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=20230404072833.3676891-1-michal.swiatkowski@linux.intel.com \
--to=michal.swiatkowski@linux.intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=netdev@vger.kernel.org \
--cc=piotr.raczynski@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 NNTP newsgroup(s).