On Mon, 1 Apr 2013, Jeff Moyer wrote:
> Mikulas Patocka 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
> >
Mikulas Patocka 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 adv
Hi
Here I'm sending a patch to change block device buffer flush semantics:
only processes that created some dirty data do buffer flush on close.
Mikulas
---
Track block device users that created dirty pages
This patch changes the block device driver to use the field
"private_data" to track "f
3 matches
Mail list logo
