Deprecated: Since 5.0.0: Calling Table::get() with options array is deprecated. Use named arguments instead. /application/src/Controller/ParagraphsController.php, line: 67 You can disable all deprecation warnings by setting `Error.errorLevel` to `E_ALL & ~E_USER_DEPRECATED`. Adding `src/Controller/ParagraphsController.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 377

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

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

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

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

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

3017

Application Apparatus, system, and method for managing data using a data pipeline
Matter Number 2380.2.01 Reference Case 1 2380.2.01
Created 3/16/21, 12:00 AM Modified 3/16/21, 12:00 AM
Application Number

11952091

Paragraph Number

104

Content

In one embodiment, packets are written sequentially to the solid-state storage 110. For example, packets are streamed to the storage write buffers of a bank 214a of storage elements 216 and when the buffers are full, the packets are programmed to a designated virtual page. Packets then refill the storage write buffers and, when full, the packets are written to the next virtual page. The next virtual page may be in the same bank 214a or another bank (e.g. 214b). This process continues, virtual page after virtual page, typically until a virtual erase block is filled. In another embodiment, the streaming may continue across virtual erase block boundaries with the process continuing, virtual erase block after virtual erase block.

Notes

Added by DJM 3 2021