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 --
| David Miller | [GIT]: Networking |
| Linus Torvalds | Linux 2.6.26-rc4 |
| Fred . | Please add ZFS support (from GPL sources) |
| Greg KH | Linux 2.6.25.10 |
git: | |
| Alexander Gladysh | [Q] Encrypted GIT? |
| Kevin Leung | Edit log message after commit |
| Pietro Mascagni | GIT vs Other: Need argument |
| Michael Hendricks | removing content from git history |
| GVG GVG | ssh_exchange_identification: Connection closed by remote host |
| Edwin Eyan Moragas | poll(2) vs kqueue(2) performance |
| Didier Wiroth | win32-codecs, avi and amd64 question |
| Daniel Ouellet | identifying sparse files and get ride of them trick available? |
| Daniel Brewer | Re: fsync performance hit on 1.6.1 |
| Hubert Feyrer | Compressed vnd handling tested successfully |
| Elad Efrat | Integrating securelevel and kauth(9) |
| YAMAMOTO Takashi | yamt-km branch |
