mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Andi Kleen <ak@muc.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Dcache hash distrubition patches
Date: Mon, 10 Mar 2003 23:41:07 -0800	[thread overview]
Message-ID: <26350000.1047368465@[10.10.2.4]> (raw)
In-Reply-To: <20030310175221.GA20060@averell>

>> Conclusion: the hash distribution (for this simple test) looks fine
>> to me.
> 
> Yes, because of the overkill size of the hash table. With a 100K + entry
> table you can make near every hash function look good ;)
> 
> Try to reduce it to a smaller number of buckets and see what happens.

OK, after I've stopped being an idiot, and misreading the code, I have 
some numbers. They still look pretty good to me. I shrunk us from
1,048,576 buckets to 65536, and loaded 1,150,000 entries in there.



      5 3
      9 4
     44 5
    113 6
    243 7
    519 8
   1059 9
   1613 10
   2458 11
   3506 12
   4515 13
   5349 14
   6071 15
   6328 16
   6369 17
   5862 18
   5228 19
   4305 20
   3546 21
   2613 22
   1981 23
   1382 24
    928 25
    602 26
    368 27
    230 28
    115 29
     75 30
     45 31
     16 32
     14 33
      3 34
      4 35
      2 36

It's not perfect, but not bad either. Some mathematician can go calculate
just how imperfect it is over random distribution, but it looks OK to me ;-)

M


  reply	other threads:[~2003-03-11  7:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-10 17:45 Martin J. Bligh
2003-03-10 17:52 ` Andi Kleen
2003-03-11  7:41   ` Martin J. Bligh [this message]
2003-03-11  7:47     ` William Lee Irwin III
2003-03-11 15:23     ` Andi Kleen
2003-03-11 15:31       ` Martin J. Bligh
2003-03-11 16:27         ` Andi Kleen
2003-03-11 17:29           ` Anton Blanchard

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='26350000.1047368465@[10.10.2.4]' \
    --to=mbligh@aracnet.com \
    --cc=ak@muc.de \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®