[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20061030062944.c5f73661.pj@sgi.com>
Date: Mon, 30 Oct 2006 06:29:44 -0800
From: Paul Jackson <pj@....com>
To: Pavel Emelianov <xemul@...nvz.org>
Cc: vatsa@...ibm.com, dev@...nvz.org, sekharan@...ibm.com,
ckrm-tech@...ts.sourceforge.net, balbir@...ibm.com,
haveblue@...ibm.com, linux-kernel@...r.kernel.org,
matthltc@...ibm.com, dipankar@...ibm.com, rohitseth@...gle.com,
menage@...gle.com
Subject: Re: [ckrm-tech] [RFC] Resource Management - Infrastructure choices
Pavel wrote:
> My point is that a good infrastrucure doesn't care wether
> or not beancounter (group controller) has a parent.
I am far more interested in the API, including the shape
of the data model, that we present to the user across the
kernel-user boundary.
Getting one, good, stable API for the long haul is worth alot.
Whether or not some substantial semantic change in this, such
as going from a flat to a tree shape, can be done in a single
line of kernel code, or a thousand lines, is less important.
What is the right long term kernel-user API and data model?
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@....com> 1.925.600.0401
-
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