From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: HUGEPAGE SIZE a boottime option
Date: Mon, 23 Feb 2004 16:19:29 +0000 [thread overview]
Message-ID: <B05667366EE6204181EABE9C1B1C0EB501F2AB08@scsmsx401.sc.intel.com> (raw)
In-Reply-To: <20040220010731.GA28820@sgi.com>
On Fri, Feb 20, 2004 at 11:36:38AM -0800, Seth, Rohit wrote:
> As long as there are only two supported page sizes (PAGE_SIZE and
> HPAGE_SIZE), it is possible to achieve the boot time configuration
> of HUGE_PAGE_SIZE without needing to patch the kernel (and possibly
> better packing the vhpt fault handler code).
On Sat, February 21, 2004 at 9:28 PM, Chris Wedgwood wrote:
> Jack's code doesn't have this limitation. IMO it's a more
> sane way to go. Why should people be restricted to a limited
> set (two) of hugepage sizes? This seems especially important
> for vendor kernels where people want to use the same kernel
> across a variety of different machines.
It's probably a misunderstanding. We are talking about run time
user page size, and you probably referring to huge page size that
user wants to specify at boot time. These are two totally
different things.
- Ken
next prev parent reply other threads:[~2004-02-23 16:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-20 1:07 HUGEPAGE SIZE a boottime option Jack Steiner
2004-02-20 2:35 ` David Mosberger
2004-02-20 4:00 ` Chen, Kenneth W
2004-02-20 19:36 ` Seth, Rohit
2004-02-22 5:27 ` Chris Wedgwood
2004-02-22 23:08 ` Jack Steiner
2004-02-23 16:19 ` Chen, Kenneth W [this message]
2004-02-23 16:26 ` Chen, Kenneth W
2004-02-23 18:52 ` David Mosberger
2004-02-23 18:58 ` Chen, Kenneth W
2004-02-24 4:05 ` Jack Steiner
2004-02-26 1:26 ` Chen, Kenneth W
2004-02-26 2:09 ` Chen, Kenneth W
2004-02-26 5:18 ` David Mosberger
2004-02-26 20:31 ` Chen, Kenneth W
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=B05667366EE6204181EABE9C1B1C0EB501F2AB08@scsmsx401.sc.intel.com \
--to=kenneth.w.chen@intel.com \
--cc=linux-ia64@vger.kernel.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