From: Nikhilesh Reddy <reddyn@codeaurora.org>
To: Theodore Ts'o <tytso@mit.edu>, linux-ext4@vger.kernel.org
Subject: Using Cache barriers in lieu of REQ_FLUSH | REQ_FUA for emmc 5.1 (jdec spec JESD84-B51)
Date: Tue, 15 Sep 2015 16:17:46 -0700 [thread overview]
Message-ID: <55F8A71A.3030001@codeaurora.org> (raw)
Hi
The eMMC 5.1 spec defines cache "barrier" capability of the eMMC device
as defined in JESD84-B51
I was wondering if there were any downsides to replacing the
WRITE_FLUSH_FUA with the cache barrier?
I understand that REQ_FLUSH is used to ensure that the current cache be
flushed to prevent any reordering but I dont seem to be clear on why
REQ_FUA is used.
Can someone please help me understand this part?
But as far as I understand it ... the cache barriers can be used to
replace all the flush requests.
Please let me know if there is any downside to this ?
I know there there was a big decision in 2010
https://lwn.net/Articles/400541/
and http://lwn.net/Articles/399148/
to remove the software based barrier support... but with the hardware
supporting "barriers" is there a downside to using them to replace the
flushes?
--
Thanks
Nikhilesh Reddy
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project.
next reply other threads:[~2015-09-15 23:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 23:17 Nikhilesh Reddy [this message]
2015-09-20 3:42 ` Using Cache barriers in lieu of REQ_FLUSH | REQ_FUA for emmc 5.1 (jdec spec JESD84-B51) Theodore Ts'o
2015-09-28 22:28 ` Nikhilesh Reddy
2015-10-23 6:33 ` Running XFS tests on qemu Nikhilesh Reddy
2015-10-23 9:34 ` Theodore Ts'o
2015-10-27 17:55 ` Nikhilesh Reddy
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=55F8A71A.3030001@codeaurora.org \
--to=reddyn@codeaurora.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 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).