From: Yoav Artzi <yoavar@checkpoint.com>
To: Kyle McMartin <kyle@mcmartin.ca>
Cc: Adrian Bunk <bunk@kernel.org>, Jiri Slaby <jirislaby@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: PAGE_SIZE on 64bit and 32bit machines
Date: Mon, 12 Nov 2007 18:22:31 +0200 [thread overview]
Message-ID: <47387DC7.9090001@checkpoint.com> (raw)
In-Reply-To: <20071112161106.GB24243@fattire.cabal.ca>
I see. Thanks, guys.
-------- Original Message --------
Subject: Re: PAGE_SIZE on 64bit and 32bit machines
From: Kyle McMartin <kyle@mcmartin.ca>
To: Yoav Artzi <yoavar@checkpoint.com>
Date: Monday, November 12, 2007 6:11:06 PM
> On Mon, Nov 12, 2007 at 05:58:08PM +0200, Yoav Artzi wrote:
>
>> Looking at the source, I see:
>>
>> #ifdef CONFIG_4KSTACKS
>> #define THREAD_SIZE (4096)
>> #else
>> #define THREAD_SIZE (8192)
>> #endif
>>
>>
>> So if I configure the option CONFIG_4KSTACK, I will get a 4KB kernel
>> stack. Am I missing something here?
>>
>>
>
> This is only on i386 (32-bit x86...)[1] On x86-64, we have 8K kernel
> stacks (THREAD_ORDER 1), and 16K irqstacks (IRQSTACK_ORDER 2).
>
> The relevant defines are found in <asm-x86/page_64.h> for x86_64, and
> <asm-x86/thread_info_32.h> for i386.
>
> Cheers,
> Kyle
>
> 1. That is, stack size is only configurable on 32bit.
>
> Scanned by Check Point VPN-1 UTM NGX R65 with Messaging Security
>
>
next prev parent reply other threads:[~2007-11-12 16:22 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 [this message]
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=47387DC7.9090001@checkpoint.com \
--to=yoavar@checkpoint.com \
--cc=bunk@kernel.org \
--cc=jirislaby@gmail.com \
--cc=kyle@mcmartin.ca \
--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