From: Andi Kleen <ak@suse.de>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Andi Kleen <ak@suse.de>,
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 19:33:04 +0100 [thread overview]
Message-ID: <20030226183304.GA30836@wotan.suse.de> (raw)
In-Reply-To: <15730000.1046283789@[10.10.2.4]>
On Wed, Feb 26, 2003 at 10:23:09AM -0800, Martin J. Bligh wrote:
> 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 suspect it really just needs a better hash function. I'll cook
something up based on FNV hash.
-Andi
next prev parent reply other threads:[~2003-02-26 18:22 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 [this message]
2003-02-26 21:16 ` Martin J. Bligh
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=20030226183304.GA30836@wotan.suse.de \
--to=ak@suse.de \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@projects.sourceforge.net \
--cc=mbligh@aracnet.com \
/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