What sort of processor would we want for running the flash-memory wear-leveling firmware I spent the past few days describing?
Primarily we'd a decent of RAM in which to store virtual-addressing tables, freelists, tentative output, etc. And to make this fast... We'll need a cache hierarchy!
That is large memory is slow & fast memory is small, so to avoid the compromise include both! With the fast memory storing copies of the data in the large memory.
1/3?
alcinnz
npub186…snt98
2026-03-18 20:15:31 UTC
Author Public Key
npub186lgefknfnkgychnfjancqnv4k4yrdzxal486lw0p80z6vmley9qgsnt98Seen on
wss://relay.momostr.pinkPublished at
2026-03-18 20:15:31 UTCEvent JSON
{
"id": "809508ab598befab70ba9f567b830d4dc6e7378a13f21730d1850024b7276218",
"pubkey": "3ebe8ca6d34cec8262f34cbb3c026cadaa41b446efea7d7dcf09de2d337fc90a",
"created_at": 1773864931,
"kind": 1,
"tags": [
[
"proxy",
"https://floss.social/@alcinnz/116252012176220527",
"web"
],
[
"proxy",
"https://floss.social/users/alcinnz/statuses/116252012176220527",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://floss.social/users/alcinnz/statuses/116252012176220527",
"pink.momostr"
],
[
"-"
]
],
"content": "What sort of processor would we want for running the flash-memory wear-leveling firmware I spent the past few days describing?\n\nPrimarily we'd a decent of RAM in which to store virtual-addressing tables, freelists, tentative output, etc. And to make this fast... We'll need a cache hierarchy!\n\nThat is large memory is slow \u0026 fast memory is small, so to avoid the compromise include both! With the fast memory storing copies of the data in the large memory.\n\n1/3?",
"sig": "c149f52319e7cd1cd42ef03fd1b2332b644ef6407db385e9063b820ee3e9a7ae17627f1ce2ea6507e1fa7454b318e314733cf60d26d4c3a08e622b4b6d9c3248"
}