select – Wait for I/O Efficiently

来源：互联网发布：有什么美图软件编辑：程序博客网时间：2024/05/09 20:59

Purpose:Wait for notification that an input or output channel is ready.Available In:1.4 and later

The select module provides access to platform-specific I/O monitoring functions. The most portable interface is the POSIX function select(), which is available on Unix and Windows. The module also includes poll(), a Unix-only API, and several options that only work with specific variants of Unix.

select()

Python’s select() function is a direct interface to the underlying operating system implementation. It monitors sockets, open files, and pipes (anything with a fileno() method that returns a valid file descriptor) until they become readable or writable, or a communication error occurs. select() makes it easier to monitor multiple connections at the same time, and is more efficient than writing a polling loop in Python using socket timeouts, because the monitoring happens in the operating system network layer, instead of the interpreter.

Note

Using Python’s file objects with select() works for Unix, but is not supported under Windows.

The echo server example from the socket section can be extended to watch for more than one connection at a time by using select(). The new version starts out by creating a non-blocking TCP/IP socket and configuring it to listen on an address.

import selectimport socketimport sysimport Queue# Create a TCP/IP socketserver = socket.socket(socket.AF_INET, socket.SOCK_STREAM)server.setblocking(0)# Bind the socket to the portserver_address = ('localhost', 10000)print >>sys.stderr, 'starting up on %s port %s' % server_addressserver.bind(server_address)# Listen for incoming connectionsserver.listen(5)

The arguments to select() are three lists containing communication channels to monitor. The first is a list of the objects to be checked for incoming data to be read, the second contains objects that will receive outgoing data when there is room in their buffer, and the third those that may have an error (usually a combination of the input and output channel objects). The next step in the server is to set up the lists containing input sources and output destinations to be passed to select().

# Sockets from which we expect to readinputs = [ server ]# Sockets to which we expect to writeoutputs = [ ]

Connections are added to and removed from these lists by the server main loop. Since this version of the server is going to wait for a socket to become writable before sending any data (instead of immediately sending the reply), each output connection needs a queue to act as a buffer for the data to be sent through it.

# Outgoing message queues (socket:Queue)message_queues = {}

The main portion of the server program loops, calling select() to block and wait for network activity.

while inputs:    # Wait for at least one of the sockets to be ready for processing    print >>sys.stderr, '\nwaiting for the next event'    readable, writable, exceptional = select.select(inputs, outputs, inputs)

select() returns three new lists, containing subsets of the contents of the lists passed in. All of the sockets in the readable list have incoming data buffered and available to be read. All of the sockets in the writable list have free space in their buffer and can be written to. The sockets returned in exceptional have had an error (the actual definition of “exceptional condition” depends on the platform).

The “readable” sockets represent three possible cases. If the socket is the main “server” socket, the one being used to listen for connections, then the “readable” condition means it is ready to accept another incoming connection. In addition to adding the new connection to the list of inputs to monitor, this section sets the client socket to not block.

    # Handle inputs    for s in readable:        if s is server:            # A "readable" server socket is ready to accept a connection            connection, client_address = s.accept()            print >>sys.stderr, 'new connection from', client_address            connection.setblocking(0)            inputs.append(connection)            # Give the connection a queue for data we want to send            message_queues[connection] = Queue.Queue()

The next case is an established connection with a client that has sent data. The data is read with recv(), then placed on the queue so it can be sent through the socket and back to the client.

        else:            data = s.recv(1024)            if data:                # A readable client socket has data                print >>sys.stderr, 'received "%s" from %s' % (data, s.getpeername())                message_queues[s].put(data)                # Add output channel for response                if s not in outputs:                    outputs.append(s)

A readable socket without data available is from a client that has disconnected, and the stream is ready to be closed.

            else:                # Interpret empty result as closed connection                print >>sys.stderr, 'closing', client_address, 'after reading no data'                # Stop listening for input on the connection                if s in outputs:                    outputs.remove(s)                inputs.remove(s)                s.close()                # Remove message queue                del message_queues[s]

There are fewer cases for the writable connections. If there is data in the queue for a connection, the next message is sent. Otherwise, the connection is removed from the list of output connections so that the next time through the loop select() does not indicate that the socket is ready to send data.

    # Handle outputs    for s in writable:        try:            next_msg = message_queues[s].get_nowait()        except Queue.Empty:            # No messages waiting so stop checking for writability.            print >>sys.stderr, 'output queue for', s.getpeername(), 'is empty'            outputs.remove(s)        else:            print >>sys.stderr, 'sending "%s" to %s' % (next_msg, s.getpeername())            s.send(next_msg)

