From: Jens Axboe <jens.axboe@oracle.com>
To: Jan Kara <jack@suse.cz>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
fengguang.wu@intel.com
Subject: Re: [GIT PULL] a few writeback fixes
Date: Mon, 21 Sep 2009 15:41:22 +0200 [thread overview]
Message-ID: <20090921134122.GZ23126@kernel.dk> (raw)
In-Reply-To: <20090921131138.GE1099@duck.suse.cz>
On Mon, Sep 21 2009, Jan Kara wrote:
> On Mon 21-09-09 14:56:20, Jens Axboe wrote:
> Hi Jens,
>
> > Jan, since we're not really sure on the inode wait yet, I dropped that
> > patch. It's definitely something to look into, as are the congestion
> > bits.
> OK.
>
> Honza
>
> > diff --git a/mm/page-writeback.c b/mm/page-writeback.c
> > index 1eea4fa..6bb510b 100644
> > --- a/mm/page-writeback.c
> > +++ b/mm/page-writeback.c
> > @@ -485,6 +485,7 @@ static void balance_dirty_pages(struct address_space *mapping)
> > unsigned long bdi_thresh;
> > unsigned long pages_written = 0;
> > unsigned long write_chunk = sync_writeback_pages();
> > + unsigned long pause = 1;
> >
> > struct backing_dev_info *bdi = mapping->backing_dev_info;
> >
> > @@ -561,7 +562,15 @@ static void balance_dirty_pages(struct address_space *mapping)
> > if (pages_written >= write_chunk)
> > break; /* We've done our duty */
> >
> > - schedule_timeout(1);
> > + schedule_timeout_interruptible(pause);
> > +
> > + /*
> > + * Increase the delay for each loop, up to our previous
> > + * default of taking a 100ms nap.
> > + */
> > + pause <<= 1;
> > + if (pause < HZ / 10)
> > + pause = HZ / 10;
> Isn't this check the other way around?
Gah it is, how silly. I have fixed it up. Thanks, eagle eyes :-)
--
Jens Axboe
next prev parent reply other threads:[~2009-09-21 13:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-21 12:56 [GIT PULL] a few writeback fixes Jens Axboe
2009-09-21 13:08 ` Wu Fengguang
2009-09-21 13:11 ` Jan Kara
2009-09-21 13:41 ` Jens Axboe [this message]
2009-09-21 16:42 ` Ingo Molnar
2009-09-21 19:02 ` Jens Axboe
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=20090921134122.GZ23126@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=fengguang.wu@intel.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@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 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.