Re: [PATCH] Track block device users that created dirty pages

[Jeff Moyer]

Mikulas Patocka <mpatocka@xxxxxxxxxx> writes:

> The new semantics is: if a process did some buffered writes to the block
> device (with write or mmap), the cache is flushed when the process
> closes the block device. Processes that didn't do any buffered writes to
> the device don't cause cache flush. It has these advantages:
> * processes that don't do buffered writes (such as "lvm") don't flush
>   other process's data.
> * if the user runs "dd" on a block device, it is actually guaranteed
>   that the data is flushed when "dd" exits.

Why don't applications that want data to go to disk just call fsync
instead of relying on being the last process to have had the device
open?

Cheers,
Jeff
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/