From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Mark Lord <lkml@rtr.ca>
Cc: "J.A. Magallon" <jamagallon@able.es>,
"Linux-Kernel," <linux-kernel@vger.kernel.org>,
nel@vger.kernel.org
Subject: Re: About 4k kernel stack size....
Date: Tue, 20 Dec 2005 20:15:47 +0000 [thread overview]
Message-ID: <1135109747.25010.0.camel@localhost.localdomain> (raw)
In-Reply-To: <43A77205.2040306@rtr.ca>
On Llu, 2005-12-19 at 21:52 -0500, Mark Lord wrote:
> The mainline code paths are undoubtedly fine with 4K stacks.
> It's the *error paths* that are most likely to go deeper on the stack,
> and those are rarely exercised by anyone. And those are the paths
> that we *really* need to be reliable.
Very few error paths are that deep, the obvious complex exception is the
scsi one, but thats a seperate thread. Also the same argument about
reliability is why going to 4K stack + IRQ stacks helps - it makes the
stack usage predictable.
prev parent reply other threads:[~2005-12-20 20:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-18 22:14 About 4k kernel stack size J.A. Magallon
2005-12-20 2:52 ` Mark Lord
2005-12-20 13:37 ` Adrian Bunk
2005-12-20 14:37 ` Mike Snitzer
2005-12-20 15:00 ` Adrian Bunk
2005-12-20 15:55 ` Sean
2005-12-20 15:55 ` Sean
2005-12-21 15:07 ` Giridhar Pemmasani
2005-12-21 15:37 ` Kyle Moffett
2005-12-21 16:25 ` Giridhar Pemmasani
2005-12-21 16:46 ` Christoph Hellwig
2005-12-21 20:14 ` Krzysztof Halasa
2005-12-21 21:39 ` linux-os (Dick Johnson)
2005-12-22 9:14 ` Romano Giannetti
2005-12-20 17:02 ` linux-os (Dick Johnson)
2005-12-20 18:06 ` Chase Venters
2005-12-20 18:36 ` linux-os (Dick Johnson)
2005-12-20 18:43 ` Arjan van de Ven
2005-12-20 18:59 ` linux-os (Dick Johnson)
2005-12-20 22:33 ` Alan Cox
2005-12-20 22:54 ` Nikita Danilov
2005-12-21 14:02 ` linux-os (Dick Johnson)
2005-12-21 14:18 ` Nikita Danilov
2005-12-21 14:25 ` linux-os (Dick Johnson)
2005-12-21 15:19 ` Nikita Danilov
2005-12-21 22:50 ` Jan Engelhardt
2005-12-20 20:15 ` Alan Cox [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=1135109747.25010.0.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=nel@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.