public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Helge Hafting <helge.hafting@aitel.hist.no>
To: Yoav Artzi <yoavar@checkpoint.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PAGE_SIZE on 64bit and 32bit machines
Date: Tue, 13 Nov 2007 13:10:26 +0100	[thread overview]
Message-ID: <47399432.4090908@aitel.hist.no> (raw)
In-Reply-To: <473865BE.2070806@checkpoint.com>

Yoav Artzi wrote:
> According to my knowledge the PAGE_SIZE on 32bit architectures in 4KB. 
> Logically, the PAGE_SIZE on 64bit architectures should be 8KB. That's 
> at least the way I understand it. However, looking at the kernel code 
> of x86_64, I see the PAGE_SIZE is 4KB.
>
>
> Can anyone explain to me what am I missing here?
Only that there are no connection at all between the page size and
the number of bits the processor uses.


The cpu designer simply makes independent decisions for both cases.
So i386 uses 4kB pages because intel designed their processor that way.
And x86_64 uses 4kB pages because AMD designed the architecture that way.
And some processors use 8kB or 16kB pages because that is how they work.
A few  processors offer a selection of page sizes, it is then up to the
architecture maintainer to make a choice between them. No such choice
exists for intel/amd, unless you count the unrealistic option
of using generic 2MB pages.

Having said that, it is possible to get a feel of what a 8kB page system
will be like on intel, by always allocating pages in pairs.

Helge Hafting

      parent reply	other threads:[~2007-11-13 12:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-12 14:39 PAGE_SIZE on 64bit and 32bit machines Yoav Artzi
2007-11-12 15:14 ` Jiri Slaby
2007-11-12 15:32   ` Yoav Artzi
2007-11-12 15:39     ` Adrian Bunk
2007-11-12 15:58       ` Yoav Artzi
2007-11-12 16:02         ` Jiri Slaby
2007-11-12 16:11         ` Kyle McMartin
2007-11-12 16:22           ` Yoav Artzi
2007-11-12 17:13 ` Chris Snook
2007-11-13 12:10 ` Helge Hafting [this message]

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=47399432.4090908@aitel.hist.no \
    --to=helge.hafting@aitel.hist.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yoavar@checkpoint.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