From: Chris Mason <clm@fb.com>
To: "tm@tao.ma" <tm@tao.ma>
Cc: "jack@suse.cz" <jack@suse.cz>,
"gnehzuil.liu@gmail.com" <gnehzuil.liu@gmail.com>,
"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: Tue, 31 Dec 2013 15:34:40 +0000 [thread overview]
Message-ID: <1388504116.24668.0.camel@ret.masoncoding.com> (raw)
In-Reply-To: <52C2D342.8000606@tao.ma>
On Tue, 2013-12-31 at 22:22 +0800, Tao Ma wrote:
> Hi Chris,
> On 12/31/2013 09:19 PM, Chris Mason wrote:
>
> > So I'd like to throttle the rate at which dirty pages are created,
> > preferably based on the rates currently calculated in the BDI of how
> > quickly the device is doing IO. This way we can limit dirty creation to
> > a percentage of the disk capacity during the current workload
> > (regardless of random vs buffered).
> Fengguang had already done some work on this, but it seems that the
> community does't have a consensus on where this control file should go.
> You can look at this link: https://lkml.org/lkml/2011/4/4/205
I had forgotten Wu's patches here, it's very close to the starting point
I was hoping for.
-chris
next prev parent reply other threads:[~2013-12-31 15:34 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 [this message]
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=1388504116.24668.0.camel@ret.masoncoding.com \
--to=clm@fb.com \
--cc=gnehzuil.liu@gmail.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=tm@tao.ma \
/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.