From: Nikita Danilov <nikita@clusterfs.com>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: "Mike Snitzer" <snitzer@gmail.com>,
"Adrian Bunk" <bunk@stusta.de>, "Mark Lord" <lkml@rtr.ca>,
"J.A. Magallon" <jamagallon@able.es>,
"Linux-Kernel," <linux-kernel@vger.kernel.org>,
<nel@vger.kernel.org>, <mpm@selenic.com>
Subject: Re: About 4k kernel stack size....
Date: Wed, 21 Dec 2005 01:54:16 +0300 [thread overview]
Message-ID: <17320.35736.89250.390950@gargle.gargle.HOWL> (raw)
In-Reply-To: <Pine.LNX.4.61.0512201202090.27692@chaos.analogic.com>
linux-os \(Dick Johnson\) writes:
>
[...]
> See, isn't rule-making fun? This whole 4k stack-
> thing is really dumb. Other operating systems
> use paged virtual memory for stacks, except
> for the interrupt stack. If Linux used paged
> virtual memory for stacks,
... then spin-locks couldn't be held across function calls.
> the pages would not
> have to be contiguous so dynamic stack allocation
> would practically never fail. But Linux doesn't
> use paged virtual memory for stacks. So, there
> needs to be some rule to control the amount
> of kernel stack allocated to each task when it
> executes a system call.
>
> This means, in the limit, that there are two
> possibilities:
>
> (1) Implement paged virtual memory for stack.
As an exercise: subscribe to NT kernel development mailing list, and see
the fun they have when page-in code trips over paged out kernel text
page. As a rule, even code cannot pageable without very involving and
fragile analysis. Not to say about stack.
Nikita.
next prev parent reply other threads:[~2005-12-20 22:54 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-18 22:14 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
[not found] ` <46578.10.10.10.28.1135094132.squirrel@linux1>
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 [this message]
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
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=17320.35736.89250.390950@gargle.gargle.HOWL \
--to=nikita@clusterfs.com \
--cc=bunk@stusta.de \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=lkml@rtr.ca \
--cc=mpm@selenic.com \
--cc=nel@vger.kernel.org \
--cc=snitzer@gmail.com \
/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®