From: Haiyang Zhang <haiyangz@exchange.microsoft.com>
To: davem@davemloft.net, netdev@vger.kernel.org
Cc: haiyangz@microsoft.com, kys@microsoft.com,
sthemmin@microsoft.com, olaf@aepfle.de, vkuznets@redhat.com,
linux-kernel@vger.kernel.org
Subject: [PATCH net-next,0/3] hv_netvsc: support changing TCP hash level
Date: Fri, 6 Oct 2017 08:33:56 -0700 [thread overview]
Message-ID: <20171006153359.8400-1-haiyangz@exchange.microsoft.com> (raw)
From: Haiyang Zhang <haiyangz@microsoft.com>
The patch set simplifies the existing hash level switching code for
UDP. It also adds the support for changing TCP hash level. So users
can switch between L3 an L4 hash levels for TCP and UDP.
Haiyang Zhang (3):
hv_netvsc: Change the hash level variable to bit flags
hv_netvsc: Add ethtool handler to set and get TCP hash levels
hv_netvsc: Update netvsc Document for TCP hash level setting
Documentation/networking/netvsc.txt | 8 ++--
drivers/net/hyperv/hyperv_net.h | 11 ++++-
drivers/net/hyperv/netvsc_drv.c | 96 ++++++++++++++++++++++++++++---------
3 files changed, 86 insertions(+), 29 deletions(-)
--
2.14.1
next reply other threads:[~2017-10-06 15:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 15:33 Haiyang Zhang [this message]
2017-10-06 15:33 ` [PATCH net-next,1/3] hv_netvsc: Change the hash level variable to bit flags Haiyang Zhang
2017-10-06 15:33 ` [PATCH net-next,2/3] hv_netvsc: Add ethtool handler to set and get TCP hash levels Haiyang Zhang
2017-10-06 15:33 ` [PATCH net-next,3/3] hv_netvsc: Update netvsc Document for TCP hash level setting Haiyang Zhang
2017-10-08 17:11 ` [PATCH net-next,0/3] hv_netvsc: support changing TCP hash level David Miller
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=20171006153359.8400-1-haiyangz@exchange.microsoft.com \
--to=haiyangz@exchange.microsoft.com \
--cc=davem@davemloft.net \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=sthemmin@microsoft.com \
--cc=vkuznets@redhat.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
all inboxes | Powered by JetHome®