On Sat, Jun 22, 2013 at 01:40:26PM +0000, Sidorov, Andrei wrote: > Me too, but people have to do that because fs api is too generic and > at the same time one has to account fs specifics in order to make > their app take most advantage or at least to avoid inefficiencies. > For example I have an app that constantly does appending writes to > about 15 files and I must ensure that no more than 5 seconds will be > lost in an event of system crash or power loss. Stop right there. If you are doing lots of appending writes, and you dont want to lose no more than 5 seconds, why do you have 15 files? Why send your appending writes into a single file and then later on, disaggregate out the logs when you need to read them? With 15 files, no matter what you are doing, you will be forcing the heads to seek all over the place, and since the 4k blocks won't be full when you sync them, you're wasting write cycles and disk bandwidth. See what I mean? There's a reason why I said the fault was incompetent application design, not just incomplement implementation. - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
