From: Peter Chubb <peterc@gelato.unsw.edu.au>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Christoph Lameter <clameter@sgi.com>, linux-mm@kvack.org
Subject: Re: [RFC][PATCH 1/7] generic PAGE_SIZE infrastructure (v2)
Date: Tue, 29 Aug 2006 09:32:02 +1000 [thread overview]
Message-ID: <874pvw3099.peterc%peterc@gelato.unsw.edu.au> (raw)
In-Reply-To: <1156785119.5913.25.camel@localhost.localdomain>
>>>>> "Dave" == Dave Hansen <haveblue@us.ibm.com> writes:
>> > +choice > + prompt "Kernel Page Size" > + depends on
>> ARCH_GENERIC_PAGE_SIZE > +config PAGE_SIZE_4KB > + bool "4KB" > +
>> help > + This lets you select the page size of the kernel. For
>> best 64-bit > + performance, a page size of larger than 4k is
>> recommended. For best > + 32-bit compatibility on 64-bit
>> architectures, a page size of 4KB > + should be selected (although
>> most binaries work perfectly fine with > + a larger page size). >
>> + > + 4KB For best 32-bit compatibility > + 8KB and up For best
>> performance > + above 64k For kernel hackers only > + > + If you
>> don't know what to do, choose 8KB (if available). > + Otherwise,
>> choose 4KB.
>>
>> The above also would need to be genericized.
Dave> That is genericized. ;) Are there some bits that don't fit ia64
Dave> well?
IA64 wants 16k standard, 64k for better performance. So something
that says `choose 8k if you can' doesn't really fit. And it'd be
*really* nice to test larger pages --- I see ~5% improvement in
streaming I/O to a suitable RAID array with 64k as opposed to 16k
pages.
(The full range of hardware-supported page sizes for Itanium 2 is:
4K, 8K, 16K, 64K, 256K, 1M, 4M, 16M, 64M, 256M, 1G, 4G
and for Itanium 1 is:
4k, 16k, 64k, 256k, 1M, 4M, 16M, 64M, 256M)
--
Dr Peter Chubb http://www.gelato.unsw.edu.au peterc AT gelato.unsw.edu.au
http://www.ertos.nicta.com.au ERTOS within National ICT Australia
--
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:[~2006-08-28 23:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-28 15:44 Dave Hansen
2006-08-28 15:44 ` [RFC][PATCH 2/7] ia64 generic PAGE_SIZE Dave Hansen
2006-08-28 17:04 ` Christoph Lameter
2006-08-28 17:22 ` Dave Hansen
2006-08-28 17:32 ` Christoph Lameter
2006-08-28 17:45 ` Dave Hansen
2006-08-29 2:46 ` [RFC][PATCH 1/7] generic PAGE_SIZE infrastructure (v2) Paul Mundt
2006-08-29 3:51 ` Randy.Dunlap
2006-08-29 3:55 ` Paul Mundt
2006-08-29 4:02 ` Randy.Dunlap
2006-08-29 15:29 ` Dave Hansen
2006-08-30 0:37 ` Randy.Dunlap
2006-08-28 15:44 ` [RFC][PATCH 3/7] sparc64 generic PAGE_SIZE Dave Hansen
2006-08-28 15:44 ` [RFC][PATCH 4/7] mips " Dave Hansen
2006-08-28 15:44 ` [RFC][PATCH 6/7] powerpc " Dave Hansen
2006-08-28 15:44 ` [RFC][PATCH 5/7] parisc " Dave Hansen
2006-08-28 15:44 ` [RFC][PATCH 7/7] convert the "easy" architectures to " Dave Hansen
2006-08-28 17:01 ` [RFC][PATCH 1/7] generic PAGE_SIZE infrastructure (v2) Christoph Lameter
2006-08-28 17:11 ` Dave Hansen
2006-08-28 23:32 ` Peter Chubb [this message]
2006-08-29 18:59 ` Dave Hansen
2006-08-28 20:53 ` Dave Hansen
2006-08-28 21:44 ` 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=874pvw3099.peterc%peterc@gelato.unsw.edu.au \
--to=peterc@gelato.unsw.edu.au \
--cc=clameter@sgi.com \
--cc=haveblue@us.ibm.com \
--cc=linux-mm@kvack.org \
/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