Dave's PCF WIP: Paragraphs

Paragraph #3,073

Edit Paragraph

View List Paragraphs Delete

Application

Matter Number

Paragraph Number

Application Number

Reference Case 1

Reference Case 2

Content

The read data pipeline 108 includes a depacketizer 324 that receives ECC blocks of the requested packet from the ECC correction module 322, directly or indirectly, and checks and removes one or more packet headers. The depacketizer 324 may validate the packet headers by checking packet identifiers, data length, data location, etc. within the headers. In one embodiment, the header includes a hash code that can be used to validate that the packet delivered to the read data pipeline 108 is the requested packet. The depacketizer 324 also removes the headers from the requested packet added by the packetizer 302. The depacketizer 324 may directed to not operate on certain packets but pass these forward without modification. An example might be a container label that is requested during the course of a rebuild process where the header information is required by the object index reconstruction module 272. Further examples include the transfer of packets of various types destined for use within the solid-state storage device 102. In another embodiment, the depacketizer 324 operation may be packet type dependent.

Notes

Raw Data

<w:p><w:pPr><w:pStyle w:val="TPSBody100"/></w:pPr><w:r><w:t xml:space="preserve">The read data pipeline </w:t></w:r><w:r><w:t>108</w:t></w:r><w:r><w:t xml:space="preserve"> includes a depacketizer </w:t></w:r><w:r><w:t>324</w:t></w:r><w:r><w:t xml:space="preserve"> that receives ECC blocks of the requested packet from the ECC correction module </w:t></w:r><w:r><w:t>322</w:t></w:r><w:r><w:t xml:space="preserve">, directly or indirectly, and checks and removes one or more packet headers. The depacketizer </w:t></w:r><w:r><w:t>324</w:t></w:r><w:r><w:t xml:space="preserve"> may validate the packet headers by checking packet identifiers, data length, data location, etc. within the headers. In one embodiment, the header includes a hash code that can be used to validate that the packet delivered to the read data pipeline </w:t></w:r><w:r><w:t>108</w:t></w:r><w:r><w:t xml:space="preserve"> is the requested packet. The depacketizer </w:t></w:r><w:r><w:t>324</w:t></w:r><w:r><w:t xml:space="preserve"> also removes the headers from the requested packet added by the packetizer </w:t></w:r><w:r><w:t>302</w:t></w:r><w:r><w:t xml:space="preserve">. The depacketizer </w:t></w:r><w:r><w:t>324</w:t></w:r><w:r><w:t xml:space="preserve"> may directed to not operate on certain packets but pass these forward without modification. An example might be a container label that is requested during the course of a rebuild process where the header information is required by the object index reconstruction module </w:t></w:r><w:r><w:t>272</w:t></w:r><w:r><w:t xml:space="preserve">. Further examples include the transfer of packets of various types destined for use within the solid-state storage device </w:t></w:r><w:r><w:t>102</w:t></w:r><w:r><w:t xml:space="preserve">. In another embodiment, the depacketizer </w:t></w:r><w:r><w:t>324</w:t></w:r><w:r><w:t xml:space="preserve"> operation may be packet type dependent.</w:t></w:r></w:p>