From: David Miller <davem@davemloft.net>
To: haiyangz@microsoft.com
Cc: eric.dumazet@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, devel@linuxdriverproject.org
Subject: Re: [PATCH net-next] hv_netvsc: don't make assumptions on struct flow_keys layout
Date: Wed, 13 Jan 2016 23:56:43 -0500 (EST) [thread overview]
Message-ID: <20160113.235643.1373342973936029804.davem@davemloft.net> (raw)
In-Reply-To: <BN1PR0301MB07701A189AABFBF664B5775BCACB0@BN1PR0301MB0770.namprd03.prod.outlook.com>
From: Haiyang Zhang <haiyangz@microsoft.com>
Date: Wed, 13 Jan 2016 23:10:57 +0000
> I have done a comparison of the Toeplitz v.s. Jenkins Hash algorithms,
> and found that the Toeplitz provides much better distribution of the
> connections into send-indirection-table entries.
This fails to take into consideration how massively more expensive
Toeplitz is to compute.
This also fails to show what the real life performance implications
are.
Just showing distributions is meaningless if it doesn't indicate
what kind of performance distrubtion A or B achieves.
next prev parent reply other threads:[~2016-01-14 4:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 9:33 [PATCH net-next] hv_netvsc: don't make assumptions on struct flow_keys layout Vitaly Kuznetsov
2016-01-07 12:52 ` Eric Dumazet
2016-01-07 13:28 ` Vitaly Kuznetsov
2016-01-08 1:02 ` John Fastabend
2016-01-08 3:49 ` KY Srinivasan
2016-01-08 6:16 ` John Fastabend
2016-01-08 18:01 ` KY Srinivasan
2016-01-08 21:07 ` Haiyang Zhang
2016-01-09 0:17 ` Tom Herbert
2016-01-10 22:25 ` David Miller
2016-01-13 23:10 ` Haiyang Zhang
2016-01-14 4:56 ` David Miller [this message]
2016-01-14 17:14 ` Tom Herbert
2016-01-14 17:53 ` One Thousand Gnomes
2016-01-14 18:24 ` Eric Dumazet
2016-01-14 18:35 ` Haiyang Zhang
2016-01-14 18:48 ` Tom Herbert
2016-01-14 19:15 ` Haiyang Zhang
2016-01-14 19:41 ` Tom Herbert
2016-01-14 20:23 ` Haiyang Zhang
2016-01-14 21:44 ` Tom Herbert
2016-01-14 22:06 ` David Miller
2016-01-14 22:08 ` Eric Dumazet
2016-01-14 22:29 ` Haiyang Zhang
2016-01-14 17:53 ` Eric Dumazet
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=20160113.235643.1373342973936029804.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=devel@linuxdriverproject.org \
--cc=eric.dumazet@gmail.com \
--cc=haiyangz@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).