linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ric Wheeler <rwheeler@redhat.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Greg Freemyer <greg.freemyer@gmail.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: Sun, 08 Feb 2009 19:01:23 -0500	[thread overview]
Message-ID: <498F7253.1070002@redhat.com> (raw)
In-Reply-To: <20090208204434.GF31509@parisc-linux.org>

Matthew Wilcox wrote:
> On Sun, Feb 08, 2009 at 03:06:44PM -0500, Greg Freemyer wrote:
>   
>> 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.
>>     
>
> I've been working off 08-149r7.pdf.  I'm sure that's been superseded by
> now.  
>
>   
>> 08-356r4 	SBC-3: WRITE SAME unmap bit 	David L. Black 	PDF (56608)	2008/12/10
>>     
>
> Probably interesting.  Haven't read it myself.
>   

This is only a four page proposal - basically, we would use the write 
same command with a special unmap bit set to tell the target that it may 
(at its option) unmap the blocks. If not, it would in fact have to set 
the data to the indicated pattern in the command which I presume would 
be all zeros in the normal case.
>   
>> 08-356r5 	SBC-3 Thin Provisioning Commands 	Fred Knight, David L.
>> Black 	PDF (387549)	2009/01/15
>>     
>
> Fred Knight seems to be the main coordinator of this effort, so yes.
>   

Fred and David Black both have been quite active.
>   
>> 08-149r7 	SBC - Thin Provisioning 	Frederick Knight 	PDF (281001)	2008/12/08
>>     
>
> That's the one I'm working from.
>
>   
>> 08-149r8 	SBC - Thin Provisioning 	Frederick Knight 	PDF (281387)	2009/01/09
>>     
>
> A newer version ... thought so.
>
>   
>> 09-011r1 	SBC-3 Thin Provisioning Threshold Notification 	Frederick
>> Knight 	PDF (32757)	2009/01/09
>>     
>
> Clearly related.
>
>   
>> 08-149r9 	SBC - Thin Provisioning 	Frederick Knight 	PDF (353888)	2009/01/15
>>     
>
> Even newer version of what I've been working from.
>
>   
>> 09-012r0 	Minutes: CAP - Thin Provisioning 12/4 con-call 	Frederick
>> Knight 	PDF (38063)	2008/12/08
>>     
>
> Probably tedious.
>
>   
>> 08-396r3 	SPC-4: Reporting support for all DIF types 	George Penokie
>> 	PDF (85358)	2009/01/14
>>     
>
> Unrelated, I would think.
>
> I'd go with 08-149r9 to get a good overview.
>
>   


      reply	other threads:[~2009-02-09  0:01 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
2009-02-08 20:44         ` Matthew Wilcox
2009-02-09  0:01           ` Ric Wheeler [this message]

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=498F7253.1070002@redhat.com \
    --to=rwheeler@redhat.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=dwmw2@infradead.org \
    --cc=greg.freemyer@gmail.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 \
    /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).