Re: Linux scheduler (scheduling) questions vs threads

[Paul Rolland]

> Chris Siebenmann wrote:
> > You write:
> > | Ingo Molnar wrote:
> > [...]
> > | > so the normal Linux scheduling policy applies to 
> 'threads' too. [...]
> > [...]
> > | On a multi-user machine this may result in undesirable 
> behaviour, since 
> > | each thread seems to compete for resources and the 
> machine may get VERY 
> > | slow if someone deos something anti-social.
> > 
> >  This is nothing unique to threads; the same problem appears if a
> > program (or a user) uses a bunch of CPU-eating processes. I imagine
> > that any real solution will have to be per-user 'beancounting' and
> > limits, which have yet to make it into the Linux kernel.
> 

What about ulimit'ing users ?

bash-2.05$ ulimit -a
core file size (blocks)     0
data seg size (kbytes)      unlimited
file size (blocks)          unlimited
max locked memory (kbytes)  unlimited
max memory size (kbytes)    unlimited
open files                  1024
pipe size (512 bytes)       8
stack size (kbytes)         8192
cpu time (seconds)          unlimited
max user processes          4087
virtual memory (kbytes)     unlimited

Regards,
Paul

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/