public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Sean" <seanlkml@sympatico.ca>
To: "Mike Snitzer" <snitzer@gmail.com>
Cc: "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: Tue, 20 Dec 2005 10:55:32 -0500 (EST)	[thread overview]
Message-ID: <BAYC1-PASMTP01F075F44E45AA32F0DF85AE3E0@CEZ.ICE> (raw)
Message-ID: <46578.10.10.10.28.1135094132.squirrel@linux1> (raw)
In-Reply-To: <170fa0d20512200637l169654c9vbe38c9931c23dfb1@mail.gmail.com>

On Tue, December 20, 2005 9:37 am, Mike Snitzer said:

> Given this last statement, why is it that Matt Mackall's suggestion in
> the "Light-weight dynamically extended stacks" thread didn't get any
> _real_ discussion from the big 4K stack advocates?  For all intents
> and purposes, Matt was dismissed with the same Bunk: "Ever since
> neilb's patch there are 0 bugs.. blah blah".  4K, 8K (aka "6 kB")
> aside; having more stack safety in the Linux kernel is a "good thing"
> no?  Aren't dynamic stacks a viable means to imposing 4K (but doing so
> with real safety)?

The so called 4K stack patch does add more stack safety.  Avoiding the
possibility of allocation failures due to memory fragmentation.  Besides,
the patch is really misnamed; it should have been called the split-stack
(ie. 4K + 4K).   Since nobody can show any area in the mainline code where
the split stack scheme introduces a problem the old setup should be
removed as it is no longer needed by the mainline code.

I for one hope those silly bastards using ndiswrapper fix up that code to
work with the new kernel so that we can stop hearing all these wannabe
complaints against this progress.

Sean


  parent reply	other threads:[~2005-12-20 15:56 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
     [not found]       ` <46578.10.10.10.28.1135094132.squirrel@linux1>
2005-12-20 15:55         ` Sean [this message]
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

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=BAYC1-PASMTP01F075F44E45AA32F0DF85AE3E0@CEZ.ICE \
    --to=seanlkml@sympatico.ca \
    --cc=bunk@stusta.de \
    --cc=jamagallon@able.es \
    --cc=linux-kernel@vger.kernel.org \
    --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