Frame termination condition?
Elliott, Robert (Server Storage)
Elliott at hp.com
Mon Nov 11 08:42:22 PST 2002
* From the T10 Reflector (t10 at t10.org), posted by:
* "Elliott, Robert (Server Storage)" <Elliott at hp.com>
The link layer discards a frame if 1052 bytes appear after an SOF
without an EOF (see the SSP Receive Frame Control state machine
Disparity errors and invalid characters should not cause immediate frame
discard; they should result in a CRC error and a NAK.
Rob Elliott, elliott at hp.com
Industry Standard Server Storage Advanced Technology
> -----Original Message-----
> From: Seto, Pak-lung [mailto:pak-lung.seto at intel.com]
> Sent: Friday, November 08, 2002 11:26 AM
> To: 't10 at t10.org'
> Subject: Frame termination condition?
> * From the T10 Reflector (t10 at t10.org), posted by:
> * "Seto, Pak-lung" <pak-lung.seto at intel.com>
> How to determine a frame has been received?
> A normal frame started with SOF and ended with EOF and the
> maximum payload of a SAS frame is 1024. In SAS, it allows
> certain primitive sequences to be inserted between SOF and
> EOF. Therefore, in theory, a frame can last for a long time
> with inserted ALIGNs required by the standard or or rate
> matching. What happen if hte EOF got corrupted or mutated?
> and the frame recipient keep receiving legal primitive
> sequences. When can a SAS receiving port abort "a frame"?
> Does disparity error or dword decoding error treminate a
> frame immediately? It is unclear in the spec. what can or
> cannot terminate a frame and when a frame can be terminated
> under all conditions.
> * 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