C # Socket ReceiveAsync in the completion port, the principle of overlapping or IO? The underlying u-CodePudding

Such as: c # Socket ReceiveAsync in the completion port, the principle of overlapping or IO? The underlying use of that kind of I/O model?

CodePudding user response:

Platform should be points, win platform using IOCP, other platforms, estimation is NIO

This has something to do with driver, Windows platform nic driver provide the IOCP model

CodePudding user response:

reference 1st floor wanghui0380 response:

platform should be points, win platform using IOCP, other platforms, estimation is NIO

This has something to do with driver, Windows platform nic driver provide the IOCP model

Forgot to describe the platform, is running on a Windows platform,
Is there a link and driver?
If use c + + development, need through calls GetQueuedCompletionStatus receive packets from the completion port, but the compiler system. DLL, didn't find the GetQueuedCompletionStatus, etc.,

CodePudding user response:

reference instantaneous refueling reply: 3/f

Quote: refer to 1st floor wanghui0380 response:
platform should be points, win platform using IOCP, other platforms, estimation is NIO

This has something to do with driver, Windows platform nic driver provide the IOCP model

Forgot to describe the platform, is running on a Windows platform,
Is there a link and driver?
, if use c + + development calls GetQueuedCompletionStatus, etc are needed to get the packet from the completion port, but the compilation system. DLL, didn't find the GetQueuedCompletionStatus,

Windows platform using the completion port, the bottom is actually an IRQ request network card drivers, is not recommended to see what you want to see the source code, directly find a win32api monitoring to see him call API, net on the ground floor is still calling the underlying operating system API