Quote Originally Posted by GregV
So this is the new scenario. There's a write cache in RAM. Like on a desktop computer, when anything looks to the disk the OS first checks the cache and then goes to disk if it's not there, so there's no risk of reading something outdated before the write takes place. So the new program starts immediately (or rather, starts moving from NV to RAM immediately) without the write, which should remove most of the delay. The cache is emptied in idle time in the background, so it doesn't slow down the executing program.
Hmm... isn't this how the NVFS in the Treo650/T5 is already designed?

Treo 650:
NAND Flash (Total Size = 32 MB)
Boot Code (< 1 MB)
Compressed ROM (8 MB)
User Data or Storage Heap (24 MB)
Internal Volume (Not Present)

RAM (Total Size = 32MB)
Decompressed Rom (16 MB)
DB Cache Area (10 MB)
Dynamic Heap (6 MB)

Tunsgten T5:
NAND Flash (Total Size = 256 MB)
Boot Code (< 1 MB)
Compressed ROM (14 MB)
User Data or Storage Heap (64 MB)
Internal Volume (178 MB)

RAM (Total Size = 32MB)
Decompressed Rom (16 MB)
DB Cache Area (10 MB)
Dynamic Heap (6 MB)
http://discussion.treocentral.com/sh...d=1#post472764