From: Robert Love <rml@tech9.net>
To: Dan Sturtevant <dsturtev@plogic.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: x86 Page Sizes
Date: 26 Jun 2002 18:11:08 -0400 [thread overview]
Message-ID: <1025129491.1144.7.camel@icbm> (raw)
In-Reply-To: <Pine.LNX.4.44.0206261759230.11230-100000@milhouse.plogic.internal>
On Wed, 2002-06-26 at 18:02, Dan Sturtevant wrote:
>
> I know the x86 linux kernel has 4K pages in userspace and 4M pages in
> kernel space. These two sizes seem to be limitations of the intel
> architecture (I think).
>
> Does anyone know a way to increase the userspace page size above 4K?
> Are there any patches for a 4M userspace pagesize?
Kernel has 4K pages in user and kernel space. It is the same address
space and segment, just uses MMU protection.
x86 does 4K pages.
Robert Love
next prev parent reply other threads:[~2002-06-26 22:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-26 22:02 x86 Page Sizes Dan Sturtevant
2002-06-26 22:11 ` Robert Love [this message]
2002-06-27 6:35 ` Peter Svensson
2002-06-27 14:26 ` Steven Cole
2002-06-27 15:39 ` Robert Love
2002-07-06 0:36 ` john slee
2002-07-06 6:22 ` William Lee Irwin III
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=1025129491.1144.7.camel@icbm \
--to=rml@tech9.net \
--cc=dsturtev@plogic.com \
--cc=linux-kernel@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