[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46A9ECD5.3050801@sandeen.net>
Date: Fri, 27 Jul 2007 08:02:13 -0500
From: Eric Sandeen <sandeen@...deen.net>
To: Alan Cox <alan@...rguk.ukuu.org.uk>
CC: Andrea Arcangeli <andrea@...e.de>, Matt Mackall <mpm@...enic.com>,
Rene Herman <rene.herman@...il.com>,
Ray Lee <ray-lk@...rabbit.org>, Bodo Eggert <7eggert@....de>,
Jeremy Fitzhardinge <jeremy@...p.org>,
Jesper Juhl <jesper.juhl@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
William Lee Irwin III <wli@...omorphy.com>,
David Chinner <dgc@....com>,
Arjan van de Ven <arjan@...radead.org>
Subject: Re: [PATCH][RFC] 4K stacks default, not a debug thing any more...?
Alan Cox wrote:
>> I don't think they're necessarily bugs. IMHO the WARN_ON is better off
>> at 7k level like it is today with the current STACK_WARN. 4k for a
>> stack for common code really is small. I doubt you're going to find
>
> You want the limit settable. On a production system you want to set the
> limit to somewhere appropriate for the stack size used. When debugging
> (eg to remove any last few bogus users of 8K stack space) you want to be
> able to set it to just under 4K
Hm, when cramming cxfs into 4k at sgi, I had a patch that did just that
for debugging (warn about encroaching on 4k without actually tipping
over, with a settable threshold...)
Maybe I should resurrect it & send it out...
(FWIW I think I recall that the warning itself sometimes tipped the
scales enough on 4k stacks to bring the box down)
-eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists