TimJTi commented on PR #2228: URL: https://github.com/apache/nuttx-apps/pull/2228#issuecomment-1852420562
> @TimJTi If you need to reduce the memory use of the map, why don't you try to use an [RLE](https://en.wikipedia.org/wiki/Run-length_encoding) or a [KVL](https://en.wikipedia.org/wiki/KLV) serializer? @fjpanag See all answers above. As far as this suggestion is concerned, it wouldn't fit very well with the existing storage_binary function which assumes every setting is the full sizeof settings_t? It would move the EEPROM storage outside of the entire settings feature whereas what I have done does fit in, and works, albeit needing some changes? If it is an overall objection to a third storage type that is, when all said and done, very close to storage_bin, could it perhaps be a Kconfig option to MINIMISE_BINSIZE, with the necessary differences included in storage_bin? Also, to use KLV or RLE the encoding has to be written/ported/added to NuttX too? Is there an overarching reason to move the changes, that I feel are beneficial for EEPROM devices, outside of the settings feature itself and to "offload" them to the user app? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@nuttx.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
