74e4ac0883
The NVS data lookup time grows linearly with the number of allocation table entries to walk through, meaning that if some data pair in the NVS changes frequently, access to other data pairs that change rarely can take a lot of time. It is particularly visible when the NVS is used as the settings backend since the backend needs to perform multiple NVS reads to find a requested key. Implement a simple cache that stores an address of the most recent ATE for all NVS IDs that fall into the given cache position. CRC8/16 is used as a hash function used to distribute NVS IDs across the cache entries. The cache entries are only invalidated when an NVS sector is erased as part of the garbage collector task. Signed-off-by: Damian Krolik <damian.krolik@nordicsemi.no> |
||
|---|---|---|
| .. | ||
| boards | ||
| src | ||
| CMakeLists.txt | ||
| prj.conf | ||
| testcase.yaml | ||