[T10] Doc 21-081r0 [was] RE: Recent T10 documents uploaded since 2021/07/03

John Geldman John.Geldman at kioxia.com
Sat Jul 10 17:38:18 PDT 2021


Then I found the right rabbit eventually.

My point on flash technology was only related to JEDEC's UFS (JESD 220e), as a puzzling originator for this proposal. Quite the wrong rabbit hole.

I have $0.25 burning a virtual hole in a virtual pocket to bet that the authors of JESD 220e do not care about T10 ZBC related proposals.

I was not asking for changes, just clarity, and I think we are there.

Thank you for the clarification,

From: t10-bounces at t10.org <t10-bounces at t10.org> On Behalf Of Ralph Weber
Sent: Saturday, July 10, 2021 4:01 PM
To: T10 Reflector <t10 at t10.org>
Subject: Re: [T10] Doc 21-081r0 [was] RE: Recent T10 documents uploaded since 2021/07/03


Regarding the "ordered" a,b list... Although much of the motivation is beyond what my aging grey matter can fully comprehend, I am under the strong impression that the "ordered" list can only be corrected by adding an additional entry:
"c) all of the above"
Thankfully, my meager efforts in T10 are buttressed by a multitude of experts in a wide variety of storage technology, operation systems, and mobile devices.

With respect to the "mobile focused device feature optimization (largely used for Flash technology)" observation... Perhaps it would not be talking too far out of school to note that:

  *   NVMe is optimized for ... Flash technology; and
  *   NVMe Zoned Namespaces (kissing cousins of ZBC-2 devices) are intended to improve the performance of support for Flash technology.

In summary, there seems to be a very good possibility that you are chasing the right rabbit down the right rabbit hole.

All the best,

On 7/10/2021 5:12 PM, John Geldman wrote:


I read the introduction to 21-081 and got myself a bit confused about context.

I suspect my racing focus may have followed the wrong rabbit down the wrong rabbit hole.

There are at least two possible contexts for a reference to UFS for SCSI:

1.       UFS: mobile devices that use the SCSI specifications (pre-final SAM-5/SPC-4/SBC-3 context (currently my overdue action to repair to final, mea culpa)); and

2.       UFS: UNIX File System.

(for me this is more of an ordered list 8-)

I was struggling with the incongruity of adding a mobile focused device feature optimization (largely used for Flash technology) to a data center focused interface specification (largely used for HDD technology) when my focus resolved, revealing that there might be multiple bouncy balls to follow.

21-081 is referencing the UNIX File system, correct?

Thank you,


-----Original Message-----
From: t10-bounces at t10.org<mailto:t10-bounces at t10.org> <t10-bounces at t10.org><mailto:t10-bounces at t10.org> On Behalf Of DoNotReply at t10.org<mailto:DoNotReply at t10.org>
Sent: Saturday, July 10, 2021 12:02 AM
To: T10 Reflector <t10 at t10.org><mailto:t10 at t10.org>
Subject: [T10] Recent T10 documents uploaded since 2021/07/03



SAT-5: Document the HRDRMACT bit for microcode download mode 0Eh

(by: Ralph Weber)

T10/21-071r1   Uploaded: 2021/07/08   73025 bytes


ZBC-2: Adding Zone Capacities that are different from Zone Lengths

(by: Ralph Weber)

T10/21-081r0   Uploaded: 2021/07/07   101216 bytes


SPL-5: TTIU decoding

(by: Tim Symons)

T10/21-088r0   Uploaded: 2021/07/07   251729 bytes


ZBC-2: Demystifying Zone Type Code Points

(by: Ralph Weber)

T10/21-092r0   Uploaded: 2021/07/09   69639 bytes


Working Drafts


(Report generated on 2021/07/10 at 00:02:13)


T10 mailing list

T10 at t10.org<mailto:T10 at t10.org>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.t10.org/pipermail/t10/attachments/20210711/7fe9b4f7/attachment.html>

More information about the T10 mailing list