linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wu Fengguang <fengguang.wu@intel.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	Jan Kara <jack@suse.cz>, Christoph Hellwig <hch@lst.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/5] dirty throttling bits for 3.3
Date: Mon, 28 Nov 2011 21:56:26 +0800	[thread overview]
Message-ID: <20111128135626.GA30388@localhost> (raw)
In-Reply-To: <1322052249.14799.59.camel@twins>

On Wed, Nov 23, 2011 at 08:44:09PM +0800, Peter Zijlstra wrote:
> On Mon, 2011-11-21 at 21:03 +0800, Wu Fengguang wrote:
> > Hi,
> > 
> > I'd like to push these 5 dirty throttling improvements to linux-next,
> > targeting for inclusion in Linux 3.3.
> > 
> > It's a comfortably small series for review ;) And there are no changes since
> > the last v12 post. (I went through them once again but find nothing to change.)
> > 
> >  [PATCH 1/5] writeback: balanced_rate cannot exceed write bandwidth
> >  [PATCH 2/5] writeback: charge leaked page dirties to active tasks
> >  [PATCH 3/5] writeback: fix dirtied pages accounting on sub-page writes
> >  [PATCH 4/5] writeback: fix dirtied pages accounting on redirty
> >  [PATCH 5/5] writeback: dirty ratelimit - think time compensation
> 
> Given the updates I'm ok with this series,
> 
> Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
> 
> Thanks!

Thank you! I'll post the updated series with your acks :)

Thanks,
Fengguang

      reply	other threads:[~2011-11-28 13:56 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-21 13:03 [PATCH 0/5] dirty throttling bits for 3.3 Wu Fengguang
2011-11-21 13:03 ` [PATCH 1/5] writeback: balanced_rate cannot exceed write bandwidth Wu Fengguang
2011-11-21 22:50   ` Jan Kara
2011-11-22  6:41     ` Wu Fengguang
2011-11-22 21:04       ` Jan Kara
2011-11-23 13:17         ` Wu Fengguang
2011-11-21 13:03 ` [PATCH 2/5] writeback: charge leaked page dirties to active tasks Wu Fengguang
2011-11-21 21:49   ` Andrew Morton
2011-11-21 23:46     ` Jan Kara
2011-11-22 13:35     ` Wu Fengguang
2011-11-21 13:03 ` [PATCH 3/5] writeback: fix dirtied pages accounting on sub-page writes Wu Fengguang
2011-11-22  0:11   ` Jan Kara
2011-11-22  9:21     ` Wu Fengguang
2011-11-22 12:21       ` Jan Kara
2011-11-22 12:30         ` Wu Fengguang
2011-11-22 12:48           ` Jan Kara
2011-11-22 13:02             ` Wu Fengguang
2011-11-22 12:57         ` Peter Zijlstra
2011-11-22 13:07           ` Wu Fengguang
2011-11-22 13:41             ` Wu Fengguang
2011-11-22 13:53               ` Peter Zijlstra
2011-11-22 14:11                 ` Wu Fengguang
2011-11-28 13:51         ` Wu Fengguang
2011-11-21 13:03 ` [PATCH 4/5] writeback: fix dirtied pages accounting on redirty Wu Fengguang
2011-11-21 21:51   ` Andrew Morton
2011-11-22 13:59     ` Wu Fengguang
2011-11-21 13:03 ` [PATCH 5/5] writeback: dirty ratelimit - think time compensation Wu Fengguang
2011-11-23 12:44 ` [PATCH 0/5] dirty throttling bits for 3.3 Peter Zijlstra
2011-11-28 13:56   ` Wu Fengguang [this message]

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=20111128135626.GA30388@localhost \
    --to=fengguang.wu@intel.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=hch@lst.de \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.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).