[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080219231726.4bd97520.pj@sgi.com>
Date: Tue, 19 Feb 2008 23:17:26 -0600
From: Paul Jackson <pj@....com>
To: "Paul Menage" <menage@...gle.com>
Cc: lizf@...fujitsu.com, balbir@...ux.vnet.ibm.com, balbir@...ibm.com,
xemul@...nvz.org, kamezawa.hiroyu@...fujitsu.com,
vatsa@...ux.vnet.ibm.com, akpm@...ux-foundation.org,
containers@...ts.linux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC][PATCH 1/7] CGroup API: Add cgroup.api control file
Paul M wrote:
> I guess it's not essential, I just figured that if we had that
> information, it made sense to make it available to userspace. I guess
> I'm happy with dropping the actual exposed cgroup.api file for now as
> long as we can work towards reducing the number of control files that
> just return strings, and make use of the structured output such as
> read_uint() miore.
I could certainly go along with that ... reducing the proportion of
control files returning untyped strings.
My sense of kernel-user API's is that usually the less said the better.
Identify the essential information that one side requires from the
other via a runtime API, and pass only that. API's represent a
lifetime commitment, so the less promised the better.
Perhaps my primary concern with these *.api files was that I did not
understand who or what the critical use or user was; who found this
essential, not just nice to have.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@....com> 1.940.382.4214
--
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