[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080420160327.GE1899@cs181133002.pp.htv.fi>
Date: Sun, 20 Apr 2008 19:03:27 +0300
From: Adrian Bunk <bunk@...nel.org>
To: Arjan van de Ven <arjan@...radead.org>
Cc: Eric Sandeen <sandeen@...deen.net>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Shawn Bohrer <shawn.bohrer@...il.com>,
Ingo Molnar <mingo@...e.hu>,
Andrew Morton <akpm@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: x86: 4kstacks default
On Sun, Apr 20, 2008 at 08:41:27AM -0700, Arjan van de Ven wrote:
>...
> yes. Adrian is waay off in the weeds on this one. Nobody but him is suggesting to remove
> 8Kb stacks. I think everyone else agrees that having both options is valuable; and there
> are better ways to find+fix stack bloat than removing this config option.
I'm not arguing for removing the option immediately, but long-term we
shouldn't need it.
This comes from my experience of removing obsolete drivers for hardware
for which also a more recent driver exists:
As long as there is some workaround (e.g. using an older driver or
8k stacks) the workaround will be used instead of the getting proper
bug reports and fixes.
As far as I know all problems that are known with 4k stacks are some
nested things with XFS in the trace.
If this class of issues would get fixed one day, why would it be
valuable to also offer 8k stacks long-term? Especially weigthed
against the fact that with only 4k stacks we will have more people
running into stack problems in -rc kernels if any new ones pop up,
resulting in getting more such problems fixed during -rc.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
--
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