From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752853AbcG2BKC (ORCPT ); Thu, 28 Jul 2016 21:10:02 -0400 Received: from auth-4.ukservers.net ([217.10.138.158]:55358 "EHLO auth-4.ukservers.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751975AbcG2BJ7 (ORCPT ); Thu, 28 Jul 2016 21:09:59 -0400 X-Greylist: delayed 313 seconds by postgrey-1.27 at vger.kernel.org; Thu, 28 Jul 2016 21:09:59 EDT Subject: Re: To add, or not to add, a bio REQ_ROTATIONAL flag To: Eric Wheeler , linux-block@vger.kernel.org References: Cc: dm-devel@redhat.com, linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org, linux-bcache@vger.kernel.org From: Wols Lists X-Enigmail-Draft-Status: N1110 Message-ID: <579AABAA.2020200@youngman.org.uk> Date: Fri, 29 Jul 2016 02:04:42 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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