> and, persistant data is always a pain as it doesnt go away after
> reboot, and i'm wondering wether we should provide a generic
> framework to do reliable atomic operations on persistant data
> (transactions). Otherwise we would just end up doing our own little
> imperfect transaction engine, within fdisk, within ckraid, within
> JFS/ext3fs/reiserfs. One thing is sure, the situation (ie. the size
> of persistant data) gets worse and worse :)
The ext2 journaling design has a fairly portable core which will be in
linux/fs, not linux/fs/ext2. The portable section includes the
transaction/buffer management, writeback ordering and log writing.
Only the actual generation of transactions will be ext2-specific.
--Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu