From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Using BTRFS on SSD now ?
Date: Fri, 6 Jun 2014 00:35:08 +0000 (UTC) [thread overview]
Message-ID: <pan$d0f6f$958f1e6e$ae08a321$8fc7bdc5@cox.net> (raw)
In-Reply-To: yq14mzyzz6l.fsf@sermon.lab.mkp.net
Martin K. Petersen posted on Thu, 05 Jun 2014 19:58:26 -0400 as excerpted:
>>>>>> "Duncan" == Duncan <1i5t5.duncan@cox.net> writes:
>
> Duncan> OTOH, certain high-performance hardware goes beyond the current
> Duncan> standard and does a queued trim, without forcing a flush of the
> Duncan> queue in the process. But this hardware tends to be rather rare
> Duncan> and expensive,
>
> Queued trim has started to appear in consumer SSDs. However, since we're
> the only OS that supports it the feature has come off to a bumpy start.
> We tried to enable it on a drive model that passed testing here but we
> had to revert to unqueued when bug reports started rolling in this week.
[more elided]
Thanks. Fresher and better information than I had. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2014-06-06 0:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 13:30 Using BTRFS on SSD now ? Swâmi Petaramesh
2014-06-05 14:42 ` Russell Coker
2014-06-05 15:14 ` Swâmi Petaramesh
2014-06-05 16:26 ` Marc MERLIN
2014-06-05 18:34 ` Chris Murphy
2014-06-05 14:56 ` Marc MERLIN
2014-06-05 15:11 ` Roman Mamedov
2014-06-08 14:26 ` Pavel Volkov
2014-06-05 15:59 ` Christoph Anton Mitterer
2014-06-05 17:07 ` Swâmi Petaramesh
2014-06-05 18:13 ` Chris Murphy
2014-06-05 19:05 ` Marc MERLIN
2014-06-05 22:25 ` Duncan
2014-06-05 23:58 ` Martin K. Petersen
2014-06-06 0:24 ` Chris Murphy
2014-06-06 0:35 ` Duncan [this message]
2014-06-08 14:48 ` Pavel Volkov
2014-06-08 16:51 ` Martin K. Petersen
2014-06-05 21:15 ` Duncan
2014-06-05 16:17 ` Martin Steigerwald
2014-06-05 18:00 ` Chris Murphy
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='pan$d0f6f$958f1e6e$ae08a321$8fc7bdc5@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.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 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).