On 8/16/05, David Masover <[EMAIL PROTECTED]> wrote: > Something Reiser4 does very well. If you have enough RAM, it's possible > to avoid any reads/writes at all -- given enough RAM, it behaves as a
Well that's cool if it's true. But IMO for this application it ought to have a deadline - after the writes have been pending for 10 seconds or so, go ahead and commit all of them, in case I forget to unmount before I remove the card. > ramdisk, which is why I wish I knew how to tell Gentoo to *not* mount > tmpfs over /dev. > > One other thing you might try is disabling the write-twice behavior. > Currently, if you've got a huge, fairly well-sorted file that you're > making lots of tiny writes to, such as a database, it makes sense to > write twice to keep the file from getting fragmented. But, > fragmentation isn't nearly as much an issue on truly random-access > media, so you'd want the default small-file behavior to be used > everywhere -- first write the data to the new location, then atomically > update the pointer to it as you deallocate the old location. What would you change to do that?
