From: Wu Fengguang <fengguang.wu@intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Jan Kara <jack@suse.cz>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: [PATCH] mm: Avoid livelocking of WB_SYNC_ALL writeback
Date: Sat, 6 Nov 2010 10:55:48 +0800 [thread overview]
Message-ID: <20101106025548.GA16378@localhost> (raw)
In-Reply-To: <20101105223038.GA16666@lst.de>
[add CC to linux-mm list]
On Sat, Nov 06, 2010 at 06:30:38AM +0800, Christoph Hellwig wrote:
> > + /*
> > + * In WB_SYNC_ALL mode, we just want to ignore nr_to_write as
> > + * we need to write everything and livelock avoidance is implemented
> > + * differently.
> > + */
> > + if (wbc.sync_mode == WB_SYNC_NONE)
> > + write_chunk = MAX_WRITEBACK_PAGES;
> > + else
> > + write_chunk = LONG_MAX;
Good catch!
>
> I think it would be useful to elaborate here on how livelock avoidance
> is supposed to work.
It's supposed to sync files in a big loop
for each dirty inode
write_cache_pages()
(quickly) tag currently dirty pages
(maybe slowly) sync all tagged pages
Ideally the loop should call write_cache_pages() _once_ for each inode.
At least this is the assumption made by commit f446daaea (mm:
implement writeback livelock avoidance using page tagging).
Setting wbc.nr_to_write to LONG_MAX ensures that writeback_inodes_wb()
will complete the above loop before returning to wb_writeback(), and
to prevent wb_writeback() from looping (thus re-syncing extra data) in
the below range of code.
643 wbc.nr_to_write = MAX_WRITEBACK_PAGES;
644 wbc.pages_skipped = 0;
645
646 trace_wbc_writeback_start(&wbc, wb->bdi);
647 if (work->sb)
648 __writeback_inodes_sb(work->sb, wb, &wbc);
649 else
650 writeback_inodes_wb(wb, &wbc);
651 trace_wbc_writeback_written(&wbc, wb->bdi);
652
653 work->nr_pages -= MAX_WRITEBACK_PAGES - wbc.nr_to_write;
654 wrote += MAX_WRITEBACK_PAGES - wbc.nr_to_write;
655
656 /*
657 * If we consumed everything, see if we have more
658 */
659 if (wbc.nr_to_write <= 0)
660 continue;
Thanks,
Fengguang
next prev parent reply other threads:[~2010-11-06 2:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-05 21:26 [PATCH] mm: Avoid livelocking of WB_SYNC_ALL writeback Jan Kara
2010-11-05 22:30 ` Christoph Hellwig
2010-11-06 2:54 ` Wu Fengguang
2010-11-06 11:45 ` Christoph Hellwig
2010-11-06 2:55 ` Wu Fengguang [this message]
2010-11-06 16:39 ` Wu Fengguang
2010-11-07 13:34 ` Jan Kara
2010-11-06 1:36 ` Johannes Weiner
2010-11-07 13:07 ` Jan Kara
2010-11-06 4:12 ` Wu Fengguang
2010-11-07 13:22 ` Jan Kara
2010-11-07 13:37 ` Wu Fengguang
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=20101106025548.GA16378@localhost \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.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).