The technology generally relates to network traffic management, and more particularly, to handling communications among network applications involving the transfer of data in protocols with different throughput and latency characteristics.
The large number of network applications engaged in communications over various private and public networks (e.g., Internet) have imposed different demands on the network interface cards (“NICs”) employed by the network devices involved in handling those communications. NICs generally handle data sent to or from a network device, generating processor interrupts as data is received or needs to be transmitted. Since interrupts are computationally expensive because the network device processors must switch context, it is generally desirable to interrupt the processors only as needed. Some data transfer protocols, such as FTP, however, are high throughput in nature because large numbers of packets are transferred at a time without requiring a relatively high number of processor interrupts for applications handling the packets. In this case, many packets may be coalesced before interrupting the processor.
Other types of data transfer protocols are low latency in nature because more frequent processor interrupts are needed by applications handling the packets. For example, the NFS protocol requires the receipt of confirmatory acknowledgement messages before subsequent file portions can be transmitted. In this case, the file transfer performance depends on the request to acknowledgement processing time or latency. Thus for such low latency type data, the best performance is achieved by interrupting processors immediately upon the arrival of packets embodying the file portions, which as noted above, is the exact opposite for high throughput type data.
An application delivery controller device is configured to manage network communications among one or more network applications operating on devices in a network. The application delivery controller device has one or more processors coupled to a memory and a network interface controller configured to receive, transmit and process network communication data packets. The application delivery controller device receives the data packets from the network to be processed by one of the processors in accordance with one or more traffic management applications executing on the processors. The data packets are stored in either a low latency packet queue or a high throughput packet queue in the memory coupled to the one or more processors of the device. The application delivery controller device processes the low latency classified packets until determining one or more high throughput classified packets are ready to be processed. The determination may be based on whether a threshold number of high throughput packets have been coalesced in the memory or periodically polling the memory to ascertain whether one or more high throughput packets are present. After processing the high throughput classified packets, the application delivery controller device resumes processing low latency classified packets.
This summary is intended to provide a brief introduction to some of the concepts covered in this disclosure. Additional aspects will be apparent to those of ordinary skill in the art in view of the detailed description of various embodiments, which is made with reference to the drawings, a brief description of which is provided below.
These examples may be practiced in many different forms without departing from the spirit and scope of the teachings in this disclosure. Therefore, it should be understood that the present disclosure should be considered an exemplification and is not limited to the example illustrations.
Referring to
As will be described in further detail below in connection with
In this example, the application delivery controller device 110 runs one or more traffic management applications on one or more host system processors 210 to manage network traffic by optimizing, securing and accelerating the traffic between clients 106 and servers 102, for example, although the controller device 110 may perform other network related functions, such as establishing virtual private networks. Moreover, the network traffic managed by the application delivery controller device 110 may be received and transmitted by the device 110 from and to the LAN 104 and network 108 in the form of network data packets in the TCP/IP protocol, although the network data packets could be in other network protocols.
Referring now to
NIC 200 may comprise specialized hardware to achieve maximum execution speeds, such a field programmable gate arrays (“FPGAs”), although other hardware and/or software may be used, such as ASICs, field programmable logic devices (“FPLDs”), programmable logic units (“PLUs”), software executed by the host system processor 210, and combinations thereof. The use of the specialized hardware in this example, however, allows the NIC 200 to rapidly respond to received packets and to rapidly classify packets as being low latency or high throughput, as will be described in further detail below.
The bus 208 is a hyper-transport bus in this example, although other bus types may be used, such as PCI. Host system input/output interfaces 202 include one or more keyboard/mouse interfaces, display devices interfaces, and other physical and/or logical mechanisms for enabling the controller 110 to communicate with the outside environment, which includes network 108, LAN 104 and users (e.g., administrators) desiring to interact with the controller 110, such as to configure, program or operate it.
Host system processor(s) 210 executes the traffic management applications 212 that handle the network traffic between applications on the clients 106 and servers 102 being managed by the controller device 110, as mentioned earlier, as well as one or more computer-executable instructions stored in the host system memory 218, as well as other operations as mentioned herein. The host system processor(s) 210 may comprise one or more central processing units (“CPUs”) or general purpose processors with one or more processing cores, such as AMD® processor(s), although other types of processor(s) could be used (e.g., Intel®).
Host system memory 218 may comprise one or more tangible storage media such as, for example, RAM, ROM, flash memory, CD-ROM, floppy disk, hard disk drive(s), solid state memory, DVD, or any other memory storage type or devices, including combinations thereof, which are known to those of ordinary skill in the art. Host system memory 218 stores the data packets received by NIC 200 in a packet buffer area 224, which is a non-contiguous memory storage space area, although contiguous memory may be used. Data packets classified by the classification module 230 (and/or the processor 210) are stored as low latency packets 229 and high throughput packets 228 in the packet buffer area 224 within memory 218. Further, the memory 218 includes a packet ring buffer indices area 226, which is a dedicated contiguous memory space that includes high throughput packet buffer index 234 and low latency packet buffer index 236, although other memory storage constructs could be used. Generally, the indices 234, 236 store an index to the location of the next low latency packet(s) 229 or high throughput packet 228 within the packet buffer area 224 to be processed by the processor(s) 210 the next time an interrupt is generated for processing either type of data in the form of a ring buffer, although other types of buffers may be used. As shown in
Further, host system memory 218 also stores one or more computer-readable instructions that may be executed by the one or more host system processor(s) 210 and/or the NIC 200. When these stored instructions are executed, they may implement a process that is illustrated, for exemplary purposes only, by the flow chart diagram shown in
Moreover, persons of ordinary skill in the art will readily appreciate that the entire algorithm or computer program, and/or parts thereof, could alternatively be executed by a device other than a processor and/or embodied in firmware or dedicated hardware in a well-known manner (e.g., it may be implemented by an application specific integrated circuit (ASIC), a programmable logic device (PLD), a field programmable logic device (FPLD), a field programmable gate array (FPGA), discrete logic, etc.). For example, any or all of the components of the NIC 200, the application delivery controller device 110, or even the clients 106/server 102, could be implemented by software, hardware, and/or firmware (and combinations thereof). Further, although the example algorithm is described with reference to the flowchart illustrated in
Packet switch fabric 214 includes one or more physical network ports (not shown), such as Ethernet ports, a host system bus interface 216, a classification logic module 230 and a configuration register 232. The NIC 200 accesses the memory 218 of the application delivery controller device 110 via one or more DMA transfer channels established to transfer packets 246. The packets 228 and 229 stored in the packet buffer area 224 of the memory 218 are indexed via either a high throughput queue 234 or a low latency queue 236 stored in the ring buffer area 226 in the memory 218. Incoming packets 228 or 229 may be written to the buffer area 224 by the NIC 200 for handling by the appropriate processor 210 in the application delivery controller device 110 when an interrupt is sent. A low latency pointer 252 or a high throughput pointer 254 to the location of the packet in the buffer area 224 is assigned to either the high throughput queue 234 or the low latency queue 236 in the ring buffer area 226. The queues 234 and 236 also store DMA descriptors of the packets.
As will be further explained, the NIC 200 may use the high throughput queue 234 and the low latency queue 236 to interrupt the processors 210 of the application delivery controller device 110 and direct one of the processors 210 to the location of a packet or packets in the buffer area 224 for the purpose of processing the incoming data packets depending on the type of data by sending the packets 244 to the respective applications 212 run by the host system processor(s) 210. The NIC 200 in the controller device 110 in this example may establish one or more DMA channels 246 over which to perform one or more DMA memory transfers to write data packets received by NIC 200 in the appropriate locations of the memory 218 in the application delivery controller device 110. The frequency of sending interrupts 240 to handle each of the respective queues 234 and 236 and the corresponding indexed packets in the buffer area 224 may be determined by setting the configuration register 232. The classification logic 230 may determine the type of data in incoming packets and therefore may assign the packet to one of the queues 234 or 236, which are in turn set for interrupt frequencies for either high throughput or low latency.
If the incoming packet includes data in a particular protocol that requires high throughput, such as the packets 228, the pointer or pointers 254 to the location of the packets 228 stored in the buffer area 224 may be added to the high throughput packet buffer queue or index 234. The high throughput packet queue 234 may be used with interrupt coalescing and therefore the NIC 200 allows numerous packets 228 to be stored in the buffer area 224 of the memory 218 before interrupting one or more of the host system processor(s) 210 to use the high throughput queue 234 for accessing multiple packets 228 from the buffer area 224. The intermittent interrupts 240 ensure the ability to maintain a high throughput through the NIC 200 since interrupts 240 are kept at a minimum, allowing one or more of the processor(s) 210 maximum uninterrupted processing of high throughput classified data packets. Alternatively, the high throughput queue 234 in memory 218 may be polled periodically by an application executing on one or more of the processors 210 to determine if pointers have been written in the queue, although logic in the NIC 200 could be configured to poll the memory 218 as well. In either case, the processor 210 handles the accumulated packets associated with the pointers in the high throughput queue 234.
Conversely, if the classification logic 230 determines the incoming packets require low latency, a low latency pointer 252 to the location of low latency packets 229 stored in the buffer area 224 may be added to the low latency packet buffer index or queue 236. The NIC 200 may be configured via the configuration register 232 to interrupt the processor(s) 210 immediately upon determining that a pointer 252 has been added to cause generating numerous interrupts 240 to use the low latency queue 236 for accessing the indexed packets 229, if so desired. Such a configuration would decrease the latency time for files that require multiple requests and acknowledgments to be sent for receiving the entirety of data.
One example of the classification logic 230 may classify the packets as high throughput or low latency according to the information in the packet header, such as information the logic 230 may use to either infer or directly identify the protocols that the packet data is in, since certain protocols are known to be low latency or high throughput in nature as mentioned previously, although a variety of other packet characteristics and methods may be used to classify the packets, such as using mappings maintained by the controller 110 between high throughput and low latency classifications with packets from particular data flows, for example. Alternatively, the classification logic 230 may classify packets as high throughput or low latency according to the data in the packet payload according to predefined rules for identifying certain data patterns, characteristics, or particular content, although the control 110 may be flexibly configured by a user of the controller 110, such as a network administrator, for example, to classify the packets based on any type of desired criteria.
Alternatively, a dedicated processor of the processors 210 on the application delivery controller device 110 may assist in processing packets received by the NIC 200. The dedicated processor is external to the NIC 200 and may perform various functions as described below. In this example, the NIC 200 receives the packets via the Ethernet link 206 and stores the packet in the buffer area 224 of the memory 218. The NIC 200 may pass the packet pointer to a high speed polling application 212 run by the dedicated processor 210 on the application delivery controller device 110. The high speed polling application 212 may determine whether the packet pointer should be assigned to the high throughput queue 234 or the low latency queue 236 and then adds the pointer to the appropriate queue 234 or 236 instead of the classification logic 230 in
Each of the server 102, application delivery controller device 110, and client computers 106 may include a central processing unit (CPU), controller or processor, a memory, and an interface system that are coupled together by a bus or other link, although other numbers and types of each of the components and other configurations and locations for the components can be used. The processors in the server 102, application delivery controller device 110, and client computers 106 may execute a program of stored instructions for one or more aspects of the methods and systems as described herein, including for efficient handling of different types of data, although the processor could execute other types of programmed instructions. The memory may store these programmed instructions for one or more aspects of the methods and systems as described herein, including the method for efficient handling of different types of data, although some or all of the programmed instructions could be stored and/or executed elsewhere. A variety of different types of memory storage devices, such as a random access memory (RAM) or a read only memory (ROM) in the system or a floppy disk, hard disk, CD ROM, DVD ROM, or other computer readable medium that is read from and/or written to by a magnetic, optical, or other reading and/or writing system that is coupled to the processor, may be used for the memory. The user input device may comprise a computer keyboard and a computer mouse, although other types and numbers of user input devices may be used. The display may comprise a computer display screen, such as a CRT or LCD screen by way of example only, although other types and numbers of displays could be used.
Although an example of the server 102, application delivery controller device 110, and client computers 106 are described and illustrated herein in connection with
Furthermore, each of the devices of the system 100 may be conveniently implemented using one or more general purpose computer systems, microprocessors, digital signal processors, micro-controllers, application specific integrated circuits (ASIC), programmable logic devices (PLD), field programmable logic devices (FPLD), field programmable gate arrays (FPGA) and the like, programmed according to the teachings as described and illustrated herein, as will be appreciated by those skilled in the computer, software, and networking arts.
In addition, two or more computing systems or devices may be substituted for any one of the systems in the system 100. Accordingly, principles and advantages of distributed processing, such as redundancy, replication, and the like, also can be implemented, as desired, to increase the robustness and performance of the devices and systems of the system 100. The system 100 may also be implemented on a computer system or systems that extend(s) across any network environment using any suitable interface mechanisms and communications technologies including, for example telecommunications in any suitable form (e.g., voice, modem, and the like), Public Switched Telephone Network (PSTNs), Packet Data Networks (PDNs), the Internet, intranets, a combination thereof, and the like.
The operation of the example process to handle both high throughput and low latency data shown in
Referring now to
A coalesce count is incremented after the pointer is written to the high throughput queue (408). The high throughput queue 234 is accessed by the NIC 200 according to the configuration register 232 to coalesce interrupts 240 sent to a processor, such as the host system processor(s) 210 of the application delivery controller 110 shown in
The NIC 200 then sends an interrupt to the appropriate processor such as the processor 210 (414). The processor 210 may receive the interrupt and access the appropriate locations of the buffer area 224 shown in
If the packet is determined to require low latency (402), the packet is written to the buffer area 224 of the memory 218 (418). The classification logic 230 then updates the low latency queue 236 (420) with the pointer to the area where the packet is stored. In this example, the NIC 200 is configured via the configuration register 232 to send an interrupt based on a new pointer written in the low latency queue 236 (422).
Since low latency classified data packets involve more frequent data accesses to process the packets for achieving low latency, the determination of whether to send an interrupt may be based on simply the arrival of a new packet written in the low latency queue 236. In this example, the NIC 200 may determine whether there is a new packet indexed in the queue 236. The NIC 200 sends an interrupt for a particular one of the processor(s) 210 to process the packet, although any available one of the processor(s) 210 could be directed to process the packet (422). The processor 210 may receive the interrupt and access the appropriate locations of the buffer area 224 shown in
Having thus described the basic concepts, it will be rather apparent to those skilled in the art that the foregoing detailed disclosure is intended to be presented by way of example only, and is not limiting. Various alterations, improvements, and modifications will occur and are intended to those skilled in the art, though not expressly stated herein. For example, different non-TCP networks may be selected by a system administrator. Also, rather than having one device or server with different processors, a virtualized server where one guest operating system is running a low latency application and another guest operating system is running a high throughput application may be serviced via the network interface controller. The processes described herein may be applied to egress or ingress packets. In such a case, the host processor 210 of the application controller 110, after the application running on the processor 210 finishes processing a packet from the LAN 104, would notify the NIC 200 to let it know that it has buffered a packet into host memory 218 that is ready to be transmitted out to the network by the NIC 200 (and DMA transferred by the NIC from the host memory when it is ready to do so). The order that the measures are implemented may also be altered. These alterations, improvements, and modifications are intended to be suggested hereby, and are within the spirit and scope of the examples. Additionally, the recited order of processing elements or sequences, or the use of numbers, letters, or other designations therefore, is not intended to limit the claimed processes to any order except as may be specified in the claims. Accordingly, the disclose technology is limited only by the following claims and equivalents thereto.
Number | Name | Date | Kind |
---|---|---|---|
3950735 | Patel | Apr 1976 | A |
4644532 | George et al. | Feb 1987 | A |
4897781 | Chang et al. | Jan 1990 | A |
4914650 | Sriram | Apr 1990 | A |
4965772 | Daniel et al. | Oct 1990 | A |
5023826 | Patel | Jun 1991 | A |
5053953 | Patel | Oct 1991 | A |
5299312 | Rocco, Jr. | Mar 1994 | A |
5327529 | Fults et al. | Jul 1994 | A |
5367635 | Bauer et al. | Nov 1994 | A |
5371852 | Attanasio et al. | Dec 1994 | A |
5388237 | Sodos et al. | Feb 1995 | A |
5406502 | Haramaty et al. | Apr 1995 | A |
5475857 | Dally | Dec 1995 | A |
5477541 | White et al. | Dec 1995 | A |
5517617 | Sathaye et al. | May 1996 | A |
5519694 | Brewer et al. | May 1996 | A |
5519778 | Leighton et al. | May 1996 | A |
5521591 | Arora et al. | May 1996 | A |
5528701 | Aref | Jun 1996 | A |
5581764 | Fitzgerald et al. | Dec 1996 | A |
5596742 | Agarwal et al. | Jan 1997 | A |
5606665 | Yang et al. | Feb 1997 | A |
5611049 | Pitts | Mar 1997 | A |
5663018 | Cummings et al. | Sep 1997 | A |
5699361 | Ding et al. | Dec 1997 | A |
5742765 | Wong et al. | Apr 1998 | A |
5752023 | Choucri et al. | May 1998 | A |
5761484 | Agarwal et al. | Jun 1998 | A |
5761534 | Lundberg et al. | Jun 1998 | A |
5768423 | Aref et al. | Jun 1998 | A |
5774660 | Brendel et al. | Jun 1998 | A |
5790554 | Pitcher et al. | Aug 1998 | A |
5797033 | Ecclesine | Aug 1998 | A |
5802052 | Venkataraman | Sep 1998 | A |
5812550 | Sohn et al. | Sep 1998 | A |
5825772 | Dobbins et al. | Oct 1998 | A |
5828835 | Isfeld et al. | Oct 1998 | A |
5875296 | Shi et al. | Feb 1999 | A |
5892914 | Pitts | Apr 1999 | A |
5892932 | Kim | Apr 1999 | A |
5919247 | Van Hoff et al. | Jul 1999 | A |
5936939 | Des Jardins et al. | Aug 1999 | A |
5941988 | Bhagwat et al. | Aug 1999 | A |
5946690 | Pitts | Aug 1999 | A |
5949885 | Leighton | Sep 1999 | A |
5951694 | Choquier et al. | Sep 1999 | A |
5959990 | Frantz et al. | Sep 1999 | A |
5974460 | Maddalozzo, Jr. et al. | Oct 1999 | A |
5983281 | Ogle et al. | Nov 1999 | A |
6006260 | Barrick, Jr. et al. | Dec 1999 | A |
6006264 | Colby et al. | Dec 1999 | A |
6026090 | Benson et al. | Feb 2000 | A |
6026443 | Oskouy et al. | Feb 2000 | A |
6026452 | Pitts | Feb 2000 | A |
6028857 | Poor | Feb 2000 | A |
6051169 | Brown et al. | Apr 2000 | A |
6070219 | McAlpine et al. | May 2000 | A |
6078956 | Bryant et al. | Jun 2000 | A |
6085234 | Pitts et al. | Jul 2000 | A |
6092196 | Reiche | Jul 2000 | A |
6108703 | Leighton et al. | Aug 2000 | A |
6111876 | Frantz et al. | Aug 2000 | A |
6115802 | Tock et al. | Sep 2000 | A |
6128279 | O'Neil et al. | Oct 2000 | A |
6128657 | Okanoya et al. | Oct 2000 | A |
6170022 | Linville et al. | Jan 2001 | B1 |
6178423 | Douceur et al. | Jan 2001 | B1 |
6182139 | Brendel | Jan 2001 | B1 |
6192051 | Lipman et al. | Feb 2001 | B1 |
6233612 | Fruchtman et al. | May 2001 | B1 |
6246684 | Chapman et al. | Jun 2001 | B1 |
6253226 | Chidambaran et al. | Jun 2001 | B1 |
6253230 | Couland et al. | Jun 2001 | B1 |
6263368 | Martin | Jul 2001 | B1 |
6298380 | Coile et al. | Oct 2001 | B1 |
6327622 | Jindal et al. | Dec 2001 | B1 |
6343324 | Hubis et al. | Jan 2002 | B1 |
6347337 | Shah et al. | Feb 2002 | B1 |
6347339 | Morris et al. | Feb 2002 | B1 |
6360270 | Cherkasova et al. | Mar 2002 | B1 |
6374300 | Masters | Apr 2002 | B2 |
6388989 | Malhotra | May 2002 | B1 |
6396833 | Zhang et al. | May 2002 | B1 |
6411986 | Susai et al. | Jun 2002 | B1 |
6484261 | Wiegel | Nov 2002 | B1 |
6490624 | Sampson et al. | Dec 2002 | B1 |
6510135 | Almulhem et al. | Jan 2003 | B1 |
6519643 | Foulkes et al. | Feb 2003 | B1 |
6529508 | Li et al. | Mar 2003 | B1 |
6574220 | Petty | Jun 2003 | B1 |
6601084 | Bhaskaran et al. | Jul 2003 | B1 |
6636503 | Shiran et al. | Oct 2003 | B1 |
6636894 | Short et al. | Oct 2003 | B1 |
6650640 | Muller et al. | Nov 2003 | B1 |
6650641 | Albert et al. | Nov 2003 | B1 |
6654701 | Hatley | Nov 2003 | B2 |
6691165 | Bruck et al. | Feb 2004 | B1 |
6700871 | Harper et al. | Mar 2004 | B1 |
6708187 | Shanumgam et al. | Mar 2004 | B1 |
6742045 | Albert et al. | May 2004 | B1 |
6748457 | Fallon et al. | Jun 2004 | B2 |
6751663 | Farrell et al. | Jun 2004 | B1 |
6754228 | Ludwig | Jun 2004 | B1 |
6760775 | Anerousis et al. | Jul 2004 | B1 |
6772219 | Shobatake | Aug 2004 | B1 |
6779039 | Bommareddy et al. | Aug 2004 | B1 |
6781986 | Sabaa et al. | Aug 2004 | B1 |
6781990 | Puri et al. | Aug 2004 | B1 |
6785236 | Lo et al. | Aug 2004 | B1 |
6798777 | Ferguson et al. | Sep 2004 | B1 |
6816901 | Sitaraman et al. | Nov 2004 | B1 |
6820133 | Grove et al. | Nov 2004 | B1 |
6829238 | Tokuyo et al. | Dec 2004 | B2 |
6868082 | Allen, Jr. et al. | Mar 2005 | B1 |
6876629 | Beshai et al. | Apr 2005 | B2 |
6876654 | Hegde | Apr 2005 | B1 |
6888836 | Cherkasova | May 2005 | B1 |
6904040 | Salapura et al. | Jun 2005 | B2 |
6928082 | Liu et al. | Aug 2005 | B2 |
6934776 | Connor et al. | Aug 2005 | B2 |
6950434 | Viswanath et al. | Sep 2005 | B1 |
6954780 | Susai et al. | Oct 2005 | B2 |
6957272 | Tallegas et al. | Oct 2005 | B2 |
6975592 | Seddigh et al. | Dec 2005 | B1 |
6999457 | Shinohara | Feb 2006 | B2 |
7007092 | Peiffer | Feb 2006 | B2 |
7046628 | Luhmann et al. | May 2006 | B2 |
7065630 | Ledebohm et al. | Jun 2006 | B1 |
7107348 | Shimada et al. | Sep 2006 | B2 |
7117308 | Mitten et al. | Oct 2006 | B1 |
7124196 | Hooper | Oct 2006 | B2 |
7139792 | Mishra et al. | Nov 2006 | B1 |
7142540 | Hendel et al. | Nov 2006 | B2 |
7164678 | Connor | Jan 2007 | B2 |
7174393 | Boucher et al. | Feb 2007 | B2 |
7236491 | Tsao et al. | Jun 2007 | B2 |
7272150 | Bly et al. | Sep 2007 | B2 |
7281030 | Davis | Oct 2007 | B1 |
7321926 | Zhang et al. | Jan 2008 | B1 |
7324525 | Fuhs et al. | Jan 2008 | B2 |
7327674 | Eberle et al. | Feb 2008 | B2 |
7343413 | Gilde et al. | Mar 2008 | B2 |
7349391 | Ben-Dor et al. | Mar 2008 | B2 |
7349405 | Deforche | Mar 2008 | B2 |
7353326 | Cho et al. | Apr 2008 | B2 |
7355977 | Li | Apr 2008 | B1 |
7359321 | Sindhu et al. | Apr 2008 | B1 |
7376772 | Fallon | May 2008 | B2 |
7403542 | Thompson | Jul 2008 | B1 |
7411957 | Stacy et al. | Aug 2008 | B2 |
7415034 | Muller et al. | Aug 2008 | B2 |
7420931 | Nanda et al. | Sep 2008 | B2 |
7457313 | Patrick | Nov 2008 | B2 |
7475122 | Azpitarte | Jan 2009 | B2 |
7478186 | Onufryk et al. | Jan 2009 | B1 |
7490162 | Masters | Feb 2009 | B1 |
7493398 | Bush | Feb 2009 | B2 |
7496689 | Sharp et al. | Feb 2009 | B2 |
7496695 | Go et al. | Feb 2009 | B2 |
7500028 | Yamagishi | Mar 2009 | B2 |
7512078 | Swain | Mar 2009 | B2 |
7512721 | Olson | Mar 2009 | B1 |
7533197 | Leonard et al. | May 2009 | B2 |
7552232 | Helmer, Jr. et al. | Jun 2009 | B2 |
7558197 | Sindhu et al. | Jul 2009 | B1 |
7558910 | Alverson et al. | Jul 2009 | B2 |
7571299 | Loeb | Aug 2009 | B2 |
7590753 | Wolde et al. | Sep 2009 | B2 |
7620046 | Ronciak et al. | Nov 2009 | B2 |
7620071 | Makineni et al. | Nov 2009 | B2 |
7621162 | Bartky | Nov 2009 | B2 |
7647416 | Chiang et al. | Jan 2010 | B2 |
7657659 | Lambeth et al. | Feb 2010 | B1 |
7660916 | Moskalev et al. | Feb 2010 | B2 |
7668727 | Mitchell et al. | Feb 2010 | B2 |
7668851 | Triplett | Feb 2010 | B2 |
7680915 | Still et al. | Mar 2010 | B2 |
7710989 | Chew | May 2010 | B2 |
7729239 | Aronov et al. | Jun 2010 | B1 |
7734809 | Joshi et al. | Jun 2010 | B2 |
7735099 | Micalizzi, Jr. | Jun 2010 | B1 |
7742412 | Medina | Jun 2010 | B1 |
7784093 | Deng et al. | Aug 2010 | B2 |
7813277 | Okholm et al. | Oct 2010 | B2 |
7826487 | Mukerji et al. | Nov 2010 | B1 |
7840841 | Huang et al. | Nov 2010 | B2 |
7877524 | Annem et al. | Jan 2011 | B1 |
7916728 | Mimms | Mar 2011 | B1 |
7929433 | Husak et al. | Apr 2011 | B2 |
7936772 | Kashyap | May 2011 | B2 |
7991918 | Jha et al. | Aug 2011 | B2 |
7996569 | Aloni et al. | Aug 2011 | B2 |
8006016 | Muller et al. | Aug 2011 | B2 |
8077620 | Solomon et al. | Dec 2011 | B2 |
8099528 | Millet et al. | Jan 2012 | B2 |
8103809 | Michels et al. | Jan 2012 | B1 |
8112491 | Michels et al. | Feb 2012 | B1 |
8112594 | Giacomoni et al. | Feb 2012 | B2 |
8130650 | Allen, Jr. et al. | Mar 2012 | B2 |
8233380 | Subramanian et al. | Jul 2012 | B2 |
8279865 | Giacomoni et al. | Oct 2012 | B2 |
8306036 | Bollay et al. | Nov 2012 | B1 |
8346993 | Michels et al. | Jan 2013 | B2 |
8447884 | Baumann | May 2013 | B1 |
8448234 | Mondaeev et al. | May 2013 | B2 |
8799403 | Chan et al. | Aug 2014 | B2 |
8848715 | Izenberg et al. | Sep 2014 | B2 |
8880632 | Michels et al. | Nov 2014 | B1 |
8880696 | Michels et al. | Nov 2014 | B1 |
8984178 | Michels et al. | Mar 2015 | B2 |
9032113 | Conroy et al. | May 2015 | B2 |
20010023442 | Masters | Sep 2001 | A1 |
20010038629 | Shinohara | Nov 2001 | A1 |
20010042200 | Lamberton et al. | Nov 2001 | A1 |
20020143955 | Shimada et al. | Oct 2002 | A1 |
20020156927 | Boucher et al. | Oct 2002 | A1 |
20020161913 | Gonzalez et al. | Oct 2002 | A1 |
20020198993 | Cudd et al. | Dec 2002 | A1 |
20030046291 | Fascenda | Mar 2003 | A1 |
20030067930 | Salapura et al. | Apr 2003 | A1 |
20030086415 | Bernhard et al. | May 2003 | A1 |
20030204636 | Greenblat et al. | Oct 2003 | A1 |
20030225485 | Fritz et al. | Dec 2003 | A1 |
20040032830 | Bly et al. | Feb 2004 | A1 |
20040062245 | Sharp et al. | Apr 2004 | A1 |
20040202161 | Stachura et al. | Oct 2004 | A1 |
20040249881 | Jha et al. | Dec 2004 | A1 |
20040249948 | Sethi et al. | Dec 2004 | A1 |
20040267897 | Hill et al. | Dec 2004 | A1 |
20050007991 | Ton et al. | Jan 2005 | A1 |
20050050364 | Feng | Mar 2005 | A1 |
20050083952 | Swain | Apr 2005 | A1 |
20050091390 | Helmer et al. | Apr 2005 | A1 |
20050114559 | Miller | May 2005 | A1 |
20050122977 | Lieberman | Jun 2005 | A1 |
20050141427 | Bartky | Jun 2005 | A1 |
20050175014 | Patrick | Aug 2005 | A1 |
20050187866 | Lee | Aug 2005 | A1 |
20050213570 | Stacy et al. | Sep 2005 | A1 |
20050226234 | Sano et al. | Oct 2005 | A1 |
20060007928 | Sangillo | Jan 2006 | A1 |
20060059267 | Cugi et al. | Mar 2006 | A1 |
20060067349 | Ronciak et al. | Mar 2006 | A1 |
20060104303 | Makineni et al. | May 2006 | A1 |
20060174324 | Zur et al. | Aug 2006 | A1 |
20060221832 | Muller et al. | Oct 2006 | A1 |
20060221835 | Sweeney | Oct 2006 | A1 |
20060224820 | Cho et al. | Oct 2006 | A1 |
20060235996 | Wolde et al. | Oct 2006 | A1 |
20060288128 | Moskalev et al. | Dec 2006 | A1 |
20070083646 | Miller et al. | Apr 2007 | A1 |
20070107048 | Halls et al. | May 2007 | A1 |
20070118879 | Yeun | May 2007 | A1 |
20070162619 | Aloni et al. | Jul 2007 | A1 |
20070174491 | Still et al. | Jul 2007 | A1 |
20080126509 | Subramanian et al. | May 2008 | A1 |
20080133518 | Kapoor et al. | Jun 2008 | A1 |
20080184248 | Barua et al. | Jul 2008 | A1 |
20080201772 | Mondaeev et al. | Aug 2008 | A1 |
20080219279 | Chew | Sep 2008 | A1 |
20090003204 | Okholm et al. | Jan 2009 | A1 |
20090007266 | Wu et al. | Jan 2009 | A1 |
20090016217 | Kashyap | Jan 2009 | A1 |
20090049230 | Pandya | Feb 2009 | A1 |
20090089619 | Huang et al. | Apr 2009 | A1 |
20090141891 | Boyen et al. | Jun 2009 | A1 |
20090154459 | Husak et al. | Jun 2009 | A1 |
20090222598 | Hayden | Sep 2009 | A1 |
20090248911 | Conroy et al. | Oct 2009 | A1 |
20090279559 | Wong et al. | Nov 2009 | A1 |
20090287935 | Aull et al. | Nov 2009 | A1 |
20100082849 | Millet et al. | Apr 2010 | A1 |
20100085875 | Solomon et al. | Apr 2010 | A1 |
20100094945 | Chan et al. | Apr 2010 | A1 |
20100122091 | Huang et al. | May 2010 | A1 |
20100325277 | Muthiah et al. | Dec 2010 | A1 |
20110228781 | Izenberg et al. | Sep 2011 | A1 |
20120191800 | Michels et al. | Jul 2012 | A1 |
20130250777 | Ziegler | Sep 2013 | A1 |
20140032695 | Michels et al. | Jan 2014 | A1 |
20140185442 | Newman et al. | Jul 2014 | A1 |
20140301207 | Durand et al. | Oct 2014 | A1 |
Number | Date | Country |
---|---|---|
0744850 | Nov 1996 | EP |
1813084 | Aug 2007 | EP |
WO 9114326 | Sep 1991 | WO |
WO 9505712 | Feb 1995 | WO |
WO 9709805 | Mar 1997 | WO |
WO 9745800 | Dec 1997 | WO |
WO 9905829 | Feb 1999 | WO |
WO 9906913 | Feb 1999 | WO |
WO 9910858 | Mar 1999 | WO |
WO 9939373 | Aug 1999 | WO |
WO 9964967 | Dec 1999 | WO |
WO 0004422 | Jan 2000 | WO |
WO 0004458 | Jan 2000 | WO |
2004079930 | Sep 2004 | WO |
WO 2006055494 | May 2006 | WO |
2009158680 | Dec 2009 | WO |
Entry |
---|
Anonymous, “Memory Mapping and DMA,” Chapter 15, pp. 412-463, Jan. 21, 2005. |
Bell Laboratories, “Layer 4/7 Switching and Other Custom IP Traffic Processing using the NEPPI API,” Lucent Technologies, pp. 1-11, Murray Hill, NJ. |
“DMA and Interrupt Handling,” EventHelix.com. |
Harvey A.F. et al., “DMA Fundamentals on Various PC Platforms,” National Instruments Corporation: Application Note 011, Apr. 1991, pp. 1-18, 340023-01. |
Mangino John, “Using DMA with High Performance Peripherals to Maximize System Performance,” WW TMS470 Catalog Applications, SPNA105, Jan. 2007, PowerPoint presentation, slides 1-23. |
Mogul, Jeffrey, C., “The Case for Persistent-Connection HTTP,” SIGCOMM '95, 1995, pp. 299-313, Cambridge, MA. |
Rabinovich, Michael et al., “DHTTP: An Efficient and Cache-Friendly Transfer Protocol for the Web,” IEEE/ACM Transactions on Networking, Dec. 2004, pp. 1007-1020, vol. 12, No. 6. |
Stevens, W., “TCP Slow Start, Congestion Avoidance, Fast Retransmit, and Fast Recovery Algorithms,” Network Working Group; RFC: 2001; Standards Track, Jan. 1997, pp. 1-6, NOAO. |
“TCP-Transmission Control Protocol (TCP Fast Retransmit and Recovery),” EventHelix.com/EventStudio1.0, Mar. 28, 2002, pp. 1-5. |
Wadge, Wallace, “Achieving Gigabit Performance on Programmable Ethernet Network Interface Cards,” May 29, 2001, pp. 1-9. |
Wikipedia, “Direct memory access,” <http://en.wikipedida.org/wiki/Direct—memory—access>, last modified Oct. 1, 2009. |
Wikipedia, “Nagle's algorithm,” <http://en.wikipedia.org/wiki/Nagle%27s—algorithm>, last modified Oct. 9, 2009. |
“Cavium Networks Product Selector Guide—Single & Multi-Core MIPS Processors, Security Processors and Accelerator Boards—Spring 2008,” (2008) pp. 1-44, Cavium Networks, Mountain View, CA, US. |
“Comtech AHA Announces 3.0 Gbps GZIP Compression/Decompression Accelerator AHA362-PCIX offers high-speed GZIP compression and decompression,” www.aha.com, Apr. 20, 2005, pp. 1-2, Comtech AHA Corporation, Moscow, ID, USA. |
“Comtech AHA Announces GZIP Compression and Decompression IC Offers the highest speed and compression ratio performance in hardware on the market,” www.aha.com, Jun. 26, 2007, pp. 1-2, Comtech AHA Corporation, Moscow, ID, USA. |
“Gigabit Ethernet/PCI Network Interface Card; Host/NIC Software Interface Definition,” Jul. 1999, pp. 1-80, Revision 12.4.13, P/N 020001, Alteon WebSystems, Inc., San Jose, California. |
“NITROX™ XL Security Acceleration Modules PCI 3V or 3V/5V-Universal Boards for SSL and IPSec,” at http://www.Caviumnetworks.com, (2002) pp. 1, Cavium Networks, Mountain View, CA USA. |
“PCI, PCI-X,” at http://www.cavium.com/acceleration—boards—PCI—PCI-X.htm (Downloaded Oct. 2008), Cavium Networks—Products > Acceleration Boards > PCI, PCI-X. |
“Plan 9 kernel history: overview / file list / diff list,” <http://switch.com/cgi-bin/plan9history.cgi?f=2001/0126/pc/etherga620.com>, accessed Oct. 22, 2007, pp. 1-16. |
Welch, Von, “A User's Guide to TCP Windows,” http://www.vonwelch.com/report/tcp—windows, updated 1996, last accessed Jan. 29, 2010, pp. 1-5. |
Salchow, Jr., KJ, “Clustered Multiprocessing: Changing the Rules of the Performance Game,” F5 White Paper, Jan. 2008, pp. 1-11, F5 Networks, Inc. |
“A Process for Selective Routing of Servlet Content to Transcoding Modules,” Research Disclosure 422124, Jun. 1999, pp. 889-890, IBM Corporation. |
F5 Networks, Inc., “BIG-IP Controller with Exclusive OneConnect Content Switching Feature Provides a Breakthrough System for Maximizing Server and Network Performance,” Press Release, May 8, 2001, 2 pages, Las Vegas, Nevada. |
Crescendo Networks, “Application Layer Processing (ALP),” 2003-2009, pp. 168-186, Chapter 9, CN-5000E/5500E, Foxit Software Company. |
Fielding et al., “Hypertext Transfer Protocol—HTTP/1.1,” Network Working Group, RFC: 2068, Jan. 1997, pp. 1-162. |
Fielding et al., “Hypertext Transfer Protocol—HTTP/1.1,” Network Working Group, RFC: 2616, Jun. 1999, pp. 1-176, The Internet Society. |
Floyd et al., “Random Early Detection Gateways for Congestion Avoidance,” Aug. 1993, pp. 1-22, IEEE/ACM Transactions on Networking, California. |
Hochmuth, Phil, “F5, CacheFlow pump up content-delivery lines,” Network World Fusion, May 4, 2001, 1 page, Las Vegas, Nevada. |
Schaefer, Ken, “IIS and Kerberos Part 5—Protocol Transition, Constrained Delegation, S4U2S and S4U2P,” Jul. 18, 2007, 21 pages, http://www.adopenstatic.com/cs/blogs/ken/archive/2007/07/19/8460.aspx. |
“Servlet/Applet/HTML Authentication Process With Single Sign-On,” Research Disclosure 429128, Jan. 2000, pp. 163-164, IBM Corporation. |
“Traffic Surges; Surge Queue; Netscaler Defense,” 2005, PowerPoint Presentation, slides 1-12, Citrix Systems, Inc. |
Williams et al., “The Ultimate Windows Server 2003 System Administrator's Guide: Forwarding Authentication,” 2003, 2 pages, Figure 10.7, Addison-Wesley Professional, Boston, Massachusetts. |
“Windows Server 2003 Kerberos Extensions,” Microsoft TechNet, 2003 (Updated Jul. 31, 2004), http://technet.microsoft.com/en-us/library/cc738207, Microsoft Corporation. |
MacVittie, Lori, “Message-Based Load Balancing,” Technical Brief, Jan. 2010, pp. 1-9, F5 Networks, Inc. |
International Search Report for Europe Patent Application No. 14191232.9 (Oct. 31, 2014). |
Number | Date | Country | |
---|---|---|---|
20150049763 A1 | Feb 2015 | US |