From: "Seth, Rohit" <rohit.seth@intel.com>
To: 'Steven Cole' <elenstev@mesatop.com>,
"Martin J. Bligh" <mbligh@aracnet.com>
Cc: Andrew Morton <akpm@zip.com.au>,
"Seth, Rohit" <rohit.seth@intel.com>,
linux-mm@kvack.org
Subject: RE: [PATCH] Config.help entry for CONFIG_HUGETLB_PAGE
Date: Wed, 11 Sep 2002 10:39:47 -0700 [thread overview]
Message-ID: <25282B06EFB8D31198BF00508B66D4FA03EA5806@fmsmsx114.fm.intel.com> (raw)
Thanks Steve. Your description in config.help file looks good.
> -----Original Message-----
> From: Steven Cole [mailto:elenstev@mesatop.com]
> Sent: Wednesday, September 11, 2002 8:18 AM
> To: Martin J. Bligh
> Cc: Andrew Morton; Seth, Rohit; linux-mm@kvack.org
> Subject: Re: [PATCH] Config.help entry for CONFIG_HUGETLB_PAGE
>
>
> On Wed, 2002-09-11 at 09:05, Martin J. Bligh wrote:
> >
> > > +CONFIG_HUGETLB_PAGE
> > > + This enables support for huge pages (4MB for x86). User space
> > > + applications can make use of this support with the
> sys_alloc_hugepages
> > > + and sys_free_hugepages system calls. If your applications are
> > > + huge page aware and your processor (Pentium or later
> for x86) supports
> > > + this, then say Y here.
> > > +
> > > + Otherwise, say N.
> >
> > They're not always 4Mb on x86 ... they're 2Mb if you have PAE
> > turned on ... maybe just leave out the "(4MB for x86)" comment?
> >
> > M.
>
> Better?
>
> --- linux-2.5.34-mm1/arch/i386/Config.help.orig Wed Sep
> 11 07:54:49 2002
> +++ linux-2.5.34-mm1/arch/i386/Config.help Wed Sep 11 09:14:52 2002
> @@ -25,6 +25,15 @@
>
> If you don't know what to do here, say N.
>
> +CONFIG_HUGETLB_PAGE
> + This enables support for huge pages. User space applications
> + can make use of this support with the sys_alloc_hugepages and
> + sys_free_hugepages system calls. If your applications are
> + huge page aware and your processor (Pentium or later for x86)
> + supports this, then say Y here.
> +
> + Otherwise, say N.
> +
> CONFIG_PREEMPT
> This option reduces the latency of the kernel when reacting to
> real-time or interactive events by allowing a low priority
> process to
>
--
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/
next reply other threads:[~2002-09-11 17:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-11 17:39 Seth, Rohit [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-11 14:48 Steven Cole
2002-09-11 15:05 ` Martin J. Bligh
2002-09-11 15:17 ` Steven Cole
2002-09-11 15:29 ` Martin J. Bligh
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=25282B06EFB8D31198BF00508B66D4FA03EA5806@fmsmsx114.fm.intel.com \
--to=rohit.seth@intel.com \
--cc=akpm@zip.com.au \
--cc=elenstev@mesatop.com \
--cc=linux-mm@kvack.org \
--cc=mbligh@aracnet.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