From: menage@google.com
To: kamezawa.hiroyu@jp.fujitsu.com, yamamoto@valinux.co.jp,
akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
balbir@in.ibm.com, xemul@openvz.org
Subject: [PATCH 0/2] cgroup map files: Add a key/value map file type to cgroups
Date: Thu, 21 Feb 2008 13:28:54 -0800 [thread overview]
Message-ID: <20080221212854.408662000@menage.corp.google.com> (raw)
[ Updated from the previous version to remove the colon from the map output ]
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 that needs to be parsed programmatically
- less boilerplate required in cgroup subsystems
- simplifies transition to a future efficient cgroups binary API
Signed-off-by: Paul Menage <menage@google.com>
--
WARNING: multiple messages have this Message-ID (diff)
From: menage@google.com
To: kamezawa.hiroyu@jp.fujitsu.com, yamamoto@valinux.co.jp,
akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
balbir@in.ibm.com, xemul@openvz.org
Subject: [PATCH 0/2] cgroup map files: Add a key/value map file type to cgroups
Date: Thu, 21 Feb 2008 13:28:54 -0800 [thread overview]
Message-ID: <20080221212854.408662000@menage.corp.google.com> (raw)
[ Updated from the previous version to remove the colon from the map output ]
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 that needs to be parsed programmatically
- 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-21 21:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 21:28 menage [this message]
2008-02-21 21:28 ` [PATCH 0/2] cgroup map files: Add a key/value map file type to cgroups menage
2008-02-21 21:28 ` [PATCH 1/2] cgroup map files: Add cgroup map data type menage
2008-02-21 21:28 ` menage
2008-02-22 3:51 ` YAMAMOTO Takashi
2008-02-22 3:51 ` YAMAMOTO Takashi
2008-02-23 8:04 ` Andrew Morton
2008-02-23 8:04 ` Andrew Morton
2008-02-23 15:22 ` Paul Menage
2008-02-23 15:22 ` Paul Menage
2008-02-21 21:28 ` [PATCH 2/2] cgroup map files: Use cgroup map for memcontrol stats file menage
2008-02-21 21:28 ` menage
2008-02-23 8:04 ` Andrew Morton
2008-02-23 8:04 ` Andrew Morton
2008-02-23 8:04 ` [PATCH 0/2] cgroup map files: Add a key/value map file type to cgroups Andrew Morton
2008-02-23 8:04 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2008-02-20 5:15 menage
2008-02-20 5:15 ` menage
2008-02-20 5:48 ` YAMAMOTO Takashi
2008-02-20 5:48 ` YAMAMOTO Takashi
2008-02-20 6:02 ` Paul Menage
2008-02-20 6:02 ` Paul Menage
2008-02-20 6:14 ` YAMAMOTO Takashi
2008-02-20 6:14 ` YAMAMOTO Takashi
2008-02-20 6:25 ` Paul Menage
2008-02-20 6:25 ` 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=20080221212854.408662000@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.