public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gianni Tedesco <gianni@ecsc.co.uk>
To: Andi Kleen <ak@suse.de>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
	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: 27 Feb 2003 11:21:38 +0000	[thread overview]
Message-ID: <1046344898.28559.12.camel@lemsip> (raw)
In-Reply-To: <20030226183304.GA30836@wotan.suse.de>

[-- Attachment #1: Type: text/plain, Size: 720 bytes --]

On Wed, 2003-02-26 at 18:33, Andi Kleen wrote:
> 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.

Didn't wli do some work in this area? I seem to recall him recommending
FNV1a for dcache...

-- 
// Gianni Tedesco (gianni at scaramanga dot co dot uk)
lynx --source www.scaramanga.co.uk/gianni-at-ecsc.asc | gpg --import
8646BE7D: 6D9F 2287 870E A2C9 8F60 3A3C 91B5 7669 8646 BE7D

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2003-02-27 11:10 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
2003-02-27 11:21     ` Gianni Tedesco [this message]
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=1046344898.28559.12.camel@lemsip \
    --to=gianni@ecsc.co.uk \
    --cc=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