Western Digital issues with 'operations' definitions in SBC-3 r35j

Ralph Weber Ralph.Weber at wdc.com
Thu Oct 10 14:28:47 PDT 2013

Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1310103_f.htm">HTML-formatted message</a>

I wish to begin this note with a Thank You to the numerous contributors who
commented upon the previous WD postings on the confusion raised by the
caching changes SBC-3 r35j.
A great deal of floundering about was required to gain true insight regarding
the problems to be resolved, which have proven to be:
  *   an over use of the glossary as coordination point for the true meaning
and usage of "operations", specifically read operations, unmap operations,
verify operations, and write operations;
  *   fuzzy glossary logic promoted as a necessary evil to avoid writing
"read operations and verify operations" in hundreds of places (necessary,
yes, evil, not so much ... as long as enough words, including a 'shall', can
be thrown at the problem, all of which is not the province of the glossary);
  *   uncertainty about how completely the SYNCHRONIZE CACHE aspects of the
VERIFY command had been rendered in the new text.
A proposal that includes detailed text changes based the fruits of the
tedious investigations of these issues is now available:
The changes in this document are at once more wordy and less technical than
anything previously proposed. Reviewing it should provide plenty of
"interesting times".
It goes without saying that WD sees some form of resolution to the issues
described in 13-257r0 as a necessary precursor to publication of SBC-3.
All the best,

More information about the T10 mailing list