linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Dave Chinner <david@fromorbit.com>
Cc: torvalds@linux-foundation.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, xfs@oss.sgi.com, stable@kernel.org
Subject: Re: [PATCH 2/3] xfs: remove nr_to_write writeback windup.
Date: Wed, 9 Jun 2010 14:10:26 -0700	[thread overview]
Message-ID: <20100609141026.977baebf.akpm@linux-foundation.org> (raw)
In-Reply-To: <1276043840-1946-3-git-send-email-david@fromorbit.com>

On Wed,  9 Jun 2010 10:37:19 +1000
Dave Chinner <david@fromorbit.com> wrote:

> From: Dave Chinner <dchinner@redhat.com>
> 
> Now that the background flush code has been fixed, we shouldn't need to
> silently multiply the wbc->nr_to_write to get good writeback. Remove
> that code.
> 

And anyone who merges [1/3] will want to merge this.  Otherwise they
might suffer adverse effects ;)

  reply	other threads:[~2010-06-09 21:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-09  0:37 [PATCH 0/3] writeback: bug fixes for 2.6.35 Dave Chinner
2010-06-09  0:37 ` [PATCH 1/3] writeback: pay attention to wbc->nr_to_write in write_cache_pages Dave Chinner
2010-06-09 21:09   ` Andrew Morton
2010-06-09 22:58     ` Dave Chinner
2010-06-10  0:08       ` Dave Chinner
2010-06-23 20:36         ` [stable] " Greg KH
2010-06-09  0:37 ` [PATCH 2/3] xfs: remove nr_to_write writeback windup Dave Chinner
2010-06-09 21:10   ` Andrew Morton [this message]
2010-06-09  0:37 ` [PATCH 3/3] writeback: limit write_cache_pages integrity scanning to current EOF Dave Chinner
2010-06-09 21:12   ` Andrew Morton

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=20100609141026.977baebf.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=david@fromorbit.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=xfs@oss.sgi.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).