From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Avi Kivity <avi@scylladb.com>,
linux-xfs@vger.kernel.org, michaelcallahan@fb.com
Subject: Re: discard improvements
Date: Mon, 7 Nov 2016 10:21:02 +1100 [thread overview]
Message-ID: <20161106232102.GQ14023@dastard> (raw)
In-Reply-To: <20161106163642.GB15675@lst.de>
On Sun, Nov 06, 2016 at 05:36:42PM +0100, Christoph Hellwig wrote:
> On Sat, Nov 05, 2016 at 08:18:05PM +0200, Avi Kivity wrote:
> > The big problem with "it depends" is that usually the information it
> > depends on is not available, so the application has to rely on a human to
> > guess correctly. With the trend for machines to be managed by machines,
> > it's really hard to get optimal performance. So exposure of any
> > information that can help to make a decision, including that the kernel can
> > make good use of TRIM, will be very helpful.
>
> I agree with you, but until devices tell us that their discard
> implementation sucks on their own there is not much I can help
> you there.
The problem is that we keep seeing cases where devices fail discards
because of firmware issues. These problems are not going away, and
it's just not the cheap SSDs that are the problem here.
e.g an 800GB Intel p3700 NVMe drive that was reported to the ext4
list last week that failed discard for all LBAs over 700GB. Whatever
the problem was, it was quietly fixed in a firmware update...
https://bugzilla.kernel.org/show_bug.cgi?id=186551
If we can't trust the high end enterprise SSDs to have a reliable
discard implementation, then discard will continue to be a "use at
your own risk" kind of feature...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2016-11-06 23:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 20:22 discard improvements Christoph Hellwig
2016-10-17 20:22 ` [PATCH 1/3] xfs: fix the AG loop in xfs_alloc_vextent for busy extents Christoph Hellwig
2016-10-19 13:48 ` Brian Foster
2016-10-21 12:48 ` Christoph Hellwig
2016-10-21 14:41 ` Brian Foster
2016-11-08 6:15 ` Dave Chinner
2016-11-10 19:17 ` Christoph Hellwig
2016-10-17 20:22 ` [PATCH 2/3] xfs: don't block the log commit handler for discards Christoph Hellwig
2016-10-17 23:29 ` Dave Chinner
2016-10-18 5:05 ` Christoph Hellwig
2016-10-19 10:58 ` Christoph Hellwig
2016-10-28 16:16 ` Michael Callahan
2016-10-31 15:16 ` Christoph Hellwig
2016-10-17 20:22 ` [PATCH 3/3] xfs: merge discard requests Christoph Hellwig
2016-10-28 10:11 ` discard improvements Avi Kivity
2016-10-31 15:14 ` Christoph Hellwig
2016-11-05 18:18 ` Avi Kivity
2016-11-06 16:36 ` Christoph Hellwig
2016-11-06 23:21 ` Dave Chinner [this message]
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=20161106232102.GQ14023@dastard \
--to=david@fromorbit.com \
--cc=avi@scylladb.com \
--cc=hch@lst.de \
--cc=linux-xfs@vger.kernel.org \
--cc=michaelcallahan@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.