Message195941
Currently, "mmap.flush()" does a synchronous write to the backend file. The call will wait until data is actually flushed to disk, because internally it is doing a "msync(MS_SYNC)".
But the value of "mmap.flush()" is to synchronize file and memory. You don't need a synchronous write in the general case.
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).
I am talking about UNIX MMAP. No idea about Windows.
Check "man msync" for useful cases. |
|
Date |
User |
Action |
Args |
2013-08-23 04:55:08 | jcea | set | recipients:
+ jcea |
2013-08-23 04:55:08 | jcea | set | messageid: <1377233708.52.0.141761715851.issue18816@psf.upfronthosting.co.za> |
2013-08-23 04:55:08 | jcea | link | issue18816 messages |
2013-08-23 04:55:08 | jcea | create | |
|