[issue35580] Windows IocpProactor: CreateIoCompletionPort 4th arg 0xffffffff -- why is this value the default?
Jeff Robbins
report at bugs.python.org
Mon Dec 24 20:35:56 EST 2018
Jeff Robbins <jeffr at livedata.com> added the comment:
Per https://stackoverflow.com/questions/38133870/how-the-parameter-numberofconcurrentthreads-is-used-in-createiocompletionport, it seems that `NumberOfConcurrentThreads` controls what happens when multiple threads call `GetQueuedCompletionStatus`.
But since a given instance of `IocpProactor` only calls `GetQueuedCompletionStatus` from a single thread, probably this arg doesn't matter, and the value `1` would be more explicit about the pattern asyncio is using? A huge number is, presumably, either not relevant or, at worst, wasteful of some kernel resource.
Am I correct that only one thread calls `GetQueuedCompletionStatus` on a given `iocp` object in asyncio under Windows `IocpProactor`?
----------
_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35580>
_______________________________________
More information about the Python-bugs-list
mailing list