[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20170822.140827.1102230677662395664.davem@davemloft.net>
Date: Tue, 22 Aug 2017 14:08:27 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: haiyangz@...rosoft.com, haiyangz@...hange.microsoft.com
Cc: netdev@...r.kernel.org, kys@...rosoft.com, olaf@...fle.de,
vkuznets@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next,0/4] hv_netvsc: Ethtool handler to change UDP
hash levels
From: Haiyang Zhang <haiyangz@...hange.microsoft.com>
Date: Mon, 21 Aug 2017 19:22:36 -0700
> From: Haiyang Zhang <haiyangz@...rosoft.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.
Powered by blists - more mailing lists