Netdev List
 help / color / mirror / Atom feed
From: Edward Cree <ecree@solarflare.com>
To: <linux-net-drivers@solarflare.com>, <netdev@vger.kernel.org>
Cc: <davem@davemloft.net>, <bkenward@solarflare.com>
Subject: [RFC PATCH net-next 0/2] sfc: enable 4-tuple UDP RSS hashing
Date: Tue, 27 Sep 2016 17:32:19 +0100	[thread overview]
Message-ID: <cc07d60a-189c-8475-ecb3-b612ff13bd5a@solarflare.com> (raw)

EF10 based NICs have configurable RSS hash fields, and can be made to take the
ports into the hash on UDP (they already do so for TCP).  This patch series
enables this, in order to improve spreading of UDP traffic.
Patch 2/2, which updates the ETHTOOL_GRXFH handling to report the new RSS hash
settings, uses a somewhat unorthodox construct to control fall-through flow in
a switch statement - is this acceptable style?

Edward Cree (2):
  sfc: enable 4-tuple RSS hashing for UDP
  sfc: report 4-tuple UDP hashing to ethtool, if it's enabled

 drivers/net/ethernet/sfc/ef10.c       | 84 +++++++++++++++++++++++++++++++++++
 drivers/net/ethernet/sfc/ethtool.c    | 14 ++++--
 drivers/net/ethernet/sfc/net_driver.h |  2 +
 3 files changed, 96 insertions(+), 4 deletions(-)

             reply	other threads:[~2016-09-27 16:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-27 16:32 Edward Cree [this message]
2016-09-27 16:35 ` [RFC PATCH net-next 1/2] sfc: enable 4-tuple RSS hashing for UDP Edward Cree
2016-09-27 16:35 ` [RFC PATCH net-next 2/2] sfc: report 4-tuple UDP hashing to ethtool, if it's enabled Edward Cree
2016-09-27 18:12   ` Mintz, Yuval
2016-09-28  9:12   ` David Laight
2016-09-28 14:56     ` Edward Cree

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=cc07d60a-189c-8475-ecb3-b612ff13bd5a@solarflare.com \
    --to=ecree@solarflare.com \
    --cc=bkenward@solarflare.com \
    --cc=davem@davemloft.net \
    --cc=linux-net-drivers@solarflare.com \
    --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