As I said previously, I was researching to implement VAAI for ietd,
and recently I was pointed to T10 spec that has explanation of all the
VAAI primitives, the SBC spec is accessible but the SPC-3 spec is
only accessible to the T10 members. Does someone here have access to
it? I'm not even sure whether that's something I should read actually,
command 93 WRITE_SAME(16) seems to be defined in SBC part.
Cheers.
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Iscsitarget-devel mailing list
Iscsitar...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/iscsitarget-devel
Perhaps you can ask whomever pointed you to said spec for a copy of at
least the relevant sections?
On 03/23/2012 07:46 PM, Yucong Sun (叶雨飞) wrote:
> no one? I guess that makes things harder....
>
> On Wed, Mar 21, 2012 at 10:30 AM, Yucong Sun (叶雨飞) <suny...@gmail.com> wrote:
>> Hi,
>>
>> As I said previously, I was researching to implement VAAI for ietd,
>> and recently I was pointed to T10 spec that has explanation of all the
>> VAAI primitives, the SBC spec is accessible but the SPC-3 spec is
>> only accessible to the T10 members. Does someone here have access to
>> it? I'm not even sure whether that's something I should read actually,
>> command 93 WRITE_SAME(16) seems to be defined in SBC part.
>>
>> Cheers.
>
--
Lee Duncan
SUSE Labs
But once a draft is agreed upon, i.e. become the current standard, then
you have to be a "member" to get a copy. Or, I think you can buy a copy
at non-member prices, but that's going on my hazy memory, so don't quote
me on that one.
Here's a link to the current SPC-4 standard:
http://www.t10.org/cgi-bin/ac.pl?t=f&f=spc4r35.pdf
(link requires free registration)
It's certainly possible that somebody that's been around a while would
have a _draft_ version of SPC-3 that they downloaded before it was
finalized, but even so such a copy would not represent the current SPC-3
standard.
Maybe somebody wanted to refer you to something that is in SPC-3 that is
not present (has been removed) from SPC-4, but if so I'd ask "why?".
However I and Ross decided we should play safe on certain
interpretation, so a new patch would be post here soon.
Cheers.