Charles-François Natali added the comment: > I propose to add an optional keyword parameter with default value "SYNC" > (compatibility) but that can be "ASYNC", "INVALIDATE" (can be > "SYNC|INVALIDATE" and "ASYNC|INVALIDATE" too).
AFAICT it's mostly useless on a modern OS. MS_INVALIDATE is a no-op on systems with merged VM-buffer cache, i.e. it's not needed for mmap() to reflect write() and vice-versa. So nothing's normally needed to "synchronize file and memory". As for MS_ASYNC, it actually doesn't do anything at all on recent OS, e.g. it's a no-op on Linux since a couple years, since modified pages will be written back as part of the normal writeback process. The only thing a user might actually need for an mmap object is to make sure data is actually committed to disk, and MS_SYNC covers this. See e.g. this post by Andrew Morton: http://thread.gmane.org/gmane.linux.kernel/1312660 ---------- nosy: +neologix _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue18816> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