Finally, if there is an error with a socket, it is closed.

    # Handle "exceptional conditions"    for s in exceptional:        print >>sys.stderr, 'handling exceptional condition for', s.getpeername()        # Stop listening for input on the connection        inputs.remove(s)        if s in outputs:            outputs.remove(s)        s.close()        # Remove message queue        del message_queues[s]

The example client program uses two sockets to demonstrate how the server with select()manages multiple connections at the same time. The client starts by connecting each TCP/IP socket to the server.

import socketimport sysmessages = [ 'This is the message. ',             'It will be sent ',             'in parts.',             ]server_address = ('localhost', 10000)# Create a TCP/IP socketsocks = [ socket.socket(socket.AF_INET, socket.SOCK_STREAM),          socket.socket(socket.AF_INET, socket.SOCK_STREAM),          ]# Connect the socket to the port where the server is listeningprint >>sys.stderr, 'connecting to %s port %s' % server_addressfor s in socks:    s.connect(server_address)

Then it sends one pieces of the message at a time via each socket, and reads all responses available after writing new data.

for message in messages:    # Send messages on both sockets    for s in socks:        print >>sys.stderr, '%s: sending "%s"' % (s.getsockname(), message)        s.send(message)    # Read responses on both sockets    for s in socks:        data = s.recv(1024)        print >>sys.stderr, '%s: received "%s"' % (s.getsockname(), data)        if not data:            print >>sys.stderr, 'closing socket', s.getsockname()            s.close()

Run the server in one window and the client in another. The output will look like this, with different port numbers.

$ python ./select_echo_server.pystarting up on localhost port 10000waiting for the next eventnew connection from ('127.0.0.1', 55821)waiting for the next eventnew connection from ('127.0.0.1', 55822)received "This is the message. " from ('127.0.0.1', 55821)waiting for the next eventsending "This is the message. " to ('127.0.0.1', 55821)waiting for the next eventoutput queue for ('127.0.0.1', 55821) is emptywaiting for the next eventreceived "This is the message. " from ('127.0.0.1', 55822)waiting for the next eventsending "This is the message. " to ('127.0.0.1', 55822)waiting for the next eventoutput queue for ('127.0.0.1', 55822) is emptywaiting for the next eventreceived "It will be sent " from ('127.0.0.1', 55821)received "It will be sent " from ('127.0.0.1', 55822)waiting for the next eventsending "It will be sent " to ('127.0.0.1', 55821)sending "It will be sent " to ('127.0.0.1', 55822)waiting for the next eventoutput queue for ('127.0.0.1', 55821) is emptyoutput queue for ('127.0.0.1', 55822) is emptywaiting for the next eventreceived "in parts." from ('127.0.0.1', 55821)received "in parts." from ('127.0.0.1', 55822)waiting for the next eventsending "in parts." to ('127.0.0.1', 55821)sending "in parts." to ('127.0.0.1', 55822)waiting for the next eventoutput queue for ('127.0.0.1', 55821) is emptyoutput queue for ('127.0.0.1', 55822) is emptywaiting for the next eventclosing ('127.0.0.1', 55822) after reading no dataclosing ('127.0.0.1', 55822) after reading no datawaiting for the next event

The client output shows the data being sent and received using both sockets.

$ python ./select_echo_multiclient.pyconnecting to localhost port 10000('127.0.0.1', 55821): sending "This is the message. "('127.0.0.1', 55822): sending "This is the message. "('127.0.0.1', 55821): received "This is the message. "('127.0.0.1', 55822): received "This is the message. "('127.0.0.1', 55821): sending "It will be sent "('127.0.0.1', 55822): sending "It will be sent "('127.0.0.1', 55821): received "It will be sent "('127.0.0.1', 55822): received "It will be sent "('127.0.0.1', 55821): sending "in parts."('127.0.0.1', 55822): sending "in parts."('127.0.0.1', 55821): received "in parts."('127.0.0.1', 55822): received "in parts."

Timeouts

select() also takes an optional fourth parameter which is the number of seconds to wait before breaking off monitoring if no channels have become active. Using a timeout value lets a main program call select() as part of a larger processing loop, taking other actions in between checking for network input.

When the timeout expires, select() returns three empty lists. Updating the server example to use a timeout requires adding the extra argument to the select() call and handling the empty lists after select() returns.

    # Wait for at least one of the sockets to be ready for processing    print >>sys.stderr, '\nwaiting for the next event'    timeout = 1    readable, writable, exceptional = select.select(inputs, outputs, inputs, timeout)    if not (readable or writable or exceptional):        print >>sys.stderr, '  timed out, do some other work here'        continue

