From: Lukasz Plachno <lukasz.plachno@intel.com>
To: intel-wired-lan@lists.osuosl.org
Cc: netdev@vger.kernel.org, Lukasz Plachno <lukasz.plachno@intel.com>
Subject: [Intel-wired-lan] [PATCH iwl-next v3 0/2] ice: Support flow director ether type filters
Date: Thu, 14 Dec 2023 05:34:47 +0100 [thread overview]
Message-ID: <20231214043449.15835-1-lukasz.plachno@intel.com> (raw)
Ethtool allows creating rules with type=ether, add support for such
filters in ice driver.
Patch 1 allows extending ice_fdir_comp_rules() with handling additional
type of filters.
v3: fixed possible use of uninitialized variable "perfect_filter"
v2: fixed compilation warning by moving default: case between commits
Jakub Buchocki (1):
ice: Implement 'flow-type ether' rules
Lukasz Plachno (1):
ice: Remove unnecessary argument from ice_fdir_comp_rules()
.../net/ethernet/intel/ice/ice_ethtool_fdir.c | 128 +++++++++++++++++-
drivers/net/ethernet/intel/ice/ice_fdir.c | 112 ++++++++-------
drivers/net/ethernet/intel/ice/ice_fdir.h | 11 ++
drivers/net/ethernet/intel/ice/ice_type.h | 1 +
4 files changed, 205 insertions(+), 47 deletions(-)
--
2.34.1
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next reply other threads:[~2023-12-14 11:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 4:34 Lukasz Plachno [this message]
2023-12-14 4:34 ` [Intel-wired-lan] [PATCH iwl-next v3 1/2] ice: Remove unnecessary argument from ice_fdir_comp_rules() Lukasz Plachno
2023-12-16 10:04 ` Simon Horman
2023-12-14 4:34 ` [Intel-wired-lan] [PATCH iwl-next v3 2/2] ice: Implement 'flow-type ether' rules Lukasz Plachno
2023-12-16 10:03 ` Simon Horman
2023-12-19 14:04 ` Plachno, Lukasz
2023-12-19 17:35 ` Brett Creeley
2023-12-20 14:19 ` Plachno, Lukasz
2023-12-20 17:11 ` Brett Creeley
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=20231214043449.15835-1-lukasz.plachno@intel.com \
--to=lukasz.plachno@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox