From: Christoph Lameter <clameter@sgi.com>
To: Nishanth Aravamudan <nacc@us.ibm.com>
Cc: melgor@ie.ibm.com, apw@shadowen.org, agl@us.ibm.com,
wli@holomorphy.com, linux-mm@kvack.org
Subject: Re: [RFC][PATCH 2/2] Explicitly retry hugepage allocations
Date: Fri, 8 Feb 2008 11:19:54 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0802081117340.1654@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20080208171132.GE15903@us.ibm.com>
On Fri, 8 Feb 2008, Nishanth Aravamudan wrote:
> I also am not 100% positive on how I would test the result of such a
> change, since there are not that many large-order allocations in the
> kernel... Did you have any thoughts on that?
Boot the kernel with
slub_min_order=<whatever order you wish>
to get lots of allocations of a higher order.
You can run slub with huge pages by booting with
slub_min_order=9
this causes some benchmarks to run much faster...
In general the use of higher order pages is discouraged right now due
to the page allocators flaky behavior when allocating pages but
there are several projects that would benefit from that. Amoung them large
bufferer support for the I/O layer and larger page support for the VM to
reduce 4k page scanning overhead.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-02-08 19:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 23:07 [RFC][PATCH 1/2] Smarter retry of costly-order allocations Nishanth Aravamudan
2008-02-06 23:12 ` [RFC][PATCH 2/2] Explicitly retry hugepage allocations Nishanth Aravamudan
2008-02-06 23:30 ` Christoph Lameter
2008-02-07 1:04 ` Nishanth Aravamudan
2008-02-08 17:11 ` Nishanth Aravamudan
2008-02-08 19:19 ` Christoph Lameter [this message]
2008-02-08 23:40 ` Nishanth Aravamudan
2008-02-08 23:42 ` Christoph Lameter
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=Pine.LNX.4.64.0802081117340.1654@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=agl@us.ibm.com \
--cc=apw@shadowen.org \
--cc=linux-mm@kvack.org \
--cc=melgor@ie.ibm.com \
--cc=nacc@us.ibm.com \
--cc=wli@holomorphy.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