Pavel Machek wrote: > More politely said: "I believe you would be better off modifying > ramdisk to include the functionality for persistence." New filesystem > should not really be neccessary. ext2 for performance, ext3 if you > need robustness from journalling, maybe something else makes sense, > too. I agree that a persistent block device makes more sense. However, as someone with some experience in using this type of mechanism, a special filesystem (separate from the special block device) could also be useful. We often use things like circular buffers, per-cpu areas, both log-structured and variable-length records, etc. A filesystem that would take care of this type of thing under the hood might simplify a few things. Also note that it's very useful for the kernel itself to be able to access the contents of this persistent area...we use it for parts of the log stream, various forms of "flight recorder" information, panic tracebacks, etc. as well as making it available to select userspace apps. Chris -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
