From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: HUGEPAGE SIZE a boottime option
Date: Fri, 20 Feb 2004 02:35:38 +0000 [thread overview]
Message-ID: <16437.29306.947060.600300@napali.hpl.hp.com> (raw)
In-Reply-To: <20040220010731.GA28820@sgi.com>
>>>>> On Thu, 19 Feb 2004 19:07:31 -0600, Jack Steiner <steiner@sgi.com> said:
Jack> Here is a preliminary version of a patch that makes the size
Jack> of HUGEPAGES a boottime option. Only ia64-specific files are
Jack> changed (except for the Documentation file).
Jack> We have a number of customers using large
Jack> pages. Unfortunately, the "optimum" size of a large page is
Jack> application & configuration dependent. Rather that having each
Jack> customer recompile to specify their own HUGEPAGESIZE, this
Jack> patch make the size a boottime option.
Jack> Does this patch look reasonable? If so, I will incorporate feedback,
Jack> finish testing it, update it to 2.6.3 & resubmit.
Looks neat to me. But, man, do lose that trailing whitespace!
(especially in Kconfig---all 166 characters of it! ;-)
Rohit?
--david
next prev parent reply other threads:[~2004-02-20 2:35 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 [this message]
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
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=16437.29306.947060.600300@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.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