Linux and I/O completion ports?

Question

Using winsock, you can configure sockets or seperate I/O operations to "overlap". This means that calls to perform I/O are returned immediately, while the actual operations are completed asynchronously by separate worker threads.

Winsock also provides "completion ports". From what I understand, a completion port acts as a multiplexer of handles (sockets). A handle can be demultiplexed if it isn't in the middle of an I/O operation, i.e. if all its I/O operations are completed.

So, on to my question... does linux support completion ports or even asynchronous I/O for sockets?

Answer 1

I don't fully understand what you mean by "completion ports". All I can say is that you can use sockets in non-blocking mode, which means that calls return immediately.

This reference is quite old but is comprehensive in a sense that it covers select() etc.: http://rhoden.id.au/doc/sockets2.html

And here is the GNU manual on sockets: http://www.gnu.org/software/libc/manual/html_node/Sockets.html

Answer 2

IOCP is pronounced "asynchronous I/O" on various UNIX platforms:

• POSIX AIO is the standard
• Kernel AIO and epoll seems to be a Linux-specific implementations
• Kqueue is the *BSD and Mac OSX implementation
• Message Passing Interface (MPI) is an option for high-performance computing
• obligatory Boost reference - Boost.Asio

Answer 3

Besides everything cited by @D.Shawley, I recommend libevent.

This may help you with samples. However, it's a comprehensive reference on the libevent API, not on the AIO mechanisms (poll, epoll, kqueue, event ports, select).

Answer 4

Read the blog entry from Google on libevent, you can implement IOCP semantics on Unix using asynchronous IO but cannot directly implement asynchronous IO semantics using IOCP,

http://google-opensource.blogspot.com/2010/01/libevent-20x-like-libevent-14x-only.html

For an example cross platform asynchronous IO with a BSD socket API look at ZeroMQ as recently published on LWN.net,

http://www.zeromq.org/

LWN article,

http://lwn.net/Articles/370307/

Answer 5

If you're looking for something exactly like IOCP, you won't find it, because it doesn't exist.

Windows uses a notify on completion model (hence I/O Completion Ports). You start some operation asynchronously, and receive a notification when that operation has completed.

Linux applications (and most other Unix-alikes) generally use a notify on ready model. You receive a notification that the socket can be read from or written to without blocking. Then, you do the I/O operation, which will not block.

With this model, you don't need asynchronous I/O. The data is immediately copied into / out of the socket buffer.

The programming model for this is kind of tricky, which is why there are abstraction libraries like libevent. It provides a simpler programming model, and abstracts away the implementation differences between the supported operating systems.

There is a notify on ready model in Windows as well (select or WSAWaitForMultipleEvents), which you may have looked at before. It can't scale to large numbers of sockets, so it's not suitable for high-performance network applications.

Don't let that put you off - Windows and Linux are completely different operating systems. Something that doesn't scale well on one system may work very well on the other. This approach actually works very well on Linux, with performance comparable to IOCP on Windows.