From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Andi Kleen <ak@suse.de>
Cc: lse-tech@projects.sourceforge.net, akpm@digeo.com,
linux-kernel@vger.kernel.org
Subject: Re: [Lse-tech] [PATCH] New dcache / inode hash tuning patch
Date: Wed, 26 Feb 2003 13:16:15 -0800 [thread overview]
Message-ID: <6000000.1046294173@[10.10.2.4]> (raw)
In-Reply-To: <20030226183304.GA30836@wotan.suse.de>
>> It actually seems a fraction slower (see systimes for Kernbench-16,
>> for instance).
>
> Can you play a bit with the hash table sizes? Perhaps double the
> dcache hash and half the inode hash ?
I quadrupled the dcache hash size ... helped a bit. Is still a little
slower, which I don't understand ... your plan should make it go faster,
AFAICS. Those off-node accesses to ZONE_NORMAL are really expensive for me.
Kernbench-2: (make -j N vmlinux, where N = 2 x num_cpus)
Elapsed User System CPU
2.5.62-mjb3 44.24 558.12 94.17 1473.83
2.5.62-mjb3-andi 44.28 557.90 95.79 1475.67
2.5.62-mjb3-andi-4x 44.20 557.96 94.77 1475.83
Kernbench-16: (make -j N vmlinux, where N = 16 x num_cpus)
Elapsed User System CPU
2.5.62-mjb3 45.19 560.95 114.77 1495.00
2.5.62-mjb3-andi 45.39 561.29 117.73 1495.67
2.5.62-mjb3-andi-4x 45.34 560.54 116.85 1493.50
> I suspect it really just needs a better hash function. I'll cook
> something up based on FNV hash.
Sounds good ;-)
M.
next prev parent reply other threads:[~2003-02-26 21:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 16:49 [PATCH] New dcache / inode hash tuning patch Andi Kleen
2003-02-26 18:23 ` [Lse-tech] " Martin J. Bligh
2003-02-26 18:33 ` Andi Kleen
2003-02-26 21:16 ` Martin J. Bligh [this message]
2003-02-27 11:21 ` Gianni Tedesco
2003-02-27 11:28 ` William Lee Irwin III
2003-02-27 23:10 ` Linus Torvalds
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='6000000.1046294173@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--cc=ak@suse.de \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@projects.sourceforge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox