Recherche Images Maps Play YouTube Actualités Gmail Drive Plus »
Connexion
Les utilisateurs de lecteurs d'écran peuvent cliquer sur ce lien pour activer le mode d'accessibilité. Celui-ci propose les mêmes fonctionnalités principales, mais il est optimisé pour votre lecteur d'écran.

Brevets

  1. Recherche avancée dans les brevets
Numéro de publicationUS7831720 B1
Type de publicationOctroi
Numéro de demandeUS 12/122,570
Date de publication9 nov. 2010
Date de dépôt16 mai 2008
Date de priorité17 mai 2007
État de paiement des fraisPayé
Numéro de publication12122570, 122570, US 7831720 B1, US 7831720B1, US-B1-7831720, US7831720 B1, US7831720B1
InventeursWael Noureddine, Asgeir Thor Eiriksson
Cessionnaire d'origineChelsio Communications, Inc.
Exporter la citationBiBTeX, EndNote, RefMan
Liens externes: USPTO, Cession USPTO, Espacenet
Full offload of stateful connections, with partial connection offload
US 7831720 B1
Résumé
A method of operating a system including a host and intelligent network interface circuitry extends a passive open operation to accomplish full offload of a stateful connection between a host and a peer. In response to observing a synchronization signal from the peer, an offload target creates a connection control block in the offload target in anticipation of a corresponding stateful connection being offloaded from the host. The observed synchronization signal is allowed to be provided to the host. In response to observing a synchronization acknowledgment signal from the host and destined for the peer, the offload target performs establishment processing for the stateful connection. Based on an acknowledgment of the synchronization acknowledgment signal from the peer, acknowledgement of the synchronization acknowledgement signal is processed and a corresponding acknowledgment signal is provided to the host. In response to receiving an offload event indication from the host, the stateful connection is operated between the host and the peer.
Images(7)
Previous page
Next page
Revendications(11)
1. A method of operating an offload target in a system including a host and the offload target, to extend a passive open operation to accomplish full offload of a stateful connection between the host and a peer via a network, the method comprising:
in response to observing a synchronization signal from the peer, processing an offload listening server corresponding to the observed synchronization signal and, in accordance with a result of processing the offload listening server, creating a connection control block in anticipation of a corresponding stateful connection being offloaded from the host;
allowing the observed synchronization signal to be provided to the host;
in response to observing a synchronization acknowledgment signal from the host and destined for the peer and, performing establishment processing for the stateful connection;
receiving an acknowledgment of the synchronization acknowledgment signal from the peer, processing the acknowledgement of the synchronization acknowledgement signal and providing a corresponding acknowledgment signal to the host; and
in response to receiving an offload event indication from the host, operating the stateful connection between the host and the peer,
the method further comprising, in response to not receiving a offload event indication from the host, not operating the stateful connection between the host and the peer, causing data packets received from the peer to be provided to the host without maintaining a connection state in the offload target.
2. The method of claim 1, wherein:
observing a synchronization signal includes observing a TCP packet including a set SYN flag.
3. The method of claim 1, wherein:
observing a synchronization acknowledgement signal from the host includes observing a TCP packet from the host including set SYN and ACK flags.
4. The method of claim 1, wherein:
the stateful connection is a connection according to a TCP/IP protocol.
5. A method of operating an offload target that interfaces a host to a network for communication with a peer via a stateful connection; comprising:
observing signals to establish a connection between the host and the peer;
processing an offload listening server corresponding to the observed connection establishment signals and, in accordance with a result of processing the offload listening server, establishing a shadow connection between the host and peer, usable for the offload target to offload data transfer phase processing of the connection, from the host; and
carrying out, in the offload target, data transfer phase processing of the connection,
the method further comprising, in response to not receiving an offload event indication from the host, not carrying out, in the offload target, data transfer phase processing of the connection, causing data packets received from the peer to be provided to the host without maintaining the shadow connection in the offload target.
6. A system including a host and an offload target, configured to extend a passive open operation to accomplish full offload of a stateful connection between the host and a peer via a network, wherein the offload target is configured to:
in response to observing a synchronization signal from the peer, process an offload listening server corresponding to the observed synchronization signal and, in accordance with a result of processing the offload listening server, create a connection control block in anticipation of a corresponding stateful connection being offloaded from the host;
allow the observed synchronization signal to be provided to the host;
in response to observing a synchronization acknowledgment signal from the host and destined for the peer and, performing establishment processing for the stateful connection;
receive an acknowledgment of the synchronization acknowledgment signal from the peer, and process the acknowledgement of the synchronization acknowledgement signal and provide a corresponding acknowledgment signal to the host; and
in response to receiving an offload event indication from the host, operate the stateful connection between the host and the peer,
wherein the offload target is further configured to, in response to not receiving an offload event indication from the host, not operate the stateful connection between the host and the peer, cause data packets received from the peer to be provided to the host without maintaining a connection state in the intelligent network interface circuitry.
7. The system of claim 6, wherein:
observing a synchronization signal includes observing a TCP packet including a set SYN flag.
8. The system of claim 6, wherein:
observing a synchronization acknowledgement signal from the host includes observing a TCP packet from the host including set SYN and ACK flags.
9. The system of claim 6, wherein:
the stateful connection is a connection according to a TCP/IP protocol.
10. An offload target that interfaces a host to a network for communication with a peer via a stateful connection; the offload target configured to:
observe signals to establish a connection between the host and the peer;
process an offload listening server corresponding to the observed connection establishment signals and, in accordance with a result of processing the offload listening server, establish a shadow connection between the host and peer, usable for the offload target to offload data transfer phase processing of the connection, from the host; and
carry out, in the offload target, data transfer phase processing of the connection,
the offload target further configured to, in response to not receiving an offload event indication from the host, not carry out, in the offload target, data transfer phase processing of the connection, and cause data packets received from the peer to be provided to the host without maintaining the shadow connection in the offload target.
11. The system of claim 10, wherein:
the offload target is further configured to carry out shutdown phase processing of the connection.
Description
RELATED APPLICATIONS

