From: Fredrik Tolf <fredrik@dolda2000.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: I/O blocked while dirty pages are being flushed
Date: Mon, 25 Mar 2013 08:31:43 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.02.1303250827120.4028@shack.dolda2000.com> (raw)
In-Reply-To: <514ED516.4020009@acm.org>
On Sun, 24 Mar 2013, Bart Van Assche wrote:
> On 03/24/13 06:12, Fredrik Tolf wrote:
>> While this flush is running, I find that many a process goes into disk
>> sleep waiting for the flush to complete. This includes the process
>> manipulating the mmapped file whenever it tries to redirty a page
>> currently waiting to be flushed, but also, for instance, programs that
>> write() to log files (since, I guess, the buffer page backing the last
>> written portion of the log file is being flushed).
>
> Had you already encountered this article: Jonathan Corbet, The trouble with
> stable pages, March 13, 2012 (http://lwn.net/Articles/486311/) ?
I had not, but that certainly does seem to be the exact problem I'm
having. Thanks for the link; it was a very interesting read! Does anyone
know if any progress has been made since about any resolution of the
situation?
I notice linked mail threads with people saying that they have simply
removed the calls to wait_on_page_writeback to resolve their problems. Can
this still be considered safe, or have other systems than this
block-device checksumming started depending on stable pages since? Like
software RAID, for instance?
--
Fredrik Tolf
next prev parent reply other threads:[~2013-03-25 7:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-24 5:12 Fredrik Tolf
2013-03-24 6:56 ` Eric Wong
2013-03-25 7:34 ` Fredrik Tolf
2013-03-24 10:27 ` Bart Van Assche
2013-03-25 7:31 ` Fredrik Tolf [this message]
2013-04-09 22:11 ` Jan Kara
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=alpine.DEB.2.02.1303250827120.4028@shack.dolda2000.com \
--to=fredrik@dolda2000.com \
--cc=bvanassche@acm.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
all inboxes | Powered by JetHome®