Message312758
On POSIX, mmap objects could expose a method wrapping the madvise() library call. I suggest the following API
mmap_object.madvise(option[, start[, length]])
If omitted, *start* and *length* would span the whole memory area described by the mmap object. *option* must be a recognized OS option for the madvise() library call.
The mmap module would expose the various MADV_* options available on the current platform.
Open question: should we expose madvise() or posix_madvise()? (these are two different calls, at least on Linux) posix_madvise() is arguably more portable, but madvise() is much more powerful, so I'd lean towards madvise(). |
|
Date |
User |
Action |
Args |
2018-02-24 21:15:23 | pitrou | set | recipients:
+ pitrou, ronaldoussoren, larry, ned.deily, neologix |
2018-02-24 21:15:23 | pitrou | set | messageid: <1519506923.52.0.467229070634.issue32941@psf.upfronthosting.co.za> |
2018-02-24 21:15:23 | pitrou | link | issue32941 messages |
2018-02-24 21:15:23 | pitrou | create | |
|