From: Wols Lists <antlists@youngman.org.uk>
To: Eric Wheeler <bcache@lists.ewheeler.net>, linux-block@vger.kernel.org
Cc: dm-devel@redhat.com, linux-raid@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-bcache@vger.kernel.org
Subject: Re: To add, or not to add, a bio REQ_ROTATIONAL flag
Date: Fri, 29 Jul 2016 02:04:42 +0100 [thread overview]
Message-ID: <579AABAA.2020200@youngman.org.uk> (raw)
In-Reply-To: <alpine.LRH.2.11.1607281603530.10662@mail.ewheeler.net>
On 29/07/16 01:50, Eric Wheeler wrote:
> Hello all,
>
> With the many SSD caching layers being developed (bcache, dm-cache,
> dm-writeboost, etc), how could we flag a bio from userspace to indicate
> whether the bio is preferred to hit spinning disks instead of an SSD?
>
> Unnecessary promotions, evections, and writeback increase the write burden
> on the caching layer and burns out SSDs too fast (TBW), thus requring
> equipment replacement.
What's the spec of these devices? How long are they expected to last?
Other recent posts on this (linux-raid) mailing list refer to tests on
SSDs that indicates their typical life is way beyond their nominal life,
and that in normal usage they are actually likely to outlive "spinning
rust".
http://techreport.com/review/24841/introducing-the-ssd-endurance-experiment
http://techreport.com/review/27909/the-ssd-endurance-experiment-theyre-all-dead/3
Looking at the results, the FIRST drives only started failing once
they'd written some 700 Terabytes. How long is it going to take you to
write that much data over a SATA3 link?
Cheers,
Wol
next prev parent reply other threads:[~2016-07-29 1:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 0:50 To add, or not to add, a bio REQ_ROTATIONAL flag Eric Wheeler
2016-07-29 1:04 ` Wols Lists [this message]
2016-07-29 1:16 ` Martin K. Petersen
2016-08-01 2:58 ` Eric Wheeler
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=579AABAA.2020200@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=bcache@lists.ewheeler.net \
--cc=dm-devel@redhat.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 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).