From: Eric Mei <meijia@gmail.com>
To: linux-raid@vger.kernel.org
Subject: write barrier in RAID5
Date: Wed, 01 Apr 2015 12:24:38 -0600 [thread overview]
Message-ID: <551C37E6.6090201@gmail.com> (raw)
I can see how FUA is handled, but REQ_FLUSH seems problematic. My
understanding of REQ_FLUSH semantics: all requests before the flush
request must *complete* before the flush request complete. For IO remap
layer like MD, we need to guarantee all previous requests are
*submitted* to component devices before submitting the flush request. Is
that correct?
If so why I don't see the code which make sure the pending write
requests in stripe cache are processed & submitted before
submit_flushes() get called? Thanks
Eric
next reply other threads:[~2015-04-01 18:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 18:24 Eric Mei [this message]
2015-04-07 1:25 ` write barrier in RAID5 NeilBrown
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=551C37E6.6090201@gmail.com \
--to=meijia@gmail.com \
--cc=linux-raid@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 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.