From: Andi Kleen <ak@muc.de>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Andi Kleen <ak@muc.de>, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Dcache hash distrubition patches
Date: Tue, 11 Mar 2003 17:27:34 +0100 [thread overview]
Message-ID: <20030311162734.GA5640@averell> (raw)
In-Reply-To: <31840000.1047396682@[10.10.2.4]>
On Tue, Mar 11, 2003 at 04:31:23PM +0100, Martin J. Bligh wrote:
> I can try 1Mb or something I suppose ... what's the purpose here,
> to keep the cachelines of the bucket heads warm? Not sure it's worth
> the tradeoff, as we have to touch another line for each element we
> walk?
Use less cache for the hash table overall.
Use less lowmem.
Ideally there would be no tradeoff if you can still get reasonable
hash chain length with smaller tables (= overall win)
>
> I take it you're happy enough with the current hash function distribution?
At least I don't know how to improve it.
> > Also same for inode hash (but I don't have statistics for that right now)
>
> I could hack something up ... but 1 machine ain't going to cut it. I
> suspect I'd have a much smaller inode hash, as I tend to have masses
> of kernel trees, mostly hardlinked to each other.
I doubt inode cache is very critical, except perhaps in NFS server loads
(but even the nfs server has an own frontend cache)
Normally the dcache should bear most of the load.
-Andi
next prev parent reply other threads:[~2003-03-11 16:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-10 17:45 Dcache hash distrubition patches Martin J. Bligh
2003-03-10 17:52 ` Andi Kleen
2003-03-11 7:41 ` Martin J. Bligh
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 [this message]
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=20030311162734.GA5640@averell \
--to=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--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