This application claims priority under 35 USC 119(e) to U.S. Provisional Patent Application No. 60/938,640, filed May 17, 2007 and entitled “FULL OFFLOAD WITH PARTIAL OFFLOAD” which is incorporated by reference herein in its entirety.

BACKGROUND

Protocol offload processing is known. For example, an interface device (sometimes known as intelligent network interface circuitry or an “offload target”) may be provided to operate in coordination with a host, for protocol offload processing with a peer device across a network. For example, the protocol offload processing may be according to the Transmission Control Protocol (TCP) whereas communication across the network may be via high-speed Ethernet, such as 10 Gbps Ethernet. FIG. 1 illustrates an architecture of a system including a host, network interface circuitry including an offload target, and a peer configured for communication with the host according to a stateful protocol such as TCP/IP.

Furthermore, it is known that the protocol offload processing may be, for example, “partial offload” or “full offload.” For example, with “full offload,” the offload target handles all the phases of a connection. That is, in addition to handling the data transfer phase of a connection, the offload target is additionally at least responsible for establishing a connection, including handling retransmissions, if necessary, during connection establishment.

“Partial offload” has various flavors. Examples include the following:

    • offload target handles only the data transfer phase of a connection-oriented protocol, which for example might include processing to reorder the received packets when they are received out of order.
    • offload target handles only the data transfer phase and the connection teardown phase of a connection-oriented protocol.
    • offload target handles the “mainstream” part of the data transfer phase, deferring exceptions, such as out of order processing, to the host system.

Partial offload solutions have been promulgated such as, for example, the “TCP Chimney” feature of recently released Vista operating system from Microsoft. Like conventional partial offload solutions, the TCP Chimney feature appears to be designed to retain full control over connection acceptance while, in addition, simplifying management of listening servers.

A listening server, for example, is used when a peer requests a connection to a local host, such as a TCP/IP connection at a specified IP address and port number. A listening server typically has an LIP, LP, FIP, and FP attribute, such that a listening server on the local host is listening for connect requests to local IP address LIP, at local port number LP, from a foreign IP address FIP, and from foreign port FP at the FIP. The FIP and FP fields for the listening server many times have “don't care values,” such that connect requests are accepted from any FP on any FIP. A listening server may, in addition, have a protocol attribute such as TCP, or SCTP (Stream Control Transfer Protocol), as the SCTP protocol and other connection oriented protocols use a similar listening server mechanism to receive connect requests.

The connect request is received by the listening server that then forwards the request to a connection manager that either accepts all connect requests, or that uses various criteria such as ACL (Access Control Lists) to either accept or reject a connect request.

FIG. 2 illustrates an example of an “active open” operation to open a TCP/IP connection between the host and the peer, according to the TCP Chimney architecture. At 201, the host stack sends an active open request to the peer via a SYN packet. At 202, the peer responds with a SYN/ACK. The host stack sends an ACK in response to the SYN/ACK. At this point, the connection has been established on the host stack.

At 204, the host stack initiates offload of the connection to the offload target. At 205, a data packet arrives from the peer after the host stack initiates the connection offload but before the connection has been set up on the offload target. The data packet is therefore sent to the host. At 206, the host stack receives the data packet. Detecting that the offload is in progress, the host stack retains the data packet.

At 207, the offloading is complete. At 208, the host stack forwards the data packet back to the offload target for processing. At 209, the offload target processes the packet and provides an acknowledgment back to the peer.

We now discuss how a control block may be configured in accordance with an example of an active open operation. An example of such a control block is shown immediately below:

CONST_STATE
 Flags = 0x0
 RemotePort = 0xF3FB
 LocalPort = 0x46B4
 SndWindScale = 0x0
 RcvWindScale = 0x0
 RemoteMss = 1460:0
CACHED_STATE
 Flags = 0x2
 InitialRcvWnd = 0
 RcvIndicationSize = 0
 KaProbeCount = 0
 KaTimeout = 0x0
 KaInterval = 0x0
 MaxRT = 0x0
 FlowLabel = 0x0
 TtlOrHopLimit = 0x80
 TosOrTrafficClass = 0x0
 UserPriority = 0x0
DELEGATED_STATE
 State = TcpConnectionSynSent
 Flags = 0x0
 RcvNxt = 0x0
 RcvWnd = 0x0
 SndUna = 0x0
 SndNxt = 0x0
 SndMax = 0x0
 SndWnd = 17520
 MaxSndWnd = 0x0
 SendWL1 = 0x0
 CWnd = 0xB68
 SsThresh = 0xFFFFFFFF
 SRtt = 0x0
 RttVar = 0x1E
 TsRecent = 0x0
 TsRecentAge = 0x0
 TsTime = 0x0
 TotalRT = 0x0
 DupAckCount = 0x0
 SndWndProbeCount = 0x0
 KeepAlive.ProbeCount = 0x0
 KeepAlive.TimeoutDelta = 0x0
 Retransmit.Count = 0x0
 Retransmit.TimeoutDelta = 0xFFFFFFFF
 SendDataHead = 0x0
 SendDataTail = 0x0
 SendBacklogSize = 0x0
 Buffered Data = 0x0
 ReceiveBacklogSize = 0x0

In accordance with one example of an active open operation, a “constant state” portion of a connection control block is provided in a manner that it may otherwise be provided in a configuration that does not include an offload target. A “cached state” portion of the connection control block may be partly determined by the offload target. The delegated state portion may be partially filled in by the offload target when the connection establishment succeeds. It is noted that, prior to connection establishment succeeding, all send and receive sequence numbers are undefined and the TCP state is SYN_SENT. The offload target interprets such a control block as being for an offloaded active open.

In accordance with other conventional implementations, an active open operation is achieved in a full offload manner. That is, in essence, the host requests the offload target to establish and operate a connection. FIG. 3 illustrates an example of an active open operation, for a TCP/IP connection, being achieved in a full offload manner. At 301, the host stack provides an “initiate offload” request to the offload target. The “initiate offload” request may be more generally referred to an offload event indication. At 302, the offload target provides a SYN packet to the remote peer. It is noted that the offload target handles any SYN retransmission issues, if any. At 303, the peer responds with a SYN/ACK packet. At this point, the connection is established and the connection control block is populated on the offload target. At 304, the offload target provides an “initiate complete” indication back to the host stack.

At 305, the offload target provides an ACK packet to the peer, in response to the SYN/ACK packet provided from the peer. At 306 and 307, the offload target receives a data packet (306) and acknowledges the data packet (307).

FIG. 4 illustrates an example of a partial offload “passive open” operation to open a TCP/IP connection between the host and the peer, according to the TCP Chimney architecture. At 401, the host stack receives a passive open request from the peer via a SYN packet. At 402, the host stack responds with a SYN/ACK. At 403, the peer sends an ACK in response to the SYN/ACK. At this point, the connection has been established on the host stack.

At 404, a data packet arrives from the peer. Meanwhile, at 405, the host receives the ACK and initiates a connection offload to the offload target. At 406, the host stack receives the data packet before the connection has been set up on the offload target. Detecting that the offload operation is in progress, the host stack retains the data packet. At 407, the host stack receives a message from the offload target that the offload operation is complete.

At 408, the host stack forwards the data packet to the offload target for processing. At 409, the offload target processes the data packet and sends an ACK to the peer. At 410, the peer receives the ACK corresponding to receipt of the data packet by the host.

We now discuss how a control block may be configured in accordance with an example of a partial offload passive open operation such as described relative to FIG. 4. An example of such a control block is shown immediately below:

CONST_STATE
 Flags = 0x0
 RemotePort = 0xF3FB
 LocalPort = 0x46B4
 SndWindScale = 0x0
 RcvWindScale = 0x0
 RemoteMss = 1460:0
CACHED_STATE
 Flags = 0x2
 InitialRcvWnd = 0
 RcvIndicationSize = 0
 KaProbeCount = 0
 KaTimeout = 0x0
 KaInterval = 0x0
 MaxRT = 0x0
 FlowLabel = 0x0
 TtlOrHopLimit = 0x80
 TosOrTrafficClass = 0x0
 UserPriority = 0x0
DELEGATED_STATE
 State = TcpConnectionSynRcvd
 Flags = 0x0
 RcvNxt = 0xA1CD
 RcvWnd = 0xFFFF
 SndUna = 0x0
 SndNxt = 0x0
 SndMax = 0x0
 SndWnd = 17520
 MaxSndWnd = 0xFFFF
 SendWL1 = 0x0
 CWnd = 0xB68
 SsThresh = 0xFFFFFFFF
 SRtt = 0x0
 RttVar = 0x1E
 TsRecent = 0x0
 TsRecentAge = 0x0
 TsTime = 0x0
 TotalRT = 0x0
 DupAckCount = 0x0
 SndWndProbeCount = 0x0
 KeepAlive.ProbeCount = 0x0
 KeepAlive.TimeoutDelta = 0x0
 Retransmit.Count = 0x0
 Retransmit.TimeoutDelta = 0xFFFFFFFF
 SendDataHead = 0x0
 SendDataTail = 0x0
 SendBacklogSize = 0x0
 Buffered Data = 0x0
 ReceiveBacklogSize = 0x0

In accordance with one example of a passive open operation, a “constant state” portion of a connection control block is provided in a manner that it may otherwise be provided in a configuration that does not include an offload target. In addition, a “cached state” portion of the connection control block may also be provided in a manner that may otherwise be provided in a configuration that does not include an offload target.

The “delegated state” portion of the connection control block may be partially filled in by the offload target when the connection establishment succeeds. It is noted that, prior to connection establishment succeeding, all send and receive sequence numbers are undefined and the TCP state is SYN_RCVD. The offload target interprets such a control block as being for an offloaded passive open.

FIG. 5 illustrates an example of a full offload “passive open” operation to open a connection (in this case, a TCP/IP connection) between the host and the peer. At 501, the peer issues a passive open via a SYN packet. The offload target initiates a connection control block in the SYN_RCVD state and, also, provides the SYN packet to the host stack. At 502, the host stack provides an initiate offload indication to the offload target. Alternately, the indication may be an indication that the connection is not to be established.

At 503, based on the initiate offload indication, the offload target provides a SYN/ACK to the peer. Furthermore, at 503, the offload target deals with connection establishment issues such as SYN/ACK retransmission issues. At 504, the peer issues an ACK packet for the SYN/ACK packet. At 505, the peer sends a data packet. At 506, the offload target provides an “initiate complete” indication to the host stack. It is noted that the initiate complete indication may be temporally before or after the offload target receives the data packet (505). In any case, the offload target handles the data packet and, at 507, provides a corresponding ACK packet back to the peer.

SUMMARY

A method of operating a system including a host and intelligent network interface circuitry extends a passive open operation to accomplish full offload of a stateful connection between a host and a peer. In response to observing a synchronization signal from the peer, an offload target creates a connection control block in the offload target in anticipation of a corresponding stateful connection being offloaded from the host. The observed synchronization signal is allowed to be provided to the host;

In response to observing a synchronization acknowledgment signal from the host and destined for the peer, the offload target performs establishment processing for the stateful connection. Based on an acknowledgment of the synchronization acknowledgment signal from the peer, acknowledgement of the synchronization acknowledgement signal is processed and a corresponding acknowledgment signal is provided to the host.

In response to receiving an offload event indication from the host, the stateful connection is operated between the host and the peer.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an architecture of a system including a host and an offload target, configured to communicate with a peer via a stateful connection.

FIG. 2 illustrates an example of an “active open” operation to open a TCP/IP connection between the host and the peer, according to the TCP Chimney architecture.

FIG. 3 illustrates an example of an active open operation, for a TCP/IP connection, being achieved in a full offload manner.

FIG. 4 illustrates an example of a partial offload “passive open” operation to open a TCP/IP connection between the host and the peer, according to the TCP Chimney architecture.

FIG. 5 illustrates an example of a full offload “passive open” operation to open a connection (in this case, a TCP/IP connection) between the host and the peer.

FIG. 6 illustrates an example of a method to utilize a full offload capability of an offload target to “shadow” a host that operates according to a partial offload model.

DETAILED DESCRIPTION

In accordance with an aspect, a method is provided to utilize a full offload capability of an offload target to “shadow” a host that operates according to a partial offload model. The offload target accomplishes a passive open operation including “shadowing” connection establishment with the remote peer. The host retains control over connection acceptance. In addition, connection “handoff” may be simplified. In some examples, no change to the application program interface (API) for TCP offload may be required.

FIG. 6 illustrates one such example, for a TCP/IP connection. At 601, the peer issues a passive open via a SYN packet. At 602, the offload target observes the SYN and creates a connection control block at the offload target. This is in anticipation by the offload target of the connection being offloaded. In addition, a SYN packet is provided to the host.

At 603, the host begins connection establishment processing, responding to the provided SYN packet with a SYN/ACK packet and, for example, creating a connection control block at the offload target. At 604, the offload target detects the SYN/ACK packet from the host and performs connection establishment processing for the connection, including causing a SYN/ACK packet to be transmitted to the peer. The offload target may retransmit the SYN/ACK if necessary. At 605, the peer issues an ACK for the SYN/ACK and, at 606, the peer sends a data packet.

At 607, the host provides an “initiate offload” event to the offload target and the offload target provides an “initiate complete” event in response. In this case, a device driver in the host, for the offload target, knows that the offload target has been shadowing the connection setup process. The initiate offload event signals the offload target that it can now be in control of the connection and that the offload target can deliver to the host any data that may have been held in the offload target, including providing ACK packets to the peer as appropriate (608).

On the other hand, if the “initiate offload” event is not received by the device driver, the offload target operates under the assumption that the connection is to remain under control of the host. In this case, the data packets received by the offload target from the peer are provided to the host without maintaining the connection state in the offload target.

In the FIG. 6 example, at 602, the offload target may fetch an offloaded listening server process, if any the SYN packet received from the peer matches the LIP,LP, FIP,FP criteria of the listening server. Listening server processes (in the context of TCP/IP connections being handled by a host stack, in a non-offloaded manner) are conventionally used in some operating systems such as Linux as a coarse-grained mechanism to filter connect requests to the host stack. In particular, as is well-known, the TCP (Transmission Control Protocol) uses point to point connections to connect two communicating endpoints, with the endpoints often referred to as the local peer, and the foreign peer. The connection is typically identified by the IP (Internet Protocol) addresses of the local peer (LIP), and foreign peer (FIP), and the port number of the connection on the local peer (LP), and the port number on the foreign peer (FP). A listening server is utilized for the foreign peer to request a connect to the local peer at a specified IP address and port number. A listening server therefore has an LIP, LP, FIP, and FP attribute, such that a listening server on the local peer is listening for connect requests to local IP address LIP, at local port number LP, from a foreign IP address FIP, and from foreign port FP at the FIP. Typically the FIP and FP for the listening server have “don't care” values, i.e. accept connect requests from any FP on any FIP. A listening server in addition has a protocol attribute such as TCP, or SCTP (Stream Control Transfer Protocol), as the SCTP protocol and other connection oriented protocols use a similar listening server mechanism to receive connect requests. The connect request is received by the listening server that than forwards the request to a connection manager that either accepts all connect requests, or that uses various criteria such as ACL (Access Control Lists) to either accept or reject a connect request.

In the context of a system including an offload target, the listening server process concept has been extended to include an “offload policy” portion. Turning back to the FIG. 6 example, if the offload policy in the listening server matching the received SYN packet is set to offload, then the offload target creates the connection control block in anticipation of the connection being offloaded. If no matching listening server is found, or if one is found and the offload policy is set to “don't offload,” then no connection control block is created.

