Re: [RFC] How to handle the rules engine for cgroups
From: Paul Menage
Date: Thu Jul 10 2008 - 12:52:22 EST
On Thu, Jul 10, 2008 at 7:30 AM, Vivek Goyal <vgoyal@xxxxxxxxxx> wrote:
>
> Well, that would mean first wrappers need to be created around all the
> applications which needs to be controlled. Then wrapper needs to
> synchronize with the classification daemon
I was suggesting that you wouldn't need a classification daemon in
this case. The logic of which cgroup to enter would be in the
script/command invoked by the wrapper.
>> - grid jobs, which are moved into the appropriate cgroup (actually,
>> currently cpuset) by the grid daemon when it starts the job
>
> So grid daemon probably first forks off, determines the right cpuset
> move the job there and then do exec?
Pretty much, yes. Most jobs have their own cpuset that's created for
them dynamically when the job starts on the machine.
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/