On 18/05/10 16:36, Chris Mason wrote: >> >> The idea would be to delay the rename hitting the disk until the data >> has been written anyway. >> The mv would return immediately, and someday, after the data has been >> written to disk, the rename would be written to disk. > > This is possible, but we have to choose between consuming unbounded > resources while we queue up all the mvs or sometimes forcing the things > to disk. At the end of the day, disks are so slow that eventually you > do end up waiting on them. > > -chris >
I'm not sure how much memory a queued rename takes up, but the time that would be spent flushing it to disk would then be spent flushing file data, draining the write buffer and freeing memory, no? That would be writing to disk [Data..................][Rename] or [Rename][Data..................] Whether you drain the file data queue or the rename queue first, in the end you'd have to write it all.... I thought the problem of delaying the renames was complexity, well, at least T'Tso said it was [1] - I'm not sure if this applies to btrfs as well. Thanks, Jakob [1] https://bugzilla.kernel.org/show_bug.cgi?id=15910#c9 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