The many features and advantages of the invention are apparent from the written description and, thus, it is intended by the appended claims to cover all such features and advantages of the invention. Further, since numerous modifications and changes will readily occur to those skilled in the art, it is not desired to limit the invention to the exact construction and operation as illustrated and described. Hence, all suitable modifications and equivalents may be resorted to as falling within the scope of the invention.

Citations de brevets
Brevet cité Date de dépôt Date de publication Déposant Titre
US44451163 sept. 198224 avr. 1984Burroughs CorporationMethod for allocating bandwidth between stations in a local area network
US453399623 févr. 19826 août 1985International Business Machines CorporationPeripheral systems accommodation of guest operating systems
US549747621 sept. 19935 mars 1996International Business Machines CorporationScatter-gather in data processing system
US577818921 janv. 19977 juil. 1998Fujitsu LimitedSystem and method for converting communication protocols
US60875818 juin 199811 juil. 2000Mve, Inc.Regenerable thermal insulation and cooling elements insulated thereby
US622668027 avr. 19981 mai 2001Alacritech, Inc.Intelligent network interface system method for protocol processing
US624009422 déc. 199729 mai 2001Bell Atlantic Network Services, Inc.Statistical time division multiplexer for a wireless asymmetric local loop communication system
US624706012 nov. 199912 juin 2001Alacritech, Inc.Passing a communication control block from host to a local device such that a message is processed on the device
US633415326 déc. 200025 déc. 2001Alacritech, Inc.Passing a communication control block from host to a local device such that a message is processed on the device
US638947928 août 199814 mai 2002Alacritech, Inc.Intelligent network interface device and system for accelerated communication
US639348712 mars 200121 mai 2002Alacritech, Inc.Passing a communication control block to a local device such that a message is processed on the device
US639731624 juil. 199728 mai 2002Intel CorporationSystem for reducing bus overhead for communication with a network interface
US640117728 avr. 19994 juin 2002Nec CorporationMemory system for restructuring a main memory unit in a general-purpose computer
US642717128 févr. 200030 juil. 2002Alacritech, Inc.Protocol processing stack for use with intelligent network interface device
US642717315 déc. 199930 juil. 2002Alacritech, Inc.Intelligent network interfaced device and system for accelerated communication
US643462027 août 199913 août 2002Alacritech, Inc.TCP/IP offload network interface device
US647041513 oct. 199922 oct. 2002Alacritech, Inc.Queue system involving SRAM head, SRAM tail and DRAM body
US651016416 nov. 199821 janv. 2003Sun Microsystems, Inc.User-level dedicated interface for IP applications in a data packet switching and load balancing system
US6564267 *22 nov. 199913 mai 2003Intel CorporationNetwork adapter with large frame transfer emulation
US65913026 mars 20028 juil. 2003Alacritech, Inc.Fast-path apparatus for receiving data corresponding to a TCP connection
US659426811 mars 199915 juil. 2003Lucent Technologies Inc.Adaptive routing system and method for QOS packet networks
US66256713 mai 199923 sept. 2003Computer Network Technology CorporationCompression of buffered data
US66584809 mars 20012 déc. 2003Alacritech, Inc.Intelligent network interface system and method for accelerated protocol processing
US66812449 juin 200020 janv. 20043Com CorporationSystem and method for operating a network adapter when an associated network computing system is in a low-power state
US66877587 mars 20013 févr. 2004Alacritech, Inc.Port aggregation for network connections that are offloaded to network interface devices
US669786829 juil. 200224 févr. 2004Alacritech, Inc.Protocol processing stack for use with intelligent network interface device
US670137220 août 19982 mars 2004Canon Kabushiki KaishaData communication apparatus and method
US67082239 déc. 199916 mars 2004Microsoft CorporationAccelerating a distributed component architecture over a network using a modified RPC communication
US670823212 févr. 200116 mars 2004Hitachi, Ltd.Data migration method, protocol converter and switching apparatus using it
US671794631 oct. 20026 avr. 2004Cisco Technology Inc.Methods and apparatus for mapping ranges of values into unique values of particular use for range matching operations using an associative memory
US675166519 févr. 200315 juin 2004Alacritech, Inc.Providing window updates from a computer to a network interface device
US67572451 juin 200029 juin 2004Nokia CorporationApparatus, and associated method, for communicating packet data in a network including a radio-link
US675774620 févr. 200129 juin 2004Alacritech, Inc.Obtaining a destination address so that a network interface device can write network data without headers directly into host memory
US679250212 oct. 200014 sept. 2004Freescale Semiconductor, Inc.Microprocessor having a content addressable memory (CAM) device as a functional unit therein and method of operation
US679874322 mars 199928 sept. 2004Cisco Technology, Inc.Packet prioritization processing technique for routing traffic in a packet-switched computer network
US680758129 sept. 200019 oct. 2004Alacritech, Inc.Intelligent network storage interface system
US681365211 avr. 20022 nov. 2004Chelsio Communications, Inc.Reduced-overhead DMA
US686264829 oct. 20011 mars 2005Sun Microsystems, Inc.Interface emulation for storage devices
US69250555 mars 20012 août 2005Advanced Micro Devices, Inc.Systems and methods for traffic shaping
US693809227 août 200230 août 2005Alacritech, Inc.TCP offload device that load balances and fails-over between aggregated ports having different MAC addresses
US694138612 nov. 20036 sept. 2005Alacritech, Inc.Protocol processing stack for use with intelligent network interface device
US696594117 déc. 200115 nov. 2005Alacritech, Inc.Transmit fast-path processing on TCP/IP offload network interface device
US69960705 déc. 20037 févr. 2006Alacritech, Inc.TCP/IP offload device with reduced sequential processing
US703126721 déc. 200018 avr. 2006802 Systems LlcPLD-based packet filtering methods with PLD configuration data update of filtering rules
US70428989 mars 20019 mai 2006Alacritech, Inc.Reducing delays associated with inserting a checksum into a network message
US70765689 mars 200111 juil. 2006Alacritech, Inc.Data communication apparatus for computer intelligent network interface card which transfers data between a network and a storage device according designated uniform datagram protocol socket
US70893266 mai 20028 août 2006Alacritech, Inc.Fast-path processing for receiving data on TCP connection offload devices
US70930992 avr. 200315 août 2006Alacritech, Inc.Native lookup instruction for file-access processor searching a three-level lookup cache for variable-length keys
US71140962 avr. 200326 sept. 2006International Business Machines CorporationState recovery and failover of intelligent network adapters
US71242052 oct. 200117 oct. 2006Alacritech, Inc.Network interface device that fast-path processes solicited session layer read commands
US713390214 août 20037 nov. 2006Oracle International CorporationTransmitting acknowledgements using direct memory access
US713391431 oct. 20017 nov. 2006Cisco Technology, Inc.Statistics-preserving ACL flattening system and method
US713394014 mai 20017 nov. 2006Alacritech, Inc.Network interface device employing a DMA command queue
US716465619 avr. 200216 janv. 2007The Boeing CompanyCommunicating data through a network so as to ensure quality of service
US71679267 nov. 200123 janv. 2007Alacritech, Inc.TCP/IP offload network interface device
US716792726 févr. 200223 janv. 2007Alacritech, Inc.TCP/IP offload device with fast-path TCP ACK generating and transmitting mechanism
US717439312 mars 20026 févr. 2007Alacritech, Inc.TCP/IP offload network interface device
US718526612 févr. 200327 févr. 2007Alacritech, Inc.Network interface device for error detection using partial CRCS of variable length message portions
US719124127 sept. 200213 mars 2007Alacritech, Inc.Fast-path apparatus for receiving data corresponding to a TCP connection
US71913187 avr. 200313 mars 2007Alacritech, Inc.Native copy instruction for file-access processor with copy-rule-based validation
US723964216 juil. 20023 juil. 2007Network Appliance, Inc.Multi-protocol network interface card
US725463710 nov. 20057 août 2007Microsoft CorporationMethod to offload a network stack
US726063119 déc. 200321 août 2007Nvidia CorporationSystem and method for receiving iSCSI protocol data units
US72840478 nov. 200116 oct. 2007Microsoft CorporationSystem and method for controlling network demand via congestion pricing
US731362329 août 200325 déc. 2007Broadcom CorporationSystem and method for TCP/IP offload independent of bandwidth delay product
US737614718 déc. 200320 mai 2008Intel CorporationAdaptor supporting different protocols
US740890620 févr. 20025 août 2008Ericsson Inc.Mobile data communications apparatus, methods and computer program products implementing cellular wireless data communications via a wireless local area network
US745389216 févr. 200518 nov. 2008Slt Logic, LlcSystem and method for policing multiple data flows and multi-protocol data flows
US74746708 juil. 20036 janv. 2009Brooktree Broadband Holding, Inc.Method and system for allocating bandwidth
US749342714 juil. 200417 févr. 2009International Business Machines CorporationApparatus and method for supporting received data processing in an offload of network protocol processing
US7533176 *14 juil. 200412 mai 2009International Business Machines CorporationMethod for supporting connection establishment in an offload of network protocol processing
US758359628 juin 20041 sept. 2009Juniper Networks, Inc.Priority scheduling using per-priority memory structures
US7609696 *9 déc. 200327 oct. 2009Nvidia CorporationStoring and accessing TCP connection information
US200100100461 mars 200126 juil. 2001Muyres Matthew R.Client content management and distribution system
US2001002194914 mai 200113 sept. 2001Alacritech, Inc.Network interface device employing a DMA command queue
US200200393663 oct. 20014 avr. 2002Nec CorporationPacket switch and multicasting control system used for the same
US2002019162218 juin 200119 déc. 2002Zdan Michael A.System for and method of differentiated queuing in a routing system
US2003001851620 juil. 200123 janv. 2003International Business Machines CorporationMethod for dynamically evaluating projected days of supply of inventory levels in a supply chain
US200300354369 août 200220 févr. 2003International Business Machines CorporationMethod of allocating bandwidth on request to the stations of a local area network
US20030046330 *4 sept. 20016 mars 2003Hayes John W.Selective offloading of protocol processing
US20030158906 *18 nov. 200221 août 2003Hayes John W.Selective offloading of protocol processing
US2003020028414 avr. 200323 oct. 2003Alacritech, Inc.Freeing transmit memory on a network interface device prior to receiving an acknowledgement that transmit data has been received by a remote device
US2003020463130 avr. 200230 oct. 2003Microsoft CorporationMethod to synchronize and upload an offloaded network stack connection with a network stack
US2004000309418 juin 20031 janv. 2004Michael SeeMethod and apparatus for mirroring traffic over a network
US200400196896 janv. 200329 janv. 2004Fan Kan FrankieSystem and method for managing multiple stack environments
US200400280697 août 200212 févr. 2004Tindal Glen D.Event bus with passive queuing and active routing
US2004003074514 mai 200312 févr. 2004Boucher Laurence B.Method and apparatus for distributing network traffic processing on a multiprocessor computer
US2004004248719 août 20034 mars 2004Tehuti Networks Inc.Network traffic accelerator system and method
US2004005481317 sept. 200218 mars 2004Alacritech, Inc.TCP offload network interface device
US2004006224522 avr. 20031 avr. 2004Sharp Colin C.TCP/IP offload device
US2004006224619 juin 20031 avr. 2004Alacritech, Inc.High performance network interface
US2004006457827 sept. 20021 avr. 2004Alacritech, Inc.Fast-path apparatus for receiving data corresponding to a TCP connection
US2004006459030 sept. 20021 avr. 2004Alacritech, Inc.Intelligent network storage interface system
US2004007370327 sept. 200215 avr. 2004Alacritech, Inc.Fast-path apparatus for receiving data corresponding a TCP connection
US2004007848018 oct. 200222 avr. 2004Boucher Laurence B.Parsing a packet header
US200400882626 nov. 20026 mai 2004Alacritech, Inc.Enabling an enhanced function of an electronic device
US200401009523 oct. 200327 mai 2004Boucher Laurence B.Method and apparatus for dynamic packet batching with a high performance network interface
US2004011153528 nov. 200310 juin 2004Boucher Laurence B.Intelligent network interface system and method for accelerated protocol processing
US20040117509 *12 nov. 200317 juin 2004Alacritech, Inc.Protocol processing stack for use with intelligent network interface device
US2004015864030 avr. 200312 août 2004Philbrick Clive M.Transferring control of a TCP connection between devices
US2004016559221 févr. 200326 août 2004Sbc Properties, L.P.Extended virtual user-to-network interface with ATM network
US2004019053327 mars 200330 sept. 2004Prashant ModiMethod and apparatus for performing connection management with multiple stacks
US200401998082 avr. 20037 oct. 2004International Business Machines CorporationState recovery and failover of intelligent network adapters
US200402132358 avr. 200328 oct. 2004Marshall John W.Programmable packet classification system using an array of uniform content-addressable memories
US2004024043529 juin 20042 déc. 2004Alacritech, Inc.Obtaining a destination address so that a network interface device can write network data without headers directly into host memory
US20050216597 *24 mars 200429 sept. 2005Shah Hemal VMessage context based TCP transmission
US20060031524 *14 juil. 20049 févr. 2006International Business Machines CorporationApparatus and method for supporting connection establishment in an offload of network protocol processing
US20060235977 *15 avr. 200519 oct. 2006Wunderlich Mark WOffloading data path functions
US20070083638 *31 août 200512 avr. 2007Microsoft CorporationOffloaded neighbor cache entry synchronization
Citations hors brevets
Référence
1Allowed Claims from U.S. Appl. No. 10/474,500.
2Allowed Claims from U.S. Appl. No. 11/217,661.
3Allowed Claims from U.S. Appl. No. 11/250,894.
4Allowed Claims from U.S. Appl. No. 11/282,933.
5Allowed Claims from U.S. Appl. No. 11/313,003.
6Allowed Claims from U.S. Appl. No. 11/356,850.
7Allowed Claims in U.S. Appl. No. 11/330,898.
8Clark et al., "An Analysis of TCP Processing Overhead," IEEE Communications Magazine, Jun. 1989, pp. 23-29.
9Dalton et al., "Afterburner: Architectural Support for High-Performance Protocols," http://www.hpl.hp.com/techreports/93/HPL-93-46.pdf, Jul. 1993, 18 Pages.
10Final Office Action in U.S. Appl. No. 11/747,790, mailed Nov. 5, 2009.
11International Search Report in PCT/US02/12679, dated Jul. 23, 2002.
12Madsen et al., "Wireless Data Communication," Fall 2003 Presentation, Wireless Networks Division (WING), Allborg University.
13Notice of Allowance in U.S. Appl. No. 10/474,500, mailed Jul. 1, 2008.
14Notice of Allowance in U.S. Appl. No. 11/217,661 mailed Jan. 11, 2010.
15Notice of Allowance in U.S. Appl. No. 11/250,894, mailed Mar. 29, 2010.
16Notice of Allowance in U.S. Appl. No. 11/282,933 mailed Dec. 31, 2009.
17Notice of Allowance in U.S. Appl. No. 11/313,003, mailed Jun. 8, 2008.
18Notice of Allowance in U.S. Appl. No. 11/330,898, mailed Sep. 23, 2009.
19Notice of Allowance in U.S. Appl. No. 11/356,850, mailed Jun. 26, 2009.
20Office Action in U.S. Appl. No. 10/474,500, mailed Oct. 4, 2007.
21Office Action in U.S. Appl. No. 11/130,898 mailed Apr. 2, 2009.
22Office Action in U.S. Appl. No. 11/137,140 mailed Mar. 31, 2009.
23Office Action in U.S. Appl. No. 11/137,140, mailed Aug. 21, 2009.
24Office Action in U.S. Appl. No. 11/137,140, mailed Feb. 5, 2008.
25Office Action in U.S. Appl. No. 11/137,146, mailed Feb. 4, 2010.
26Office Action in U.S. Appl. No. 11/137,146, mailed Jun. 23, 2009.
27Office Action in U.S. Appl. No. 11/137,146, mailed Mar. 5, 2008.
28Office Action in U.S. Appl. No. 11/137,146, mailed Nov. 3, 2008.
29Office Action in U.S. Appl. No. 11/217,661 mailed Jun. 9, 2009.
30Office Action in U.S. Appl. No. 11/217,661, mailed Sep. 18, 2008.
31Office Action in U.S. Appl. No. 11/250,894 mailed Jan. 26, 2009.
32Office Action in U.S. Appl. No. 11/250,894, mailed Jun. 26, 2008.
33Office Action in U.S. Appl. No. 11/250,894, mailed Sep. 15, 2009.
34Office Action in U.S. Appl. No. 11/282,933 mailed Feb. 20, 2009.
35Office Action in U.S. Appl. No. 11/282,933, mailed Sep. 9, 2009.
36Office Action in U.S. Appl. No. 11/313,003, mailed Aug. 22, 2008.
37Office Action in U.S. Appl. No. 11/330,898, mailed Oct. 8, 2008.
38Office Action in U.S. Appl. No. 11/356,850 mailed Dec. 3, 2008.
39Office Action in U.S. Appl. No. 11/735,861, mailed Aug. 6, 2009.
40Office Action in U.S. Appl. No. 11/735,861, mailed Jan. 25, 2010.
41Office Action in U.S. Appl. No. 11/747,650, mailed Apr. 15, 2010.
42Office Action in U.S. Appl. No. 11/747,650, mailed Aug. 27, 2009.
43Office Action in U.S. Appl. No. 11/747,673, mailed Apr. 30, 2010.
44Office Action in U.S. Appl. No. 11/747,790 mailed May 12, 2009.
45Office Action in U.S. Appl. No. 11/747,790, mailed Mar. 9, 2010.
46Office Action in U.S. Appl. No. 11/747,793 mailed Jun. 8, 2009.
47Office Action in U.S. Appl. No. 11/747,793, mailed Jan. 25, 2010.
48Pratt, Ian and Fraser, Keir, "Arsenic: A User-Accessible Gigabit Ethernet Interface," INFOCOM 2001. Twentieth Annual Joint Conference of the IEEE Computer and Communications Societies. Proceedings. IEEE, vol. 1, Issue , 2001 pp. 67-76 vol. 1.
49Rütsche et al., "Architectures of Multimedia Communication Subsystems," IFIP Transactions; vol. C-23 archive, Proceedings of the IFIP TC6 International Conference on Information Networks and Data Communication table of contents, pp. 217-230, Year of Publication: 1994.
50Rütsche et al., "TCP/IP on the Parallel Protocol Engine," High Performace Networking, (IV, C-14), Elsevier Science Publishers, B.V. North Holland 1993.
51Thia et al., "A Reduced Operation Protocol Engine (ROPE) for a Multiple-Layer Bypass Architecture," Protocols for High-Speed Networks IV, 4th IFIP International Workshop, Aug. 10-12, 1994, Vancouver, B.C., Canada, pp. 224-239.
52Thia et al., "High-Speed OSI Protocol Bypass Algorithm with Window Flow Control," IFIP WG6.4 Third International Workshop on Protocols for High-Speed Networks, Stockholm, Sweden, May 13-15, 1992, pp. 53-68.
53TRM Technologies, Inc., "L4/L7 Switching," Downloaded from http://www.trm.ca/pages/t-tech7.html on Feb. 16, 2006, 3 Pages.
54U.S. Appl. No. 60/690,465, filed Jun. 14, 2005.
55U.S. Appl. No. 60/718,418, filed Sep. 19, 2005.
56Woodside et al., "The Protocol Bypass Concept for High Speed OSI Data Transfer," Research Paper. Available at:http://citeseer.ist.psu.edu/cache/papers/cs/26104/http:zSzzSzwww.sce.carleton.cazSzftpzSzpubzSzcmwzSzbpjan90.pdf/woodside90protocol.pdf.
57Yocum et al., "Anypoint: Extensible Transport Switching on the Edge," Proceedings of the 4th USENIX Symposium on Internet Technologies and Systems, Mar. 26-28, 2003, Seattle, WA, USA.
Référencé par
Brevet citant Date de dépôt Date de publication Déposant Titre
US813948225 sept. 200920 mars 2012Chelsio Communications, Inc.Method to implement an L4-L7 switch using split connections and an offloading NIC
US821342721 déc. 20093 juil. 2012Chelsio Communications, Inc.Method for traffic scheduling in intelligent network interface circuitry
US835611229 sept. 201115 janv. 2013Chelsio Communications, Inc.Intelligent network adaptor with end-to-end flow control
US858958711 mai 200719 nov. 2013Chelsio Communications, Inc.Protocol offload in intelligent network adaptor, including application level signalling
US88390445 janv. 201216 sept. 2014International Business Machines CorporationDebugging of adapters with stateful offload connections
US883904518 sept. 201316 sept. 2014International Business Machines CorporationDebugging of adapters with stateful offload connections
Classifications
Classification aux États-Unis709/227, 709/228
Classification internationaleG06F15/173
Classification coopérativeH04L67/104, H04L67/14
Classification européenneH04L29/08N13, H04L29/08N9P
Événements juridiques
DateCodeÉvénementDescription
9 mai 2014FPAYFee payment
Year of fee payment: 4
9 mai 2013ASAssignment
Owner name: EAST WEST BANK, MASSACHUSETTS
Free format text: SECURITY AGREEMENT;ASSIGNOR:CHELSIO COMMUNICATIONS, INC.;REEL/FRAME:030389/0982
Effective date: 20130509