From: Paul Jackson <pj@sgi.com>
To: "Paul Menage" <menage@google.com>
Cc: lizf@cn.fujitsu.com, balbir@linux.vnet.ibm.com,
balbir@in.ibm.com, xemul@openvz.org,
kamezawa.hiroyu@jp.fujitsu.com, vatsa@linux.vnet.ibm.com,
akpm@linux-foundation.org, containers@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH 1/7] CGroup API: Add cgroup.api control file
Date: Tue, 19 Feb 2008 23:17:26 -0600 [thread overview]
Message-ID: <20080219231726.4bd97520.pj@sgi.com> (raw)
In-Reply-To: <6599ad830802191851l66281e67rb49c766c2b1427c9@mail.gmail.com>
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@sgi.com> 1.940.382.4214
next prev parent reply other threads:[~2008-02-20 5:17 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 20:44 [RFC][PATCH 0/7] CGroup API: More structured API for CGroups control files Paul Menage
2008-02-15 20:44 ` [RFC][PATCH 1/7] CGroup API: Add cgroup.api control file Paul Menage
2008-02-16 10:07 ` Balbir Singh
2008-02-16 17:44 ` Paul Menage
2008-02-18 9:45 ` Li Zefan
2008-02-18 10:32 ` Balbir Singh
2008-02-19 21:57 ` Paul Jackson
2008-02-20 2:51 ` Paul Menage
2008-02-20 5:17 ` Paul Jackson [this message]
2008-02-20 5:23 ` Paul Menage
2008-02-20 2:51 ` Paul Menage
2008-02-15 20:44 ` [RFC][PATCH 2/7] CGroup API: Add cgroup map data type Paul Menage
2008-02-15 20:44 ` [RFC][PATCH 3/7] CGroup API: Use cgroup map for memcontrol stats file Paul Menage
2008-02-15 20:44 ` [RFC][PATCH 4/7] CGroup API: Add res_counter_read_uint() Paul Menage
2008-02-15 20:44 ` [RFC][PATCH 5/7] CGroup API: Use read_uint in memory controller Paul Menage
2008-02-15 20:44 ` [RFC][PATCH 6/7] CGroup API: Use descriptions for memory controller API files Paul Menage
2008-02-15 20:44 ` [RFC][PATCH 7/7] CGroup API: Update cpusets to use cgroup structured file API Paul Menage
2008-02-17 3:29 ` Paul Jackson
2008-02-17 17:18 ` Paul Menage
2008-02-17 17:28 ` Paul Jackson
2008-02-17 17:48 ` Paul Menage
2008-02-18 9:55 ` Li Zefan
[not found] ` <47B96805.7070002@linux.vnet.ibm.com>
2008-02-18 11:13 ` Balbir Singh
2008-02-18 11:52 ` Andreas Schwab
[not found] ` <47B971C6.4080807@linux.vnet.ibm.com>
2008-02-18 11:56 ` Balbir Singh
2008-02-16 4:21 ` [RFC][PATCH 0/7] CGroup API: More structured API for CGroups control files KAMEZAWA Hiroyuki
2008-02-16 9:31 ` Li Zefan
2008-02-16 17:40 ` Paul Menage
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080219231726.4bd97520.pj@sgi.com \
--to=pj@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@in.ibm.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=containers@lists.linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.com \
--cc=vatsa@linux.vnet.ibm.com \
--cc=xemul@openvz.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox