From: Jeff Moyer <jmoyer@redhat.com>
To: "Ma\, Jianpeng" <jianpeng.ma@intel.com>
Cc: Zach Brown <zab@zabbo.net>,
"viro\@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
Sage Weil <sweil@redhat.com>,
Mark Kirkwood <mark.kirkwood@catalyst.net.nz>,
"linux-aio\@kvack.org" <linux-aio@kvack.org>,
"linux-fsdevel\@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [HELP]: about aio+dio
Date: Wed, 27 Aug 2014 09:38:03 -0400 [thread overview]
Message-ID: <x49bnr68344.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <6AA21C22F0A5DA478922644AD2EC308C8B8D17@SHSMSX101.ccr.corp.intel.com> (Jianpeng Ma's message of "Wed, 27 Aug 2014 00:34:44 +0000")
"Ma, Jianpeng" <jianpeng.ma@intel.com> writes:
> For aio+directio:
> After io_submit, the content in request-queue of block-device.
Maybe. It might be in the per-cpu plug list, or in the elevator's
queues.
> In blkdev_fsync(), it will cal blkdev_issue_flush. This operation make
> all request to disk.
blkdev_issue_flush send a FLUSH to the device. It does nothing to
re-order existing requests in the queue. Thus, as Zach said, if you
want to ensure data is on stable media, then you should wait for the I/O
to complete and then issue the fsync.
Cheers,
Jeff
--
To unsubscribe, send a message with 'unsubscribe linux-aio' in
the body to majordomo@kvack.org. For more info on Linux AIO,
see: http://www.kvack.org/aio/
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>
next prev parent reply other threads:[~2014-08-27 13:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 4:05 [HELP]: about aio+dio Ma, Jianpeng
2014-08-20 17:26 ` John Utz
2014-08-20 18:43 ` Zach Brown
2014-08-21 2:01 ` Ma, Jianpeng
2014-08-21 16:58 ` Zach Brown
2014-08-22 0:40 ` Ma, Jianpeng
2014-08-26 18:52 ` Zach Brown
2014-08-27 0:34 ` Ma, Jianpeng
2014-08-27 13:38 ` Jeff Moyer [this message]
2014-08-27 16:03 ` Zach Brown
2014-08-28 1:45 ` Ma, Jianpeng
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=x49bnr68344.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=jianpeng.ma@intel.com \
--cc=linux-aio@kvack.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mark.kirkwood@catalyst.net.nz \
--cc=sweil@redhat.com \
--cc=viro@zeniv.linux.org.uk \
--cc=zab@zabbo.net \
/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).