Disclosed is a process for driving a network interface card. The process includes monitoring the status of a plurality of ports connected between a computer and a network. Detecting a failure in one of the plurality of ports connected to the network. Re-assigning data transmitted over the failed one of the plurality of ports to an active port of the plurality of ports selected in a round robin technique. The process further including receiving data over one of the plurality of ports designated as a primary receiving port. Preferably, when the failed one of the plurality of ports is the primary receiving port, the receiving tasks are assigned to a next active port selected in a round robin technique.
|
33. An apparatus for driving a network interface card having at least three ports for connecting a computer system to a network, the apparatus comprising:
means for monitoring the status of the at least three ports connected between the computer and the network, the at least three ports being capable of transmitting data from the computer to the network as transmit ports at the same time to a remote host at an aggregated bandwidth of the at least three ports, a selected port from the at least three ports being capable of receiving data from the network as a primary receiving port, wherein the multi-port network interface card is configured to transmit new data over a selected transmit port while transmitting other data over the other transmit ports at the same time so as to improve load balancing of data from the computer to the network; means for initializing each of the at least three ports, the initializing means further including, means for ascertaining the connection type for the ports, and means for scanning the indices of a lookup table to determine if the ports are active; means for detecting a failure in one of the at least three ports connected to the network; means for re-assigning data transmitted over the failed one of the at least three ports to an active port of the at least three ports selected in a round robin technique such that data transfer load is automatically redistributed over active ports; and means for receiving data over one of the at least three ports designated as a primary receiving port.
22. A computer readable media containing program instructions for driving a multi-port network interface card having at least three ports for connecting a computer system to a network, the computer readable media comprising:
program instructions for monitoring a status of the at least three ports of the multi-port network card that connects the computer to the network, the at least three ports being capable of transmitting data from the computer to the network as transmit ports at the same time to a remote host at an aggregated bandwidth of the at least three ports, a selected port from the at least three ports being capable of receiving data from the network as a primary receiving port, wherein the multi-port network interface card is configured to transmit new data over a selected transmit port while transmitting other data over the other transmit ports at the same time so as to improve load balancing of data from the computer to the network; program instructions for building a port resolution table indexing connections to at least one remote host that is communicating through a selected one of the at least three ports, the building further including instructions for, determining whether a host is associated with the port resolution table by referring to a timer parameter; program instructions for periodically updating the port resolution table after a predetermined time-out; and program instructions for performing a link check timer routine, the performing further including instructions for, determining if a receiver port of the at least three ports is active. 30. A computer readable media containing program instructions for driving a network interface card having at least three ports for connecting a computer system to a network, comprising:
program instructions for monitoring a status of the at least three ports of the network interface card connected between the computer and the network, the at least three ports being capable of transmitting data from the computer to the network as transmit ports at the same time to a remote host at an aggregated bandwidth of the at least three ports, a selected port from the at least three ports being capable of receiving data from the network as a primary receiving port, wherein the multi-port network interface card is configured to transmit new data over a selected transmit port while transmitting other data over the other transmit ports at the same time so as to improve load balancing of data from the computer to the network; program instructions for initializing each of the at least three ports, the initializing further including instructions for, ascertaining the connection type for the ports, and scanning the indices of a lookup table to determine if the ports are active; program instructions for detecting a failure in one of the at least three ports that connect the computer system to the network; program instructions for re-assigning data transmitted over the failed one of the at least three ports to an active port of the at least three ports selected in a round robin technique such that data transfer load is automatically redistributed over active ports; and program instructions for receiving data over one of the at least three ports designated as a primary receiving port.
13. A method for transmitting and receiving data over a network from a server computer system, comprising:
providing a multi-port network interface card on the server computer system, the multi-port network interface card having at least three ports for connecting the server computer system to a network, the at least three ports being capable of transmitting data from the computer as transmit ports at the same time to a remote host at an aggregated bandwidth of the at least three ports, a selected port from the at least three ports being capable of receiving data from the network as a primary receiving port, wherein the multi-port network interface card is configured to transmit new data over a selected transmit port while transmitting other data over the other transmit ports at the same time so as to improve load balancing of data from the computer to the network; connecting the server computer system with the network through the at least three ports for communicating with a plurality of remote hosts coupled to the network; transmitting a load of data from the server computer system through the at least three ports to the plurality of remote hosts, the transmitting further including, retrieving a destination address from the load of data, and determining whether the destination address is listed in a lookup table; detecting, by the server computer system, a failure in one of the at least three ports during a transmit to a selected one of the plurality of remote hosts; and redistributing, by the server computer system, the load of data assigned to the failed one of the at least three ports to an available port of the plurality of ports, the redistributing further including, determining if the available port is free by referring to the lookup table.
1. A process for driving a network interface card, comprising:
providing a multi-port network interface card on a computer, the multi-port network interface card having at least three ports for connecting the computer to a network, the at least three ports being capable of transmitting data from the computer to the network as transmit ports at the same time to a remote host at an aggregated bandwidth of the at least three ports, a selected port from the at least three ports being capable of receiving data from the network as a primary receiving port, wherein the multi-port network interface card is configured to transmit new data over a selected transmit port while transmitting other data over the other transmit ports at the same time so as to improve load balancing of data from the computer; initializing each of the at least three ports, the initializing further including, ascertaining the connection type for the ports, and scanning the indices of a lookup table to determine if the ports are active; creating registry groups by selecting ports from the at least three ports; defining start time-out values to assist in the efficient load balancing of active ports; monitoring a status of the at least three ports between the computer and the network; detecting a failure in one of the at least three ports that connect the computer to the network; upon detecting the failure in one of the ports, re-assigning data to be transmitted over the failed one of the at least three ports to an active port of the at least three ports, the active port being selected in a round robin technique such that data transfer load is automatically redistributed over active ports; and receiving data over one of the at least three ports designated as the primary receiving port.
2. A process for driving a network interface card as recited in
3. A process for driving a network interface card as recited in
4. A process for driving a network interface card as recited in
examining the at least three ports to determine whether any one of the at least three ports is free, if one or more ports are determined to be free, assigning data transfer to a next free port selected in a round robin manner; and if no ports are determined to be free, assigning data transfer to a least busiest port among the more than two ports.
5. A process for driving a network interface card as recited in
6. A process for driving a network interface card as recited in
7. A process for driving a network interface card as recited in
scanning the plurality of ports to ascertain whether each of the at least three ports is active; determining whether the primary port is active based on the scanning; determining that the primary port is not active; determining that the primary port is assigned the receiving; and assigning a next active port of the plurality of ports with the receiving.
8. A process for driving a network interface card as recited in
9. A process for driving a network interface card as recited in
10. A process for driving a network interface card as recited in
performing a port configuration to assign a bandwidth to each of the at least three ports; performing a grouping of selected ones of the at least three ports to attain a group of load balanced transmission ports; and initializing the configured ports and the group of load balanced transmission ports.
11. A process for driving a network interface card as recited in
12. A process for driving a network interface card as recited in
14. A method for transmitting and receiving data over a network from a server computer system as recited in
receiving data through one of the at least three ports designated as a primary receiving port.
15. A method for transmitting and receiving data over a network from a server computer system as recited in
receiving data through a next active port of the at least three ports selected in a round robin orientation.
16. A method for transmitting and receiving data over a network from a server computer system as recited in
17. A method for transmitting and receiving data over a network from a server computer system as recited in
18. A method for transmitting and receiving data over a network from a server computer system as recited in
19. A method for transmitting and receiving data over a network from a server computer system as recited in
monitoring activity of a plurality of links connecting the plurality of ports to selected ones of the plurality of remote hosts; detecting a failure in one of the plurality of links; redistributing the load of data assigned to one of the at least three ports connected to the failed one of the plurality of links to an available port of the at least three ports, such that the available port is connected to an active one of the plurality of links.
20. A method for transmitting and receiving data over a network from a server computer system as recited in
21. A method for transmitting and receiving data over a network from a server computer system as recited in
selecting a least busy port of the at least three ports after detecting the failure in one of the at least three ports.
23. A computer readable media containing program instructions for driving a network interface card as recited in
24. A computer readable media containing program instructions for driving a network interface card as recited in
25. A computer readable media containing program instructions for driving a network interface card as recited in
26. A computer readable media containing program instructions for driving a network interface card as recited in
program instructions for removing the port resolution table index for the at least one remote host when the timer is already set to the logical zero and a pass is made through the port resolution table.
27. A computer readable media containing program instructions for driving a network interface card as recited in
28. A computer readable media containing program instructions for driving a network interface card as recited in
29. A computer readable media containing program instructions for driving a network interface card as recited in
31. A computer readable media containing program instructions for driving a network interface card as recited in
32. A computer readable media containing program instructions for driving a network interface card as recited in
34. An apparatus for driving a network interface card as recited in
35. An apparatus for driving a network interface card as recited in
|
|||||||||||||||||||||||||
1. Field of the Invention
This invention relates generally to computer networks, and more particularly to software drivers used for controlling network interface cards.
2. Description of the Related Art
Computers are increasingly being coupled together into computer networks. In typical networks, hardware devices known as network interface cards (NICs) are used by computer systems to enable them to communicate over networks with other computer systems. Commonly, NICs are available as plug in devices that are connected to a computer's interface bus (e.g., PCI Bus), or are built directly into a computer's mother board. Traditionally, a computer's NIC enables communication over a single computer network, such as a Local Area Network (LAN), which may include a multitude of switches and network devices. Through these network devices, remote hosts are capable of communicating with other similarly connected remote hosts or to a server computer system. Through these networks, remote hosts are able to, for example, request data from a server computer system, and the server computer system is able to transfer the requested data to the requesting host over the network. In response to the increased demand for resources stored on networked server computers, many NICs are now capable of communicating over more than one network. In this manner, data stored on one server computer system may be accessed by hosts coupled to different networks (e.g., different LANs).
Because NIC 30 is responsible for providing the communication path between a multitude of remote hosts, the loading experienced by NICs installed on a server computer system 20 are far greater than the typical loads experienced by NICs installed on the individual remote hosts. By way of example, server computer system 20 typically receives a few short requests from the remote hosts and then responds by transmitting out a great deal of data to the requesting hosts. In addition, because NIC 30 is only able to transmit out to each network at a fixed bandwidth (e.g., about 10 Mbps/100 Mbps), the server computer system 20 will unfortunately be tied up responding to data transmit requests for extended periods of time.
Another common problem with conventional NICs is that access to server computer system 20 may be completely blocked-off to an entire network whenever one port fails to operate properly. By way of example, if port P1 fails, all hosts connected to LAN-1 10 will be prevented from accessing data stored on server computer system 20. As is well known, port failures are common, and are typically caused by network overloads, NIC software driver bugs, NIC link interface failures, and NIC hardware failures. In any event, when a failure occurs, a large number of users attempting to access or transfer data between the server computer system 20 will be unable to accomplish their networking task. Typically, when a NIC port (e.g., port P1) failure occurs, the server computer system 20 is typically shut down to all network traffic (i.e., LANs 10, 12, 14, and 16) while network technicians trouble shoot and fix the NIC port failure. Of course, network repairs may disable a network for several hours or even days.
As businesses continue to intensely network their operations, port failures will unfortunately lead to substantial losses in worker productivity. For example, many companies use a central server to network their employees that may be located in several remote office locations. As such, when the port servicing a particular office goes down, that entire office will be unable access shared data stored on the central server. NIC port failures are also common in large corporations such as, banks, hotel chains, and airlines that critically depend on real-time access to data stored on a central server computer. Consequently, NIC port failures are commonly to blame for significant yearly losses in revenue as well as lower customer satisfaction.
In view of the foregoing, there is a need for a network interface card(s) (NICs) that provide increased load balancing transmit throughput to networks connected to the NIC, while providing resilient backup capabilities that enable continuous data transferring connections when port failures occur. Further, there is a need for NIC software drivers to intelligently detect port failures and automatically redistribute data transfer loads over functioning NIC ports.
Broadly speaking, the present invention fills these needs by providing methods and apparatus for increasing throughput in a load balancing manner over a multi-port NIC. Each port of the multi-port NIC preferably has its own link to the network, hub, or switch, which enables the multi-port NIC to reconfigure automatically to recover from a port failure. The multi-port NIC, driven by a smart NIC driver preferably reconfigures the multi-port driver by redistributing the load (both transmit and receive) over the remaining active ports. It should be appreciated that the present invention can be implemented in numerous ways, including as a process, an apparatus, a system, a device, a method, or a computer readable medium. Several inventive embodiments of the present invention are described below.
In one embodiment, a process for driving a network interface card is disclosed. The process includes monitoring the status of a plurality of ports connected between a computer and a network. Detecting a failure in one of the plurality of ports connected to the network. Re-assigning data transmitted over the failed one of the plurality of ports to an active port of the plurality of ports selected in a round robin technique. The process further including receiving data over one of the plurality of ports designated as a primary receiving port. In a preferred embodiment, when the failed one of the plurality of ports is the primary receiving port, the receiving tasks are assigned to a next active port selected in a round robin technique.
In another embodiment, a method for transmitting and receiving data over a network from a server computer system is disclosed. The method includes connecting a plurality of ports between the server computer system and the network for communicating with a plurality of remote hosts coupled to the network. Transmitting a load of data through the plurality of ports to the plurality of remote hosts. Detecting a failure in one of the plurality of ports during a transmit to a selected one of the plurality of remote hosts. The method further includes redistributing the load of data assigned to the failed one of the plurality of ports to an available port of the plurality of ports. Preferably, data is received through one of the plurality of ports designated as a primary receiving port.
In yet a further embodiment, a computer readable media containing program instructions for driving a network interface card is disclosed. The computer readable media includes program instructions for monitoring a status of a plurality of ports connected between a computer and a network. Program instructions for building a port resolution table indexing connections to at least one remote host that is communicating through a selected one of the plurality of ports. The computer readable media further includes program instructions for periodically updating the port resolution table after a predetermined time-out. Preferably, the at least one remote host is assigned host parameters identifying a media access control address of the at least one remote host, a number assigned to the selected one of the plurality of ports, and a timer.
In still another embodiment, a computer readable media containing program instructions for driving a network interface card is disclosed. The computer readable media includes program instructions for monitoring a status of a plurality of ports connected between a computer and a network. Program instructions for detecting a failure in one of the plurality of ports connected to the network. Program instructions for re-assigning data transmitted over the failed one of the plurality of ports to an active port of the plurality of ports selected in a round robin technique. The computer readable media further includes program instructions for receiving data over one of the plurality of ports designated as a primary receiving port.
In another embodiment, an apparatus for driving a network interface card is disclosed. That apparatus includes means for monitoring a status of a plurality of ports connected between a computer and a network. Means for detecting a failure in one of the plurality of ports connected to the network. Means for re-assigning data transmitted over the failed one of the plurality of ports to an active port of the plurality of ports selected in a round robin technique. The apparatus further includes means for receiving data over one of the plurality of ports designated as a primary receiving port.
Advantageously, the embodiments of the present invention provide a multi-port network interface card having a plurality of ports connected to a single network, and a smart network interface driver for controlling the functions of the multi-port card and interactions with existing server operating systems. As such, it should be appreciated that no changes are required to be made to existing operating systems or other applications to take advantage of the increased throughput and redundancy provided in accordance with the present invention. Further, all internal load balancing and aggregation provides a resilient network interface card that automatically reconfigures itself in case of failure to one or more of the ports, and the re-configuration occurs in real-time without requiring operator intervention. These and other aspects and advantages of the invention will become apparent from the following detailed description, taken in conjunction with the accompanying drawings, illustrating by way of example the principles of the invention.
The present invention will be readily understood by the following detailed description in conjunction with the accompanying drawings, wherein like reference numerals designate like structural elements, and in which:
An invention is described for methods and apparatus for increasing throughput in a load balancing manner over a multi-port NIC. The present invention also provides a smart NIC driver for managing loads over the multi-port NIC and redistributing loads over active ports when failures occur with a given port of the multi-port NIC. In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be obvious, however, to one skilled in the art, that the present invention may be practiced without some or all of these specific details. In other instances, well known process operations have not been described in detail in order not to unnecessarily obscure the present invention.
In one embodiment, the multi-port NIC is well suited for server computer systems that are required to transfer large amounts of data over a network in response to numerous short data requests. Preferably, the multi-port NIC of the present invention has each of its ports linked to the network, hub, or switch, and each port acts as an independent NIC having an associated bandwidth. Accordingly, the multi-port NIC of the present invention is capable of simultaneously transmitting data over each of the ports to a particular remote host located within a network with an aggregated bandwidth. By way of example, if each port of the multi-port NIC has a bandwidth of 100 Mbps, and the multi-port NIC is a 4-port card, the total aggregated bandwidth can be 400 Mbps, or higher for NICs with additional ports. Further, when ever a port of the multi-port NIC fails, the smart NIC driver that controls the operability of the multi-port NIC will automatically redistribute the load over the remaining ports that remain active.
Preferably, the present invention uses a "single" instance of the smart NIC driver 126 to control each port of the multi-port NIC 130. In this manner, the operating system 124 is capable of interfacing with the smart NIC driver 126 to control the multiple ports of a multi-port NIC 130 in a manner that is transparent to the operating system 124. That is, although smart NIC driver 126 is controlling multiple ports to a single network, its interface with existing operating systems will be essentially identical to software drivers used to conventionally control data flow through a single port. Therefore, the smart NIC driver 126 is seamlessly able to communicate with any of the well established network protocols controlled by operating system 124, including TCP/IP, Netware and NetBEUI.
In the example of
To manage packet switching, switch 140 typically creates routing tables and stores packet data in queues before routing the data to its destination, which may be any one or more Hosts 132a through 132n, that may be connected to switch 140 of network 110. Although only one switch has been illustrated for ease of description, it should be understood that typical networks include a multitude of network devices interconnecting a plurality of hosts through many hubs, switches, repeaters, bridges and routers.
It is important to note that each one of the ports P1, P2, P3, and P4 may transmit data through switch 140 at the same time in a load balanced manner which advantageously enables multi-port NIC 130 to increase its transmit throughput. For example, assume that ports P1, P2 and P4 are currently transmitting packets through switch 140 of network 110, and when a new transmit request is received for a new host (currently not in the PRT table) by multi-port NIC 130, the smart NIC driver 126 of
As mentioned above, port P1 is preferably designated as the primary receive (Rx) port assigned all receiving tasks of packet data coming from Hosts 132a through 132n shown connected to network 110. Because NICs resident in server computers are typically requested to transmit out substantially more data than it is required to receive, only one port is actually necessary for efficiently performing the receive functions of multi-port NIC 130. However, if port P1 fails for any reason, smart NIC driver 126 will automatically re-assign the receive (Rx) tasks to the next active port (in a round robin orientation) of multi-port NIC 130. Once assigned to the next active port, the port that is now assigned with the receiving tasks will also be assigned the Ethernet MAC address of port P1. In this manner, all upper layer protocols will continue sending data to the same destination address "DA" associated with the Ethernet MAC address of P1.
It is important to point out that because the primary Rx's Ethernet MAC address is assigned the port taking over the receiving functions, all external hosts connected to the network 110 will be unable to tell a difference in the internal and transparent re-assignment of server 120 receiving functions. As such, the internal re-assignment of the primary Rx Ethernet MAC address is transparently controlled by the smart NIC driver 126, and all that external hosts understand is that the multi-port NIC 130 is continuing to function smoothly and uninterrupted.
In one embodiment, if the primary Rx Ethernet MAC address is re-assigned to another port, the port newly assigned with the receiving Rx functions will also transmit (Tx) using the source address "SA" of the primary. By way of example, assuming that the primary Rx port P1 were to fail, and the next active port was port P3, then when port P3 transmits a packet over the network, that transmitted packet will have the source address SA-1 associated with P1. As will be described in greater detail with reference to
In a like manner, if any one of the transmit ports, e.g., port P3 fails at any point during a transmission, the load assigned to port P3 will be redistributed in a round robin manner to the next active and free port of multi-port NIC 130. However, if all ports that remain active are currently busy (i.e., not free), then the load of port P3 will be assigned to the least busiest of the remaining ports, thereby enabling efficient load balancing over the remaining active ports.
Once multi-port NIC 130 has been installed into a computer and connected to a network, the method proceeds to an operation 504 where a multi-port NIC 130 configuration panel is called up in the form of a graphical user interface (GUI). The method then proceeds to an operation 506 where port configuration is performed for each port in the multi-port NIC 130 to ascertain the bandwidth (e.g., 10 Mbps, 100 Mbps, etc.) of each port. By way of example, as shown in
By default, the connection type for the available network ports is set to "auto detect default connection" which is configured to ascertain the type of connection associated with each of the particular ports. However, if the user desires to manually change the connection types, the connection types window 522 may be modified through the drop-down list box to make an appropriate change. Once the changes are made, the apply icon button is preferably selected to implement the newly entered connection types.
Referring back to
By way of example, when a port is selected from the available port list 534 and the ADD button 542a is clicked, the selected port will be shifted to a group ports list 536. Of course, ports may also be removed from the group ports list 536 by clicking remove button 542b after a port is selected from the group ports list 536. Once the selected ports are moved in or out of the group ports list 536, the user may name that group in a groups window 540, where a link check time-out is provided. As will be described in greater detail below, the link check time-out (LCT) is used to check the activity of the selected ports during operation. In the example shown, the LCT time is set to 10 seconds, however, the LCT timer may be set to any number of seconds between about 1 second and about 20 seconds.
If the user selects the status icon 548 within the port aggregation GUI 530, a port aggregation window 540 of
Returning to
Next, the method proceeds to an operation 604 where the smart NIC driver 126 creates registry groups from the registry values associated with the groups configured through the graphical user interfaces. Once the smart NIC driver 126 creates the groups as shown in
The method then proceeds to an operation 704 where the destination Ethernet media access control (MAC) address is retrieved from packets that are to be transmitted over the network. By way of example, if a data packet is requested to be transmitted to a remote Host A, then the destination address "DA" of the Host A will be retrieved from the packet that is to be transmitted. The method then proceeds to a decision operation 706 where it is determined whether the retrieved Ethernet MAC address is currently listed in a PRT table.
By way of example,
If the examination of the 6th byte of the destination address "DA" of the packet to be transmitted returns, for example, a number 3, then the entire destination address "DA" of the packet being transmitted is compared to the MAC destination address of any hosts linked to the entry indexed in the PRT table. In this example, only one Host C 132c is linked to index number 3, and therefore the comparison of the DA of the packet being sent and the MAC destination address of Host C 132c should match up. However, as will be described below, if there are multiple hosts doubly linked to the same index number (i.e., both hosts have the same 6th byte) then the comparison is done for those multiple hosts that are doubly linked. Although destination and source addresses are typically 6 bytes long, comparisons are preferably performed based on 8 bytes (two words) at one time to improve processing efficiency. That is, additional zero values are added to the 6 bytes of the SA and DA to ensure that comparisons are based on two words. It should be appreciated that this lookup table comparison technique is well suited to reduce the amount of processing required by the CPU of the computer containing the multi-port NIC 130, thereby reducing the number of possible CPU interrupts.
Assuming that the first packet to be transferred through multi-port NIC 130 (i.e., when none of the ports are currently in use) is a packet destined for Host C 132c as described above, then the first available port P1 will be selected in a round robin selection technique. As pictorially shown in
Continuing with the example of
As will be described with reference to
Returning to
Alternatively, if it is determined in operation 708 that the port for the Ethernet MAC address is not active, the method will proceed to an operation 710 where a new port is selected for transmission to a desired remote host. Once a new port is selected from the remaining active ports (or least busiest) in a round robin technique, the method will proceed to an operation 712 where the packet(s) are transmitted over the port to the desired Ethernet MAC address of the recipient host.
On the other hand, if it is determined that the next port is not free in operation 804, the method will proceed to an operation 806 where it is determined whether all ports have been checked and been determined to have been busy. If all ports have been not been checked and been determined to have been busy, the method will proceed back to operation 802 where the method proceeds to select the next active port in a round robin orientation. Once the next active port is selected, the method will again proceed to decision operation 804 where it is determined if this next port is free. If it is again determined to not have been free, then the method will again proceed to decision operation 806 where it is again determined whether all ports have been checked and are busy.
Once all ports have been checked and have been ascertained to be busy, the method will proceed from operation 806 to operation 810, where the least busiest port is selected for transmission. Once the least busiest port has been selected for transmission, the method returns to operation 712 of FIG. 7A. In a like manner, if one port was ascertained to be free in operation 808, that port would be selected and the method would proceed to operation 712 of FIG. 7A. In sum, the selection of a new port is performed in a load balancing manner that first determines whether there are any free ports that may be used for transmission, and if there are no free ports, the method will proceed to select the least busiest port for transmission.
In operation 902, the method will then proceed to the next entry in the PRT table. The next entry is entry number 2, which again does not satisfy the condition of operation 904, therefore, the method will again proceed to operation 902 where the method moves to entry number 3. Once at entry number 3, it is determined in decision operation 904 that there is a host associated with the current PRT table entry. At this point, the method proceeds to a decision operation 906 where it is determined whether the timer of the parameters box 750 is currently set to "0." In this example, the timer is currently shown set to "1," and therefore the method proceeds to operation 910 where the PRT timer is re-set to "0" as shown in parameters box 750a.
On the other hand, if it is determined in operation 906 that the timer was already set to "0," then the method would proceed to operation 908, where the host entry would be deleted from the PRT table as shown in FIG. 7C. The removal of Host C 132c from the PRT table essentially means that port P1 was idle for at least a predetermined PRT timer delay time-out. In one embodiment, the PRT timer delay (TIMEOUT) is calibrated for performance optimization to a time of between about ¼ second and 1 second, and most preferably about ½ second. Of course, these preferred optimizations may vary depending on network loading as well as other factors.
Once Host C 132c entry is removed from the PRT table as shown in
Once the timer is set to "0," the method will proceed to decision operation 912 where it is determined if there is a pointer to a next doubly linked host. Because Host B 132b is doubly linked to Host A 132a, the method will proceed back to operation 906 where it is determined if the timer of the parameters box 754 is set to "0." Because the timer is currently set to "1," the method will proceed to operation 910 where the timer is set to "0." On the other hand, if the timer had been set to 0 as shown in parameters box 754a, the method would have proceeded to operation 908 where the host would be deleted from the PRT table as shown in FIG. 7C. This process will therefore continue until all 255 entries have been analyzed and the method will proceed to operation 916, where the routine will wait for a PRT timer delay (TIMEOUT). Once the TIMEOUT is complete, the method will again proceed through the PRT timer routine and commence marching through each of the entries beginning with 0, and checking the timers of each host that is currently linked (or doubly-linked) with an entry of the PRT table.
As mentioned above, if the timer of any host was previously set to 0 in a prior PRT timer routine, that host will be deleted as an entry to the PRT table as described with reference to operation 908 of FIG. 9. As such, when a host is deleted from the PRT table, the port number allocated to that host will likewise become available when a new packet transfer operation is requested to a new remote host not currently linked to the table, or the same port link may again be re-established.
Therefore, if it is determined that the primary Rx port is active, the method will proceed to a decision operation 1010 where it is determined if the primary Rx port is functioning as the receiver. By way of example, if the primary Rx port had previously failed for any reason, the receiving tasks would have been assigned to the next available active port. However, assuming that the primary Rx port is the receiver, the method will proceed to an operation 1016 where the LCT timer is re-started.
On the other hand, if it is determined that the primary Rx port is not currently the receiver in operation 1010, the method would proceed to an operation 1014 where the primary Rx port would be designated as the receiver, because it was determined in operation 1004 that the primary Rx port was active. Then, once the primary port Rx is designated as the receiver, the method would proceed to operation 1016 where the LCT timer would be restarted. Referring back to operation 1004, if it is determined that the primary Rx port is not active, then the method would proceed to a decision operation 1006.
In decision operation 1006, it is determined whether the primary Rx port is currently designated as the receiver. By way of example, assuming that the primary Rx port was functioning as the receiver, and then failed to operate properly (i.e., not active) in operation 1004, then the receiving tasks would have to be assigned to another port. Therefore, if the primary Rx port is currently the receiver and it is no longer active, the method would proceed to an operation 1012, where the next active port (selected in a round robin orientation) would be designated as the receiver. On the other hand, if it was determined in operation 1006 that the primary Rx port was not the receiver, the method would proceed to a decision operation 1008 where it is determined if the port designated as the receiver is active.
By way of example, assuming that the primary Rx port was not functioning as the receiver, and the port assigned all receiving functions also became inactive as determined in operation 1008, the method would proceed to operation 1012 where the next active port would be designated as a receiver. On the other hand, if the port designated as the receiver in operation 1008 was active, the method would proceed to operation 1016 where the LCT timer would be re-started as described above. Once the LCT timer is restarted in operation 1016, the method will proceed to an operation 1018 where a link check timer delay (TIMEOUT) would commence. In one embodiment, the LCT time-out is preferably set by the user to be between about 1 second and about 10 seconds, and most preferably, about 2 seconds. Of course, these LCT time-out parameters may be modified outside the preferred times to fit well within networks of varying load requirements. After the TIMEOUT of operation 1018, the method will proceed through the link check timer routine again as described above.
Tables A through D below illustrate the re-assignment of receiver functions to the active ports when the port assigned the receiving functions fails to operate due to software errors, hardware errors, network over-loading errors, or a combination thereof. In table A below, all ports are currently active, and the primary Rx port P1 is assigned all receiving functions. As such, each port will have its own MAC address, and transmits will be performed with their own source addresses attached to the packet.
| TABLE A | |||
| MAC | Source | ||
| Ports | Address | Address | |
| Port P1 (Active) (Primary Rx) | MAC-1 | SA-1 | |
| * Receiver | |||
| Port P2 (Active) | MAC-2 | SA-2 | |
| Port P3 (Active) | MAC-3 | SA-3 | |
| Port P4 (Active) | MAC-4 | SA-4 | |
When port P1 fails for any reason, the smart NIC driver 126 will look to the next active port, and assign the receiving functions to that port. As illustrated in Table B below, port P2 is now the receiver. As mentioned above, because port P2 is now the receiver, it will be assigned the MAC address of port P1, and when port P2 transmits out, it will transmit packets with the source address SA-1 of port P1.
| TABLE B | |||
| MAC | Source | ||
| Ports | Address | Address | |
| Port P1 (Down) (Primary Rx) | MAC-1 | SA-1 | |
| Port P2 (Active) | MAC-1 | SA-1 | |
| * Receiver | |||
| Port P3 (Active) | MAC-3 | SA-3 | |
| Port P4 (Active) | MAC-4 | SA-4 | |
If after an LCT timer routine it is determined that port P2 is no longer active (operation 1008), then the smart NIC driver 126 will designate the next active port as the receiver. As shown in Table C below, the next active port is port P3. Because port P3 is now the receiver, it will be assigned the MAC address of the primary Rx port P1, and any transmits performed from port P3 will have the source address SA-1.
| TABLE C | |||
| MAC | Source | ||
| Ports | Address | Address | |
| Port P1 (Down) (Primary Rx) | MAC-1 | SA-1 | |
| Port P2 (Down) | MAC-2 | SA-2 | |
| Port P3 (Active) | MAC-1 | SA-1 | |
| * Receiver | |||
| Port P4 (Active) | MAC-4 | SA-4 | |
When the link check timer routine is performed again after the predetermined timeout, the smart NIC driver 126 will proceed to decision operation 1004 where it will be determined that the primary Rx port P1 is again active as shown in Table D below. As such, the primary Rx port will be once again designated as the receiver as described in operation 1014, after it is determined that the primary Rx port was not the receiver in operation 1010, and shown in Table C above.
| TABLE D | |||
| MAC | Source | ||
| Ports | Address | Address | |
| Port P1 (Active) (Primary Rx) | MAC-1 | SA-1 | |
| * Receiver | |||
| Port P2 (Down) | MAC-2 | SA-2 | |
| Port P3 (Active) | MAC-3 | SA-3 | |
| Port P4 (Active) | MAC-4 | SA-4 | |
The present invention may be implemented using any type of integrated circuit logic or software driven computer-implemented operations. By way of example, a hardware description language (HDL) based design and synthesis program may be used to design the silicon-level circuitry necessary to appropriately perform the data and control operations in accordance with one embodiment of the present invention. By way of example, a VHDL® hardware description language available from IEEE of New York, N.Y. may be used to design an appropriate silicon-level layout. Although any suitable design tool may be used, another layout tool may include a hardware description language "Verilog®" tool available from Cadence Design Systems, Inc. of Santa Clara, Calif.
The invention may also employ various computer-implemented operations involving data stored in computer systems. These operations are those requiring physical manipulation of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. Further, the manipulations performed are often referred to in terms, such as producing, identifying, determining, or comparing.
Any of the operations described herein that form part of the invention are useful machine operations. The invention also relates to a device or an apparatus for performing these operations. The apparatus may be specially constructed for the required purposes, or it may be a general purpose computer selectively activated or configured by a computer program stored in the computer. In particular, various general purpose machines may be used with computer programs written in accordance with the teachings herein, or it may be more convenient to construct a more specialized apparatus to perform the required operations. An exemplary structure for the invention is described below.
The microprocessor 1116 is a general purpose digital processor which controls the operation of the computer system 1100. The microprocessor 1116 can be a single-chip processor or can be implemented with multiple components. Using instructions retrieved from memory, the microprocessor 1116 controls the reception and manipulation of input data and the output and display of data on output devices. According to the invention, a particular function of microprocessor 1116 is to assist in the port aggregation and load balancing tasks controlled by smart NIC driver 126 of multi-port NIC 130.
The memory bus 1118 is used by the microprocessor 1116 to access the RAM 1120 and the ROM 1122. The RAM 1120 is used by the microprocessor 1116 as a general storage area and as scratch-pad memory, and can also be used to store input data and processed data. The ROM 1122 can be used to store instructions or program code followed by the microprocessor 1116 as well as other data.
The peripheral bus 1124 is used to access the input, output, and storage devices used by the digital computer 1102. In the described embodiment, these devices include the display screen 1104, the printer device 1106, the floppy disk drive 1108, the hard disk drive 1110, and the network interface 1112. The keyboard controller 1126 is used to receive input from keyboard 1114 and send decoded symbols for each pressed key to microprocessor 116 over bus 1128.
The display screen 1104 is an output device that displays images of data provided by the microprocessor 1116 via the peripheral bus 1124 or provided by other components in the computer system 1100. The printer device 1106 when operating as a printer provides an image on a sheet of paper or a similar surface. Other output devices such as a plotter, typesetter, etc. can be used in place of, or in addition to, the printer device 1106.
The floppy disk drive 1108 and the hard disk drive 1110 can be used to store various types of data. The floppy disk drive 1108 facilitates transporting such data to other computer systems, and hard disk drive 1110 permits fast access to large amounts of stored data.
The microprocessor 1116 together with an operating system operate to execute computer code and produce and use data. The computer code and data may reside on the RAM 1120, the ROM 1122, or the hard disk drive 1110. The computer code and data could also reside on a removable program medium and loaded or installed onto the computer system 1100 when needed. Removable program mediums include, for example, CD-ROM, PC-CARD, floppy disk and magnetic tape.
The network interface 1112 is used to send and receive data over a network connected to other computer systems. An interface card or similar device and appropriate software implemented by the microprocessor 1116 can be used to connect the computer system 1100 to an existing network and transfer data according to standard protocols.
The keyboard 1114 is used by a user to input commands and other instructions to the computer system 1100. Other types of user input devices can also be used in conjunction with the present invention. For example, pointing devices such as a computer mouse, a track ball, a stylus, or a tablet can be used to manipulate a pointer on a screen of a general-purpose computer.
The invention can also be embodied as computer readable code on a computer readable medium. The computer readable medium is any data storage device that can store data which can be thereafter be read by a computer system. Examples of the computer readable medium include read-only memory, random-access memory, CD-ROMs, magnetic tape, optical data storage devices. The computer readable medium can also be distributed over a network coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.
Although the foregoing invention has been described in some detail for purposes of clarity of understanding, it will be apparent that certain changes and modifications may be practiced within the scope of the appended claims. In addition, it should be understood that the various processing functions described above may be implemented both in silicon as hardware integrated circuits, or as software code that may be stored and retrieved from any suitable storage medium. Accordingly, the present embodiments are to be considered as illustrative and not restrictive, and the invention is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.
Sharma, Pramod, Latif, Faisal, Saya, Suleman, Kuhfeld, Jim J.
| Patent | Priority | Assignee | Title |
| 10148501, | Jun 27 2014 | TELEFONAKTIEBOLAGET LM ERICSSON PUBL | Method for TRX installation in BSC |
| 10148746, | Jan 28 2014 | MELLANOX TECHNOLOGIES, LTD.; Mellanox Technologies Ltd | Multi-host network interface controller with host management |
| 10402765, | Feb 17 2015 | T-MOBILE INNOVATIONS LLC | Analysis for network management using customer provided information |
| 10581637, | Mar 01 2016 | PayPal, Inc | Computational node adaptive correction system |
| 10592223, | Apr 30 2014 | MICRO FOCUS LLC | Using a single deployer agent to deploy a plurality of programs on a server |
| 10733135, | Apr 03 2017 | FUTUREWEI TECHNOLOGIES, INC | Universal serial bus network switch |
| 10855551, | Dec 31 2014 | Dell Products L.P. | Multi-port selection and configuration |
| 10880235, | Aug 20 2009 | Oracle International Corporation | Remote shared server peripherals over an ethernet network for resource virtualization |
| 10997106, | Sep 22 2020 | PENSANDO SYSTEMS INC | Inter-smartNIC virtual-link for control and datapath connectivity |
| 11121941, | Mar 12 2020 | Cisco Technology, Inc; Cisco Technology, Inc. | Monitoring communications to identify performance degradation |
| 11258687, | Oct 10 2017 | BULL SAS | Method for generating requests for the segmentation of the monitoring of an interconnection network and associated hardware |
| 11425579, | Jul 09 2013 | CommScope Technologies LLC | Signal distribution interface |
| 11606310, | Sep 28 2020 | VMware, Inc. | Flow processing offload using virtual port identifiers |
| 11736565, | Sep 28 2020 | VMWARE, INC | Accessing an external storage through a NIC |
| 11736566, | Sep 28 2020 | VMWARE, INC | Using a NIC as a network accelerator to allow VM access to an external storage via a PF module, bus, and VF module |
| 11792134, | Sep 28 2020 | VMware, Inc. | Configuring PNIC to perform flow processing offload using virtual port identifiers |
| 11824931, | Sep 28 2020 | VMWARE, INC | Using physical and virtual functions associated with a NIC to access an external storage through network fabric driver |
| 11829793, | Sep 28 2020 | VMware, Inc.; VMWARE, INC | Unified management of virtual machines and bare metal computers |
| 11843691, | Aug 30 2017 | Intel Corporation | Technologies for managing a flexible host interface of a network interface controller |
| 11863376, | Dec 22 2021 | VMWARE, INC | Smart NIC leader election |
| 11875172, | Sep 28 2020 | VMware LLC; VMWARE, INC | Bare metal computer for booting copies of VM images on multiple computing devices using a smart NIC |
| 11899594, | Jun 21 2022 | VMware LLC | Maintenance of data message classification cache on smart NIC |
| 6560630, | Mar 18 1999 | HEWLETT-PACKARD DEVELOPMENT COMPANY, L P | Receive load balancing and fail over with multiple network interface cards |
| 6567377, | Mar 18 1999 | HEWLETT-PACKARD DEVELOPMENT COMPANY, L P | High performance load balancing of outbound internet protocol traffic over multiple network interface cards |
| 6601186, | May 20 2000 | Ciena Corporation | Independent restoration of control plane and data plane functions |
| 6646991, | Dec 22 1999 | U S BANK NATIONAL ASSOCIATION, AS COLLATERAL AGENT | Multi-link extensions and bundle skew management |
| 6687840, | Apr 21 2000 | Intel Corporation | Multi-link extensions and bundle skew management |
| 6701449, | Apr 20 2000 | CIPRICO INC | Method and apparatus for monitoring and analyzing network appliance status information |
| 6701462, | May 19 2000 | Rockwell Automation Technologies, Inc. | Situational aware output configuration and execution |
| 6711159, | Dec 15 1999 | Hewlett Packard Enterprise Development LP | Load balancing among media gateways |
| 6728848, | Jun 11 2001 | Hitachi, LTD | Method and system for backing up storage system data |
| 6742134, | May 20 2000 | Ciena Corporation | Maintaining a local backup for data plane processes |
| 6760781, | Feb 16 2000 | Hewlett Packard Enterprise Development LP | Intelligent packet transmission engine |
| 6799202, | Dec 16 1999 | STREAMONIX LIMITED | Federated operating system for a server |
| 6868062, | Mar 28 2000 | Intel Corporation | Managing data traffic on multiple ports |
| 6868476, | Aug 27 2001 | Intel Corporation | Software controlled content addressable memory in a general purpose execution datapath |
| 6874011, | Jul 31 2000 | Cisco Technology, Inc | Scalable IP-based notification architecture for unified messaging |
| 6876561, | Dec 28 1999 | Intel Corporation | Scratchpad memory |
| 6895457, | Sep 16 2003 | Intel Corporation | Bus interface with a first-in-first-out memory |
| 6928086, | Nov 21 1997 | International Business Machines Corporation | Dynamic detection of LAN network protocol |
| 6934951, | Jan 17 2002 | TAHOE RESEARCH, LTD | Parallel processor with functional pipeline providing programming engines by supporting multiple contexts and critical section |
| 6941438, | Jan 10 2003 | Intel Corporation | Memory interleaving |
| 6976095, | Dec 30 1999 | Intel Corporation | Port blocking technique for maintaining receive packet ordering for a multiple ethernet port switch |
| 6983350, | Aug 31 1999 | Intel Corporation | SDRAM controller for parallel processor architecture |
| 6993027, | Mar 17 1999 | AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE LIMITED | Method for sending a switch indicator to avoid out-of-ordering of frames in a network switch |
| 7016484, | Oct 13 2000 | Verizon Patent and Licensing Inc | System and method for effecting inside plant load balancing in a telecommunications system |
| 7020871, | Dec 21 2000 | Intel Corporation | Breakpoint method for parallel hardware threads in multithreaded processor |
| 7085234, | Oct 24 1996 | Hewlett Packard Enterprise Development LP | Method and apparatus for automatic load-balancing on multisegment devices |
| 7107413, | Dec 17 2001 | Intel Corporation | Write queue descriptor count instruction for high speed queuing |
| 7111296, | Dec 28 1999 | Intel Corporation | Thread signaling in multi-threaded processor |
| 7126952, | Sep 28 2001 | Intel Corporation | Multiprotocol decapsulation/encapsulation control structure and packet protocol conversion method |
| 7149226, | Feb 01 2002 | Intel Corporation | Processing data packets |
| 7158964, | Dec 12 2001 | Intel Corporation | Queue management |
| 7177952, | Oct 01 1999 | Apple | Method and system for switching between two network access technologies without interrupting active network applications |
| 7181573, | Jan 07 2002 | Intel Corporation | Queue array caching in network devices |
| 7181594, | Jan 25 2002 | TAHOE RESEARCH, LTD | Context pipelines |
| 7191309, | Sep 01 1999 | Intel Corporation | Double shift instruction for micro engine used in multithreaded parallel processor architecture |
| 7191321, | Aug 31 1999 | Intel Corporation | Microengine for parallel processor architecture |
| 7206955, | Dec 22 1999 | U S BANK NATIONAL ASSOCIATION, AS COLLATERAL AGENT | Bundle skew management and cell synchronization |
| 7213099, | Dec 30 2003 | Intel Corporation | Method and apparatus utilizing non-uniformly distributed DRAM configurations and to detect in-range memory address matches |
| 7216204, | Aug 27 2001 | Intel Corporation | Mechanism for providing early coherency detection to enable high performance memory updates in a latency sensitive multithreaded environment |
| 7222255, | Feb 28 2001 | VALTRUS INNOVATIONS LIMITED | System and method for network performance testing |
| 7225281, | Aug 27 2001 | Intel Corporation | Multiprocessor infrastructure for providing flexible bandwidth allocation via multiple instantiations of separate data buses, control buses and support mechanisms |
| 7228397, | Jun 11 2001 | Hitachi, Ltd. | Method and system for backing up storage system data |
| 7246197, | Jan 25 2005 | Intel Corporation | Software controlled content addressable memory in a general purpose execution datapath |
| 7269179, | Dec 18 2001 | Intel Corporation | Control mechanisms for enqueue and dequeue operations in a pipelined network processor |
| 7302549, | Jan 17 2002 | TAHOE RESEARCH, LTD | Processing packet sequence using same function set pipelined multiple threads spanning over multiple processing engines and having exclusive data access |
| 7305500, | Aug 31 1999 | Intel Corporation | Sram controller for parallel processor architecture including a read queue and an order queue for handling requests |
| 7307948, | Oct 21 2002 | AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE LIMITED | System with multiple path fail over, fail back and load balancing |
| 7328284, | May 06 2002 | TAHOE RESEARCH, LTD | Dynamic configuration of network data flow using a shared I/O subsystem |
| 7328289, | Dec 30 1999 | Intel Corporation | Communication between processors |
| 7337275, | Aug 13 2002 | Intel Corporation | Free list and ring data structure management |
| 7352769, | Sep 12 2002 | Intel Corporation | Multiple calendar schedule reservation structure and method |
| 7356046, | Feb 09 2004 | MERCURY INSTRUMENTS LLC | Method and apparatus for remotely monitoring and controlling devices |
| 7356608, | May 06 2002 | TAHOE RESEARCH, LTD | System and method for implementing LAN within shared I/O subsystem |
| 7394758, | Sep 04 2001 | Method for supporting SDH/SONET APS on Ethernet | |
| 7394766, | Dec 22 1999 | Intel Corporation | Multi-link extensions and bundle skew management |
| 7404012, | May 06 2002 | TAHOE RESEARCH, LTD | System and method for dynamic link aggregation in a shared I/O subsystem |
| 7418571, | Jan 10 2003 | Intel Corporation | Memory interleaving |
| 7421572, | Aug 31 2000 | Intel Corporation | Branch instruction for processor with branching dependent on a specified bit in a register |
| 7424579, | Aug 31 1999 | Intel Corporation | Memory controller for processor having multiple multithreaded programmable units |
| 7433307, | Nov 05 2002 | Intel Corporation | Flow control in a network environment |
| 7434221, | Dec 30 1999 | Intel Corporation | Multi-threaded sequenced receive for fast network port stream of packets |
| 7437724, | Apr 03 2002 | TAHOE RESEARCH, LTD | Registers for data transfers |
| 7443836, | Jun 16 2003 | Intel Corporation | Processing a data packet |
| 7447778, | May 06 2002 | TAHOE RESEARCH, LTD | System and method for a shared I/O subsystem |
| 7460470, | Mar 18 2005 | VALTRUS INNOVATIONS LIMITED | Systems and methods of priority failover determination |
| 7471688, | Jun 18 2002 | Intel Corporation | Scheduling system for transmission of cells to ATM virtual circuits and DSL ports |
| 7480706, | Dec 30 1999 | Intel Corporation | Multi-threaded round-robin receive for fast network port |
| 7487505, | Aug 27 2001 | Intel Corporation | Multithreaded microprocessor with register allocation based on number of active threads |
| 7505401, | Jan 31 2005 | International Business Machines Corporation | Method, apparatus and program storage device for providing mutual failover and load-balancing between interfaces in a network |
| 7506074, | Aug 08 2003 | Intel Corporation | Method, system, and program for processing a packet to transmit on a network in a host system including a plurality of network adaptors having multiple ports |
| 7519916, | Jun 16 2003 | Microsoft Technology Licensing, LLC | Methods for tailoring a bandwidth profile for an operating environment |
| 7546444, | Sep 01 1999 | Intel Corporation | Register set used in multithreaded parallel processor architecture |
| 7551615, | Dec 29 2004 | Intel Corporation | Method for packet encapsulation and redirection of data packets |
| 7610451, | Jan 25 2002 | Intel Corporation | Data transfer mechanism using unidirectional pull bus and push bus |
| 7620702, | Dec 28 1999 | Intel Corporation | Providing real-time control data for a network processor |
| 7668919, | Jul 31 2000 | Cisco Technology, Inc. | Scalable IP-based notification architecture for unified messaging |
| 7676691, | Aug 18 2006 | EMC IP HOLDING COMPANY LLC | Systems and methods for providing nonlinear journaling |
| 7680836, | Aug 18 2006 | EMC IP HOLDING COMPANY LLC | Systems and methods for a snapshot of data |
| 7680842, | Aug 18 2006 | EMC IP HOLDING COMPANY LLC | Systems and methods for a snapshot of data |
| 7681018, | Aug 31 2000 | Intel Corporation | Method and apparatus for providing large register address space while maximizing cycletime performance for a multi-threaded register file set |
| 7685126, | Aug 03 2001 | EMC IP HOLDING COMPANY LLC | System and methods for providing a distributed file system utilizing metadata to track information about data stored throughout the system |
| 7685334, | Nov 28 2005 | International Business Machines Corporation | Method for efficient communication between a host library controller and a medium changer library |
| 7698415, | Oct 27 2004 | Sprint Communications Company L.P. | Networked port-inventory system and method |
| 7710862, | Aug 30 2006 | VALTRUS INNOVATIONS LIMITED | Method and system of assigning media access control (MAC) addresses across teamed communication ports |
| 7734744, | Nov 09 1999 | Cisco Technology, Inc. | System for communicating management information and method of operation |
| 7743033, | Aug 03 2001 | EMC IP HOLDING COMPANY LLC | Systems and methods for providing a distributed file system utilizing metadata to track information about data stored throughout the system |
| 7743125, | Nov 09 2000 | General Electric Company | Computer multiple communications port unit |
| 7743235, | Aug 31 2000 | Intel Corporation | Processor having a dedicated hash unit integrated within |
| 7746768, | Sep 04 2001 | System and method for supporting SDH/SONET APS on ethernet | |
| 7751402, | Oct 10 2003 | Intel Corporation | Method and apparatus for gigabit packet assignment for multithreaded packet processing |
| 7752402, | Aug 18 2006 | EMC IP HOLDING COMPANY LLC | Systems and methods for allowing incremental journaling |
| 7778157, | Mar 30 2007 | Veritas Technologies LLC | Port identifier management for path failover in cluster environments |
| 7779048, | Apr 13 2007 | EMC IP HOLDING COMPANY LLC | Systems and methods of providing possible value ranges |
| 7788303, | Oct 21 2005 | EMC IP HOLDING COMPANY LLC | Systems and methods for distributed system scanning |
| 7797283, | Oct 21 2005 | EMC IP HOLDING COMPANY LLC | Systems and methods for maintaining distributed data |
| 7822932, | Aug 18 2006 | EMC IP HOLDING COMPANY LLC | Systems and methods for providing nonlinear journaling |
| 7831681, | Sep 29 2006 | Veritas Technologies LLC | Flexibly provisioning and accessing storage resources using virtual worldwide names |
| 7844617, | Dec 22 2006 | EMC IP HOLDING COMPANY LLC | Systems and methods of directory entry encodings |
| 7848261, | Feb 17 2006 | EMC IP HOLDING COMPANY LLC | Systems and methods for providing a quiescing protocol |
| 7882068, | Aug 21 2007 | EMC IP HOLDING COMPANY LLC | Systems and methods for adaptive copy on write |
| 7882071, | Aug 18 2006 | EMC IP HOLDING COMPANY LLC | Systems and methods for a snapshot of data |
| 7895239, | Jan 04 2002 | Intel Corporation | Queue arrays in network devices |
| 7899800, | Aug 18 2006 | EMC IP HOLDING COMPANY LLC | Systems and methods for providing nonlinear journaling |
| 7900015, | Apr 13 2007 | EMC IP HOLDING COMPANY LLC | Systems and methods of quota accounting |
| 7903543, | Jan 31 2005 | International Business Machines Corporation | Method, apparatus and program storage device for providing mutual failover and load-balancing between interfaces in a network |
| 7917474, | Oct 21 2005 | EMC IP HOLDING COMPANY LLC | Systems and methods for accessing and updating distributed data |
| 7920555, | Apr 24 1998 | BEXLEY SOLUTIONS LLC | Composite trunking |
| 7937421, | Nov 14 2002 | EMC IP HOLDING COMPANY LLC | Systems and methods for restriping files in a distributed file system |
| 7949636, | Mar 27 2008 | EMC IP HOLDING COMPANY LLC | Systems and methods for a read only mode for a portion of a storage system |
| 7949692, | Aug 21 2007 | EMC IP HOLDING COMPANY LLC | Systems and methods for portals into snapshot data |
| 7953704, | Aug 18 2006 | EMC IP HOLDING COMPANY LLC | Systems and methods for a snapshot of data |
| 7953709, | Mar 27 2008 | EMC IP HOLDING COMPANY LLC | Systems and methods for a read only mode for a portion of a storage system |
| 7962779, | Aug 03 2001 | EMC IP HOLDING COMPANY LLC | Systems and methods for a distributed file system with data recovery |
| 7966289, | Aug 21 2007 | EMC IP HOLDING COMPANY LLC | Systems and methods for reading objects in a file system |
| 7971021, | Mar 27 2008 | EMC IP HOLDING COMPANY LLC | Systems and methods for managing stalled storage devices |
| 7984324, | Mar 27 2008 | EMC IP HOLDING COMPANY LLC | Systems and methods for managing stalled storage devices |
| 7991983, | Sep 01 1999 | Intel Corporation | Register set used in multithreaded parallel processor architecture |
| 8005865, | Mar 31 2006 | EMC IP HOLDING COMPANY LLC | Systems and methods for notifying listeners of events |
| 8010493, | Aug 18 2006 | EMC IP HOLDING COMPANY LLC | Systems and methods for a snapshot of data |
| 8015156, | Aug 18 2006 | EMC IP HOLDING COMPANY LLC | Systems and methods for a snapshot of data |
| 8015216, | Apr 13 2007 | EMC IP HOLDING COMPANY LLC | Systems and methods of providing possible value ranges |
| 8027984, | Aug 18 2006 | EMC IP HOLDING COMPANY LLC | Systems and methods of reverse lookup |
| 8031632, | Aug 30 2006 | Hewlett Packard Enterprise Development LP | Method and system of implementing virtual local area networks (VLANS) with teamed communication ports |
| 8051425, | Oct 29 2004 | EMC IP HOLDING COMPANY LLC | Distributed system with asynchronous execution systems and methods |
| 8054765, | Oct 21 2005 | EMC IP HOLDING COMPANY LLC | Systems and methods for providing variable protection |
| 8055711, | Oct 29 2004 | EMC IP HOLDING COMPANY LLC | Non-blocking commit protocol systems and methods |
| 8060521, | Dec 22 2006 | EMC IP HOLDING COMPANY LLC | Systems and methods of directory entry encodings |
| 8082379, | Jan 05 2007 | EMC IP HOLDING COMPANY LLC | Systems and methods for managing semantic locks |
| 8112395, | Aug 03 2001 | EMC IP HOLDING COMPANY LLC | Systems and methods for providing a distributed file system utilizing metadata to track information about data stored throughout the system |
| 8122120, | Dec 16 2002 | Unisys Corporation | Failover and failback using a universal multi-path driver for storage devices |
| 8140623, | Oct 29 2004 | EMC IP HOLDING COMPANY LLC | Non-blocking commit protocol systems and methods |
| 8176013, | Oct 21 2005 | EMC IP HOLDING COMPANY LLC | Systems and methods for accessing and updating distributed data |
| 8181065, | Aug 18 2006 | EMC IP HOLDING COMPANY LLC | Systems and methods for providing nonlinear journaling |
| 8195905, | Apr 13 2007 | EMC IP HOLDING COMPANY LLC | Systems and methods of quota accounting |
| 8200632, | Aug 21 2007 | EMC IP HOLDING COMPANY LLC | Systems and methods for adaptive copy on write |
| 8214334, | Oct 21 2005 | EMC IP HOLDING COMPANY LLC | Systems and methods for distributed system scanning |
| 8214400, | Oct 21 2005 | EMC IP HOLDING COMPANY LLC | Systems and methods for maintaining distributed data |
| 8238350, | Oct 29 2004 | EMC IP HOLDING COMPANY LLC | Message batching with checkpoints systems and methods |
| 8266261, | Mar 27 2009 | NEC Corporation | Server system, collective server apparatus, and MAC address management method |
| 8286029, | Dec 21 2006 | EMC IP HOLDING COMPANY LLC | Systems and methods for managing unavailable storage devices |
| 8289878, | May 09 2007 | T-MOBILE INNOVATIONS LLC | Virtual link mapping |
| 8301762, | Jun 08 2009 | Sprint Communications Company L.P. | Service grouping for network reporting |
| 8316191, | Aug 31 1999 | Intel Corporation | Memory controllers for processor having multiple programmable units |
| 8355316, | Dec 16 2009 | T-MOBILE INNOVATIONS LLC | End-to-end network monitoring |
| 8356013, | Aug 18 2006 | EMC IP HOLDING COMPANY LLC | Systems and methods for a snapshot of data |
| 8356150, | Aug 18 2006 | EMC IP HOLDING COMPANY LLC | Systems and methods for providing nonlinear journaling |
| 8380689, | Aug 18 2006 | EMC IP HOLDING COMPANY LLC | Systems and methods for providing nonlinear journaling |
| 8380923, | Jan 04 2002 | Intel Corporation | Queue arrays in network devices |
| 8412919, | Nov 10 2010 | Inventec Corporation | Method for controlling multi-port network interface card |
| 8441935, | Aug 09 2004 | Viavi Solutions Inc | Method and apparatus to distribute signaling data for parallel analysis |
| 8458323, | Aug 24 2009 | Sprint Communications Company L.P.; SPRINT COMMUNICATIONS COMPANY L P | Associating problem tickets based on an integrated network and customer database |
| 8539056, | Aug 02 2006 | EMC IP HOLDING COMPANY LLC | Systems and methods for configuring multiple network interfaces |
| 8565077, | Apr 28 2004 | INTERDIGITAL CE PATENT HOLDINGS | System and method for enhancing network quality of service |
| 8625464, | Feb 17 2006 | EMC IP HOLDING COMPANY LLC | Systems and methods for providing a quiescing protocol |
| 8644146, | Aug 02 2010 | Sprint Communications Company L.P. | Enabling user defined network change leveraging as-built data |
| 8677023, | Jul 22 2004 | Oracle International Corporation | High availability and I/O aggregation for server environments |
| 8699322, | Mar 30 2007 | Veritas Technologies LLC | Port identifier management for path failover in cluster environments |
| 8738886, | Dec 27 1999 | Intel Corporation | Memory mapping in a processor having multiple programmable units |
| 8966080, | Apr 13 2007 | EMC IP HOLDING COMPANY LLC | Systems and methods of managing resource utilization on a threaded computer system |
| 8976666, | Jul 25 2013 | IBOSS, INC | Load balancing network adapter |
| 9083550, | Oct 29 2012 | Oracle International Corporation | Network virtualization over infiniband |
| 9128818, | Dec 27 1999 | Intel Corporation | Memory mapping in a processor having multiple programmable units |
| 9264384, | Jul 22 2004 | Oracle International Corporation | Resource virtualization mechanism including virtual host bus adapters |
| 9305029, | Nov 25 2011 | T-MOBILE INNOVATIONS LLC | Inventory centric knowledge management |
| 9331963, | Sep 24 2010 | Oracle International Corporation | Wireless host I/O using virtualized I/O controllers |
| 9369375, | Dec 10 2013 | Red Hat, Inc.; Red Hat, Inc | Link-layer level link aggregation autoconfiguration |
| 9571448, | Dec 12 2007 | Nokia Technologies Oy | Address assignment protocol |
| 9729440, | Feb 22 2015 | MELLANOX TECHNOLOGIES, LTD.; Mellanox Technologies Ltd | Differentiating among multiple management control instances using IP addresses |
| 9813283, | Aug 09 2005 | Oracle International Corporation | Efficient data transfer between servers and remote peripherals |
| 9824037, | Dec 27 1999 | Intel Corporation | Memory mapping in a processor having multiple programmable units |
| 9824038, | Dec 27 1999 | Intel Corporation | Memory mapping in a processor having multiple programmable units |
| 9830284, | Dec 27 1999 | Intel Corporation | Memory mapping in a processor having multiple programmable units |
| 9830285, | Dec 27 1999 | Intel Corporation | Memory mapping in a processor having multiple programmable units |
| 9973446, | Aug 20 2009 | Oracle International Corporation | Remote shared server peripherals over an Ethernet network for resource virtualization |
| 9985820, | Feb 22 2015 | MELLANOX TECHNOLOGIES, LTD.; Mellanox Technologies Ltd | Differentiating among multiple management control instances using addresses |
| 9998359, | Dec 18 2013 | Mellanox Technologies Ltd | Simultaneous operation of remote management and link aggregation |
| RE41397, | Jun 30 1997 | AVAGO TECHNOLOGIES GENERAL IP SINGAPORE PTE LTD | Method and apparatus for network interface card load balancing and port aggregation |
| RE41849, | Dec 22 1999 | Sony Corporation of America | Parallel multi-threaded processing |
| Patent | Priority | Assignee | Title |
| 4658396, | Mar 11 1985 | Redundancy arrangement for a local area network | |
| 4694487, | Feb 07 1985 | American Telephone and Telegraph Company, AT&T Bell Laboratories | Controlling multi-fort hunt groups in a distributed control switching system |
| 4847837, | Nov 07 1986 | The United States of America as represented by the Administrator of the | Local area network with fault-checking, priorities and redundant backup |
| 5179550, | Mar 07 1991 | Lockheed Martin Corporation | System and method for controlling a multi-point matrix switch |
| 5239537, | Oct 17 1990 | NEC Corporation | Packet-switched network having alternate virtual paths |
| 5289458, | Mar 30 1992 | Intel Corporation | Apparatus for accomplishing autoport selection |
| 5329520, | Jul 17 1992 | Alcatel Network Systems, Inc. | High-speed facility protection in a digital telecommunications system |
| 5335227, | Dec 20 1990 | International Business Machines Corporation | Serial network topology and recognfiguration generator |
| 5361250, | Jan 28 1993 | AVAYA Inc | Apparatus and method of token ring beacon station removal for a communication network |
| 5390188, | Aug 02 1993 | AVAYA Inc | Method and apparatus for measuring and monitoring the performance within a ring communication network |
| 5410535, | Jul 02 1992 | ENTERASYS NETWORKS, INC | Automatic selection of an interface for ethernet stations |
| 5430726, | Jan 18 1991 | Repeater interface controller with a shared data bus | |
| 5448559, | May 07 1993 | Roke Manor Research Limited; Siemens Aktiengesellschaft | ATM communication system with interrogation of output port servers for available handing capacity |
| 5450403, | Mar 02 1993 | FURUKAWA ELECTRIC CO , LTD , THE | Method and apparatus for multiplex transmission |
| 5459714, | Feb 22 1993 | Advanced Micro Devices, INC | Enhanced port activity monitor for an integrated multiport repeater |
| 5479608, | Jul 17 1992 | Alcatel Network Systems, Inc. | Group facility protection in a digital telecommunications system |
| 5490252, | Sep 30 1992 | Rockstar Consortium US LP | System having central processor for transmitting generic packets to another processor to be altered and transmitting altered packets back to central processor for routing |
| 5526492, | Feb 27 1991 | Kabushiki Kaisha Toshiba | System having arbitrary master computer for selecting server and switching server to another server when selected processor malfunctions based upon priority order in connection request |
| 5586121, | Apr 21 1995 | Hybrid Patents Incorporated | Asymmetric hybrid access system and method |
| 5596723, | Jun 23 1994 | Dell USA, LP; DELL USA, L P | Method and apparatus for automatically detecting the available network services in a network system |
| 5598536, | Aug 09 1994 | Dialogic Corporation | Apparatus and method for providing remote users with the same unique IP address upon each network access |
| 5603029, | Jun 07 1995 | International Business Machines Corporation | System of assigning work requests based on classifying into an eligible class where the criteria is goal oriented and capacity information is available |
| 5606559, | Aug 11 1995 | International Business Machines Corporation; IBM Corporation | System and method for an efficient ATM adapter/device driver interface |
| 5606664, | May 21 1990 | Constellation Technologies LLC | Apparatus and method for automatically determining the topology of a local area network |
| 5646936, | Jun 22 1995 | Verizon Patent and Licensing Inc | Knowledge based path set up and spare capacity assignment for distributed network restoration |
| 5666488, | Nov 22 1994 | THE CHASE MANHATTAN BANK, AS COLLATERAL AGENT | Port expansion network and method for lAN hubs |
| 5708779, | Jul 29 1994 | International Business Machines Corporation | Multimedia system and method of controlling data transfer between a host system and a network adapter using a DMA engine |
| 5710549, | Sep 30 1994 | QNAP SYSTEMS, INC | Routing arbitration for shared resources |
| 5734811, | Jun 26 1996 | Verizon Patent and Licensing Inc | Segment substitution/swap for network restoration pre-plans |
| 5742587, | Feb 28 1997 | LANart Corporation | Load balancing port switching hub |
| 5742761, | Mar 29 1991 | International Business Machines Corporation | Apparatus for adapting message protocols for a switch network and a bus |
| 5754552, | Jul 12 1995 | HEWLETT-PACKARD DEVELOPMENT COMPANY, L P | Automatic communication protocol detection system and method for network systems |
| 5764895, | Jan 11 1995 | Sony Corporation; Sony Electronics, INC | Method and apparatus for directing data packets in a local area network device having a plurality of ports interconnected by a high-speed communication bus |
| 5790554, | Oct 04 1995 | RPX CLEARINGHOUSE LLC | Method and apparatus for processing data packets in a network |
| 5793746, | Apr 29 1996 | International Business Machines Corporation; IBM Corporation | Fault-tolerant multichannel multiplexer ring configuration |
| 5822300, | Apr 02 1996 | Hewlett Packard Enterprise Development LP | Congestion management scheme |
| 5828879, | Dec 22 1994 | Ericsson AB | Method and a scheduler for controlling when a server provides service to an entity |
| 5982744, | Aug 14 1997 | ALCATEL USA SOURCING, L P | High density unit shelf and method |
| 6009077, | Apr 08 1997 | MASSACHUSETTS, UNIVERSITY OF | Flow admission control for a router |
| Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
| Jun 27 1997 | KUHFELD, JIM J | Adaptec, Inc | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 008664 | /0927 | |
| Jun 27 1997 | SAYA, SULEMAN | Adaptec, Inc | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 008664 | /0927 | |
| Jun 27 1997 | SHARMA, PRAMOD | Adaptec, Inc | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 008664 | /0927 | |
| Jun 27 1997 | LATIF, FAISAL | Adaptec, Inc | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 008664 | /0927 | |
| Jun 30 1997 | Adaptec, Inc. | (assignment on the face of the patent) | / | |||
| Jun 22 2010 | Adaptec, Inc | ADPT Corporation | MERGER SEE DOCUMENT FOR DETAILS | 024964 | /0177 | |
| Jul 07 2010 | ADPT Corporation | Emulex Design & Manufacturing Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 025137 | /0525 | |
| Dec 05 2013 | Emulex Design and Manufacturing Corporation | Emulex Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 032087 | /0842 | |
| Feb 01 2016 | AVAGO TECHNOLOGIES GENERAL IP SINGAPORE PTE LTD | BANK OF AMERICA, N A , AS COLLATERAL AGENT | PATENT SECURITY AGREEMENT | 037808 | /0001 | |
| Jan 19 2017 | BANK OF AMERICA, N A , AS COLLATERAL AGENT | AVAGO TECHNOLOGIES GENERAL IP SINGAPORE PTE LTD | TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS | 041710 | /0001 |
| Date | Maintenance Fee Events |
| Oct 31 2005 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
| Nov 08 2005 | ASPN: Payor Number Assigned. |
| Nov 13 2009 | M1552: Payment of Maintenance Fee, 8th Year, Large Entity. |
| Date | Maintenance Schedule |
| May 21 2005 | 4 years fee payment window open |
| Nov 21 2005 | 6 months grace period start (w surcharge) |
| May 21 2006 | patent expiry (for year 4) |
| May 21 2008 | 2 years to revive unintentionally abandoned end. (for year 4) |
| May 21 2009 | 8 years fee payment window open |
| Nov 21 2009 | 6 months grace period start (w surcharge) |
| May 21 2010 | patent expiry (for year 8) |
| May 21 2012 | 2 years to revive unintentionally abandoned end. (for year 8) |
| May 21 2013 | 12 years fee payment window open |
| Nov 21 2013 | 6 months grace period start (w surcharge) |
| May 21 2014 | patent expiry (for year 12) |
| May 21 2016 | 2 years to revive unintentionally abandoned end. (for year 12) |