From: Jes.Sorensen@redhat.com
To: neilb@suse.de
Cc: linux-raid@vger.kernel.org
Subject: [PATCH 0/1] RFC: Unreliable discard performance can cripple RAID1
Date: Tue, 23 Jun 2015 20:26:12 -0400 [thread overview]
Message-ID: <1435105573-1373-1-git-send-email-Jes.Sorensen@redhat.com> (raw)
From: Jes Sorensen <Jes.Sorensen@redhat.com>
Neil,
I have been hitting issues with discard being ridiculously slow on
arrays with certain typs of SSDs that seem to serialize discard
processing.
This is particularly bad as I have seen systems where the IMSM BIOS
defaults to 4KB chunk size, combined with these badly performing
drives, it could bump the mkfs on an array from seconds to over 40
minutes. Most users will stick to the defaults and then hit the
problem during install without understanding why it goes wrong :(
The problem is that there is no way to benchmark our way to this or
somehow test if a drive performs discard at reasonable speed. I
suggest we take an approach similar to that of RAID456 and default to
disabling discard, except for the case where the user knows the drives
are safe.
Thoughts?
Cheers,
Jes
Jes Sorensen (1):
raid0: Disable discard per default due to performance uncertainty
drivers/md/raid0.c | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
--
2.4.3
next reply other threads:[~2015-06-24 0:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-24 0:26 Jes.Sorensen [this message]
2015-06-24 0:26 ` [PATCH 1/1] raid0: Disable discard per default due to performance uncertainty Jes.Sorensen
2015-06-24 5:00 ` [PATCH 0/1] RFC: Unreliable discard performance can cripple RAID1 Roman Mamedov
2015-06-24 11:04 ` Jes Sorensen
2015-06-25 1:03 ` Martin K. Petersen
2015-06-24 7:55 ` NeilBrown
2015-06-24 11:02 ` Jes Sorensen
2015-06-25 1:05 ` Martin K. Petersen
2015-07-07 4:42 ` Mike Snitzer
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=1435105573-1373-1-git-send-email-Jes.Sorensen@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).