All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Li Zefan <lizf@cn.fujitsu.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Cgroups <cgroups@vger.kernel.org>,
	Lennart Poettering <mzxreary@0pointer.de>
Subject: Re: [PATCH 2/2] cgroup: add xattr support
Date: Wed, 18 Jan 2012 13:36:38 -0800	[thread overview]
Message-ID: <20120118213638.GA21533@google.com> (raw)
In-Reply-To: <CAPXgP13fT3V4L0x6uj9ZdAOw25BgQtEpa8QzLB-_c_Yn+9kO2Q@mail.gmail.com>

Hello,

On Wed, Jan 18, 2012 at 10:28:42PM +0100, Kay Sievers wrote:
> The idea with the cgroup fs xattrs was to be able to attach some
> general useful attributes to the 'service container' itself, instead
> of keeping them in the memory of the managing process or store them on
> disk which can get out-of-sync much easier.

Hmmm.... I can see the attraction but there really is nothing which
binds that information to cgroup.  The same information might as well
live in /proc/PID/userland_data or whatever.  It may be convenient now
but I'm pretty skeptical it's a good idea in the long run.

Given that cgroups themselves need to be explicitly created and
destroyed, maintaining a parallel tmpfs hierarchy for metadata, if
necessary, shouldn't be too bothersome, right?

Thanks.

-- 
tejun

WARNING: multiple messages have this Message-ID (diff)
From: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Kay Sievers <kay.sievers-tD+1rO4QERM@public.gmane.org>
Cc: Li Zefan <lizf-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>,
	LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Cgroups <cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Lennart Poettering
	<mzxreary-uLTowLwuiw4b1SvskN2V4Q@public.gmane.org>
Subject: Re: [PATCH 2/2] cgroup: add xattr support
Date: Wed, 18 Jan 2012 13:36:38 -0800	[thread overview]
Message-ID: <20120118213638.GA21533@google.com> (raw)
In-Reply-To: <CAPXgP13fT3V4L0x6uj9ZdAOw25BgQtEpa8QzLB-_c_Yn+9kO2Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Hello,

On Wed, Jan 18, 2012 at 10:28:42PM +0100, Kay Sievers wrote:
> The idea with the cgroup fs xattrs was to be able to attach some
> general useful attributes to the 'service container' itself, instead
> of keeping them in the memory of the managing process or store them on
> disk which can get out-of-sync much easier.

Hmmm.... I can see the attraction but there really is nothing which
binds that information to cgroup.  The same information might as well
live in /proc/PID/userland_data or whatever.  It may be convenient now
but I'm pretty skeptical it's a good idea in the long run.

Given that cgroups themselves need to be explicitly created and
destroyed, maintaining a parallel tmpfs hierarchy for metadata, if
necessary, shouldn't be too bothersome, right?

Thanks.

-- 
tejun

  reply	other threads:[~2012-01-18 21:36 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-16  8:06 [PATCH 1/2] cgroup: revise how we re-populate root directory Li Zefan
2012-01-16  8:06 ` Li Zefan
2012-01-16  8:07 ` [PATCH 2/2] cgroup: add xattr support Li Zefan
2012-01-16  8:07   ` Li Zefan
2012-01-17 17:53   ` Tejun Heo
2012-01-17 17:53     ` Tejun Heo
2012-01-18  8:27     ` Li Zefan
2012-01-18  8:27       ` Li Zefan
2012-01-18 17:47       ` Tejun Heo
2012-01-18 17:47         ` Tejun Heo
2012-01-19  1:49         ` Lennart Poettering
2012-01-18 21:28     ` Kay Sievers
2012-01-18 21:28       ` Kay Sievers
2012-01-18 21:36       ` Tejun Heo [this message]
2012-01-18 21:36         ` Tejun Heo
2012-01-19  1:47         ` Lennart Poettering
2012-01-19  2:20           ` Tejun Heo
2012-01-19  2:20             ` Tejun Heo
2012-01-19  2:40             ` Tejun Heo
2012-01-19  2:40               ` Tejun Heo
2012-01-21  3:02               ` Lennart Poettering
2012-01-21  3:02                 ` Lennart Poettering
2012-01-21  4:00                 ` Hugh Dickins
2012-01-21  4:00                   ` Hugh Dickins
2012-01-21  2:59             ` Lennart Poettering
2012-01-21  2:59               ` Lennart Poettering
2012-01-18  7:23 ` [PATCH 1/2] cgroup: revise how we re-populate root directory Sha
2012-01-18  7:23   ` Sha
2012-01-18  7:59   ` 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=20120118213638.GA21533@google.com \
    --to=tj@kernel.org \
    --cc=cgroups@vger.kernel.org \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=mzxreary@0pointer.de \
    /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.