Re: [2.6 patch] i386: always use 4k stacks

[Adrian Bunk]

On Tue, Nov 15, 2005 at 11:46:30AM -0500, Giridhar Pemmasani wrote:
> Arjan van de Ven wrote:
> 
> > the same as 2.4 effectively. 2.6 also has (and I wish it becomes "had"
> > soon) an option to get 6Kb effective stack space instead. This is an
> > increase of 2Kb compared to 2.4.
> 
> It has been asked couple of times before in this context and no one cared to
> answer:
> 
> Using 4k stacks may have advantages, but what compelling reasons are there
> to drop the choice of 4k/8k stacks? You can make 4k stacks default, but why
> throw away the option of 8k stacks, especially since the impact of this
> option on the kernel implementation is very little?


One important point is to get remaining problems reported:

All the known issues in e.g. xfs, dm or reiser4 should have been 
addressed.

But how many issues have never been reported because people noticed that 
disabling CONFIG_4KSTACKS fixed the problem for them and therefore 
didn't report it?

I experienced something similar with my patch to schedule OSS drivers 
with ALSA replacements for removal - when someone reported he needed an 
OSS driver for $reason I asked him for bug numbers in the ALSA bug 
tracking system - and the highest number were 4 new bugs against one 
ALSA driver.

Unconditionally enabling 4k stacks is the only way to achieve this.


And the fact that it might force people to help with the development or 
at least use open source drivers for their hardware instead of 
binary-only Windows drivers isn't exactly a disadvantage for the 
development of Linux.


> Giri

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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/