From: David Miller <davem@davemloft.net>
To: haiyangz@microsoft.com, haiyangz@exchange.microsoft.com
Cc: netdev@vger.kernel.org, kys@microsoft.com, olaf@aepfle.de,
vkuznets@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next,0/4] hv_netvsc: Ethtool handler to change UDP hash levels
Date: Tue, 22 Aug 2017 14:08:27 -0700 (PDT) [thread overview]
Message-ID: <20170822.140827.1102230677662395664.davem@davemloft.net> (raw)
In-Reply-To: <1503368560-14331-1-git-send-email-haiyangz@exchange.microsoft.com>
From: Haiyang Zhang <haiyangz@exchange.microsoft.com>
Date: Mon, 21 Aug 2017 19:22:36 -0700
> From: Haiyang Zhang <haiyangz@microsoft.com>
>
> The patch set adds the functions to switch UDP hash level between
> L3 and L4 by ethtool command. UDP over IPv4 and v6 can be set
> differently. The default hash level is L4. We currently only
> allow switching TX hash level from within the guests.
>
> The ethtool callback function is triggered by command line, and
> update the per device variables of the hash level.
>
> On Azure, fragmented UDP packets is not yet supported with L4
> hashing, and may have high packet loss rate. Using L3 hashing is
> recommended in this case. This ethtool option allows a user to
> make this selection.
Series applied, thanks.
prev parent reply other threads:[~2017-08-22 21:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 2:22 [PATCH net-next,0/4] hv_netvsc: Ethtool handler to change UDP hash levels Haiyang Zhang
2017-08-22 2:22 ` [PATCH net-next,1/4] hv_netvsc: Clean up unused parameter from netvsc_get_hash() Haiyang Zhang
2017-08-22 2:22 ` [PATCH net-next,2/4] hv_netvsc: Clean up unused parameter from netvsc_get_rss_hash_opts() Haiyang Zhang
2017-08-22 2:22 ` [PATCH net-next,3/4] hv_netvsc: Add ethtool handler to set and get UDP hash levels Haiyang Zhang
2017-08-22 2:22 ` [PATCH net-next,4/4] hv_netvsc: Update netvsc Document for UDP hash level setting Haiyang Zhang
2017-08-22 21:08 ` David Miller [this message]
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=20170822.140827.1102230677662395664.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=haiyangz@exchange.microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olaf@aepfle.de \
--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