From: "Jose R. Santos" <jrsantos@austin.ibm.com>
To: David Howells <dhowells@redhat.com>
Cc: "Jose R. Santos" <jrsantos@austin.ibm.com>,
akpm@osdl.org, 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:54:08 -0500 [thread overview]
Message-ID: <20040713125408.GA9149@rx8.austin.ibm.com> (raw)
In-Reply-To: <4348.1089722020@redhat.com> (from dhowells@redhat.com on Tue, Jul 13, 2004 at 07:33:40 -0500)
On 07/13/04 07:33:40, David Howells wrote:
> That's an enormous limit. Consider the fact that you will have a multiplicity
> of such hash tables, each potentially eating 1/16th of your total memory
> (remember, the bootmem allocator's only real limit is how big a chunk of
> memory it can allocate in one go).
>
> Do you have numbers to show that committing an eighth of your memory (8GB if
> you have 64GB - two hash tables at 4GB apiece) to hash tables is almost
> certainly not worth it.
I do not use all that memory but this is just the absolute limit that you can
allocate. The point is not to limit it to ORDER 14 because thats the most
gains seen on one 64GB setup. The idea is to give people some room to play
when they use the cmdline if for some reason they need to go that hi.
-JRS
next prev parent reply other threads:[~2004-07-13 12:56 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 [this message]
2004-07-13 6:25 ` Dave Hansen
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=20040713125408.GA9149@rx8.austin.ibm.com \
--to=jrsantos@austin.ibm.com \
--cc=akpm@osdl.org \
--cc=dhowells@redhat.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.