2.4.20, .text.lock.swap cpu usage? (ibm x440) [rescued]

Quoted 5 lines · William Lee Irwin III

Quoted 5 lines

IMHO multiprogramming is as valid a use for memory as any other. Or even otherwise, it's not something I care to get in design debates about, it's just how the things are used.

Quoted 7 lines · Brian Tinsley

I agree with the philosophy in general, but if I sit down to write a threaded application for Linux on IA-32 and wind up with a design that uses 800+ threads in any instance (other than a bug, which was our case), it's time to give up the day job and start riding on the back of the garbage truck ;)

I could care less what userspace does: mechanism, not policy. Userspace wants, and I give if I can, just as the kernel does with system calls.

800 threads isn't even a high thread count anyway, the 2.5.x testing was with a peak thread count of 100,000. 800 threads, even with an 8KB stack, is no more than 6.4MB of lowmem for stacks and so shouldn't stress the system unless many instances of it are run.

I suspect your issue is elsewhere. I'll submit accounting patches for Marcelo's and/or Andrea's trees so you can find out what's actually going on.

Quoted 6 lines

In all honesty, I would enjoy nothing more than contributing to kernel
development. Unfortunately it's a bit out of my scope right now (but not forever). If I only believed aliens seeded our gene pool with clones, I could hook up with those folks that claim to have cloned a human and get one of me made! ;)

I don't know what to tell you here. I'm lucky that this is my day job and that I can contribute so much. However, there are plenty who contribute major changes (many even more important than my own) without any such sponsorship. Perhaps emulating them would satisfy your wish.