This “slow” version of the client program pauses after sending each message, to simulate latency or other delay in transmission.

import socketimport sysimport time# Create a TCP/IP socketsock = socket.socket(socket.AF_INET, socket.SOCK_STREAM)# Connect the socket to the port where the server is listeningserver_address = ('localhost', 10000)print >>sys.stderr, 'connecting to %s port %s' % server_addresssock.connect(server_address)time.sleep(1)messages = [ 'Part one of the message.',             'Part two of the message.',             ]amount_expected = len(''.join(messages))try:    # Send data    for message in messages:        print >>sys.stderr, 'sending "%s"' % message        sock.sendall(message)        time.sleep(1.5)    # Look for the response    amount_received = 0        while amount_received < amount_expected:        data = sock.recv(16)        amount_received += len(data)        print >>sys.stderr, 'received "%s"' % datafinally:    print >>sys.stderr, 'closing socket'    sock.close()

Running the new server with the slow client produces:

$ python ./select_echo_server_timeout.pystarting up on localhost port 10000waiting for the next event  timed outwaiting for the next event  timed outwaiting for the next eventnew connection from ('127.0.0.1', 57776)waiting for the next eventreceived "Part one of the message." from ('127.0.0.1', 57776)waiting for the next eventsending "Part one of the message." to ('127.0.0.1', 57776)waiting for the next eventoutput queue for ('127.0.0.1', 57776) is emptywaiting for the next event  timed outwaiting for the next eventreceived "Part two of the message." from ('127.0.0.1', 57776)waiting for the next eventsending "Part two of the message." to ('127.0.0.1', 57776)waiting for the next eventoutput queue for ('127.0.0.1', 57776) is emptywaiting for the next event  timed outwaiting for the next eventclosing ('127.0.0.1', 57776) after reading no datawaiting for the next event  timed outwaiting for the next event

And the client output is:

$ python ./select_echo_slow_client.pyconnecting to localhost port 10000sending "Part one of the message."sending "Part two of the message."received "Part one of the "received "message.Part two"received " of the message."closing socket

poll()

The poll() function provides similar features to select(), but the underlying implementation is more efficient. The trade-off is that poll() is not supported under Windows, so programs using poll() are less portable.

An echo server built on poll() starts with the same socket configuration code used in the other examples.

import selectimport socketimport sysimport Queue# Create a TCP/IP socketserver = socket.socket(socket.AF_INET, socket.SOCK_STREAM)server.setblocking(0)# Bind the socket to the portserver_address = ('localhost', 10000)print >>sys.stderr, 'starting up on %s port %s' % server_addressserver.bind(server_address)# Listen for incoming connectionsserver.listen(5)# Keep up with the queues of outgoing messagesmessage_queues = {}

The timeout value passed to poll() is represented in milliseconds, instead of seconds, so in order to pause for a full second the timeout must be set to 1000.

# Do not block forever (milliseconds)TIMEOUT = 1000

Python implements poll() with a class that manages the registered data channels being monitored. Channels are added by calling register() with flags indicating which events are interesting for that channel. The full set of flags is:

EventDescriptionPOLLINInput readyPOLLPRIPriority input readyPOLLOUTAble to receive outputPOLLERRErrorPOLLHUPChannel closedPOLLNVALChannel not open

The echo server will be setting up some sockets just for reading, and others to be read from or written to. The appropriate combinations of flags are saved to the local variables READ_ONLYand READ_WRITE.

# Commonly used flag setesREAD_ONLY = select.POLLIN | select.POLLPRI | select.POLLHUP | select.POLLERRREAD_WRITE = READ_ONLY | select.POLLOUT

The server socket is registered so that any incoming connections or data triggers an event.

# Set up the pollerpoller = select.poll()poller.register(server, READ_ONLY)

Since poll() returns a list of tuples containing the file descriptor for the socket and the event flag, a mapping from file descriptor numbers to objects is needed to retrieve the socket to read or write from it.

# Map file descriptors to socket objectsfd_to_socket = { server.fileno(): server,               }

The server’s loop calls poll(), then processes the “events” returned by looking up the socket and taking action based on the flag in the event.

while True:    # Wait for at least one of the sockets to be ready for processing    print >>sys.stderr, '\nwaiting for the next event'    events = poller.poll(TIMEOUT)    for fd, flag in events:        # Retrieve the actual socket from its file descriptor        s = fd_to_socket[fd]

