From: Jens Axboe <jens.axboe@oracle.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-ext4@vger.kernel.org,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: [PATCH, RFC] Use WRITE_SYNC in __block_write_full_page() if WBC_SYNC_ALL
Date: Mon, 5 Jan 2009 20:38:20 +0100 [thread overview]
Message-ID: <20090105193820.GW32491@kernel.dk> (raw)
In-Reply-To: <20090105193517.GC11632@mit.edu>
On Mon, Jan 05 2009, Theodore Tso wrote:
> So long-term, I suspect the hueristic which makes sense is that in the
> case where there is an fsync() in progress, any writes which take
> place as a result of that fsync (which includes the journal records as
> well as ordered writes that are being forced out as a result of
> data=ordered and which block the fsync from returning), should get a
> hint which propagates down to the block layer that these writes *are*
> synchronous in that someone is waiting for them to complete. They
If someone is waiting for them, they are by definition sync!
> shouldn't necessarily be prioritized ahead of other reads (unless they
> are readahead operations that couldn't be combined with reads that
> *are* synchronous that someone is waiting for completion), but they
> should be prioritized ahead of asynchronous writes.
And that is *exactly* what flagging the write as sync will do...
--
Jens Axboe
next prev parent reply other threads:[~2009-01-05 19:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-04 21:52 [PATCH, RFC] Use WRITE_SYNC in __block_write_full_page() if WBC_SYNC_ALL Theodore Ts'o
2009-01-04 22:23 ` Andrew Morton
2009-01-04 22:43 ` Theodore Tso
2009-01-04 22:43 ` Theodore Tso
2009-01-04 23:19 ` Andrew Morton
2009-01-05 0:21 ` Theodore Tso
2009-01-05 8:02 ` Jens Axboe
2009-01-05 14:47 ` Theodore Tso
2009-01-05 15:58 ` Jens Axboe
2009-01-05 18:47 ` Andrew Morton
2009-01-05 19:35 ` Theodore Tso
2009-01-05 19:38 ` Jens Axboe [this message]
2009-01-05 21:16 ` Theodore Tso
2009-01-06 7:34 ` 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=20090105193820.GW32491@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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.