On 13/07/07, Jeremy Fitzhardinge <jeremy@goop.org> wrote:Yes and no. If that will get things moving in the direction of getting rid of the stack size as a config option, then I'm all for it. But on the other hand it is my personal opinion that this is an area where we should just make up our minds as to whether we want 4K or 8K stacks and whether we want interrupt stacks or not, and then not have it configurable at all. I believe the goal is 4K stacks + interrupt stacks, so let's just aim for that and get rid of the configurability of the damn thing - make a choice, make it work, make it be that that's what we use and rid ourselves of the alternatives... -- Jesper Juhl <jesper.juhl@gmail.com> Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html Plain text mails only, please http://www.expita.com/nomime.html -
| Eric W. Biederman | [PATCH 02/10] sysfs: Support for preventing unmounts. |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Bart Van Assche | Integration of SCST in the mainstream Linux kernel |
| david | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
git: | |
| Antonio Almeida | HTB accuracy for high speed |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 26/37] dccp: Integration of dynamic feature activation - part 1 (socket set... |
| David Miller | [GIT]: Networking |
