linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Dave Chinner <david@fromorbit.com>,
	"Darrick J. Wong" <darrick.wong@oracle.com>,
	linux-xfs@vger.kernel.org, David Teigland <teigland@redhat.com>
Subject: Re: dm-writecache issue
Date: Tue, 18 Sep 2018 09:36:16 -0500	[thread overview]
Message-ID: <b359bcc7-bc76-33cc-30fb-2c8ad2ba4682@sandeen.net> (raw)
In-Reply-To: <alpine.LRH.2.02.1809181024150.28565@file01.intranet.prod.int.rdu2.redhat.com>

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

  reply	other threads:[~2018-09-18 20:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180911221147.GA23308@redhat.com>
2018-09-18 11:46 ` dm-writecache issue Mikulas Patocka
2018-09-18 12:32   ` Dave Chinner
2018-09-18 12:48     ` Eric Sandeen
2018-09-18 14:09       ` Mikulas Patocka
2018-09-18 14:16         ` Eric Sandeen
2018-09-18 14:19           ` Eric Sandeen
2018-09-18 14:29             ` Mikulas Patocka
2018-09-18 14:36               ` Eric Sandeen [this message]
2018-09-18 14:42                 ` Mikulas Patocka
2018-09-18 15:04                   ` Eric Sandeen
2018-09-18 15:27                     ` Eric Sandeen
2018-09-18 15:29                       ` Christoph Hellwig
2018-09-18 17:15                     ` Mikulas Patocka
2018-09-18 14:20       ` David Teigland
2018-09-18 14:23         ` Eric Sandeen
2018-09-18 14:22     ` Mikulas Patocka
2018-09-18 15:33       ` Christoph Hellwig
2018-09-18 17:39         ` Mikulas Patocka
2018-09-18 22:52           ` Dave Chinner

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=b359bcc7-bc76-33cc-30fb-2c8ad2ba4682@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=darrick.wong@oracle.com \
    --cc=david@fromorbit.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=mpatocka@redhat.com \
    --cc=teigland@redhat.com \
    /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).