On Wednesday 10 October 2007 11:26, Christoph Lameter wrote: > On Tue, 9 Oct 2007, Nick Piggin wrote: > > > We already use 32k stacks on IA64. So the memory argument fail there. > > > > I'm talking about generic code. > > The stack size is set in arch code not in generic code.
Generic code must assume a 4K stack on 32-bit, in general (modulo huge cpumasks and such, I guess). > > > > The solution has until now always been to fix the problems so they > > > > don't use so much stack. Maybe a bigger stack is OK for you for 1024+ > > > > CPU systems, but I don't think you'd be able to make that assumption > > > > for most normal systems. > > > > > > Yes that is why I made the stack size configurable. > > > > Fine. I just don't see why you need this fallback. > > So you would be ok with submitting the configurable stacksize patches > separately without the fallback? Sure. It's already configurable on other architectures. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
