From: 谢纲 <xiegang112@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Can I/O order be guaranteed by submitting sycn bio
Date: Sat, 9 May 2009 10:25:29 +0800 [thread overview]
Message-ID: <d364733c0905081925y795fefc3ie76515609c95cf3e@mail.gmail.com> (raw)
Hi,
Some journal file systems submits sycn bio to do ordered write if the
device does not support barrier i/o. But the sync bio only implies the
unplug of the request queue. Some elevators may reorder the request.
It's seems that the bio only with BIO_RW_SYNC flag could not guarantee
the write order. Is this true?
If so, is there any better way to do ordered write when there is no
barrier i/o support.
Thanks,
--
Xie Gang
reply other threads:[~2009-05-09 2:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=d364733c0905081925y795fefc3ie76515609c95cf3e@mail.gmail.com \
--to=xiegang112@gmail.com \
--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®