[lkml]   [2004]   [May]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 4k stacks in 2.6
On Wed, 26 May 2004 14:53:00 +0200, Arjan van de Ven wrote:
> On Wed, May 26, 2004 at 02:50:14PM +0200, Jörn Engel wrote:
> >
> > Experience indicates that for whatever reason, big stack consumers for
> > all three contexts never hit at the same time. Big stack consumers
> > for one context happen too often, though. "Too often" may be quite
> > rare, but considering the result of a stack overflow, even "quite
> > rare" is too much. "Never" is the only acceptable target.
> Actually it's not mever in 2.4. It does get here there by our customers once
> in a while. Esp with several NICs hitting an irq on the same CPU (eg the irq
> context goes over it's 2Kb limit)
> > done, a stack overflow will merely cause a kernel panic. Until then,
> > I am just as conservative as Andreas.
> actually the 4k stacks approach gives MORE breathing room for the problem
> cases that are getting hit by our customers...

For the cases you described, yes. For some others like nvidia, no.
Not sure if we want to make things worse for some users in order to
improve things for others (better paying ones?). I want the seperate
interrupt stacks, sure. I'm just not comfy with 4k per process yet.

But I'll shut up now and see if I can generate better data over the
weekend. -test11 still had fun stuff like 3k stack consumption over
some code paths in a pretty minimal kernel. Wonder what 2.6.6 will do
with allyesconfig. ;)


He who knows that enough is enough will always have enough.
-- Lao Tsu
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:03    [W:0.289 / U:6.404 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site