mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Mark Hahn <hahn@physics.mcmaster.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 4K vs 8K stacks- Which to use?
Date: Sat, 3 Jul 2004 10:44:44 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.60.0407031043070.13543@p500> (raw)
In-Reply-To: <Pine.LNX.4.44.0407031038310.32173-100000@coffee.psychology.mcmaster.ca>

> does it matter?
Well the option is available :)

> why do you think it would be processor-specific?
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?

  On Sat, 3 Jul 2004, Mark 
Hahn wrote:

>> I use an array of machines with all sorts of CPU's (but no 64bit CPU's
>> yet):
>>
>> Which should I use for each CPU?
>
> does it matter?  4k stacks are primarily for benchmark machines
> under high load, where smaller stacks mean more threads available,
> and less chance of failing to allocate two contiguous pages.
>
>> Which is better and why?
>
> can't possibly matter for any normal use.
>
>> Pentium 1 CPU's
>> Cyrix P150 (120MHZ)
>> Pentium 2 CPU's
>> Pentium 3 CPU's
>> Pentium 4 W/HT
>> Pentium 4 W/OUT HT
>
> why do you think it would be processor-specific?
>

       reply	other threads:[~2004-07-03 14:44 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 ` Justin Piszcz [this message]
2004-07-03 18:48   ` William Lee Irwin III
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=Pine.LNX.4.60.0407031043070.13543@p500 \
    --to=jpiszcz@lucidpixels.com \
    --cc=hahn@physics.mcmaster.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

all inboxes | Powered by JetHome®