From: Paul Durrant <Paul.Durrant@citrix.com>
To: David Miller <davem@davemloft.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: RE: [PATCH net-next v1 0/8] xen-netback: support toeplitz hashing
Date: Fri, 12 Feb 2016 11:07:50 +0000 [thread overview]
Message-ID: <47dcce9fc54b42f591284cd8ea72ddba@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <20160212.055408.1901988218281607996.davem@davemloft.net>
> -----Original Message-----
> From: netdev-owner@vger.kernel.org [mailto:netdev-
> owner@vger.kernel.org] On Behalf Of David Miller
> Sent: 12 February 2016 10:54
> To: Paul Durrant
> Cc: netdev@vger.kernel.org; xen-devel@lists.xenproject.org
> Subject: Re: [PATCH net-next v1 0/8] xen-netback: support toeplitz hashing
>
> From: Paul Durrant <paul.durrant@citrix.com>
> Date: Fri, 12 Feb 2016 10:13:17 +0000
>
> > This patch series adds support for frontend-configurable toeplitz hashing
> > in xen-netback (on the guest receive side). This support has been testing
> > against a Windows frontend and has proven to be sufficient to pass the
> > Microsoft HCK NDIS RSS tests.
>
> We want less Toeplitz users, not more of them. It is a more unsuitable
> hash than jhash2.
>
> I'm not applying these patches, sorry.
Windows *requires* use of Teoplitz so your position completely rules out being able to support receive side scaling in Windows PV frontends on Linux kernel backends, not only for Xen but for any other hypervisor, which I think is totally unreasonable.
Paul
next prev parent reply other threads:[~2016-02-12 11:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 10:13 [PATCH net-next v1 0/8] xen-netback: support toeplitz hashing Paul Durrant
2016-02-12 10:13 ` [PATCH net-next v1 1/8] skbuff: store hash type in socket buffer Paul Durrant
2016-02-14 22:25 ` Tom Herbert
2016-02-15 8:50 ` Paul Durrant
2016-02-12 10:13 ` [PATCH net-next v1 2/8] xen-netback: re-import canonical netif header Paul Durrant
2016-02-12 10:13 ` [PATCH net-next v1 3/8] xen-netback: support multiple extra info fragments passed from frontend Paul Durrant
2016-02-12 10:13 ` [PATCH net-next v1 4/8] xen-netback: reduce log spam Paul Durrant
2016-02-12 10:13 ` [PATCH net-next v1 5/8] xen-netback: add support for the control ring Paul Durrant
2016-02-12 10:13 ` [PATCH net-next v1 6/8] xen-netback: add an implementation of toeplitz hashing Paul Durrant
2016-02-14 22:13 ` Tom Herbert
2016-02-12 10:13 ` [PATCH net-next v1 7/8] xen-netback: pass toeplitz hash value to the frontend Paul Durrant
2016-02-14 22:17 ` Tom Herbert
2016-02-12 10:13 ` [PATCH net-next v1 8/8] xen-netback: use toeplitz hash value from " Paul Durrant
2016-02-12 10:54 ` [PATCH net-next v1 0/8] xen-netback: support toeplitz hashing David Miller
2016-02-12 11:07 ` Paul Durrant [this message]
2016-02-12 16:41 ` David Miller
2016-02-12 16:59 ` Paul Durrant
2016-02-14 22:01 ` Tom Herbert
2016-02-15 8:48 ` Paul Durrant
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=47dcce9fc54b42f591284cd8ea72ddba@AMSPEX02CL03.citrite.net \
--to=paul.durrant@citrix.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).