From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Tejun Heo <tj@kernel.org>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata: Whitelist SSDs that are known to properly return zeroes after TRIM
Date: Wed, 10 Dec 2014 16:02:32 -0500 [thread overview]
Message-ID: <yq1oarbcj6f.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <20141210142927.GA6294@htj.dyndns.org> (Tejun Heo's message of "Wed, 10 Dec 2014 09:29:27 -0500")
>>>>> "Tejun" == Tejun Heo <tj@kernel.org> writes:
Tejun> If raid consistency truly is the only reason for this, that
Tejun> approach seems way more fruitful to me than playing this optional
Tejun> feature game with hardware vendors which so often leads to
Tejun> eventual abysmal outcomes.
The other use case is the filesystem one where it is common to zero
block ranges for bitmaps, etc. In many workloads there's is a
significant win to trimming over writing out many blocks of zeroes.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2014-12-10 21:02 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 2:44 [PATCH] libata: Whitelist SSDs that are known to properly return zeroes after TRIM Martin K. Petersen
2014-12-04 3:02 ` Phillip Susi
2014-12-04 3:24 ` Martin K. Petersen
2014-12-04 3:28 ` Phillip Susi
2014-12-04 3:35 ` Martin K. Petersen
2014-12-04 4:40 ` Phillip Susi
2014-12-05 1:53 ` Martin K. Petersen
2014-12-04 21:49 ` One Thousand Gnomes
2014-12-05 2:46 ` Martin K. Petersen
2014-12-04 17:06 ` Tejun Heo
2014-12-05 2:13 ` Martin K. Petersen
2014-12-05 14:51 ` Tejun Heo
2014-12-10 4:09 ` James Bottomley
2014-12-10 14:29 ` Tejun Heo
2014-12-10 20:34 ` James Bottomley
2014-12-10 21:02 ` Martin K. Petersen [this message]
2014-12-12 8:35 ` Ming Lei
2015-01-05 16:28 ` Tejun Heo
2015-01-07 0:05 ` Martin K. Petersen
2015-01-07 2:54 ` Tejun Heo
2015-01-07 4:15 ` Dave Chinner
2015-01-07 15:26 ` Tejun Heo
2015-01-08 14:28 ` Martin K. Petersen
2015-01-08 15:11 ` Tejun Heo
2015-01-08 15:34 ` Martin K. Petersen
2015-01-08 15:36 ` Tejun Heo
2015-01-08 15:58 ` Tim Small
2015-01-09 20:52 ` Martin K. Petersen
2015-01-09 21:39 ` Tejun Heo
2015-01-08 14:29 ` Martin K. Petersen
2015-01-08 4:05 ` Phillip Susi
2015-01-08 4:58 ` Andreas Dilger
2015-01-08 14:09 ` Phillip Susi
2015-01-08 22:31 ` Andreas Dilger
2014-12-10 15:43 ` Tim Small
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=yq1oarbcj6f.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-ide@vger.kernel.org \
--cc=tj@kernel.org \
/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.