From: menage@google.com
To: kamezawa.hiroyu@jp.fujitsu.com, akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
balbir@in.ibm.com, xemul@openvz.org, yamamoto@valinux.co.jp
Subject: [PATCH 0/2] cgroup map files: Add a key/value map file type to cgroups
Date: Tue, 19 Feb 2008 21:15:44 -0800 [thread overview]
Message-ID: <20080220051544.018684000@menage.corp.google.com> (raw)
These patches add a new cgroup control file output type - a map from
strings to u64 values - and make use of it for the memory controller
"stat" file.
It is intended for use when the subsystem wants to return a collection
of values that are related in some way, for which a separate control
file for each value would make the reporting unwieldy.
The advantages of this are:
- more standardized output from control files that report
similarly-structured data
- less boilerplate required in cgroup subsystems
- simplifies transition to a future efficient cgroups binary API
Signed-off-by: Paul Menage <menage@google.com>
--
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2008-02-20 5:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-20 5:15 menage [this message]
2008-02-20 5:15 ` [PATCH 1/2] cgroup map files: Add cgroup map data type menage
2008-02-20 5:15 ` [PATCH 2/2] cgroup map files: Use cgroup map for memcontrol stats file menage
2008-02-20 5:48 ` [PATCH 0/2] cgroup map files: Add a key/value map file type to cgroups YAMAMOTO Takashi
2008-02-20 6:02 ` Paul Menage
2008-02-20 6:14 ` YAMAMOTO Takashi
2008-02-20 6:25 ` Paul Menage
2008-02-21 21:28 menage
2008-02-23 8:04 ` Andrew Morton
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=20080220051544.018684000@menage.corp.google.com \
--to=menage@google.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@in.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=xemul@openvz.org \
--cc=yamamoto@valinux.co.jp \
/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