[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6599ad830704100845o23d8fb1dn17450ed48c51ad95@mail.gmail.com>
Date: Tue, 10 Apr 2007 08:45:13 -0700
From: "Paul Menage" <menage@...gle.com>
To: vatsa@...ibm.com
Cc: sekharan@...ibm.com, ckrm-tech@...ts.sourceforge.net,
linux-kernel@...r.kernel.org, xemul@...ru, dev@...ru,
rohitseth@...gle.com, ebiederm@...ssion.com, mbligh@...gle.com,
containers@...ts.osdl.org, serue@...ibm.com,
akpm@...ux-foundation.org, devel@...nvz.org
Subject: Re: [ckrm-tech] [PATCH 3/7] Containers (V8): Add generic multi-subsystem API to containers
On 4/10/07, Srivatsa Vaddagiri <vatsa@...ibm.com> wrote:
>
> Is the first argument into all the callbacks, struct container_subsys *ss,
> necessary?
I added it to support library-like abstractions - where one subsystem
can have its container callbacks and file accesses all handled by a
library which converts to a higher-level abstraction. See the
res_group example patch to see how it can be used.
>
> > +struct container_subsys cpuset_subsys = {
> > + .name = "cpuset",
> > + .create = cpuset_create,
> > + .destroy = cpuset_destroy,
> > + .can_attach = cpuset_can_attach,
> > + .attach = cpuset_attach,
> > + .populate = cpuset_populate,
> > + .subsys_id = cpuset_subsys_id,
> > + .early_init = 1,
> > +};
>
> We seem to be missing a register call here as well ..
Registration is done at compile time in the new patch set, thanks to
the static declaration of subsystems and subsystem ids.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists