All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Mark Hahn <hahn@physics.mcmaster.ca>, linux-kernel@vger.kernel.org
Subject: Re: 4K vs 8K stacks- Which to use?
Date: Sat, 3 Jul 2004 11:48:49 -0700	[thread overview]
Message-ID: <20040703184849.GS21066@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.60.0407031043070.13543@p500>

On Sat, 3 Jul 2004, Mark Hahn wrote:
>> why do you think it would be processor-specific?

On Sat, Jul 03, 2004 at 10:44:44AM -0400, Justin Piszcz wrote:
> Well I know IA32 is limited to a 4096 byte page size in the Linux Kernel; 
> hence filesystems can only use 4KB blocks on IA32, therefore I was 
> wondering if anything might change in 64bit land?

64-bit ports tend to have stacks around twice the native pagesize, e.g.
sparc64 has 16K stacks and 8K pages, similar to 32-bit ports, except for
ia64. The ia32 port has adopted the order 0 stacksize in the interest
of space savings relatively early among Linux ports. It would be nice
to get the same for all architectures, as higher-order allocations are
not good to have as anything but speculative (and obviously stacks are
not variable-sized) for reasons of fragmentation.


-- wli

  reply	other threads:[~2004-07-03 18:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44.0407031038310.32173-100000@coffee.psychology.mcmaster.ca>
2004-07-03 14:44 ` 4K vs 8K stacks- Which to use? Justin Piszcz
2004-07-03 18:48   ` William Lee Irwin III [this message]
2004-07-03 10:50 Justin Piszcz
2004-07-04 10:55 ` Ikke
2004-07-04 12:34   ` Chris Wedgwood
2004-07-05 11:06     ` Ikke

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=20040703184849.GS21066@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=hahn@physics.mcmaster.ca \
    --cc=jpiszcz@lucidpixels.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.