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: Wed, 18 Jul 2012 15:10:44 -0700 [thread overview]
Message-ID: <20120718221044.GJ24336@google.com> (raw)
In-Reply-To: <alpine.LSU.2.00.1207181237010.2160@eggly.anvils>
Hello, Hugh.
On Wed, Jul 18, 2012 at 01:02:03PM -0700, Hugh Dickins wrote:
> > I don't know. I
> > really hope it used anonymous page cache instead of kmem tho. Hugh,
> > would something like that be difficult?
>
> Yes, it would be difficult.
>
> You don't use the word "swappable", but I take that to be implicit
> when you say "anonymous ... instead of kmem": it might as well be
> kmem if it cannot be swapped.
Yeah, I just am not mm-savvy enough to be able to use the correct
term. :)
> So you're wondering whether to introduce a new category of swappable
> memory: not the original anon pages mapped into userspace, not shmem
> use of swappable pages, but xattrs in the cgroup filesystem?
But why do we need something completely new? Can't we hijack some
inodes used by tmpfs and use them for xattr storage? ie. Would it be
difficult to use tmpfs as backend storage for on-memory xattr? With
that, we would already have the mechanism and interface(!) for
limiting the size.
> Or am I misunderstanding, or looking at this from the wrong angle?
>
> If there's not a reasonable upper bound on what gets stored here
> (did I see the word "icon" earlier in the thread? which made me
> think people would be loading their photo albums into these xattrs),
> maybe the problem does need turning around.
>
> Let userspace manage a tmpfs hierarchy parallel to the cgroupfs one?
IIRC xattr for cgroupfs was suggested from systemd which currently is
using tmpfs to manage parallel hierarchy. It's reportedly cumbersome
to keep in sync and they would much prefer if they can store metadata
right inside cgroup. If we can have a shared implementation which
doesn't complicate each pseudo filesystem much, I think why not.
Thanks.
--
tejun
next prev parent reply other threads:[~2012-07-18 22: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 [this message]
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
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=20120718221044.GJ24336@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 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.