From: Mateusz Palczewski <mateusz.palczewski@intel.com>
To: intel-wired-lan@lists.osuosl.org
Cc: Michal Jaron <michalx.jaron@intel.com>
Subject: [Intel-wired-lan] [PATCH net-next v2 0/2] i40e: Fix ethtool rx-flow-hash setting for X722
Date: Tue, 12 Jul 2022 16:16:51 +0200 [thread overview]
Message-ID: <20220712141653.2590868-1-mateusz.palczewski@intel.com> (raw)
From: Michal Jaron <michalx.jaron@intel.com>
When enabling flow type for RSS hash via ethtool:
ethtool -N $pf rx-flow-hash tcp4|tcp6|udp4|udp6 s|d
the driver would fail to setup this setting on X722
device since it was using the mask on the register
dedicated for X710 devices.
Implement a bitmap to collect the flow pc types that
shall be applied on the inset and hena registers.
Apply a different mask on the register when setting the
RSS hash for the X722 device.
Michal Jaron (2):
i40e: Fix ethtool rx-flow-hash setting for X722
i40e: Refactor i40e_set_rss_hash_opt
.../net/ethernet/intel/i40e/i40e_ethtool.c | 105 +++++++++++-------
drivers/net/ethernet/intel/i40e/i40e_type.h | 4 +
2 files changed, 69 insertions(+), 40 deletions(-)
--
2.27.0
_______________________________________________
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-12 14:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 14:16 Mateusz Palczewski [this message]
2022-07-12 14:16 ` [Intel-wired-lan] [PATCH net-next v2 1/2] i40e: Fix ethtool rx-flow-hash setting for X722 Mateusz Palczewski
2022-07-12 14:16 ` [Intel-wired-lan] [PATCH net-next v2 2/2] i40e: Refactor i40e_set_rss_hash_opt Mateusz Palczewski
2022-07-12 22:37 ` [Intel-wired-lan] [PATCH net-next v2 0/2] i40e: Fix ethtool rx-flow-hash setting for X722 Tony Nguyen
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=20220712141653.2590868-1-mateusz.palczewski@intel.com \
--to=mateusz.palczewski@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=michalx.jaron@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