[issue1572968] release GIL while doing I/O operations in the mmap module

Change by Zackery Spytz : -- components: +Extension Modules -Library (Lib) nosy: +ZackerySpytz versions: +Python 3.9 -Python 2.7, Python 3.1 ___ Python tracker ___ __

[issue1572968] release GIL while doing I/O operations in the mmap module

Change by Zackery Spytz : -- keywords: +patch pull_requests: +13963 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/14114 ___ Python tracker _

[issue1572968] release GIL while doing I/O operations in the mmap module

Nic Watson added the comment: I'll add one more system I/O call that's not GIL-wrapped in the mmap module that can take some time: mmap itself. mmap on Linux with MAP_POPULATE (0x8000) as the flags can take quite a bit of time. That's the flag that prefaults the memory range. MAP_POPULATE

[issue1572968] release GIL while doing I/O operations in the mmap module

Batuhan added the comment: Any news? If a patch is not ready, i can work on a patch too. -- nosy: +BTaskaya ___ Python tracker ___ __

[issue1572968] release GIL while doing I/O operations in the mmap module

Change by Josiah Carlson : -- nosy: -josiahcarlson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue1572968] release GIL while doing I/O operations in the mmap module

Changes by Adi Roiban : -- nosy: +adiroiban ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue1572968] release GIL while doing I/O operations in the mmap module

Changes by Brian Curtin : -- nosy: +brian.curtin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue1572968] release GIL while doing I/O operations in the mmap module

Antoine Pitrou added the comment: > This shouldn't really care about VMS here. Correction: /we/ shouldn't really care about VMS here. And the reason being, of course, that we have neither developers nor known testers under VMS. (we don't even know if the current trunk builds there or not)

[issue1572968] release GIL while doing I/O operations in the mmap module

Antoine Pitrou added the comment: This shouldn't really care about VMS here. As for the rest, feel free to propose a patch :) Please note that most non-trivial system calls, such as ftruncate(), mremap(), even mmap() itself, deserve to be enclosed in Py_BEGIN_ALLOW_THREADS/Py_END_ALLOW_THREAD

[issue1572968] release GIL while doing I/O operations in the mmap module

Charles-Francois Natali added the comment: As soon as you're dealing with files (not anonymous mapping), you can get the same type of latency than when using open/read/write... While it's probably not worth the trouble to release the GIL for every operation involving mmaped-files, there are a

[issue1572968] release GIL while doing I/O operations in the mmap module

Antoine Pitrou added the comment: I don't know mmap myself but patches are welcome. -- nosy: +pitrou priority: -> normal stage: test needed -> needs patch type: feature request -> performance versions: +Python 3.1 ___ Python tracker

[issue1572968] release GIL while doing I/O operations in the mmap module

Changes by Daniel Diniz : -- priority: normal -> stage: -> test needed versions: +Python 2.7 ___ Python tracker ___ ___ Python-bug