Lines Matching full:storage

3 Zephyr Memory Storage (ZMS)
5 Zephyr Memory Storage is a new key-value storage system that is designed to work with all types
6 of non-volatile storage technologies. It supports classical on-chip NOR flash as well as new
99 Mounting the Storage system
102 Mounting the storage starts by getting the flash parameters, checking that the file system
104 make the storage ready.
114 		/** Storage system is split into sectors, each sector size must be multiple of
185 Some applications need to make sure that storage writes have a maximum defined latency.
214 							    * such as storage version.
286 This storage system is optimized for devices that do not require an erase.
287 Using storage systems that rely on an erase-value (NVS as an example) will need to emulate the
301 data (including extra headers) that could be written in the storage.
308 Storage devices whether they are classical Flash or new technologies like RRAM/MRAM has a limited
311 memory cells cannot be overwritten) and for non-erasable storage devices memory cells can be
317 Each write of the variable requires 16 bytes of storage.
319 storage system, we are going to rewrite the first location of the first sector after
326 For storage devices that could be written 20000 times, the storage will last about
334 the storage and that the partition is well dimensioned (double of the effective size) to avoid
349 ``MAX_NUM_WRITES``: is the life expectancy of the storage device in number of writes
357 ZMS has introduced many features compared to existing storage system like NVS and will evolve
359 such as low latency and bigger storage space.
384 - Add a recovery function that can recover a storage partition if something went wrong
386 - Add the possibility to force formatting the storage partition to the ZMS format if something
387   went wrong when mounting the storage.
389 ZMS and other storage systems in Zephyr
391 This section describes ZMS in the wider context of storage systems in Zephyr (not full filesystems,
399   best fit for your storage subsystem as it is designed to avoid emulating erase operation using
408 - If your application needs more than 64K IDs for storage, :ref:`ZMS <zms_api>` is recommended here…
411   the best storage solution for this use case.
424 - The total size of the storage partition should be well dimensioned to achieve the best
428   We recommend choosing a storage partition that can hold double the size of the key-value pairs
429   that will be written in the storage.
436   The header needed by the two entries should be accounted when computing the needed storage space.
446   the number of different entries that will be written in the storage.