Deprecated: Passing query options as paginator settings is deprecated. Use a custom finder through `finder` config instead. Extra keys found are: contain /application/vendor/cakephp/cakephp/src/Datasource/Paging/NumericPaginator.php, line: 189 You can disable all deprecation warnings by setting `Error.errorLevel` to `E_ALL & ~E_USER_DEPRECATED`. Adding `vendor/cakephp/cakephp/src/Datasource/Paging/NumericPaginator.php` to `Error.ignoredDeprecationPaths` in your `config/app.php` config will mute deprecations from that file only. in /application/vendor/cakephp/cakephp/src/Core/functions.php on line 318

Warning: Unable to emit headers. Headers sent in file=/application/vendor/cakephp/cakephp/src/Core/functions.php line=318 in /application/vendor/cakephp/cakephp/src/Http/ResponseEmitter.php on line 71

Warning: Cannot modify header information - headers already sent by (output started at /application/vendor/cakephp/cakephp/src/Core/functions.php:318) in /application/vendor/cakephp/cakephp/src/Http/ResponseEmitter.php on line 164

Warning: Cannot modify header information - headers already sent by (output started at /application/vendor/cakephp/cakephp/src/Core/functions.php:318) in /application/vendor/cakephp/cakephp/src/Http/ResponseEmitter.php on line 197

Warning: Cannot modify header information - headers already sent by (output started at /application/vendor/cakephp/cakephp/src/Core/functions.php:318) in /application/vendor/cakephp/cakephp/src/Http/ResponseEmitter.php on line 197

Warning: Cannot modify header information - headers already sent by (output started at /application/vendor/cakephp/cakephp/src/Core/functions.php:318) in /application/vendor/cakephp/cakephp/src/Http/ResponseEmitter.php on line 235
Dave's PCF WIP: Paragraphs
New Paragraph

Paragraphs