As with select(), when the main server socket is “readable,” that really means there is a pending connection from a client. The new connection is registered with the READ_ONLY flags to watch for new data to come through it.

        # Handle inputs        if flag & (select.POLLIN | select.POLLPRI):            if s is server:                # A "readable" server socket is ready to accept a connection                connection, client_address = s.accept()                print >>sys.stderr, 'new connection from', client_address                connection.setblocking(0)                fd_to_socket[ connection.fileno() ] = connection                poller.register(connection, READ_ONLY)                # Give the connection a queue for data we want to send                message_queues[connection] = Queue.Queue()

Sockets other than the server are existing clients, and recv() is used to access the data waiting to be read.

            else:                data = s.recv(1024)

If recv() returns any data, it is placed into the outgoing queue for the socket and the flags for that socket are changed using modify() so poll() will watch for the socket to be ready to receive data.

                if data:                    # A readable client socket has data                    print >>sys.stderr, 'received "%s" from %s' % (data, s.getpeername())                    message_queues[s].put(data)                    # Add output channel for response                    poller.modify(s, READ_WRITE)

An empty string returned by recv() means the client disconnected, so unregister() is used to tell the poll object to ignore the socket.

                else:                    # Interpret empty result as closed connection                    print >>sys.stderr, 'closing', client_address, 'after reading no data'                    # Stop listening for input on the connection                    poller.unregister(s)                    s.close()                    # Remove message queue                    del message_queues[s]

The POLLHUP flag indicates a client that “hung up” the connection without closing it cleanly. The server stops polling clients that disappear.

        elif flag & select.POLLHUP:            # Client hung up            print >>sys.stderr, 'closing', client_address, 'after receiving HUP'            # Stop listening for input on the connection            poller.unregister(s)            s.close()

The handling for writable sockets looks like the version used in the example for select(), except that modify() is used to change the flags for the socket in the poller, instead of removing it from the output list.

        elif flag & select.POLLOUT:            # Socket is ready to send data, if there is any to send.            try:                next_msg = message_queues[s].get_nowait()            except Queue.Empty:                # No messages waiting so stop checking for writability.                print >>sys.stderr, 'output queue for', s.getpeername(), 'is empty'                poller.modify(s, READ_ONLY)            else:                print >>sys.stderr, 'sending "%s" to %s' % (next_msg, s.getpeername())                s.send(next_msg)

And finally, any events with POLLERR cause the server to close the socket.

        elif flag & select.POLLERR:            print >>sys.stderr, 'handling exceptional condition for', s.getpeername()            # Stop listening for input on the connection            poller.unregister(s)            s.close()            # Remove message queue            del message_queues[s]

When the poll-based server is run together with select_echo_multiclient.py (the client program that uses multiple sockets), the output is:

$ python ./select_poll_echo_server.pystarting up on localhost port 10000waiting for the next eventwaiting for the next eventwaiting for the next eventnew connection from ('127.0.0.1', 58447)waiting for the next eventnew connection from ('127.0.0.1', 58448)received "This is the message. " from ('127.0.0.1', 58447)waiting for the next eventsending "This is the message. " to ('127.0.0.1', 58447)received "This is the message. " from ('127.0.0.1', 58448)waiting for the next eventoutput queue for ('127.0.0.1', 58447) is emptysending "This is the message. " to ('127.0.0.1', 58448)waiting for the next eventoutput queue for ('127.0.0.1', 58448) is emptywaiting for the next eventreceived "It will be sent " from ('127.0.0.1', 58447)received "It will be sent " from ('127.0.0.1', 58448)waiting for the next eventsending "It will be sent " to ('127.0.0.1', 58447)sending "It will be sent " to ('127.0.0.1', 58448)waiting for the next eventoutput queue for ('127.0.0.1', 58447) is emptyoutput queue for ('127.0.0.1', 58448) is emptywaiting for the next eventreceived "in parts." from ('127.0.0.1', 58447)received "in parts." from ('127.0.0.1', 58448)waiting for the next eventsending "in parts." to ('127.0.0.1', 58447)sending "in parts." to ('127.0.0.1', 58448)waiting for the next eventoutput queue for ('127.0.0.1', 58447) is emptyoutput queue for ('127.0.0.1', 58448) is emptywaiting for the next eventclosing ('127.0.0.1', 58448) after reading no dataclosing ('127.0.0.1', 58448) after reading no datawaiting for the next event

Platform-specific Options

Less portable options provided by select are epoll, the edge polling API supported by Linux;kqueue, which uses BSD’s kernel queue; and kevent, BSD’s kernel event interface. Refer to the operating system library documentation for more detail about how they work.