From: Tejun Heo <tj@kernel.org>
To: Hugh Dickins <hughd@google.com>
Cc: Aristeu Rozanski <aris@redhat.com>,
linux-kernel@vger.kernel.org, Li Zefan <lizefan@huawei.com>,
Hillf Danton <dhillf@gmail.com>
Subject: Re: [PATCH v3 0/3] cgroup: add xattr support
Date: Fri, 20 Jul 2012 11:10:41 -0700 [thread overview]
Message-ID: <20120720181041.GK32763@google.com> (raw)
In-Reply-To: <alpine.LSU.2.00.1207181736020.3323@eggly.anvils>
Hello, Hugh.
On Wed, Jul 18, 2012 at 06:11:32PM -0700, Hugh Dickins wrote:
> So systemd is already doing it as I suggested, but finds that awkward in
> some respects, and wants more help from the kernel in synchronization.
Yeah, pretty much.
> Stuffing an unbounded amount of data into cgroupfs xattrs doesn't sound
> the right way to go.
>
> I wonder if it could be turned completely on its head, and the cgroupfs
> parts be represented in xattrs on a tmpfs hierarchy? The data contents of
> the tmpfs files being entirely up to userspace i.e. systemd in ths case.
Probably not. We can't change the userland-visible cgroup interface
and the cgroup filesystem is unfortunately ***DEEPLY*** (yes, it's
crazily deep) entangled with cgroup core implementation. :(
Longer term goal is to factor out sysfs from kobject / driver model
and share it between cgroup and sysfs. I think it's generally not a
bad idea to support xattr on pseudo filesystems if it isn't too hairy
to support. Low level system management software should be able to
make pretty good use of them.
Thanks.
--
tejun
prev parent reply other threads:[~2012-07-20 18:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-02 14:29 [PATCH v3 0/3] cgroup: add xattr support Aristeu Rozanski
2012-07-02 14:29 ` [PATCH v3 1/3] xattr: extract simple_xattr code from tmpfs Aristeu Rozanski
2012-07-03 16:53 ` [PATCH v4 " Aristeu Rozanski
2012-07-02 14:29 ` [PATCH v3 2/3] cgroup: revise how we re-populate root directory Aristeu Rozanski
2012-07-09 17:17 ` Tejun Heo
2012-07-09 17:22 ` Tejun Heo
2012-07-09 17:28 ` Tejun Heo
2012-07-10 19:27 ` Aristeu Rozanski
2012-07-17 13:56 ` Aristeu Rozanski
2012-07-17 18:38 ` Tejun Heo
2012-07-17 21:29 ` Aristeu Rozanski
2012-07-17 21:40 ` Tejun Heo
2012-07-18 14:16 ` Aristeu Rozanski
2012-07-18 16:32 ` Tejun Heo
2012-07-02 14:29 ` [PATCH v3 3/3] cgroup: add xattr support Aristeu Rozanski
2012-07-17 20:41 ` [PATCH v3 0/3] " Tejun Heo
2012-07-18 20:02 ` Hugh Dickins
2012-07-18 22:10 ` Tejun Heo
2012-07-19 1:11 ` Hugh Dickins
2012-07-20 17:59 ` Aristeu Rozanski
2012-07-20 18:04 ` Tejun Heo
2012-08-07 15:22 ` Aristeu Rozanski
2012-07-22 19:12 ` Hugh Dickins
2012-07-23 18:12 ` Aristeu Rozanski
2012-07-24 18:28 ` Tejun Heo
2012-07-24 21:44 ` Aristeu Rozanski
2012-07-20 18:10 ` Tejun Heo [this message]
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=20120720181041.GK32763@google.com \
--to=tj@kernel.org \
--cc=aris@redhat.com \
--cc=dhillf@gmail.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
/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;
as well as URLs for NNTP newsgroup(s).