On Sun, Apr 20, 2008 at 10:36:11AM +0100, Alan Cox wrote: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. 6k is known to work, and there aren't many problems known with 4k. 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. 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 --
| debian developer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 014/196] kobject: remove incorrect comment in kobject_rename |
| Vladislav Bolkhovitin | Re: Integration of SCST in the mainstream Linux kernel |
| Stephen Rothwell | Re: Announce: Linux-next (Or Andrew's dream :-)) |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | [GIT]: Networking |
| Radu Rendec | htb parallelism on multi-core platforms |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
