rghaddab/zms settings backend cache sdk zephyr #2567
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ction" This reverts commit 14d166f. Signed-off-by: Riadh Ghaddab <[email protected]>
…emory Storage)" This reverts commit 88e9f91. Signed-off-by: Riadh Ghaddab <[email protected]>
…orage) This adds the initial backend support for the ZMS storage system. Signed-off-by: Riadh Ghaddab <[email protected]> (cherry picked from commit ef4e8dd)
This adds a on target performance test for Settings SS. Using this test performance of the Setting SS + NVS/ZMS backend can be benchmarked. The test repeatedly write 128 settings entries. Each setting entry has a size of 4 bytes, and path length of 16 bytes (excluding the null-terminator). The test has two variants, with and without Bluetooth scan running. This is useful to benchmark performance along with some component of BT subsystem activated. The test could be enhanced in future to include or create combinations of different functionalities running, when agreesive store operations are happening. Signed-off-by: Omkar Kulkarni <[email protected]> (cherry picked from commit c795596604ea06f3d463bf36c4c1106b83165e72)
This resolves some addressed comments in this PR zephyrproject-rtos#77930 as well as this PR zephyrproject-rtos#80407 Signed-off-by: Riadh Ghaddab <[email protected]> (cherry picked from commit 5f7cda5)
To avoid collisions between IDs used by settings and IDs used directly by subsystems using ZMS API, the MSB is always set to 1 for Setting's name ID written to ZMS backend Add as well a recovery path if the hash linked list is broken. Upstream PR #: 86170 Signed-off-by: Riadh Ghaddab <[email protected]> (cherry picked from commit e56b55885b19628c6944a2544ca724717fbbb7b3)
adding a lookup cache for hash collisions improves write speed as it doesn't look for the name in the storage if no hash collision exists Signed-off-by: Riadh Ghaddab <[email protected]>
Signed-off-by: Riadh Ghaddab <[email protected]>
This was referenced Feb 28, 2025
Closed
rghaddab
force-pushed
the
rghaddab/zms-settings-backend-cache-sdk-zephyr
branch
10 times, most recently
from
acee636 to
9fc0338
Compare
rghaddab
force-pushed
the
rghaddab/zms-settings-backend-cache-sdk-zephyr
branch
3 times, most recently
from
9ee933b to
d0cfc45
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.