Comment 144 for bug 317781

@Theo: thanks for addressing this point.

> So it's not as simple as "delaying the truncate"; you can delay committing all operations in the journal, but you can't just delay one transaction but not another.

I think this is the overall idea people are expressing here, delaying the entire journal operation stack, not swapping operations.

> However, various disk buffers will get pinned in memory until the commit takes place, so extending commits may end up chewing up more memory used by the kernel. TNSTAAFL.

If I understand you correctly, you are implying that delaying the journal commits is more expensive memory-wise than delaying the data write? Else I don't understand you concern, the data writes are already delayed for longer...

Is it possible to exactly synchronize the journal commits and the data writes (i.e., one immediately after the other)? Would this prevent data loss for the programs that rely on posixly-unsafe file rewrites?