From: Larry McVoy <lm@bitmover.com>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: "Brian J. Watson" <Brian.J.Watson@compaq.com>,
Larry McVoy <lm@bitmover.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Common hash table implementation
Date: Sun, 22 Jul 2001 09:37:32 -0700 [thread overview]
Message-ID: <20010722093732.A6000@work.bitmover.com> (raw)
In-Reply-To: <01071815464209.12129@starship> <3B58CBA3.BD2C194@compaq.com> <01072122255100.02679@starship>
In-Reply-To: <01072122255100.02679@starship>; from phillips@bonn-fries.net on Sat, Jul 21, 2001 at 10:25:51PM +0200
On Sat, Jul 21, 2001 at 10:25:51PM +0200, Daniel Phillips wrote:
> 1) How random is the hash
> 2) How efficient is it
The hash is not the only part to consider for performance. The rest of the
code is important as well. The code I pointed you to has been really carefully
tuned for performance. And it can be made to be MP safe, SGI did that and
managed to get 455,000 random fetches/second on an 8 way R4400 (each of
these is about the same as the original Pentium at 150Mhz).
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2001-07-22 16:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-18 0:57 Common hash table implementation Brian J. Watson
2001-07-18 1:34 ` Larry McVoy
2001-07-18 13:46 ` Daniel Phillips
2001-07-21 0:24 ` Brian J. Watson
2001-07-21 20:25 ` Daniel Phillips
2001-07-22 10:18 ` Richard Guenther
2001-07-23 14:36 ` Daniel Phillips
2001-07-22 16:37 ` Larry McVoy [this message]
2001-07-23 14:24 ` Daniel Phillips
2001-07-22 23:34 ` Eyal Lebedinsky
2001-07-24 12:57 ` Daniel Phillips
2001-07-22 2:23 ` Rusty Russell
2001-07-24 12:28 ` Daniel Phillips
2001-07-18 9:48 ` Richard Guenther
[not found] <oupitgqjxoi.fsf@pigdrop.muc.suse.de>
2001-07-20 22:32 ` Brian J. Watson
2001-07-21 22:57 ` Daniel Phillips
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=20010722093732.A6000@work.bitmover.com \
--to=lm@bitmover.com \
--cc=Brian.J.Watson@compaq.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@bonn-fries.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.