All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: Andrew Morton <akpm@osdl.org>
Cc: dgc@sgi.com, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, Nathan Scott <nathans@sgi.com>
Subject: Re: [PATCH] Prevent large file writeback starvation
Date: Mon, 6 Feb 2006 22:57:25 +1100	[thread overview]
Message-ID: <20060206115725.GL43335175@melbourne.sgi.com> (raw)
In-Reply-To: <20060205223611.5789a062.akpm@osdl.org>

On Sun, Feb 05, 2006 at 10:36:11PM -0800, Andrew Morton wrote:
> Andrew Morton <akpm@osdl.org> wrote:
> >
> > If so, why would that happen?  Take a look at wb_kupdate().  It's supposed
> >  to work *continuously* on the inodes until writeback_inodes() failed to
> >  write back enough pages.  It takes this as an indication that there's no
> >  more work to do at this time.
> > 
> >  It'd be interesting to take a look at what's happening in wb_kupdate().
> 
> Took a quick look at xfs_convert_page().  I don't immediately see a cause
> in there, but
> 
> 		if (count) {
> 			struct backing_dev_info *bdi;
> 
> 			bdi = inode->i_mapping->backing_dev_info;
> 			if (bdi_write_congested(bdi)) {
> 				wbc->encountered_congestion = 1;
> 				done = 1;
> 			} else if (--wbc->nr_to_write <= 0) {
> 				done = 1;
> 			}
> 		}
> 		xfs_start_page_writeback(page, wbc, !page_dirty, count);
> 
> shouldn't we be decrementing wbc->nr_to_write even if the queue is congested?

Yes, you are right. I'll fix it tomorrow.

Cheers,

Dave.
-- 
Dave Chinner
R&D Software Enginner
SGI Australian Software Group

  reply	other threads:[~2006-02-06 11:57 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-06  4:00 [PATCH] Prevent large file writeback starvation David Chinner
2006-02-06  4:27 ` Andrew Morton
2006-02-06  5:48   ` David Chinner
2006-02-06  6:22     ` Andrew Morton
2006-02-06  6:36       ` Andrew Morton
2006-02-06 11:57         ` David Chinner [this message]
2006-02-06 11:55       ` David Chinner
2006-02-06 23:14         ` Andrew Morton
2006-02-07  0:34           ` David Chinner
2006-02-07  1:04             ` Andrew Morton
2006-02-07  1:31               ` David Chinner
2006-02-07  5:27                 ` Andrew Morton
2006-02-07  7:42                   ` David Chinner
2006-02-07 22:51                     ` Andrew Morton
2006-02-07  7:49           ` David Chinner
2006-02-06 14:36   ` Mark Lord
2006-02-06 14:39     ` Mark Lord
2006-02-06 15:53       ` Several Hangs on diferent Hardwares and diferent kernels Pedro Alves
2006-02-06 20:11       ` [PATCH] Prevent large file writeback starvation Andrew Morton
2006-02-13 13:59         ` dirty pages (Was: Re: [PATCH] Prevent large file writeback starvation) Johannes Stezenbach
2006-02-13 20:08           ` Andrew Morton
2006-02-13 22:48             ` Johannes Stezenbach
2006-02-13 23:04               ` Andrew Morton
2006-02-13 23:31                 ` Johannes Stezenbach
2006-02-13 23:52             ` Mark Lord
2006-02-14  0:50               ` Mark Lord
2006-02-14 16:32               ` Mark Lord
2006-04-11 12:42           ` Alexander Bergolth
2006-03-20 22:40         ` [PATCH] Prevent large file writeback starvation Alexander Bergolth

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=20060206115725.GL43335175@melbourne.sgi.com \
    --to=dgc@sgi.com \
    --cc=akpm@osdl.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathans@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 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.