From: Dave Hansen <haveblue@us.ibm.com>
To: "Jose R. Santos" <jrsantos@austin.ibm.com>
Cc: 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: Mon, 12 Jul 2004 23:25:10 -0700 [thread overview]
Message-ID: <1089699910.19847.13357.camel@nighthawk> (raw)
In-Reply-To: <20040713023721.GA7461@austin.ibm.com>
On Mon, 2004-07-12 at 19:37, Jose R. Santos wrote:
> * Jose R. Santos <jrsantos@austin.ibm.com> [2004-07-12 12:56:05 -0500]:
> > Also, any particular reason why MAX_SYS_HASH_TABLE_ORDER was set to 14?
> > I am already seeing the need to go higher on my 64GB setup and was
> > wondering if this could be bumped up to 19.
>
> Actualy, it doesnt look like we need MAX_SYS_HASH_TABLE_ORDER at all so
> I'm resending the patch which now limits the max size of a hash table to
> 1/16 total memory pages. This would keep people from doing dangerous
> things when using the hash_entries.
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.
-- Dave
next prev parent reply other threads:[~2004-07-13 6:25 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 [this message]
2004-07-13 12:59 ` Jose R. Santos
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=1089699910.19847.13357.camel@nighthawk \
--to=haveblue@us.ibm.com \
--cc=akpm@osdl.org \
--cc=dhowells@redhat.com \
--cc=jrsantos@austin.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.