This generally relates to computer networking and communications, and more particularly, to enhanced data communications over certain local networks, such as the Enhanced Ethernet, by use of accelerated socket interfaces.
Socket technology, as one of the most fundamental technologies of computer networking, has been employed for roughly two decades. A socket represents a single bidirectional connection between two pieces of software or applications, which allows either side of the connection to send and receive data. Usually socket-based software runs on two separate computers over a network, although sockets can also be used to communicate locally within a single computer, i.e., inter-process communications. The implementation of sockets can be based on standard mechanisms built into network hardware and operating systems, such as code libraries packaged with the operating system. Several libraries exist for implementing socket Application Programmable Interfaces (APIs), among which the first mainstream socket library is called the Berkeley Sockets API. These code libraries provide various functions for creating and using sockets. For example, socket ( ) is used to create a new socket of a certain socket type, connect ( ) is used to assign a free local port number to a socket, and the functions of send ( ) and receive ( ) are used for sending and receiving data to/from a remote socket.
Socket interfaces can be divided into three categories. The most commonly-used type, stream socket, implements connection-oriented semantics. Essentially, a “stream” requires that the two communicating parties first establish a socket connection, after which any data passed through that connection will be guaranteed to arrive in the same order in which it was sent. In comparison, the second type, datagram socket, offers connection-less semantics. With datagrams, connections are implicit rather than explicit as with streams. Either party simply sends datagrams as needed and waits for the other to respond. This means, messages can be lost in transmission or received out of order, and the socket is not configured to address these problems. In general, datagram sockets provide more flexibility as compared to stream sockets. The third type of socket is called raw sockets, which bypasses the built-in support for standard protocols such as Transmission Control Protocol (TCP) and User Datagram Protocol (UDP). Raw sockets are often used for custom low-level protocol development.
Today, sockets are typically used in conjunction with various Internet protocols, including Internet Protocol (IP), TCP and UDP. The combined use of sockets and TCP may be ideal for unreliable wide area networks, but in a semi-reliable local area network, such as the enhanced Ethernet with growing popularity in enterprise data centers, there are quite a few disadvantages due to certain specific algorithms under TCP. For instance, TCP uses a slow start algorithm to avoid congestion when data transmission is started. However, this can be unnecessary in the context of the enhanced Ethernet that already provides congestion management. Also, certain applications require high bandwidths for data transfer or involve frequent stops and starts in data transmission (e.g., file system or disk storage protocols). The use of slow start algorithm under TCP may compromise or even conflict these requirements. Similarly, the congestion avoidance algorithm in TCP may be unnecessary in view of the congestion management provided in the enhanced Ethernet protocol. As another example, TCP allows data packets to be received out of order, which typically occurs when some packets are being dropped due to network congestion or packet reordering in the network. According to the TCP protocol, the out-of-order packets would be buffered and put back in order when the dropped packets are resent and received. This may create significant complexity and memory overhead in Network Interface Cards (NICs) in support of TCP operations. In contrast, in the enhanced Ethernet, out-of-order packets are simply dropped, thereby avoiding any buffering and the associated overhead.
In view of the above, there is a need for an improved method of using sockets in connection with TCP over certain local networks, such as the enhanced Ethernet, to ensure efficient data transfer and communications within the network.
Embodiments of the present invention relate to an improved method of using sockets in connection with TCP over semi-reliable local networks, such as the enhanced Ethernet, to ensure efficient data transfer and network communications thereof. In one embodiment, provided is a method for enhancing data communications between a first computer and a second computer connected therewith via a computer network, which comprises the steps of: advertising receiving space in the second computer to the first computer, the receiving space comprising one or more receive buffers posted by a receive application at the second computer; transmitting a plurality of data packets from the first computer to the second computer over the computer network, wherein the plurality of data packets are received in a few buffers to be returned to the receiving application; and advertising updated receiving space at the second computer to the first computer, the updated receiving space comprising the one or more receive buffers posted by the receiving application excluding the few buffers returned to the receiving application, wherein the updated receiving space is advertised concurrently with sending an acknowledgement message of receiving the data packets. Computer-readable storage medium comprising computer-executable instructions for executing one or more steps of the above method is also provided according to various embodiments of the invention.
Another embodiment of the invention provides a method for enhancing data communications between computers connected to a computer network. Such a method comprises: transmitting a plurality of data packets from a first computer to a second computer over the computer network; setting a PUSH bit in one data packet amongst the plurality of data packets to indicate the one data packet is a last ready packet out of all data packets ready to be sent from the first computer before a break; sending an acknowledgement message to confirm receipt of the one data packet with the PUSH bit set therein at the second computer; and after receiving the acknowledgement message at the first computer, re-assuming data transmission from the first computer to the second computer.
Yet another embodiment of the invention provides a network interface controller implemented in a network capable device, wherein the network interface controller configured for: establishing a network connection between the network capable device and a receiver over a computer network; posting transmit buffers on the network connection for a sending application in the network capable device; transmitting a plurality of data packets from the transmit buffers to the receiver over the computer network; and setting a PUSH bit in one data packet amongst the plurality of data packets to indicate the one data packet is a last ready data packet out of all data packets ready to be sent from the sending application.
Also, according to one embodiment of the invention, a host computer system connected to a computer network comprises a host processor configured to execute one or more host applications; a host memory accessible to the host processor, the host memory comprising a plurality of data buffers; and a network interface controller coupled to the host processor, the network interface controller configured to enable a network connection between the host computer system and the computer network, the network interface controller further configured for: posting transmit buffers for a sending application in the host computer system; transmitting a plurality of data packets from the transmit buffers to a receiver over the computer network; and setting a PUSH bit in one data packet amongst the plurality of data packets to indicate the one data packet is a last ready data packet out of all data packets ready to be sent from the sending application.
In the following description of preferred embodiments, reference is made to the accompanying drawings which form a part hereof, and in which it is shown by way of illustration specific embodiments in which the invention can be practiced. It is to be understood that other embodiments can be used and structural changes can be made without departing from the scope of the embodiments of this invention.
Embodiments of the present invention relate to an improved method of using sockets in connection with TCP over semi-reliable local networks, such as the enhanced Ethernet, to ensure efficient data transfer and network communications thereof. Particularly, an accelerated socket protocol is provided, for which a PUSH bit used in conventional protocols such as TCP is re-defined so as to enhance communications between different host computer systems connected to an enhanced Ethernet network. According to the accelerated socket protocol, a host computer, and more specifically, through a network interface controller (NIC) implemented therein, while sending a number of data packets, is able to indicate a final data packet by setting the PUSH bit and thereby invite an automatic acknowledgement confirming receipt of data from the receiving computer. In addition, the accelerated socket protocol allows a host computer, while receiving data packets, to advertise an effective window that always correspond to the actually available receiving space of posted receiving buffers in the host computer. As compared to conventional sockets and TCP protocols, the accelerated sockets according to various embodiments of the invention not only improve the performance but also reduce cost in hardware implementations. In addition, from the software standpoint, the use of accelerated socket stacks can significantly lower the overhead in a host computer.
Although embodiments of the invention may be described and illustrated herein in terms of socket APIs in conjunction with the TCP protocol over the enhanced Ethernet, it should be understood that embodiments of this invention are not so limited, but may additionally be applied in the context of other protocols, such as iSCSI, CIFS and NFS, as applied in semi-reliable local networks. In addition, embodiments of the invention essentially allows a receiving computer to advertise a window equal to the size of receive buffers posted by the receiving application and keep the sending computer in synchronization in the event that a partially-filled buffer is returned to the receiving application. Although these embodiments of the invention may be described and illustrated herein using specific mechanisms such as the PUSH bit, it should be understood that many other mechanisms can be employed for the same or similar purposes without departing from the spirit of the invention.
Referring to
Within the host computer A 110, there is a Network Interface Controller (NIC) 112, which is a hardware interface for handling the network connectivity between the host computer 110 and other elements on the network, for example, another host computer 120. The NIC 112 has a ROM chip with a unique Media Access Control (MAC) address burned therein. The MAC address, typically a 48-bit serial number, identifies the vendor MAC address within the LAN. Through the MAC address the NIC 112 provides a low-level addressing system. The NIC 112 also provides physical access to a networking medium, as it exists on both the “Physical Layer” and “Data Link Layer” of the OSI model. The NIC 112 is generally configured with one or more data transfer techniques, such as data polling, programmed I/O or interrupt-drive I/O, and DMA (Direct Media Access), etc. In some circumstances, a TCP Offload Engine (TOE) is implemented in the NIC to facilitate data transfer between host systems over the network. Specifically, the TOE offloads processing of the entire TCP/IP stack to the network controller. TOEs are primarily employed with high-speed network interfaces, such as gigabit Ethernet, where processing overhead of the network stack can be significant. However, the inclusion of TOE in every NIC also increases the implementation cost significantly.
The host computer 110 also includes one or more host applications or programs 114 having data communications with components within or outside the host computer 110. To facilitate these communications, particularly the communications with the NIC 112, and further, with the network, a networking Application Programmable Interface (API) 116 is often implemented, which, for instance, can be one of the conventional socket interfaces as discussed above.
Similar to the host computer A 110, the other host computer B 120 also contains a NIC 122, a host application or program 124 and an API 126 connected thereto. It should be understood that although only two computers are illustrated in
Further to the exemplary network configuration in
As shown in
Ideally, the data from the sending buffer 216 should be able to be exported to the NIC 212 and thereafter directly placed into the receiving buffer 226 over the network in order to achieve the most efficient zero-copy data transmission. However, for many applications, the data transfer process involves copying at least part of the received data. In fact, under the conventional TCP operations, a significant amount of processor time is consumed for copying received data from the system packet buffers to the application receiving buffer. When the amount of data requested by the receiving program is large, it is preferable to hold the data in the sending buffer until it is requested. But if the amount of data to be transferred is small, it is desirable to copy the data and avoid the expensive context switches, since the copying step can be done almost synchronously within a socket receive or read call, as shown in
The above-stated problem can be further demonstrated in the data transmission process in
Back to the data transfer process, at step 454, after the sender is informed of the buffer space, it starts transmitting the first data packet over the network to the receiver. Then the sender continues to send one or more data packets to the receiver at step 456. For reliable data transmission and delivery, most protocols require an acknowledgment from the receiver regarding the received data. As an example, TCP requires the receiver send an acknowledgement message every two received data packets. Thus, at step 458, the receiver sends an acknowledgement (ACK) message to confirm receipt of the data packets. Concurrently with sending the ACK message, the receiver may also advertise the updated receiving space to the sender. However, as mentioned above, it can be complicated to dynamically calculate the remaining receiving space in the receive buffer. Also, there can cause significant time overhead each time the updated space is reported along with the acknowledgement message because the acknowledgement of data receipt can be required as frequent as every two data packets.
In practice, the methods, processes or steps described herein may constitute one or more programs made up of machine-executable or computer-executable instructions. The above description with reference to the flowcharts in
Although embodiments of this invention have been fully described with reference to the accompanying drawings, it is to be noted that various changes and modifications will become apparent to those skilled in the art. Such changes and modifications are to be understood as being included within the scope of embodiments of this invention as defined by the appended claims.
Number | Date | Country | |
---|---|---|---|
Parent | 12707594 | Feb 2010 | US |
Child | 14483633 | US |