SAS DONE timers
Elliott, Robert (Server Storage)
Elliott at hp.com
Tue Jul 18 11:45:19 PDT 2006
Attachment #1: <A HREF="r0607180_smime.p7s">smime.p7s</A>
> -----Original Message-----
> From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf
> Of Richard Deglin
> Sent: Monday, July 17, 2006 1:36 PM
> To: t10 at t10.org
> Subject: SAS DONE timers
> I have been studying section 126.96.36.199 of the SAS-1.1 standard
> and I have a few questions.
> 1. What exactly does paragraph 6 mean, when it says "the DONE Timeout
> timer shall be reinitialized" ?
Set it to its initial value (1 ms, per table 119 in sas2r04a).
> 2. Why does the ACK/NAK timeout situation treat incoming EOF
> than the other states? Just curious about the reasoning for this
When a phy sends DONE (any reason), it starts the 1 ms timer.
If it sent DONE (NORMAL) or DONE (CREDIT TIMEOUT), it will
keep reinitializing the DONE timeout timer if the other side
continues to send frames; useful work is still being performed.
If it sent DONE (ACK/NAK TIMEOUT), it does not keep reinitializing
the timer, since this is an error condition and it needs to
close the connection.
> Also, I cannot find any specific definitions of the terms used when
> describing timer operations, such as initialize, reinitialize, start,
> stop, etc. Did I miss something?
Those are intended to be common engineering terms. A timer is
intialized to a certain value. Once started, it counts down. Once
stopped, it stops counting. When it reaches zero, it is considered
to be expired.
> Rich Deglin
> Principal Software Engineer
> Storage Products Division
> Vitesse Semiconductor
> Milpitas, CA
Rob Elliott, elliott at hp.com
Hewlett-Packard Industry Standard Server Storage Advanced Technology
More information about the T10