Log page consistency

Kevin D Butt kdbutt at us.ibm.com
Wed Oct 7 08:39:21 PDT 2009

Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r0910072_f.htm">HTML-formatted message</a>
Attachment #1: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r0910072_nameless-4068-5.gif">nameless-4068-5.gif</a>
Attachment #2: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r0910072_nameless-4068-6.gif">nameless-4068-6.gif</a>
Attachment #3: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r0910072_nameless-4068-7.gif">nameless-4068-7.gif</a>
Attachment #4: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r0910072_nameless-4068-8.gif">nameless-4068-8.gif</a>
Attachment #5: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r0910072_nameless-4068-9.gif">nameless-4068-9.gif</a>
Attachment #6: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r0910072_nameless-4068-10.gif">nameless-4068-10.gif</a>
Attachment #7: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r0910072_nameless-4068-11.gif">nameless-4068-11.gif</a>
Attachment #8: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r0910072_nameless-4068-12.gif">nameless-4068-12.gif</a>
Attachment #9: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r0910072_nameless-4068-13.gif">nameless-4068-13.gif</a>

I am not comfortable adding a list of which commands to which the counters 
apply.	For one, probably the least important reason, a list of commands 
if desired would belong in the command set standards.
Kevin D. Butt
SCSI & Fibre Channel Architect, Tape Firmware
MS 6TYA, 9000 S. Rita Rd., Tucson, AZ 85744
Tel: 520-799-5280
Fax: 520-799-2723 (T/L:321)
Email address: kdbutt at us.ibm.com
Gerry.Houlder at seagate.com
t10 at t10.org
10/07/2009 08:08 AM
Re: Log page consistency
Sent by:
owner-t10 at t10.org
My suggestion for achieving this goal would be:
(a) have an overview clause that introduces the four log pages and 
includes a generic "log page header with a number of parameters" table and 
a generic "parameter descriptor with header and parameter bytes" table.
(b) Have 4 sub-clauses, one for each log page, that consist of a parameter 
table (i.e., a table showing each parameter number and parameter 
description in a row of the table) and a unique description of each 
parameter. The parameter descriptions (or maybe boilerplate at the start 
of each sub-clause) should include a list of commands for which the 
counters apply; we may need to decide whether to include such new commands 
like ORWRITE and nuclear Test and Set in these lists. We may have to 
re-establish whether each counter applies to bytes transferred over the 
interface or to bytes transferred to/ from the medium (I think we intended 
"transferred over the interface" but that isn't clear in the existing 
(c) We may want to sprinkle in some implementation guidance. For example, 
recommend that parameter lengths be a multiple of four and perhaps 
recommend a minimum parameter length for each parameter. This is new 
material needs discussion at a CAP meeting.
Ralph Weber <roweber at IEEE.org>
Ralph Weber <roweber at IEEE.org> 
Sent by: owner-t10 at t10.org
No Phone Info Available 
10/06/2009 04:39 PM
"'t10 at t10.org'" <t10 at t10.org>
Log page consistency
* From the T10 Reflector (t10 at t10.org), posted by:
* Ralph Weber <roweber at ieee.org>
One of the recently espoused goals it to "describe all
log pages consistently".
This goal might be taken to mean that each and every
log page should be described in a separate subclause.
If this interpretation of the goal is applied to SPC-4,
then the subclause numbered 7.2.5 in r22 will become
four subclauses each with approximately the same content.
Does anybody care to express an opinion on the goal
and/or its interpretation?
All the best,
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org
[attachment "pic26177.gif" deleted by Kevin D Butt/Tucson/IBM] 

More information about the T10 mailing list