Re: CpuSet on PAGG (Re: PAGG in Open Source projects?)

Guillaume Thouvenin <[email protected]>
Newsgroups gmane.linux.process-aggregates,gmane.linux.lse
Message-ID <[email protected]>
On Mon, 2005-01-31 at 18:39 +0900, Kaigai Kohei wrote: 
> For example, we must append individually cpuset_fork() for CpuSet,
> pagg_attach() for PAGG(CSA+Job), ckrm_cb_fork() for CKRM in kernel/fork.c
> when we try to use those advanced features.
> In this case, we need to patch into three points in kernel/fork.c.
> But if we have a common purpose hook in kernel/fork.c, those advanced
> features does not need to modify kernel/fork.c directly.
> They have only to register their own event handler for the fork-hook.

Thus in this case, the interesting aspect of PAGG is not the "container"
aspect but it's the "hook manager" aspect, right? 

PAGG has only a callback for "exec" and not for "fork". So, if you want
to use PAGG has a common hook in "fork" for several applications, we
need to add new hook (like pagg_fork in kernel/fork.c:do_fork()). 

Is it be possible to split PAGG into two pieces: 
    1. The container manager part 
    2. The hook manager part

Thanks,
Guillaume
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.