From: Greg Freemyer <greg.freemyer@gmail.com>
To: Ric Wheeler <rwheeler@redhat.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
"Martin K. Petersen" <mkp@mkp.net>,
Matthew Wilcox <matthew@wil.cx>, 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: Sun, 8 Feb 2009 15:06:44 -0500 [thread overview]
Message-ID: <87f94c370902081206v71106c5fp9a7ef0400301a1ab@mail.gmail.com> (raw)
In-Reply-To: <498DA052.6090605@redhat.com>
On Sat, Feb 7, 2009 at 9:53 AM, Ric Wheeler <rwheeler@redhat.com> 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.
I found a list of T10 activities just since just Dec. 1, 2008 and it
is a bit overwhelming. (ie. 08-356r4 is but one of many recent
reports)
http://www.t10.org/new_a.htm
For those of us that don't live and breath the SCSI spec, is there an
overview site describing what is going on.
Maybe:
09-059r0 T10 Project Summary - January 2009 John Lohmeyer PDF
(34729) 2009/01/22
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-059r0.pdf
I have not read any of the Post Dec. 1 stuff including the above
project summary, but based on the names these seem potentially
relevant:
09-055r0 T13 Liaison Report January 09 Dan Colegrove PDF (4770) 2009/01/15
08-356r4 SBC-3: WRITE SAME unmap bit David L. Black PDF (56608) 2008/12/10
08-356r5 SBC-3 Thin Provisioning Commands Fred Knight, David L.
Black PDF (387549) 2009/01/15
08-149r7 SBC - Thin Provisioning Frederick Knight PDF (281001) 2008/12/08
08-149r8 SBC - Thin Provisioning Frederick Knight PDF (281387) 2009/01/09
09-011r1 SBC-3 Thin Provisioning Threshold Notification Frederick
Knight PDF (32757) 2009/01/09
08-149r9 SBC - Thin Provisioning Frederick Knight PDF (353888) 2009/01/15
09-012r0 Minutes: CAP - Thin Provisioning 12/4 con-call Frederick
Knight PDF (38063) 2008/12/08
09-011r0 SBC-3 Thin Provisioning Threshold Notification Frederick
Knight PDF (48523) 2008/12/08
08-396r3 SPC-4: Reporting support for all DIF types George Penokie
PDF (85358) 2009/01/14
09-058r0 Agenda for T10 Meeting #90 March 2009 John Lohmeyer PDF
(61437) 2009/01/19
09-020r0 T11 Liaison Report, December 2008 Robert Snively PDF
(13117) 2008/12/19
09-032r0 Minutes of T10 Plenary Meeting #89 - January 15, 2009 Weber
& Lohmeyer HTM (141593) 2009/01/23
09-032r0 Minutes of T10 Plenary Meeting #89 - January 15, 2009 Weber
& Lohmeyer PDF (344891) 2009/01/23
Greg
--
Greg Freemyer
Litigation Triage Solutions Specialist
http://www.linkedin.com/in/gregfreemyer
First 99 Days Litigation White Paper -
http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf
The Norcross Group
The Intersection of Evidence & Technology
http://www.norcrossgroup.com
next prev parent reply other threads:[~2009-02-08 20:06 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
2009-02-07 23:46 ` Jeff Garzik
2009-02-08 0:24 ` Matthew Wilcox
2009-02-08 20:06 ` Greg Freemyer [this message]
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=87f94c370902081206v71106c5fp9a7ef0400301a1ab@mail.gmail.com \
--to=greg.freemyer@gmail.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=dwmw2@infradead.org \
--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).