On Sun, Apr 20, 2008 at 12:02:50PM +0100, Alan Cox wrote:
quoted text
> > The code in the kernel that gets the fewest coverage at all are our 
> > error paths, and some vendor might try 4k stacks, validate it works in 
> > all use cases - and then it will blow up in some error condition he 
> > didn't test.
> 
> Which you won't fix by changing the x86 defaults.

Stuff like nfsd, xfs and raid is covered by the x86 defaults.

It's not a 100% coverage, but quite much.

quoted text
> More of a problem in
> embedded small devices is the 8K allocation failing in the first place -
> plus 4K x 80 processes == lots.
> 
> > And from a QA point of view the only way of getting 4k thoroughly tested 
> > by users, and well also tested in -rc kernels for catching regressions 
> > before they get into stable kernels, is if we get 4k stacks enabled 
> > unconditionally on i386.
> 
> At which point some distros will simply patch it back no doubt.

Red Hat seems to get usable kernels with 4k for some years?

If we get whatever is still missing for 4k working once and then the 
coverage of all i386 -rc testers for noticing new issues immediately
there should be no stability reason for distros to patch it back in.

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

--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/