From: "tj@kernel.org" <tj@kernel.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Chris Mason <clm@fb.com>, "jack@suse.cz" <jack@suse.cz>,
"vgoyal@redhat.com" <vgoyal@redhat.com>,
"lizefan@huawei.com" <lizefan@huawei.com>,
"gnehzuil.liu@gmail.com" <gnehzuil.liu@gmail.com>,
"tm@tao.ma" <tm@tao.ma>,
"lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [Lsf-pc] [LSF/MM ATTEND] Filesystems -- Btrfs, cgroups, Storage topics from Facebook
Date: Thu, 2 Jan 2014 13:36:41 -0500 [thread overview]
Message-ID: <20140102183641.GA12062@htj.dyndns.org> (raw)
In-Reply-To: <1388687238.2399.18.camel@dabdike.int.hansenpartnership.com>
Hey, James.
On Thu, Jan 02, 2014 at 10:27:18AM -0800, James Bottomley wrote:
> Well, you know, since bdis are block device tied, there's a natural
> question if this can be a similar (or identical) control plane to the
> one Oren is proposing for the device namespace. I know you've never
> really liked the idea, but this is pushing us down that path.
The reason I'm reluctant about Oren's proposal is not about where or
how it'll be implemented but about whether it's something we want to
have at all. The proposed use case seemed exceedingly niche and
transient to me, which is not to say that the use case shouldn't be
supported but more that it probably should be implemented in a way
which is a lot less intrusive even if that means taking compromises
elsewhere (for example, userland basesystem might not experience full
transparency).
> Perhaps what we should do is a half day on cgroups before the main LSF
> (so in collab summit time, or just in the pub the night before) ... I'm
> not sure all our audience are cgroup aware ...
I think a single slot should suffice. Talking longer doesn't
necessarily seem to lead to something actually useful.
Thanks.
--
tejun
next prev parent reply other threads:[~2014-01-02 18:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-30 21:36 [LSF/MM ATTEND] Filesystems -- Btrfs, cgroups, Storage topics from Facebook Chris Mason
2013-12-31 8:49 ` Zheng Liu
2013-12-31 9:36 ` Jeff Liu
2013-12-31 12:45 ` [Lsf-pc] " Jan Kara
2013-12-31 13:19 ` Chris Mason
2013-12-31 14:22 ` Tao Ma
2013-12-31 15:34 ` Chris Mason
2014-01-02 6:46 ` Jan Kara
2014-01-02 15:21 ` Chris Mason
2014-01-02 16:01 ` tj
2014-01-02 16:14 ` tj
2014-01-03 6:03 ` Jan Kara
2014-01-02 17:06 ` Vivek Goyal
2014-01-02 17:10 ` tj
2014-01-02 19:11 ` Chris Mason
2014-01-03 6:39 ` Jan Kara
2014-01-02 18:27 ` James Bottomley
2014-01-02 18:36 ` tj [this message]
2014-01-03 7:44 ` James Bottomley
2014-01-08 15:04 ` Mel Gorman
2014-01-08 16:14 ` Chris Mason
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=20140102183641.GA12062@htj.dyndns.org \
--to=tj@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=clm@fb.com \
--cc=gnehzuil.liu@gmail.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=tm@tao.ma \
--cc=vgoyal@redhat.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).