SAS rate matching - ALIGNs in OPEN

Seto, Pak-lung pak-lung.seto at intel.com
Thu Feb 20 06:13:37 PST 2003


* From the T10 Reflector (t10 at t10.org), posted by:
* "Seto, Pak-lung" <pak-lung.seto at intel.com>
*
The receiver can do whatever it want, the receiver should not care about the
requirement of ALIGNs for every 500 or so dwords.  The receiver can even
delete every ALIGN and insert ALIGNs if device needs to retransmit the
dwords whenever it is necessary or required.

Pak


-----Original Message-----
From: Gerry.Houlder at seagate.com [mailto:Gerry.Houlder at seagate.com]
Sent: Wednesday, February 19, 2003 2:13 PM
To: t10 at t10.org
Subject: Re: SAS rate matching - ALIGNs in OPEN


* From the T10 Reflector (t10 at t10.org), posted by:
* Gerry.Houlder at seagate.com
*

I think the important part is how the receiving end is going to figure out
how to remove the rate matching ALIGNs.

What if the rate matching starts with EAOF/ALIGN/ALIGN ? Is the first ALIGN
the one that should be thrown away or the second ALIGN? Could an
implementation intend the first ALIGN as one of the required ALIGNs
(because there has to be several ALIGNs every 500 or so dwords) and the
second ALIGN is the one that should be swallowed?



 

                      "Hoglund, Tim"

                      <thoglund at lsil.c         To:      T10 Reflector
<t10 at t10.org>                             
                      om>                      cc:

                      Sent by:                 Subject: Re: SAS rate
matching - ALIGNs in OPEN                  
                      owner-t10 at t10.or

                      g

                      No Phone Info

                      Available

 

                      02/19/2003 01:19

                      PM

 

 





* From the T10 Reflector (t10 at t10.org), posted by:
* "Hoglund, Tim" <thoglund at lsil.com>
*
I do not agree with imposing a requirement to send a rate-matching ALIGN
immediately following EOAF - this is a needless constraint on
implementations.

The OPEN address frame is not delivered through the topology, rather is
store/forward through expanders, therefore it should not matter whether
the
rate matching ALIGNs begin as EOAF/ALIGN/idle dword or as EOAF/idle
dword/ALIGN.

TimH

~~~~~~~~~~~~~~~~~~~~~~~
Tim.Hoglund at lsil.com
719/533-7450 (Voice)
719/533-7480 (Fax)
~~~~~~~~~~~~~~~~~~~~~~~



-----Original Message-----
From: Elliott, Robert (Server Storage) [mailto:Elliott at hp.com]
Sent: Tuesday, February 18, 2003 2:40 PM
To: t10 at t10.org
Subject: SAS rate matching - ALIGNs in OPEN


* From the T10 Reflector (t10 at t10.org), posted by:
* "Elliott, Robert (Server Storage)" <Elliott at hp.com>
*
sas-r03 7.15 Rate matching says:
    The OPEN address frame itself may or may not have ALIGNs
interspersed.

A letter ballot comment asked that we be very precise in mandating that
the first dword after the OPEN address frame shall be an ALIGN,
yielding:

    After transmitting the OPEN address frame, the source phy shall
start rate matching at the selected connection rate. The first dword
after the EOF shall be an ALIGN or NOTIFY for rate matching.

Should I keep or delete the sentence about ALIGNs (and NOTIFYs) in the
OPEN address frame?  It's true, but might lead someone to think they
should start rate matching in the OPEN (there's probably no reason to do
so).


--
Rob Elliott, elliott at hp.com
Hewlett-Packard Industry Standard Server Storage Advanced Technology
https://ecardfile.com/id/RobElliott



*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org

*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org





*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org




More information about the T10 mailing list