From: VASM <vasm85@gmail.com>
To: Nix <nix@esperi.org.uk>
Cc: Jesper Juhl <jesper.juhl@gmail.com>,
gbakos@cfa.harvard.edu, linux-kernel@vger.kernel.org
Subject: Re: kernel page size explanation
Date: Mon, 25 Jul 2005 19:12:47 +0530 [thread overview]
Message-ID: <4536bb73050725064273cdbb50@mail.gmail.com> (raw)
In-Reply-To: <878xzvc2qs.fsf@amaterasu.srvr.nix>
On 7/25/05, Nix <nix@esperi.org.uk> wrote:
> On Mon, 25 Jul 2005, VASM wrote:
> > i had one question
> > does the linux kernel support only one default page size even if the
> > processor on which it is working supports multiple ?
>
> No. Some architectures have compile-time support for multiple different
> page sizes (e.g. Itanium, SPARC64); many have support for a
> (non-swappable) `large pages) system, and a filesystem backed by huge
> pages. (Often, the kernel is stored in huge pages, to keep the number
> of page table entries wasted by the nonswappable kernel to a minimum.)
>
> What is *not* presently supported is using multiple page sizes to
> back userspace processes; that size is currently fixed at compile-time,
> even on architectures supporting multiple variably-sized pages.
>
are there any specific reasons for not using large page size for
userspace processes
> --
> `But of course, GR is the very best relativity for the masses.'
> --- Wayne Throop
>
next prev parent reply other threads:[~2005-07-25 13:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-21 23:31 kernel page size explanation Gaspar Bakos
2005-07-22 1:20 ` Jesper Juhl
2005-07-23 22:09 ` Gaspar Bakos
2005-07-24 18:37 ` Nix
2005-07-24 19:01 ` VASM
2005-07-24 19:24 ` Fawad Lateef
2005-07-24 21:28 ` Nix
2005-07-25 13:42 ` VASM [this message]
2005-07-25 15:03 ` Valdis.Kletnieks
[not found] <4sSO3-58H-13@gated-at.bofh.it>
2005-07-22 0:15 ` Robert Hancock
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=4536bb73050725064273cdbb50@mail.gmail.com \
--to=vasm85@gmail.com \
--cc=gbakos@cfa.harvard.edu \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nix@esperi.org.uk \
/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