From: Yoav Artzi <yoavar@checkpoint.com>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PAGE_SIZE on 64bit and 32bit machines
Date: Mon, 12 Nov 2007 17:32:36 +0200 [thread overview]
Message-ID: <47387214.2010200@checkpoint.com> (raw)
In-Reply-To: <47386DC9.4020905@gmail.com>
Well, since the size of the kernel stack is one page, I figured it will
grow when switching to 64-bit, because some of the types grow and a
similar flow/stack will be bigger in 64-bit in comparison to 32-bit.
Keeping the page size at 4kb and so keeping the stack at 4kb is a bit
dangerous. Isn't it?
I know that using one page for a kernel stack is a optional feature, but:
a) It's a good feature
b) It's already used by major distros, e.g. Red Hat
-------- Original Message --------
Subject: Re: PAGE_SIZE on 64bit and 32bit machines
From: Jiri Slaby <jirislaby@gmail.com>
To: Yoav Artzi <yoavar@checkpoint.com>
Date: Monday, November 12, 2007 5:14:17 PM
> On 11/12/2007 03:39 PM, 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.
>>
>
> Yes, it stood unchanged, the only difference is 4-level page tables.
>
>
>> Can anyone explain to me what am I missing here?
>>
>
> What led you to that it must be 8k?
>
> regards,
>
next prev parent reply other threads:[~2007-11-12 15:32 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 [this message]
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
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=47387214.2010200@checkpoint.com \
--to=yoavar@checkpoint.com \
--cc=jirislaby@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.