Adrian Bunk wrote:There are always problems. You can always come up with something that will crash in 4k, IMHO. Rather than foisting this upon everyone, I'd rather see work put into making stack size a boot parameter or something, so that people can choose what's appropriate for their workload (or their IO stack, if you prefer). -Eric --
| 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 |
