From: Anatolii Gerasymenko <anatolii.gerasymenko@intel.com>
To: intel-wired-lan@lists.osuosl.org
Cc: Anatolii Gerasymenko <anatolii.gerasymenko@intel.com>
Subject: [Intel-wired-lan] [PATCH net-next v4 0/2] ice: FCS/CRC stripping control
Date: Wed, 27 Jul 2022 09:24:04 +0200 [thread overview]
Message-ID: <20220727072406.597424-1-anatolii.gerasymenko@intel.com> (raw)
Implement possibility to change FCS/CRC stripping feature using ethtool
command.
Having FCS/CRC could be useful for:
- network sniffers to inspect FCS/CRC correctness
- for benchmarking use cases
- XDP programs
v2: rebase on top of Maciej Fijalkowski's patches
v3: fix vsi->netdev NULL pointer derreference in ice_vsi_rebuild()
v4: fix Co-developed-by tag
Anatolii Gerasymenko (1):
ice: Implement FCS/CRC and VLAN stripping co-existence policy
Jesse Brandeburg (1):
ice: Implement control of FCS/CRC stripping
drivers/net/ethernet/intel/ice/ice.h | 1 +
drivers/net/ethernet/intel/ice/ice_base.c | 2 +-
drivers/net/ethernet/intel/ice/ice_ethtool.c | 5 +-
drivers/net/ethernet/intel/ice/ice_lib.c | 22 +++++++
drivers/net/ethernet/intel/ice/ice_lib.h | 2 +
drivers/net/ethernet/intel/ice/ice_main.c | 65 ++++++++++++++++++++
drivers/net/ethernet/intel/ice/ice_txrx.h | 3 +-
7 files changed, 94 insertions(+), 6 deletions(-)
--
2.25.1
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next reply other threads:[~2022-07-27 7:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 7:24 Anatolii Gerasymenko [this message]
2022-07-27 7:24 ` [Intel-wired-lan] [PATCH net-next v4 1/2] ice: Implement control of FCS/CRC stripping Anatolii Gerasymenko
2022-08-04 17:24 ` G, GurucharanX
2022-07-27 7:24 ` [Intel-wired-lan] [PATCH net-next v4 2/2] ice: Implement FCS/CRC and VLAN stripping co-existence policy Anatolii Gerasymenko
2022-08-04 17:21 ` G, GurucharanX
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=20220727072406.597424-1-anatolii.gerasymenko@intel.com \
--to=anatolii.gerasymenko@intel.com \
--cc=intel-wired-lan@lists.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.