From: "David Woodhouse" <dwmw2@infradead.org>
To: "Matthew Wilcox" <matthew@wil.cx>
Cc: "Ric Wheeler" <rwheeler@redhat.com>,
"David Woodhouse" <dwmw2@infradead.org>,
"James Bottomley" <james.bottomley@hansenpartnership.com>,
"Martin K. Petersen" <mkp@mkp.net>,
"Jeff Garzik" <jeff@garzik.org>,
linux-scsi@vger.kernel.org, linux-fsdevel@vger.kernel.org,
"IDE/ATA development list" <linux-ide@vger.kernel.org>
Subject: Re: TRIM vs UNMAP vs WRITE SAME and thin devices
Date: Sat, 7 Feb 2009 23:36:07 -0000 (UTC) [thread overview]
Message-ID: <6e1133942a9f20e058e117a24fad9199.squirrel@baythorne.infradead.org> (raw)
In-Reply-To: <20090207224722.GA31509@parisc-linux.org>
> On Sat, Feb 07, 2009 at 09:53:06AM -0500, Ric Wheeler wrote:
>> I have been poked at by some vendors about the status of our support for
>> the virtually/thinly provisioned luns since they are getting close to
>> being able to test with real devices.
>>
>> My quick summary is that we most of the work so far has been done
>> without any real hardware to play with - in 2.6.29-rc3, I don't see any
>> low level ATA or SCSI bits that turn requests tagged with REQ_DISCARD
>> into the specific ATA or SCSI commands. Did I miss something & if not,
>> do we have plans to push anything upstream soonish?
>
> Bearing in mind that I'm now three weeks behind on email, you might want
> to look at
> http://git.kernel.org/?p=linux/kernel/git/willy/ssd.git;a=shortlog;h=trim-20081231
> which has at least one known bug (fixed by Dave Woodhouse and Ben
> Herrenschmidt). I'll be able to give a more coherent answer in a few
> days. Or maybe Dave will beat me to it ;-)
Ben's suggestion was that the IDE core wouldn't be sending the payload of
the command because it looks at the R/W bit... which is clear (read) in
our discard requests ATM. Making them appear to be writes is simple enough
though. I gave an updated test kernel to the Sandisk folks but haven't got
results back from them yet.
next prev parent reply other threads:[~2009-02-07 23:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090123041558.GC24652@parisc-linux.org>
[not found] ` <4979AF62.7070409@redhat.com>
[not found] ` <1232721777.4430.7.camel@macbook.infradead.org>
2009-02-07 14:53 ` TRIM vs UNMAP vs WRITE SAME and thin devices Ric Wheeler
2009-02-07 15:09 ` James Bottomley
2009-02-07 16:14 ` Ric Wheeler
2009-02-12 13:51 ` Eyal Shani
2009-03-23 19:05 ` Greg Freemyer
2009-03-23 19:23 ` Mark Lord
2009-02-07 22:50 ` Matthew Wilcox
2009-02-07 23:03 ` James Bottomley
2009-02-08 16:47 ` Ric Wheeler
2009-02-08 20:50 ` Matthew Wilcox
2009-02-08 23:58 ` Ric Wheeler
2009-02-07 22:47 ` Matthew Wilcox
2009-02-07 23:36 ` David Woodhouse [this message]
2009-02-07 23:46 ` Jeff Garzik
2009-02-08 0:24 ` Matthew Wilcox
2009-02-08 20:06 ` Greg Freemyer
2009-02-08 20:44 ` Matthew Wilcox
2009-02-09 0:01 ` Ric Wheeler
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=6e1133942a9f20e058e117a24fad9199.squirrel@baythorne.infradead.org \
--to=dwmw2@infradead.org \
--cc=james.bottomley@hansenpartnership.com \
--cc=jeff@garzik.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=mkp@mkp.net \
--cc=rwheeler@redhat.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 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).