From: Stephen Hemminger <shemminger@vyatta.com>
To: guenter.roeck@ericsson.com
Cc: netdev@vger.kernel.org
Subject: Re: [RFC] [PATCH] Improve hash function used for full_name_hash()
Date: Mon, 4 Jan 2010 12:29:12 -0800 [thread overview]
Message-ID: <20100104122912.5f9d1ebb@nehalam> (raw)
In-Reply-To: <1262635784.8178.253.camel@groeck-laptop>
On Mon, 04 Jan 2010 12:09:44 -0800
Guenter Roeck <guenter.roeck@ericsson.com> wrote:
> For example, when hashing "eth0" .. "eth9999" with a hash table size of 256,
> the resulting minimum hash bucket depth is 0, the maximum depth is 563,
> and the standard deviation is ~136.
The problem was a missing call to hash_32() on the result, and is
already fixed in current kernel.
--
next prev parent reply other threads:[~2010-01-04 20:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-04 20:09 [RFC] [PATCH] Improve hash function used for full_name_hash() Guenter Roeck
2010-01-04 20:29 ` Stephen Hemminger [this message]
2010-01-04 20:47 ` David Miller
2010-01-04 20:51 ` Guenter Roeck
2010-01-04 20:44 ` Eric Dumazet
2010-01-04 20:51 ` David Miller
2010-01-04 20:53 ` Guenter Roeck
2010-01-04 20:46 ` 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=20100104122912.5f9d1ebb@nehalam \
--to=shemminger@vyatta.com \
--cc=guenter.roeck@ericsson.com \
--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).