Messages in this thread | | | Date | Wed, 7 May 2003 19:47:16 +0200 | From | Jörn Engel <> | Subject | Re: top stack (l)users for 2.5.69 |
| |
On Wed, 7 May 2003 10:38:25 -0700, William Lee Irwin III wrote: > On Wed, May 07, 2003 at 06:49:01PM +0200, J?rn Engel wrote: > > It also matters if people writing applications for embedded systems > > have a fetish for many threads. 1000 threads, each eating 8k memory > > for pure existance (no actual work done yet), do put some memory > > pressure on small machines. Yes, it would be possible to educate those > > people, but changing kernel code is more fun and less work. > > If they're embedded and UP they can probably get by on a userspace > threading library that only creates one kernel thread. > > It's highly unlikely anyone will get anywhere "fixing" this in the > kernel. The closest approximations to mitigating the pinned memory > overhead with UNIX-style kernel semantics are swappable stacks a la the > u area and M:N threading, neither of which are popular notions. If > you're trying the other approach I mentioned in this thread, good luck > ever getting it done and good luck ever surviving even a single merge. > > $ grep -nr schedule . | wc -l > 3773
Ah, now I see where the misunderstanding comes from. My bad. I would merely like to save NO_THREADS * 4k, not the full 8k. People here are migrating from Readtime OS's to Linux, partially and I wouldn't think about introducing hard priorities into the scheduler either. "This is plain impossible." is a very good argument for education. "This only works under certain conditions." is where people always demand more, sometimes rightfully, sometimes not.
Jörn
-- Measure. Don't tune for speed until you've measured, and even then don't unless one part of the code overwhelms the rest. -- Rob Pike - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |