From: Li Zefan <lizf@cn.fujitsu.com>
To: Tejun Heo <tj@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Lennart Poettering <mzxreary@0pointer.de>,
Kay Sievers <kay.sievers@vrfy.org>,
Hugh Dickins <hughd@google.com>,
LKML <linux-kernel@vger.kernel.org>,
Cgroups <cgroups@vger.kernel.org>, Eric Paris <eparis@redhat.com>
Subject: [PATCH v2 0/3] cgroup: add xattr support
Date: Thu, 01 Mar 2012 14:16:57 +0800 [thread overview]
Message-ID: <4F4F1459.4080300@cn.fujitsu.com> (raw)
This can be used to attach metadata to a cgroup, which is required
by systemd.
As lazy as I am, here just quoted from Lennart for the detailed use
cases:
>> What would the use case be for this?
>
> Attaching meta information to services, in an easily discoverable
> way. For example, in systemd we create one cgroup for each service, and
> could then store data like the main pid of the specific service as an
> xattr on the cgroup itself. That way we'd have almost all service state
> in the cgroupfs, which would make it possible to terminate systemd and
> later restart it without losing any state information. But there's more:
> for example, some very peculiar services cannot be terminated on
> shutdown (i.e. fakeraid DM stuff) and it would be really nice if the
> services in question could just mark that on their cgroup, by setting an
> xattr. On the more desktopy side of things there are other
> possibilities: for example there are plans defining what an application
> is along the lines of a cgroup (i.e. an app being a collection of
> processes). With xattrs one could then attach an icon or human readable
> program name on the cgroup.
>
> The key idea is that this would allow attaching runtime meta information
> to cgroups and everything they model (services, apps, vms), that doesn't
> need any complex userspace infrastructure, has good access control
> (i.e. because the file system enforces that anyway, and there's the
> "trusted." xattr namespace), notifications (inotify), and can easily be
> shared among applications.
>
> Lennart
Changelog v1->v2:
- add kmem_xattr APIs
- use these new APIs in both tmpfs and cgroup
Early discussions can be found in this thread:
https://lkml.org/lkml/2012/1/16/51
Note: this patchset is based on Tejun's cgroup.git/for-next
--
fs/xattr.c | 167 +++++++++++++++++++++++++++++++++++++++++
include/linux/cgroup.h | 18 +++-
include/linux/shmem_fs.h | 3 +-
include/linux/xattr.h | 23 ++++++
init/Kconfig | 12 +++
kernel/cgroup.c | 184 ++++++++++++++++++++++++++++++++++++----------
mm/shmem.c | 151 +++-----------------------------------
7 files changed, 371 insertions(+), 187 deletions(-)
next reply other threads:[~2012-03-01 6:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 6:16 Li Zefan [this message]
2012-03-01 6:17 ` [PATCH v2 1/3] xattr: extract kmem_xattr code from tmpfs Li Zefan
2012-03-01 12:42 ` Hillf Danton
2012-03-02 5:23 ` Li Zefan
2012-03-01 6:17 ` [PATCH v2 3/3] cgroup: add xattr support Li Zefan
2012-03-01 6:17 ` [PATCH v2 2/3] cgroup: revise how we re-populate root directory Li Zefan
2012-03-01 12:48 ` Hillf Danton
2012-03-02 5:49 ` Li Zefan
2012-03-04 18:05 ` [PATCH v2 0/3] cgroup: add xattr support Tejun Heo
2012-03-06 21:37 ` Hugh Dickins
2012-03-08 9:03 ` Li Zefan
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=4F4F1459.4080300@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=eparis@redhat.com \
--cc=hughd@google.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mzxreary@0pointer.de \
--cc=tj@kernel.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