Alphabetical listing of connect and I/O functions

This section gives an alphabetical listing of the connect and I/O function entry points that you can fill in (the two tables passed to resmgr_attach()). Remember that if you simply call iofunc_func_init(), all these entries will be filled in with the appropriate defaults; you'd want to modify a particular entry only if you wish to handle that particular message. In the “Examples” section, below, you'll see some examples of the common functions.

Note: It may seem confusing at first, but note that there are in fact two unblock outcalls—one is a connect function and one is an I/O function. This is correct; it's a reflection of when the unblock occurs. The connect version of the unblock function is used when the kernel unblocks the client immediately after the client has sent the connect message; the I/O version of the unblock function is used when the kernel unblocks the client immediately after the client has sent an I/O message.

In order not to confuse the client's C-library call (for example, open()) with the resource manager connect outcall that goes into that particular slot, we've given all of our functions an io_ prefix. For example, the function description for the open connect outcall slot will be under io_open().