From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, netdev@vger.kernel.org
Cc: Tony Nguyen <anthony.l.nguyen@intel.com>,
michal.swiatkowski@linux.intel.com, piotr.raczynski@intel.com,
simon.horman@corigine.com, leonro@nvidia.com
Subject: [PATCH net-next 0/5][pull request] ice: allow matching on meta data
Date: Fri, 19 May 2023 10:00:13 -0700 [thread overview]
Message-ID: <20230519170018.2820322-1-anthony.l.nguyen@intel.com> (raw)
Michal Swiatkowski says:
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.
The following are changes since commit 20d5e0ef252a151ea6585cfccf32def81a624666:
net: arc: Make arc_emac_remove() return void
and are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue 100GbE
Michal Swiatkowski (5):
ice: define meta data to match in switch
ice: remove redundant Rx field from rule info
ice: specify field names in ice_prot_ext init
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 | 84 ++-----
drivers/net/ethernet/intel/ice/ice_eswitch.h | 14 --
.../ethernet/intel/ice/ice_protocol_type.h | 197 ++++++++++++++-
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 | 232 ++++++++----------
drivers/net/ethernet/intel/ice/ice_switch.h | 13 +-
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, 351 insertions(+), 259 deletions(-)
--
2.38.1
next reply other threads:[~2023-05-19 17:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 17:00 Tony Nguyen [this message]
2023-05-19 17:00 ` [PATCH net-next 1/5] ice: define meta data to match in switch Tony Nguyen
2023-05-19 17:00 ` [PATCH net-next 2/5] ice: remove redundant Rx field from rule info Tony Nguyen
2023-05-19 17:00 ` [PATCH net-next 3/5] ice: specify field names in ice_prot_ext init Tony Nguyen
2023-05-19 17:00 ` [PATCH net-next 4/5] ice: allow matching on meta data Tony Nguyen
2023-05-19 17:00 ` [PATCH net-next 5/5] ice: use src VSI instead of src MAC in slow-path Tony Nguyen
2023-05-22 12:00 ` [PATCH net-next 0/5][pull request] ice: allow matching on meta data patchwork-bot+netdevbpf
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=20230519170018.2820322-1-anthony.l.nguyen@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=michal.swiatkowski@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=piotr.raczynski@intel.com \
--cc=simon.horman@corigine.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).