Thread (4 messages) 4 messages, 4 authors, 2014-05-20

Re: [PATCH] Sync only the requested range in msync

From: Christoph Hellwig <hch@infradead.org>
Date: 2014-05-15 11:24:33
Also in: linux-fsdevel

On Tue, May 13, 2014 at 09:31:01AM -0400, Jeff Moyer wrote:
FWIW, I think we should apply the patch.  Anyone using the API properly
will not get the desired result, and it could have a negative impact on
performance.  The man page is very explicit on what you should expect,
here.  Anyone relying on undocumented behavior gets to keep both pieces
when it breaks.  That said, I do understand your viewpoint, Andrew,
especially since it's so hard to get people to sync their data at all,
much less correctly.
Agreed, we never made filesystems write out all data in the file system
in fsync either just because ext3 behaved that way.

And unlike that case I can't even see a good way to get msync wrong -
you call it on the mapped region, so expecting it to write out data
that isn't mapped at all seems rather odd.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help