Is there any historical information out there I can read that discusses why IOCP handles can't participate in WaitForMultipleObjects et al?
@cmuratori I'm assuming there was a specific kernel performance or complexity reason for it but I'm not sure what it would be.
-
-
@cmuratori WaitForMultipleObjects() scan events linearly(= scheduling bias), IOCP is designed to avoid this. Makes sense to not make interop -
@cmuratori That's my personal (unqualified) assumption, don't have any interesting discussion references for you :(
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.