From: "Daniel Xu" <dxu@dxuuu.xyz>
To: "Shakeel Butt" <shakeelb@google.com>
Cc: "Cgroups" <cgroups@vger.kernel.org>, "Tejun Heo" <tj@kernel.org>,
"Li Zefan" <lizefan@huawei.com>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"LKML" <linux-kernel@vger.kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Kernel Team" <kernel-team@fb.com>
Subject: Re: [PATCH 0/2] Support user xattrs in cgroupfs
Date: Tue, 03 Mar 2020 11:20:32 -0800 [thread overview]
Message-ID: <C11FZ3TMTIH1.2KP5NIUPPQBWT@dlxu-fedora-R90QNFJV> (raw)
In-Reply-To: <CALvZod5m3otRRqcLBebbgiZbhoYWAMbMg+ESkacJuj64OP =H4Q@mail.gmail.com>
On Tue Mar 3, 2020 at 8:50 AM, Shakeel Butt wrote:
> Hi Daniel,
>
>
> On Mon, Mar 2, 2020 at 5:42 PM Daniel Xu <dxu@dxuuu.xyz> wrote:
> >
> > User extended attributes are useful as metadata storage for kernfs
> > consumers like cgroups. Especially in the case of cgroups, it is useful
> > to have a central metadata store that multiple processes/services can
> > use to coordinate actions.
> >
> > A concrete example is for userspace out of memory killers. We want to
> > let delegated cgroup subtree owners (running as non-root) to be able to
> > say "please avoid killing this cgroup". In server environments this is
> > less important as everyone is running as root.
>
>
> I would recommend removing the "everyone is running as root" statement
> as it is not generally true.
>
>
> Shakeel
Good point, thanks.
next parent reply other threads:[~2020-03-03 19:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALvZod5m3otRRqcLBebbgiZbhoYWAMbMg+ESkacJuj64OP =H4Q@mail.gmail.com>
2020-03-03 19:20 ` Daniel Xu [this message]
2020-03-03 1:38 [PATCH 0/2] Support user xattrs in cgroupfs Daniel Xu
2020-03-03 16:50 ` Shakeel Butt
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=C11FZ3TMTIH1.2KP5NIUPPQBWT@dlxu-fedora-R90QNFJV \
--to=dxu@dxuuu.xyz \
--cc=cgroups@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=shakeelb@google.com \
--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;
as well as URLs for NNTP newsgroup(s).