From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sandeen.net ([63.231.237.45]:35952 "EHLO sandeen.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729618AbeIRUJK (ORCPT ); Tue, 18 Sep 2018 16:09:10 -0400 Subject: Re: dm-writecache issue References: <20180911221147.GA23308@redhat.com> <20180918123238.GI27618@dastard> <817349b8-b54e-a16a-276f-7a977f29b449@sandeen.net> <8975ad6d-bfde-0a50-e60c-59228493f1b2@sandeen.net> From: Eric Sandeen Message-ID: Date: Tue, 18 Sep 2018 09:36:16 -0500 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-xfs-owner@vger.kernel.org List-ID: List-Id: xfs To: Mikulas Patocka Cc: Dave Chinner , "Darrick J. Wong" , linux-xfs@vger.kernel.org, David Teigland On 9/18/18 9:29 AM, Mikulas Patocka wrote: > On Tue, 18 Sep 2018, Eric Sandeen wrote: ... >> See also >> https://www.intel.com/content/www/us/en/support/articles/000006392/memory-and-storage.html >> >> -Eric > > And does it really support native 512-byte writes? Or does it emulate > 512-byte writes by doing read-modify-write? That needs to be benchmarked, > the paper doesn't say that. Interesting from a manual tuning perspective, but not from a default behavior perspective. I'm just pointing out that Intel does seem to give the user a choice about the /advertised/ geometry for some of their SSDs. > Memory is expensive and reducing SSD sector size increases memory > requirement on the SSD. I doubt that any SSD vendor would want to use > 8-times more memory just to support 512-byte sectors natively. Marketing decisions aside, we just can't safely ignore what the device tells us about these IO sizes. We have similar issues with raid devices which report nonsensical optimal and mininum IO sizes. If it's reporting bad info, the user can override it, but they have to be sure to get it right. For default behavior, mkfs.xfs has no choice but to use what the device tells it to use. -Eric