From: Zheng Liu <gnehzuil.liu@gmail.com>
To: Chris Mason <clm@fb.com>
Cc: "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/MM ATTEND] Filesystems -- Btrfs, cgroups, Storage topics from Facebook
Date: Tue, 31 Dec 2013 16:49:27 +0800 [thread overview]
Message-ID: <20131231084927.GA29449@gmail.com> (raw)
In-Reply-To: <1388439412.16965.27.camel@ret>
Hi Chris,
On Mon, Dec 30, 2013 at 09:36:20PM +0000, Chris Mason wrote:
> Hi everyone,
>
> I'd like to attend the LSF/MM conference this year. My current
> discussion points include:
>
> All things Btrfs!
>
> Adding cgroups for more filesystem resources, especially to limit the
> speed dirty pages are created.
Interesting. If I remember correctly, IO-less dirty throttling has been
applied into upstream kernel, which can limit the speed that dirty pages
are created. Does it has any defect?
Out of curiosity, which file system resource do you want to control?
Regards,
- Zheng
>
> I'm trying to collect a short summary of how Linux sucks from my new
> employer. My inbox isn't exactly overflowing with complaints yet, but
> I'm hoping for a few unsolved warts we can all argue over.
>
> -chris
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-12-31 8:45 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 [this message]
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
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=20131231084927.GA29449@gmail.com \
--to=gnehzuil.liu@gmail.com \
--cc=clm@fb.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.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).