Mode page 1, ECC correction span field expansion?

[Hallam, Ken J]

* From the T10 Reflector (t10 at symbios.com), posted by:
* "Hallam, Ken J" <Ken.Hallam at unisys.com>
*
Anything that Jeff and Jim can agree on gets my vote too!

-----Original Message-----
From: Jim McGrath [mailto:Jim.McGrath at quantum.com]
Sent: Friday, February 12, 1999 3:55 PM
To: 'Jeffrey L Williams'; t10 at Symbios.COM
Subject: RE: Mode page 1, ECC correction span field expansion?


* From the T10 Reflector (t10 at symbios.com), posted by:
* Jim McGrath <Jim.McGrath at quantum.com>
*

I agree with Jeff (!!!)

Jim


> -----Original Message-----
> From:	Jeffrey L Williams [SMTP:Jeffrey.L.Williams at wdc.com]
> Sent:	Friday, February 12, 1999 1:38 PM
> To:	t10 at Symbios.COM
> Subject:	RE: Mode page 1, ECC correction span field expansion?
> 
> * From the T10 Reflector (t10 at symbios.com), posted by:
> * Jeffrey L Williams <Jeffrey.L.Williams at wdc.com>
> *
> I prefer (A).
> 
> Regards,
> Jeff
> 
> Jeffrey L. Williams
> Senior Staff Engineer
> Western Digital Corporation - Rochester
> Enterprise Storage Group
> Office: (507) 286-7589
> Fax: (507) 536-8089
> Pager: (888) 858-PAGE   ID: 120826
> e-mail:  Jeffrey.L.Williams at wdc.com
> 
> ----------
> From:
> 	
> Gerry_Houlder at notes.seagate.com[SMTP:Gerry_Houlder at notes.seagate.com]
> Sent: 	Friday, February 12, 1999 2:53 PM
> To: 	t10 at Symbios.COM
> Subject: 	Mode page 1, ECC correction span field expansion?
> 
> * From the T10 Reflector (t10 at symbios.com), posted by:
> * Gerry_Houlder at notes.seagate.com
> *
> Mode page 1 provides one byte for ECC Correction Span. This has been
> adequate until now, but there are products on the horizon that will have
> correction span of more than 255 bits (this is the maximum that can be
> expressed with one byte. Should this field be expanded? if so, how?
> 
> (a) We could just define 0xFF as meaning "255 or more bits correction
> capability". If the system companies (i.e., buyers of direct access
> devices) never use this field, perhaps this is explanation enough.
> 
> (b) A value of 0xFF could be used as a pointer to another (new) field in
> mode page 1 that provides two bytes to describe the ECC correction span.
> 
> (c) Since the ECC correction span tends to be an unchangeable value, we
> could define an Inquiry VPD page that reports the actual ECC Correction
> Span and maybe some other numbers as well. The values reported on this
> page
> would be the maximum, and the one byte values on Mode Page 1 could be
> redefined to be "percent of maximum" with 0xFF being 100% and lower values
> in increments of 1/256 of the maximum.
> 
> (d) Make your own suggestion on the reflector.
> 
> I would like to have discussion of this issue at the next working group
> meeting in Harrisburg, PA in March. John Lohmeyer, please add this to the
> agenda. If there is reflector discussion that seems to converge on a
> solution we won't have to spend much meeting time on it.
> 
> 
> *
> * For T10 Reflector information, send a message with
> * 'info t10' (no quotes) in the message body to majordomo at symbios.com
> 
> 
> *
> * For T10 Reflector information, send a message with
> * 'info t10' (no quotes) in the message body to majordomo at symbios.com
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at symbios.com
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at symbios.com