-
Notifications
You must be signed in to change notification settings - Fork 623
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[nrf noup] settings: nvs: use dedicated lookup cache hash function #1263
Conversation
@Damian-Nordic what about to remove DNM? |
I'm OK with that but maybe we should upstream this first? |
645bb7a
to
7b3e64b
Compare
FYI, removed DNM but only the second commit is exclusive for this PR. The first one is already upstreamed and a part of the current upmerge. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
ffb383a
to
f2ecbc0
Compare
af5ba19
to
a2131bb
Compare
Introduce NVS_LOOKUP_CACHE_FOR_SETTINGS Kconfig option that enables a dedicated hash function for the NVS lookup cache that takes advantage of the NVS ID allocation scheme used by the NVS settings backend. As such, this option should only be used if an application uses NVS via the settings layer. Signed-off-by: Damian Krolik <damian.krolik@nordicsemi.no>
a2131bb
to
6f7788a
Compare
Introduce
NVS_LOOKUP_CACHE_FOR_SETTINGS
Kconfig option that enables a dedicated hash function for the NVS lookup cache that takes advantage of the NVS ID allocation scheme used by the NVS settings backend. As such, this option should only be used if an application uses NVS via the settings layer.The commit is a
noup
patch because the original change seems not generic enough to be accepted by the Zephyr community: zephyrproject-rtos/zephyr#61619.