Adrian Bunk wrote:Heck, maybe you should make it 2k by default in all -rc kernels; that way when people run -final with the 4k it'll be 100% bulletproof, right? 'cause all those piggy drivers that blow a 2k stack will finally have to get fixed? Or leave it at 2k and find a way to share pages for stacks, think how much memory you could save and how many java threads you could run! 4K just happens to be the page size; other than that it's really just some random/magic number picked, and now dictated that if you (and everyting around you) doesn't fit, you're broken. That bugs me. -Eric (yes, I know there are advantages to only allocating a single page for a new thread, but from an "all callchains after that must fit in that space" perspective, it's just a randomly picked number) --
| Linus Torvalds | Linux 2.6.27-rc8 |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Linus Torvalds | Linux 2.6.20-rc6 |
| Mike Snitzer | Re: Distributed storage. |
git: | |
| Gerrit Renker | [PATCH 03/37] dccp: List management for new feature negotiation |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Herbert Xu | Re: Kernel oops with 2.6.26, padlock and ipsec: probably problem with fpu state ch... |
