From: Gionatan Danti <g.danti@assyoma.it>
To: linux-xfs@vger.kernel.org
Cc: g.danti@assyoma.it
Subject: Disabling barriers on NVC-backed HDD
Date: Wed, 15 Nov 2017 18:01:17 +0100 [thread overview]
Message-ID: <8b91c685e344bdc5d084b11fab1d50af@assyoma.it> (raw)
Hi list,
I'm not sure this is the correct list to post my question; if so, feel
free to ignore this message.
On XFS FAQs I (rightfully) read that barrier should be *always* enabled
(and they are, by default), unless a write-loss protected writeback
cache is used at the RAID card level. So far, so good.
Newer HDDs has themselves have a non-volatile cache (NVC) of some sort,
basically:
- DRAM + eMCL: in a powerloss event, the DRAM cache is immediately
dumped on the eMLC flash;
- DRAM + NOR flash: NOR mirrors a (small) portion of the DRAM cache,
used for write acceleration purpose;
- dedicated "dump" areas on the disks: they effectively mirror a portion
of the DRAM cache.
My question is: do you think it is safe to disable barriers, both for
XFS and in general terms, on these disks? Or they should be considered
as the same "dumb" unprotected DRAM caches found on classical HDD?
From a side, these *are* powerloss-protected caches. Problem is that all
these power-protection schemes are considered "secret sauce / trade
secret" by HDD vendors and, for this reason, there are very little (if
any) informations on their inner working.
Regards.
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8
next reply other threads:[~2017-11-15 17:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 17:01 Gionatan Danti [this message]
2017-11-15 17:31 ` Disabling barriers on NVC-backed HDD Darrick J. Wong
2017-11-15 18:53 ` Gionatan Danti
2017-11-15 19:47 ` Christoph Hellwig
2017-11-15 20:17 ` Gionatan Danti
2017-11-15 20:18 ` Gionatan Danti
2017-11-15 20:27 ` Gionatan Danti
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=8b91c685e344bdc5d084b11fab1d50af@assyoma.it \
--to=g.danti@assyoma.it \
--cc=linux-xfs@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