Actions Application Content Paragraph Number Notes Modified
View Edit
Delete
US8762658B2 Claim 21.The system of claim 13, wherein the non-volatile storage medium comprises a NAND flash storage medium. 318 Added by DJM 3 2021 3/24/21, 12:00 AM
View Edit
Delete
US8762658B2 Claim 22.A non-transitory computer-readable storage medium comprising instructions configured to cause a computing device to perform a method, comprising: 319 Added by DJM 3 2021 3/24/21, 12:00 AM
View Edit
Delete
US8762658B2 maintaining an index comprising mappings between logical identifiers and physical storage locations of a non-volatile storage device; 320 Added by DJM 3 2021 3/24/21, 12:00 AM
View Edit
Delete
US8762658B2 receiving an indication, comprising a logical identifier, that the logical identifier mapped to a physical storage location comprising data associated with the logical identifier in the index is empty; and 321 Added by DJM 3 2021 3/24/21, 12:00 AM
View Edit
Delete
US8762658B2 recording persistent data on the non-volatile storage device in response the indication, wherein the persistent data is configured to indicate that the logical identifier is empty. 322 Added by DJM 3 2021 3/24/21, 12:00 AM
View Edit
Delete
US8762658B2 Claim 23.The non-transitory computer-readable storage medium of claim 22, the method further comprising invalidating a data packet in response to the indication. 323 Added by DJM 3 2021 3/24/21, 12:00 AM
View Edit
Delete
US8762658B2 Claim 24.The non-transitory computer-readable storage medium of claim 22, the method further comprising removing the mapping between the logical identifier and the physical storage location from the index in response to the indication. 324 Added by DJM 3 2021 3/24/21, 12:00 AM
View Edit
Delete
US8762658B2 Claim 25.The non-transitory computer-readable storage medium of claim 22, the method further comprising reconstructing the index based on the contents of the non-volatile storage medium, wherein reconstructing comprises determining that the logical identifier is empty in response to the persistent data recorded on the non-volatile storage device while the data associated with the logical identifier remains on the physical storage location. 325 Added by DJM 3 2021 3/24/21, 12:00 AM
View Edit
Delete
US8762658B2 Claim 26.The non-transitory computer-readable storage medium of claim 22, further comprising responding to a request pertaining to the logical identifier with an indication the logical identifier is empty while the data associated with the logical identifier remains on the physical storage location. 326 Added by DJM 3 2021 3/24/21, 12:00 AM
View Edit
Delete
US8762658B2 An apparatus, system, and method are disclosed for managing data with an empty data segment directive at the storage device. The apparatus, system, and method for managing data include a write request receiver module and a data segment token storage module. The write request receiver module receives a storage request from a requesting device. The storage request includes a request to store a data segment in a storage device. The data segment includes a series of repeated, identical characters or a series of repeated, identical character strings. The data segment token storage module stores a data segment token in the storage device. The data segment token includes at least a data segment identifier and a data segment length. The data segment token is substantially free of data from the data segment. 327 Added by DJM 3 2021 3/24/21, 12:00 AM
View Edit
Delete
US8762658B2 In another embodiment, where the requesting device 1326 is expecting to receive a data segment, the apparatus includes a reconstitute data segment module 1318 that reconstitutes data of the data segment using the data segment token. The read request response module 1312 also includes a transmit data segment module 1316 that transmits the reconstituted requested data segment to the requesting device 1326. In another embodiment, the reconstitute data segment module 1318 resides at the requesting device 1326, possibly as in the form of a driver, and the transmit data segment token module 1314 transmits the message with the data segment token information to the requesting device 1326. The reconstitute data segment module 1318 at the requesting device 1326 reconstitutes the requested data segment from the message. 283 Added by DJM 3 2021 3/24/21, 12:00 AM
View Edit
Delete
US8762658B2 The apparatus includes a write request receiver module 1302 that receives a storage request from the requesting device 1326, where the storage request includes a request to store a data segment in the storage device 150. The data segment includes a series of repeated, identical characters or character strings. Typically, the series of repeated, identical characters signify that the data segment is empty. This is especially true when the series of repeated, identical characters are ones or zeros. The apparatus includes a data segment token storage module 1304 that stores a data segment token in the storage device 150. The data segment token includes at least a data segment identifier and a data segment length. The data segment token is substantially free of the actual data from the data segment. 269 Added by DJM 3 2021 3/24/21, 12:00 AM
View Edit
Delete
US8762658B2 The data segment token may be stored in many forms. In one embodiment, includes an entry in an index, where the index corresponds to information and data stored on the storage device 150. For example, the index may be an object index as described above in relation to the apparatus 200 depicted in FIG. 2. The index may also be file system index, a block storage index, or other index known to those of skill in the art. In another embodiment, the data segment token includes or is in the form of metadata stored on the storage device 150. In another embodiment, the data segment token is stored as metadata on the storage device 150 and includes an entry in an index. One of skill in the art will recognize other ways to storage a data segment token. 270 Added by DJM 3 2021 3/24/21, 12:00 AM
View Edit
Delete
US8762658B2 In one embodiment, the storage request includes a token directive to store the data segment token where the storage request is essentially free from data of the data segment. The token directive may include the data segment token or a command to generate a data segment token. Where the token directive does not include the data segment token, the data segment token storage module 1304 generates the data segment token from information in the token directive. If the token directive includes the data segment token, the data segment token storage module 1304 recognizes the data segment token as a data structure representing the data segment identified by the data segment identifier in the token directive and stores the data segment token appropriately. 271 Added by DJM 3 2021 3/24/21, 12:00 AM
View Edit
Delete
US8762658B2 Typically, where the data segment token storage module 1304 recognizes a data segment token, the data segment token is differentiated in some way from other data stored on the storage device 150. For example, a requesting device 1326 may merely compress data and send a compressed object, file, or data segment so that the storage device 150 does not distinguish the compressed data segment from other data received by way of other storage requests. 272 Added by DJM 3 2021 3/24/21, 12:00 AM
View Edit
Delete
US8762658B2 Where the data segment token storage module 1304 recognizes that a received data segment token is a data segment token, the data segment token storage module 1304 may store the data segment token in such a way that when read, it may appear as a data segment rather than the data segment token. One of skill in the art will recognize other ways that the data segment token storage module 1304 may store a data segment token after recognizing that a received data segment token is a data segment token rather than a data segment. 273 Added by DJM 3 2021 3/24/21, 12:00 AM
View Edit
Delete
US8762658B2 In another embodiment, storage request includes data from the data segment. In this embodiment, the apparatus includes a token generation module 1306 that generates a data segment token from the data segment, where the data segment token is created in response to the storage request to store the data segment. In a further embodiment, the token generation module 1306 resides in the requesting device 1326, possibly in the form of a driver. 274 Added by DJM 3 2021 3/24/21, 12:00 AM
View Edit
Delete
US8762658B2 In one embodiment, the apparatus includes a secure erase module 1320 that overwrites existing data with characters such that the existing data is non-recoverable, where the existing data includes data of a data segment previously stored on the storage device 150 identified with the same data segment identifier as the data segment identified in the storage request. In this embodiment, a data segment token is stored with the data segment identifier and data segment length and existing data identified by the same data segment identifier stored in the data segment token is erased by overwriting the existing data. Typically the existing characters are overwritten by zeros, ones, or some other character string so that the existing data is destroyed and is non-recoverable. 275 Added by DJM 3 2021 3/24/21, 12:00 AM
View Edit
Delete
US8762658B2 In a further embodiment, the secure erase module 1320 also includes an erase confirmation module 1322 that transmits a message indicating that the existing data has been overwritten. Typically the message is sent to the requesting device 1326. The erase confirmation message is transmitted after the secure erase module 1320 has overwritten the existing data. The message may be transmitted in the same transaction as the storage request or in a different transaction. 276 Added by DJM 3 2021 3/24/21, 12:00 AM
View Edit
Delete
US8762658B2 In another embodiment, the secure erase module 1320 overwrites the existing data during a storage space recovery operation. For example, if the storage device 150 is a solid-state storage device 102, as described above, the storage space recovery operation may be related to the garbage collection describe in relation to the apparatus 800 depicted in FIG. 8. However, a storage space recovery operation involving a request to overwrite the existing data would typically be expedited so that the storage location where the existing data is stored is necessarily recovered prior to any confirmation message is sent by the erase confirmation module 1322. In one embodiment, the existing data is marked or otherwise identified to indicate that a secure erase has been requested. The confirmation message would typically not be sent until the existing data marked for erasure has been overwritten and made non-recoverable. In another embodiment, the secure erase module 1320 merely marks the existing data as invalid for later storage space recovery. In another embodiment, the secure erase updates an index to indicate that the existing data is invalid and prevents access to this data until the data is overwritten during later storage space recovery. 277 Added by DJM 3 2021 3/24/21, 12:00 AM

Page 2 of 8, showing 20 record(s) out of 149 total