On Fri, Aug 04, 2006 at 06:20:04PM +0400, Kirill Korotaev wrote:
> For example:
> 1. Should task-group be changeable after set/inherited once?
> Are you planning to recalculate resources on group change?
> e.g. shared memory or used kernel memory is hard to recalculate.
I think this is a nice feature, although not on the top priority list.
> 2. should task-group resource container manage all the resources as a whole?
> e.g. in OpenVZ tasks can belong to different CPU and UBC containers.
> It is more flexible and e.g. we used to put some vital kernel threads
> to a separate CPU group to decrease delays in service.
We already support different resource groups for the very limit rlimit
interface. If we can keep the interface clean doing separate resource
groups is fine.
> 3. I also don't understand why normal binary interface like system call is
> not used.
> We have set_uid, sys_setrlimit and it works pretty good, does it?
Yes. If you can design a syscall interface that is as clean as the two
mentioned above a syscall interface is the best way to go forward.
> 4. do we want hierarchical grouping?
Not at all. It just causes a lot of pain an complexity for no real world
benefits.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
