pw_kvs: Don't start GC scan at first sector
This change prevents KVS from always starting a scan for a sector to GC
from the beginning of the flash parition. In cases where an application
writes the same size value to the KVS many times, it is insufficient to
start the GC scan from
This change updates the GC scan to start just past the last sector
selected as the "new" sector to write data to. This should improve wear
leveling in cases where the same key is written many times.
Change-Id: If41ed2c97797a3e549f9d69078c9724da3a4c0fa
diff --git a/pw_kvs/BUILD b/pw_kvs/BUILD
index fd17d66..5a01bff 100644
--- a/pw_kvs/BUILD
+++ b/pw_kvs/BUILD
@@ -234,6 +234,19 @@
],
)
+pw_cc_test(
+ name = "key_value_store_wear_test",
+ srcs = [
+ "key_value_store_wear_test.cc",
+ ],
+ deps = [
+ ":pw_kvs",
+ ":test_utils",
+ "//pw_log:backend",
+ "//pw_unit_test",
+ ],
+)
+
# TODO: This binary is not building due to a linker error. The error does not occur in GN Builds.
# A filegroup is used below so that the file is included in the Bazel build.
# cc_binary(