From: "Jose R. Santos" <jrsantos@austin.ibm.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: "Jose R. Santos" <jrsantos@austin.ibm.com>,
dhowells@redhat.com, Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
slpratt@us.ibm.com
Subject: Re: [PATCH] Making i/dhash_entries cmdline work as it use to.
Date: Tue, 13 Jul 2004 07:59:03 -0500 [thread overview]
Message-ID: <20040713125903.GC9149@rx8.austin.ibm.com> (raw)
In-Reply-To: <1089699910.19847.13357.camel@nighthawk> (from haveblue@us.ibm.com on Tue, Jul 13, 2004 at 01:25:10 -0500)
On 07/13/04 01:25:10, Dave Hansen wrote:
> Do you worry that you're just expanding the hash table as long as it
> gives benefit on your one, single benchmark? There have to be plenty of
> other workloads that could benefit from an extra 1/16th more memory.
> Not every workload is as dcache heavy as SFS.
This does not change the normal behavior of the kernel. This only
has effect when you use the cmdline options to increase it. I only
use 1/256 of my memory for hashes but there might be someone else
crazier than me that wants more. Of course the 1/16 number could be
change to something a lot smaller but i should give people some room
to play with.
-JRS
next prev parent reply other threads:[~2004-07-13 13:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-12 17:56 [PATCH] Making i/dhash_entries cmdline work as it use to Jose R. Santos
2004-07-13 2:37 ` Jose R. Santos
2004-07-13 2:56 ` Jose R. Santos
2004-07-13 12:33 ` David Howells
2004-07-13 12:54 ` Jose R. Santos
2004-07-13 6:25 ` Dave Hansen
2004-07-13 12:59 ` Jose R. Santos [this message]
2004-07-13 10:29 ` David Howells
2004-07-13 13:17 ` Jose R. Santos
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=20040713125903.GC9149@rx8.austin.ibm.com \
--to=jrsantos@austin.ibm.com \
--cc=akpm@osdl.org \
--cc=dhowells@redhat.com \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=slpratt@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.