From: Anton Blanchard <anton@samba.org>
To: Andi Kleen <ak@suse.de>
Cc: manfred@colorfullife.com, akpm@osdl.org,
linux-kernel@vger.kernel.org, jrsantos@austin.ibm.com,
mbligh@aracnet.com
Subject: Re: [PATCH] Use numa policy API for boot time policy
Date: Thu, 10 Jun 2004 02:12:28 +1000 [thread overview]
Message-ID: <20040609161228.GB6152@krispykreme> (raw)
In-Reply-To: <20040609175613.487903b5.ak@suse.de>
> For what?
No idea, I just want to convince myself that there arent any out there.
> IMHO 16MB hash table for a kernel structure is madness. A different data
> structure is probably needed if it's really a problem
> (is your dcache that big?). Or maybe just limit the dcache more aggressively
> to keep the max number of entries smaller.
Yep, specSFS (an NFS benchmark) shows this up quite badly. I think Jose
and Martin were looking at strategies for keeping the dcache under
control.
This was on a machine with only 64GB of RAM, if we had an NFS server
with more memory then its reasonable to want more memory dedicated to
dentries. At that point we either need to increase the hash or look at
using another structure.
Anton
next prev parent reply other threads:[~2004-06-09 16:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-05 1:43 [PATCH] Use numa policy API for boot time policy Andi Kleen
2004-06-05 1:56 ` Manfred Spraul
2004-06-05 2:18 ` Andi Kleen
2004-06-05 2:32 ` Anton Blanchard
2004-06-05 10:22 ` Andi Kleen
2004-06-05 10:48 ` Andi Kleen
2004-06-09 15:44 ` Anton Blanchard
2004-06-09 15:56 ` Andi Kleen
2004-06-09 16:12 ` Anton Blanchard [this message]
2004-06-05 10:20 ` Manfred Spraul
2004-06-05 10:33 ` Andi Kleen
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=20040609161228.GB6152@krispykreme \
--to=anton@samba.org \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=jrsantos@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--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