Skip to content
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

Our NAND part has HUGE blocks.. 256K. This means a 1K file wastes 99.6% of the block. #778

Open
zammer2023 opened this issue Feb 23, 2023 · 2 comments

Comments

@zammer2023
Copy link

Has anyone worked on improvements to increase utilization using pages within blocks? The part we are using has 2048 blocks containing 64 pages with 4096 bytes of storage. littleFS would be ideal if it could leverage pages and blocks, particularly since the page/block architecture is fundamental to NAND devices.

@thanhminhmr
Copy link

Maybe a duplication of this issue/discussion: #11

@geky
Copy link
Member

geky commented Aug 16, 2023

Hi @zammer2023, thanks for creating an issue, the feedback is always useful.

I realize I'm late in responding, but I just wanted to note that this is going into some ongoing work to improve the file data-structure.

The planned improvement is to detach the RAM requirement from inline files, allowing inline files to be quite large without an unreasonable RAM requirement.

Inline files will still have a 4x storage overhead, something I'm not sure can be avoided, but this would at least be an improvement over the current 256x overhead you are seeing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants