From: Chris Worley <worleys@gmail.com>
To: "Scott E. Armitage" <launchpad@scott.armitage.name>
Cc: Roberto Spadim <roberto@spadim.com.br>,
David Brown <david@westcontrol.com>,
linux-raid@vger.kernel.org
Subject: Re: SSD - TRIM command
Date: Wed, 9 Feb 2011 08:52:55 -0700 [thread overview]
Message-ID: <AANLkTim-S0nTC8-r1U2xQ9Gw3EVAZHDjSxT=tnNnHmCT@mail.gmail.com> (raw)
In-Reply-To: <AANLkTik6D-r1ZbgxEACHZK9760pcUBB+3e7wVX3oqrKP@mail.gmail.com>
On Wed, Feb 9, 2011 at 8:00 AM, Scott E. Armitage
<launchpad@scott.armitage.name> wrote:
<snip>
>AFAICT, reading back a trimmed page is
> not defined
... and so should be assumed that reading a trimmed/nonexistant LBA
off of two of the same vendor's SSD's would realize different results?
next prev parent reply other threads:[~2011-02-09 15:52 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 20:07 SSD - TRIM command Roberto Spadim
2011-02-08 17:37 ` maurice
2011-02-08 18:31 ` Roberto Spadim
[not found] ` <AANLkTik5SumqyTN5LZVntna8nunvPe7v38TSFf9eCfcU@mail.gmail.com>
2011-02-08 20:50 ` Roberto Spadim
2011-02-08 21:18 ` maurice
2011-02-08 21:33 ` Roberto Spadim
2011-02-09 7:44 ` Stan Hoeppner
2011-02-09 9:05 ` Eric D. Mudama
2011-02-09 15:45 ` Chris Worley
2011-02-09 13:29 ` David Brown
2011-02-09 14:39 ` Roberto Spadim
2011-02-09 15:00 ` Scott E. Armitage
2011-02-09 15:52 ` Chris Worley [this message]
2011-02-09 19:15 ` Doug Dumitru
2011-02-09 19:22 ` Roberto Spadim
2011-02-09 16:19 ` Eric D. Mudama
2011-02-09 16:28 ` Scott E. Armitage
2011-02-09 17:17 ` Eric D. Mudama
2011-02-09 18:18 ` Roberto Spadim
2011-02-09 18:24 ` Piergiorgio Sartor
2011-02-09 18:30 ` Roberto Spadim
2011-02-09 18:38 ` Piergiorgio Sartor
2011-02-09 18:46 ` Roberto Spadim
2011-02-09 18:52 ` Roberto Spadim
2011-02-09 19:13 ` Piergiorgio Sartor
2011-02-09 19:16 ` Roberto Spadim
2011-02-09 19:21 ` Piergiorgio Sartor
2011-02-09 19:27 ` Roberto Spadim
2011-02-21 18:24 ` Phillip Susi
2011-02-21 18:30 ` Roberto Spadim
2011-02-09 15:49 ` David Brown
2011-02-21 18:20 ` Phillip Susi
2011-02-21 18:25 ` Roberto Spadim
2011-02-21 18:34 ` Phillip Susi
2011-02-21 18:48 ` Roberto Spadim
2011-02-21 18:51 ` Mathias Burén
2011-02-21 19:32 ` Roberto Spadim
2011-02-21 19:38 ` Mathias Burén
2011-02-21 19:39 ` Mathias Burén
2011-02-21 19:43 ` Roberto Spadim
2011-02-21 20:45 ` Phillip Susi
2011-02-21 19:39 ` Roberto Spadim
2011-02-21 19:51 ` Doug Dumitru
2011-02-21 19:57 ` Roberto Spadim
2011-02-21 20:47 ` Phillip Susi
2011-02-21 21:02 ` Mathias Burén
2011-02-21 22:52 ` Roberto Spadim
2011-02-21 23:41 ` Mathias Burén
2011-02-21 23:42 ` Mathias Burén
2011-02-21 23:52 ` Roberto Spadim
2011-02-22 0:25 ` Mathias Burén
2011-02-22 0:30 ` Brendan Conoboy
2011-02-22 0:36 ` Eric D. Mudama
2011-02-22 1:46 ` Roberto Spadim
2011-02-22 1:52 ` Mathias Burén
2011-02-22 1:55 ` Roberto Spadim
2011-02-22 2:01 ` Eric D. Mudama
2011-02-22 2:02 ` Mikael Abrahamsson
2011-02-22 2:22 ` Guy Watkins
2011-02-22 2:27 ` Roberto Spadim
2011-02-22 3:45 ` NeilBrown
2011-02-22 4:37 ` Roberto Spadim
2011-02-22 2:38 ` Phillip Susi
2011-02-22 3:29 ` Roberto Spadim
2011-02-22 3:42 ` Roberto Spadim
2011-02-22 4:04 ` Phillip Susi
2011-02-22 4:30 ` Roberto Spadim
2011-02-22 14:45 ` Phillip Susi
2011-02-22 17:15 ` Roberto Spadim
2011-02-22 0:32 ` Eric D. Mudama
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='AANLkTim-S0nTC8-r1U2xQ9Gw3EVAZHDjSxT=tnNnHmCT@mail.gmail.com' \
--to=worleys@gmail.com \
--cc=david@westcontrol.com \
--cc=launchpad@scott.armitage.name \
--cc=linux-raid@vger.kernel.org \
--cc=roberto@spadim.com.br \
/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).