From: Gionatan Danti <g.danti@assyoma.it>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
linux-xfs@vger.kernel.org, g.danti@assyoma.it
Subject: Re: Disabling barriers on NVC-backed HDD
Date: Wed, 15 Nov 2017 21:27:21 +0100 [thread overview]
Message-ID: <fb4469d15c91569db79abb34396e7272@assyoma.it> (raw)
In-Reply-To: <e7d6cada4330c02c86e5159ef987c0d9@assyoma.it>
Il 15-11-2017 21:18 Gionatan Danti ha scritto:
> Sorry, I forgot the link:
> https://www.seagate.com/files/www-content/product-content/enterprise-performance-savvio-fam/enterprise-performance-15k-hdd/_cross-product/_shared/doc/enchanced-cache-advantage-tp691.1-1610us.pdf
Ok, it seems that for Seagate drives the real document to read is that
one[1]. Quoting:
"When WCE=0, Advanced provides NVC-protected write caching over the
portion of the DRAM used to coalesce writes. Write data only goes into
NVC when there is an unexpected power loss to the drive. The NVC has
90-day data retention. When WCE=1, a Advanced Caching drive will operate
on writes like a standard drive–writes in cache are not protected by NVC
and may be lost with power loss."
In short:
- WCE=1 -> entire cache enabled -> powerloss = dataloss;
- WCE=0 -> small write cache segment enabled -> powerloss = nodataloss.
Unfortunately, I can not find anything on that regard about HGST's
MediaCache...
Regards.
[1]
https://www.seagate.com/www-content/product-content/enterprise-performance-savvio-fam/ent-perf-10k-hdd-v9-skybolt/en-us/docs/100818015c.pdf
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8
prev parent reply other threads:[~2017-11-15 20:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 17:01 Disabling barriers on NVC-backed HDD Gionatan Danti
2017-11-15 17:31 ` 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 [this message]
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=fb4469d15c91569db79abb34396e7272@assyoma.it \
--to=g.danti@assyoma.it \
--cc=darrick.wong@oracle.com \
--cc=hch@infradead.org \
--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 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.