BOUNCE t10 at t10.org: Non-member submission from ["Yamini" <Yamini at medusalabs.com>]

[T10 Reflector Admin by way of John Lohmeyer <john.lohmeyer@lsil.com>]

Formatted message: <A HREF="r0603041_f.htm">HTML-formatted message</A>

Date: Sat, 04 Mar 2006 10:00:07 -0600
From: "Yamini" <Yamini at medusalabs.com>
To: t10 at t10.org, elliott at hp.com
Subject: Re: Redundant primitive sequences
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="_0304-1000-07-PART-BREAK"
--_0304-1000-07-PART-BREAK
Content-Type: text/plain
Hello,
Still waiting for an answer to my question in the folloing email.
Thanks,
Yamini
-----Original Message-----
From: "Yamini" <Yamini at medusalabs.com>
To: t10 at t10.org, elliott at hp.com
Date: Tue, 07 Feb 2006 22:39:55 -0600
Subject: Redundant primitive sequences
Hello,
I have a question about Primitive Sequences. The number of primitives that a
sender can send in a Redundant Primitive Sequence is not clearly mentioned
in the spec. I hope someone from the reflector can clarify this for me.
'Figure 131 - redundant primitive sequence' in	SAS spec 2.0(sas2r00.pdf)
shows 10 back to back Primitives in a redundant sequence. Is this legal?
The reason why ask is that the text preceeding this figure says:
"
7.2.4.6 Redundant primitive sequence
Primitives that form redundant primitive sequences (e.g., BROADCAST
(CHANGE)) shall be sent six times consecutively. ALIGNs and NOTIFYs may be
sent inside primitive sequences as described in 7.2.4.1.
A receiver shall detect a redundant primitive sequence after the identical
primitive is received in three
consecutive dwords. After receiving a redundant primitive sequence, a
receiver shall not detect a second instance of the same redundant primitive
sequence until it has received six consecutive dwords that are not
any of the following:
a) the original primitive; or
b) an ALIGN or NOTIFY."
I interpret it as the sender SHALL only send six consecutive primitives. So
is sending more than 6 primitives in a redundant sequence an error? Also, is
sending sequences without a six dword gap in between sequences legal? The
above section from the spec states clearly about the receiver's requirements
but not the sender's side.
Thanks in advance,
Yamini
Thanks,
Yamini
--_0304-1000-07-PART-BREAK
Content-Type: text/html
Hello,
Still waiting for an answer to my question in the folloing email.
Thanks,
Yamini
-----Original Message-----
From: "Yamini" <Yamini at medusalabs.com>
To: t10 at t10.org, elliott at hp.com
Date: Tue, 07 Feb 2006 22:39:55 -0600
Subject: Redundant primitive sequences
Hello,
I have a question about Primitive Sequences. The number of primitives that a
sender can send in a Redundant Primitive Sequence is not clearly mentioned in
the spec. I hope someone from the reflector can clarify this for me.
'Figure 131 - redundant primitive sequence' in	SAS spec 2.0(sas2r00.pdf)
shows 10 back to back Primitives in a redundant sequence. Is this legal?
The reason why ask is that the text preceeding this figure says:
"
7.2.4.6 Redundant primitive sequence
Primitives that form redundant primitive sequences (e.g., BROADCAST (CHANGE))
shall be sent six times consecutively. ALIGNs and NOTIFYs may be sent inside
primitive sequences as described in 7.2.4.1.
A receiver shall detect a redundant primitive sequence after the identical
primitive is received in three
consecutive dwords. After receiving a redundant primitive sequence, a
receiver shall not detect a second instance of the same redundant primitive
sequence until it has received six consecutive dwords that are not
any of the following:
a) the original primitive; or
b) an ALIGN or NOTIFY."
I interpret it as the sender SHALL only send six consecutive primitives. So
is sending more than 6 primitives in a redundant sequence an error? Also, is
sending sequences without a six dword gap in between sequences legal? The
above section from the spec states clearly about the receiver's requirements
but not the sender's side.
Thanks in advance,
Yamini
Thanks,
Yamini
--_0304-1000-07-PART-BREAK--