1. Field of the Invention
The described invention relates to the field of network communications. In particular, the invention relates to a method for using multiple threads to process incoming network data.
2. Description of Related Art
Networking products such as routers require high speed components for packet data movement, i.e., collecting packet data from incoming network device ports and queuing the packet data for transfer to appropriate forwarding device ports. They also require high-speed special controllers for processing the packet data, that is, parsing the data and making forwarding decisions. Because the implementation of these high-speed functions usually involves the development of ASIC or custom devices, such networking products are of limited flexibility. For example, each controller is assigned to service network packets from one or more given ports on a permanent basis.
A method of using multiple receive threads to receive data in a round robin scheme is disclosed. First, one embodiment of the hardware that enables the multiple thread system is described. Then the method of employing the multiple threads in a round robin fashion is described.
Referring to
The hardware-based multi-threaded processor 12 also includes a processor 23 that assists in loading microcode control for other resources of the hardware-based multi-threaded processor 12 and performs other general purpose computer type functions such as handling protocols, exceptions, extra support for packet processing where the microengines pass the packets off for more detailed processing. In one embodiment, the processor 23 is a StrongARM (ARM is a trademark of ARM Limited, United Kingdom) core based architecture. The processor (or core) 23 has an operating system through which the processor 23 can call functions to operate on the microengines 22a-22f. The processor 23 can use any supported operating system, preferably real-time operating system. For the core processor implemented as a StrongARM architecture, operating systems such as MicrosoftNT real-time, VXWorks and :CUS, a freeware operating system available over the Internet, can be used.
The six microengines 22a-22f each operate with shared resources including the memory system 18, a PCI bus interface 24 and an I/O bus interface 28. The PCI bus interface provides an interface to the PCI bus 14. The I/O bus interface 28 is responsible for controlling and interfacing the processor 12 to the I/O bus 16. The memory system 18 includes a Synchronous Dynamic Random Access Memory (SDRAM) 18a, which is accessed via an SDRAM controller 26a, a Static Random Access Memory (SRAM) 18b, which is accessed using an SRAM controller 26b, and a nonvolatile memory (shown as a FlashROM) 18c that is used for boot operations. The SDRAM 16a and SDRAM controller 26a are typically used for processing large volumes of data, e.g., processing of payloads from network packets. The SRAM 18b and SRAM controller 26b are used in a networking implementation for low latency, fast access tasks, e.g., accessing look-up tables, memory for the processor 23, and so forth. The microengines 22a-22f can execute memory reference instructions to either the SDRAM controller 26a or the SRAM controller 18b.
The hardware-based multi-threaded processor 12 interfaces to network devices such as a media access controller (“MAC”) device, including a “slow” device 30 (e.g., 10/100BaseT Ethernet MAC) and/or a “fast” device 31, such as Gigabit Ethernet MAC, ATM device or the like, over the I/O Bus 16. In the embodiment shown, the slow device 30 is an 10/100 BaseT Octal MAC device and thus includes 8 slow ports 32a-32h, and the fast device is a Dual Gigabit MAC device having two fast ports 33a, 33b. Each of the network devices attached to the I/O Bus 16 can include a plurality of ports to be serviced by the processor 12. Other devices, such as a host computer (not shown), that may be coupled to the PCI bus 14 are also serviced by the processor 12. In general, as a network processor, the processor 12 can interface to any type of communication device or interface that receives/sends large amounts of data. The processor 12 functioning as a network processor could receive units of packet data from the devices 30, 31 and process those units of packet data in a parallel manner, as will be described. The unit of packet data could include an entire network packet (e.g., Ethernet packet) or a portion of such a packet.
Each of the functional units of the processor 12 are coupled to one or more internal buses. The internal buses include an internal core bus 34 (labeled “AMBA”) for coupling the processor 23 to the memory controllers 26a, 26b and to an AMBA translator 36. The processor 12 also includes a private bus 38 that couples the microengines 22a-22f to the SRAM controller 26b, AMBA translator 36 and the Fbus interface 28. A memory bus 40 couples the memory controllers 26a, 26b to the bus interfaces 24, 28 and the memory system 18.
Referring to
In addition to event signals that are local to an executing thread, the microengine employs signaling states that are global. With signaling states, an executing thread can broadcast a signal state to all microengines 22. Any and all threads in the microengines can branch on these signaling states. These signaling states can be used to determine availability of a resource or whether a resource is due for servicing.
The context event logic 74 has arbitration for the four threads. In one embodiment, the arbitration is a round robin mechanism. However, other arbitration techniques, such as priority queuing or weighted fair queuing, could be used. The microengine 22a also includes an execution box (EBOX) data path 76 that includes an arithmetic logic unit (ALU) 76a and a general purpose register (GPR) set 76b. The ALU 76a performs arithmetic and logical functions as well as shift functions.
The microengine 22a further includes a write transfer register file 78 and a read transfer register file 80. The write transfer register file 78 stores data to be written to a resource. The read transfer register file 80 is for storing return data from a resource. Subsequent to or concurrent with the data arrival, an event signal from the respective shared resource, e.g., memory controllers 26a, 26b, or core 23, will be provided to the context event arbiter 74, which in turn alerts the thread that the data is available or has been sent. Both transfer register files 78, 80 are connected to the EBOX 76 through a data path. In the described implementation, each of the register files includes 64 registers.
The functionality of the microengine threads is determined by microcode loaded (via the core processor) for a particular user's application into each microengine's control store 70. Referring to
The receive scheduler thread 92 assigns packets to receive processing threads 96. In a packet forwarding application for a bridge/router, for example, the receive processing thread parses packet headers and performs lookups based in the packet header information. Once the receive processing thread or threads 96 has processed the packet, it either sends the packet as an exception to be further processed by the core 23 (e.g., the forwarding information cannot be located in lookup and the core processor must learn it), or stores the packet in the SDRAM and queues the packet in a transmit queue by placing a packet link descriptor for it in a transmit queue associated with the transmit (forwarding port) indicated by the header/lookup. The transmit queue is stored in the SRAM. The transmit arbiter thread 100 prioritizes the transmit queues and the transmit scheduler thread 94 assigns packets to transmit processing threads that send the packet out onto the forwarding port indicated by the header/lookup information during the receive processing.
The receive processing threads 96 may be dedicated to servicing particular ports or may be assigned to ports dynamically by the receive scheduler thread 92. For certain system configurations, a dedicated assignment may be desirable. For example, if the number of ports is equal to the number of receive processing threads 96, then it may be quite practical as well as efficient to assign the receive processing threads to ports in a one-to-one, dedicated assignment. In other system configurations, a dynamic assignment may provide a more efficient use of system resources.
The receive scheduler thread 92 maintains scheduling information 104 in the GPRs 76b of the microengine within which it executes. The scheduling information 104 includes thread capabilities information 106, port-to-thread assignments (list) 108 and “thread busy” tracking information 110. At minimum, the thread capabilities information informs the receive scheduler thread as to the type of tasks for which the other threads are configured, e.g., which threads serve as receive processing threads. Additionally, it may inform the receive scheduler of other capabilities that may be appropriate to the servicing of a particular port. For instance, a receive processing thread may be configured to support a certain protocol, or a particular port or ports. A current list of the ports to which active receive processing threads have been assigned by the receive scheduler thread is maintained in the thread-to-port assignments list 108. The thread busy mask register 110 indicates which threads are actively servicing a port. The receive scheduler uses all of this scheduling information in selecting threads to be assigned to ports that require service for available packet data, as will be described in further detail below.
Referring to
The processors 23 and 22 issue commands to the push/pull engine interface 122 when accessing one of the resources 120. The push/pull engine interface 122 places the commands into queues (not shown), arbitrates which commands to service, and moves data between the resources 120, the core 23 and the microengines 22. In addition to servicing requests from the core 23 and microengines 22, the push/pull engines 122 also service requests from the ready bus 128 to transfer control information to a register in the microengine read transfer registers 80.
When a thread issues a request to a resource 120, a command is driven onto an internal command bus 150 and placed in queues within the push/pull engine interface 122. Receive/read-related instructions (such as instructions for reading the CSRs) are written to a “push” command queue.
The CSRs 138 include the following types of registers: Fbus receive and transmit registers; Fbus and ready bus configuration registers; ready bus control registers; hash unit configuration registers; interrupt registers; and several miscellaneous registers, including a thread status registers. Those of the registers which pertain to the receive process will be described in further detail.
The interrupt/signal registers include an INTER_THD_SIG register for inter-thread signaling. Any thread within the microengines 22 or the core 23 can write a thread number to this register to signal an inter-thread event.
Further details of the Fbus controller 130 and the ready bus controller 126 are shown in
Some of the relevant CSRsu used to program and control the ready bus 128 and Fbus 132 for receive processes are shown in
Referring to
Although not depicted in detail, other bus registers include the following: a RDYBUS_TEMPLATE_CTL register 178 (
Referring to
When the ready bus sequencer is programmed with an appropriate instruction directing it to interrogate MAC receive ready flags, it reads the receive ready flags from the MAC device or devices specified in the instruction and places the flags into RCV_RDY_HI register 210a and a RCV_RDY_LO register 210b, collectively, RCV_RDY registers 210. Each bit in these registers corresponds to a different device port on the I/O bus.
Also, and as shown in
The RCV_RDY_CNT register 216 is one of several used by the receive scheduler to determine how to issue a receive request. It also indicates whether a flow control request is issued.
Referring to
There are two techniques for reading the ready bus registers: “autopush” and polling. The autopush instruction may be executed by the ready bus sequencer 160 during a receive process (rxautopush) or a transmit process (txautopush). Polling requires that a microengine thread periodically issue read references to the I/O bus interface 28.
The rxautopush operation performs several functions. It increments the receive ready count in the RCV_RDY_CNT register 216. If enabled by the RCV_RDY_CTL register 174, it automatically writes the RCV_RDY_CNT 216, the RCV_RDY_LO and RCV_RDY_HI registers 210b, 210a to the receive scheduler read transfer registers and signals to the receive scheduler thread 92 (via a context event signal) when the rxautopush operation is complete.
The ready bus sequencer 160 polls the MAC FIFO status flags periodically and asynchronously to other events occurring in the processor 12. Ideally, the rate at which the MAC FIFO ready flags are polled is greater than the maximum rate at which the data is arriving at the MAC ports. Thus, it is necessary for the receive scheduler thread 92 to determine whether the MAC FIFO ready flags read by the ready bus sequencer 160 are new, or whether they have been read already. The rxautopush instruction increments the receive ready count in the RCV_RDY_CNT register 216 each time the instruction executes. The RCV_RDY_CNT register 216 can be used by the receive scheduler thread 92 to determine whether the state of specific flags have to be evaluated or whether they can be ignored because receive requests have been issued and the port is currently being serviced. For example, if the FIFO threshold for a Gigabit Ethernet port is set so that the receive ready flags are asserted when 64 bytes of data are in the MAC receive FIFO 206, then the state of the flags does not change until the next 64 bytes arrive 5120 ns later. If the ready bus sequencer 160 is programmed to collect the flags four times each 5120 ns period, the next three sets of ready flags that are to be collected by the ready bus sequence 160 can be ignored.
When the receive ready count is used to monitor the freshness of the receive ready flags, there is a possibility that the receive ready flags will be ignored when they are providing new status. For a more accurate determination of ready flag freshness, the receive request count may be used. Each time a receive request is completed and the receive control information is pushed onto the RCV_CNTL register 232, the RSM 166 increments the receive request count. The count is recorded in the RCV_RDY_CNT register the first time the ready bus sequencer executes an rxrdy instruction for each program loop. The receive scheduler thread 92 can use this count to track how many requests the receive state machine has completed. As the receive scheduler thread issues commands, it can maintain a list of the receive requests it submits and the ports associated with each such request.
Referring to
Referring to
Still referring to
The RCV_REQ register 230 is used to initiate a receive transfer on the Fbus and is mapped to a two-entry FIFO that is written by the microengines. The I/O bus interface provides signals (not shown) to the receive scheduler thread indicating that the RCV_REQ FIFO 236 has room available for another receive request and that the last issued receive request has been stored in the RCV_REQ register 230.
Referring to
The RSM 166 reads the RCV_REQ register entry 231 to determine how it should receive data from the Fbus 132, that is, how the signaling should be performed on the Fbus, where the data should be placed in the RFIFO and which microengine thread should be signaled once the data is received. The RSM 166 looks for a valid receive request in the RCV_REQ FIFO 230. It selects the MAC device identified in the RM field and selects the specified port within the MAC by asserting the appropriate control signals. It then begins receiving data from the MAC device on the Fbus data lines. The receive state machine always attempts to read either eight or nine quadwords of data from the MAC device on the Fbus as specified in the receive request. If the MAC device asserts the EOP signal, the RSM 166 terminates the receive early (before eight or nine accesses are made). The RSM 166 calculates the total bytes received for each receive request and reports the value in the REC_CNTL register 232. If EOP is received, the RSM 166 determines the number of valid bytes in the last received data cycle.
The RCV_CNTL register 232 is mapped to a four-entry FIFO (referred to herein as RCV_CNTL_FIFO 232) that is written by the receive state machine and read by the microengine thread. The I/O bus interface 28 signals the assigned thread when a valid entry reaches the top of the RCV_CNTL FIFO. When a microengine thread reads the RCV_CNTL register, the data is popped off the FIFO. If the SIGRS field 230i is set in the RCV_REQ register 230, the receive scheduler thread 92 specified in the RCV_CNTL register 232 is signaled in addition to the thread specified in TID field 230k. In this case, the data in the RCV_CNTL register 232 is read twice before the receive request data is retired from the RCV_CTL FIFO 232 and the next thread is signaled. The receive state machine writes to the RCV_CTL register 232 as long as the FIFO is not full. If the RCV_CTL FIFO 232 is full, the receive state machine stalls and stops accepting any more receive requests.
Referring to
The THREAD_DONE CSRs 240 support a two-bit message for each microengine thread. The assigned receive thread may write a two-bit message to this register to indicate that it has completed its task. Each time a message is written to the THREAD_DONE register, the current message is logically ORed with the new message. The bit values in the THREAD_DONE registers are cleared by writing a “1”, so the scheduler may clear the messages by writing the data read back to the THREAD_DONE register. The definition of the 2-bit status field is determined in software. An example of four message types is illustrated in TABLE 1 below.
The assigned receive processing threads write their status to the THREAD_DONE register whenever the status changes. For example, a thread may immediately write 00 to the THREAD_DONE register after the receive state machine signals the assigned thread. When the receive scheduler thread reads the THREAD_DONE register, it can look at the returned value to determine the status of each thread and then update its thread/port assignment list.
The microengine supports a fast_wr instruction that improves performance when writing to a subset of CSR registers. The fast_wr instruction does not use the push or pull engines. Rather, it uses logic that services the instruction as soon as the write request is issued to the FBI CSR. The instruction thus eliminates the need for the pull engine to read data from a microengine transfer register when it processes the command. The meaning of the 10-bit immediate data for some of the CSRs is shown below.
It will be appreciated that the receive process as described herein assumes that no packet exemptions occurred, that is, that the threads are able to handle the packet processing without assistance from the core processor. Further, the receive process as described also assumes the availability of FIFO space. It will be appreciated that the various state machines must determine if there is room available in a FIFO, e.g., the RFIFO, prior to writing new entries to that FIFO. If a particular FIFO is full, the state machine will wait until the appropriate number of entries has been retired from that FIFO.
Round-Robin Receive of Network Data
In a multi-thread round robin scheme, there is no receive scheduler. Instead, a group of receive threads run in sequence, in a round-robin fashion, per given port or per group of ports. Each receive thread of the group passes off execution to a predetermined next receive thread. Execution continues to successively loop through all the receive threads of the group while maintaining the original ordering of the receive threads.
Referring to
The receive threads save status information to the next receive thread via a mailbox stored at predetermined common fast memory or register locations, as will be described. Then the currently-executing receive thread signals the next receive thread to begin processing network data. The signal interlock insures that the threads execute in order (the state restores occur in order), while at the same time executing in parallel (data analysis is concurrent).
The first receive thread, upon waking up, reads a control register (box 420) to obtain information about the bus transaction, i.e., which port, where in the receive FIFO the data is stored, size of data, type of port, message and other information. The receive thread then waits to be signaled (by the previous receive thread) (box 421). When the receive thread receives the signal (box 422), the receive thread reads status information from its mailbox. As shown in
The receive thread modifies the status information and saves state (status information) to the next receive thread's mailbox (box 423). In one embodiment, the next receive thread's mailbox is either in a common shared register or in fast memory, determined as follows: If the currently-executing receive thread and the next receive thread are in the same microengine, then the next receive thread's mailbox is in a common shared register. If the currently-executing receive thread and the next receive thread are in different microengines, then the next receive thread's mailbox is in common fast memory. As shown in
The receive thread signals the next receive thread to begin processing its data (box 425). In one embodiment, the next receive thread is signaled with the instruction fast_wr [n, inter_thd_sig], where n is the thread_id and inter_thd_sig identifies an interthread signal. This is a relatively fast operation because the data (which thread to signal) is contained in the command. The command is moved to the internal command interface, which then writes the INTER_THD_SIG register to assert the signal at the appropriate microengine/thread. The current receive thread is now free to continue to analyze and move data (box 426).
The next receive thread (box 431-456) behaves in a similar fashion to that just described with respect to box 401-426. However, as shown in
In one embodiment, there is a 5 cycle latency between writing the status information by one thread and reading the status information by the next receive thread when the two receive threads are on the same microengine, and a 30 cycle latency when the receive threads cross microengine boundaries. This gives rise to an average latency of approximately 12 cycles (assuming a 3 intra-microengine threads-to-1 inter-microengine thread ratio), which is quicker than can be done using a receive scheduler.
In the receive control register, there may be a cancel message. If there is no cancel, then the receive thread increments the packet address by the buffer size of the data (box 503), and saves the updated address to the next receive thread's designated mailbox (box 504). After saving the updated address, the thread copies the data from RFIFO to DRAM (box 505/506).
If there is a cancel, then the receive thread does not increment the packet address, but merely saves the packet address unmodified in the next receive thread's mailbox. In this case, no data is copied to DRAM.
In one embodiment, the receive thread then writes a thread done register to indicate it is available for re-assignment. The sequence repeats for subsequent receive threads, with the subsequent receive threads making requests to the bus interface, restoring/saving state, signaling the next thread, and processing data.
In one embodiment, application software for programming the receive threads to operate in the network processor as described can be provided as instructions stored on floppy disk, CD-ROM, or other storage media. Alternatively, the application software can be downloaded via the Internet. The application software is then installed to a storage medium on the host system, such as a hard disk, random access memory, or non-volatile memory.
Thus, a method of processing network data in a network processor includes using multiple receive threads executing in a round robin fashion. This scheme allows the network processor to receive data the full line rate. However, the specific arrangements and methods described herein are merely illustrative of the principles of this invention. Numerous modifications in form and detail may be made without departing from the scope of the described invention. Although this invention has been shown in relation to a particular embodiment, it should not be considered so limited. Rather, the described invention is limited only by the scope of the appended claims.
This application is a continuation-in-part of U.S. patent application Ser. No. 09/475,614 filed Dec. 30, 1999, now copending application.
Number | Name | Date | Kind |
---|---|---|---|
3373408 | Ling | Mar 1968 | A |
3478322 | Evans | Nov 1969 | A |
3623001 | Kleist et al. | Nov 1971 | A |
3736566 | Anderson et al. | May 1973 | A |
3792441 | Wymore et al. | Feb 1974 | A |
3889243 | Drimak | Jun 1975 | A |
3940745 | Sajeva | Feb 1976 | A |
4016548 | Law et al. | Apr 1977 | A |
4032899 | Jenny et al. | Jun 1977 | A |
4075691 | Davis et al. | Feb 1978 | A |
4130890 | Adam | Dec 1978 | A |
4400770 | Chan et al. | Aug 1983 | A |
4514807 | Nogi | Apr 1985 | A |
4523272 | Fukunaga et al. | Jun 1985 | A |
4658351 | Teng | Apr 1987 | A |
4709347 | Kirk | Nov 1987 | A |
4745544 | Renner et al. | May 1988 | A |
4788640 | Hansen | Nov 1988 | A |
4831358 | Ferrio et al. | May 1989 | A |
4858108 | Ogawa et al. | Aug 1989 | A |
4866664 | Burkhardt, Jr. et al. | Sep 1989 | A |
4890218 | Bram | Dec 1989 | A |
4890222 | Kirk | Dec 1989 | A |
4991112 | Callemyn | Feb 1991 | A |
5115507 | Callemyn | May 1992 | A |
5140685 | Sipple et al. | Aug 1992 | A |
5142683 | Burkhardt, Jr. et al. | Aug 1992 | A |
5155831 | Emma et al. | Oct 1992 | A |
5155854 | Flynn et al. | Oct 1992 | A |
5168555 | Byers et al. | Dec 1992 | A |
5173897 | Schrodi et al. | Dec 1992 | A |
5251205 | Callon et al. | Oct 1993 | A |
5255239 | Taborn et al. | Oct 1993 | A |
5263169 | Genusov et al. | Nov 1993 | A |
5313454 | Bustini et al. | May 1994 | A |
5347648 | Stamm et al. | Sep 1994 | A |
5367678 | Lee et al. | Nov 1994 | A |
5379295 | Yonehara | Jan 1995 | A |
5379432 | Orton et al. | Jan 1995 | A |
5390329 | Gaertner et al. | Feb 1995 | A |
5392391 | Caulk, Jr. et al. | Feb 1995 | A |
5392411 | Ozaki | Feb 1995 | A |
5392412 | McKenna | Feb 1995 | A |
5404464 | Bennett | Apr 1995 | A |
5404469 | Chung et al. | Apr 1995 | A |
5404482 | Stamm et al. | Apr 1995 | A |
5432918 | Stamm | Jul 1995 | A |
5448702 | Garcia, Jr. et al. | Sep 1995 | A |
5450351 | Heddes | Sep 1995 | A |
5452437 | Richey et al. | Sep 1995 | A |
5452452 | Gaetner et al. | Sep 1995 | A |
5459842 | Begun et al. | Oct 1995 | A |
5459843 | Davis et al. | Oct 1995 | A |
5463625 | Yasrebi | Oct 1995 | A |
5467452 | Blum et al. | Nov 1995 | A |
5475856 | Kogge | Dec 1995 | A |
5485455 | Dobbins et al. | Jan 1996 | A |
5515296 | Agarwal | May 1996 | A |
5517648 | Bertone et al. | May 1996 | A |
5539737 | Lo et al. | Jul 1996 | A |
5542070 | LeBlanc et al. | Jul 1996 | A |
5542088 | Jennings, Jr. et al. | Jul 1996 | A |
5544236 | Andruska et al. | Aug 1996 | A |
5550816 | Hardwick et al. | Aug 1996 | A |
5557766 | Takiguchi et al. | Sep 1996 | A |
5568476 | Sherer et al. | Oct 1996 | A |
5568617 | Kametani | Oct 1996 | A |
5574922 | James | Nov 1996 | A |
5581729 | Nishtala et al. | Dec 1996 | A |
5592622 | Isfeld et al. | Jan 1997 | A |
5613071 | Rankin et al. | Mar 1997 | A |
5613136 | Casavant et al. | Mar 1997 | A |
5617327 | Duncan | Apr 1997 | A |
5623489 | Cotton et al. | Apr 1997 | A |
5627829 | Gleeson et al. | May 1997 | A |
5630074 | Beltran | May 1997 | A |
5630130 | Perotto et al. | May 1997 | A |
5633865 | Short | May 1997 | A |
5644623 | Gulledge | Jul 1997 | A |
5649110 | Ben-Nun et al. | Jul 1997 | A |
5649157 | Williams | Jul 1997 | A |
5651002 | Van Seters et al. | Jul 1997 | A |
5659687 | Kim et al. | Aug 1997 | A |
5680641 | Sidman | Oct 1997 | A |
5689566 | Nguyen | Nov 1997 | A |
5692126 | Templeton et al. | Nov 1997 | A |
5699537 | Sharangpani et al. | Dec 1997 | A |
5701434 | Nakagawa | Dec 1997 | A |
5717898 | Kagan et al. | Feb 1998 | A |
5721870 | Matsumoto | Feb 1998 | A |
5724574 | Stratigos et al. | Mar 1998 | A |
5740402 | Bratt et al. | Apr 1998 | A |
5742587 | Zornig et al. | Apr 1998 | A |
5742782 | Ito et al. | Apr 1998 | A |
5742822 | Motomura | Apr 1998 | A |
5745913 | Pattin et al. | Apr 1998 | A |
5751987 | Mahant-Shetti et al. | May 1998 | A |
5754764 | Davis et al. | May 1998 | A |
5761507 | Govett | Jun 1998 | A |
5761522 | Hisanaga et al. | Jun 1998 | A |
5764915 | Heimsoth et al. | Jun 1998 | A |
5768528 | Stumm | Jun 1998 | A |
5781551 | Born | Jul 1998 | A |
5781774 | Krick | Jul 1998 | A |
5784649 | Begur et al. | Jul 1998 | A |
5784712 | Byers et al. | Jul 1998 | A |
5796413 | Shipp et al. | Aug 1998 | A |
5797043 | Lewis et al. | Aug 1998 | A |
5805816 | Picazo, Jr. et al. | Sep 1998 | A |
5809235 | Sharma et al. | Sep 1998 | A |
5809237 | Watts et al. | Sep 1998 | A |
5809530 | Samra et al. | Sep 1998 | A |
5812868 | Moyer et al. | Sep 1998 | A |
5828746 | Ardon | Oct 1998 | A |
5828863 | Barrett et al. | Oct 1998 | A |
5828881 | Wang | Oct 1998 | A |
5828901 | O'Toole et al. | Oct 1998 | A |
5832215 | Kato et al. | Nov 1998 | A |
5835755 | Stellwagen, Jr. | Nov 1998 | A |
5838988 | Panwar et al. | Nov 1998 | A |
5850399 | Ganmukhi et al. | Dec 1998 | A |
5850530 | Chen et al. | Dec 1998 | A |
5854922 | Gravenstein et al. | Dec 1998 | A |
5857188 | Douglas | Jan 1999 | A |
5860138 | Engebretsen et al. | Jan 1999 | A |
5860158 | Pai et al. | Jan 1999 | A |
5886992 | Raatikainen et al. | Mar 1999 | A |
5887134 | Ebrahim | Mar 1999 | A |
5890208 | Kwon | Mar 1999 | A |
5892979 | Shiraki et al. | Apr 1999 | A |
5898686 | Virgile | Apr 1999 | A |
5898701 | Johnson | Apr 1999 | A |
5905876 | Pawlowski et al. | May 1999 | A |
5905889 | Wilhelm, Jr. | May 1999 | A |
5909686 | Muller et al. | Jun 1999 | A |
5915123 | Mirsky et al. | Jun 1999 | A |
5918235 | Kirshenbaum et al. | Jun 1999 | A |
5933627 | Parady | Aug 1999 | A |
5937187 | Kosche et al. | Aug 1999 | A |
5938736 | Muller et al. | Aug 1999 | A |
5940612 | Brady et al. | Aug 1999 | A |
5940866 | Chisholm et al. | Aug 1999 | A |
5946487 | Dangelo | Aug 1999 | A |
5948081 | Foster | Sep 1999 | A |
5953336 | Moore et al. | Sep 1999 | A |
5958031 | Kim | Sep 1999 | A |
5961628 | Nguyen et al. | Oct 1999 | A |
5968169 | Pickett | Oct 1999 | A |
5970013 | Fischer et al. | Oct 1999 | A |
5974518 | Nogradi | Oct 1999 | A |
5978838 | Mohamed et al. | Nov 1999 | A |
5983274 | Hyder et al. | Nov 1999 | A |
5995513 | Harrand et al. | Nov 1999 | A |
6012151 | Mano | Jan 2000 | A |
6014729 | Lannan et al. | Jan 2000 | A |
6023742 | Ebeling et al. | Feb 2000 | A |
6032190 | Bremer et al. | Feb 2000 | A |
6032218 | Lewin et al. | Feb 2000 | A |
6047002 | Hartmann et al. | Apr 2000 | A |
6049867 | Eickemeyer et al. | Apr 2000 | A |
6058168 | Braband | May 2000 | A |
6061710 | Eickemeyer et al. | May 2000 | A |
6067300 | Baumert et al. | May 2000 | A |
6067585 | Hoang | May 2000 | A |
6070231 | Ottinger | May 2000 | A |
6072781 | Feeney et al. | Jun 2000 | A |
6073215 | Snyder | Jun 2000 | A |
6079008 | Clery, III | Jun 2000 | A |
6085215 | Ramakrishnan et al. | Jul 2000 | A |
6085248 | Sambamurthy et al. | Jul 2000 | A |
6085294 | Van Doren et al. | Jul 2000 | A |
6092127 | Tausheck | Jul 2000 | A |
6092158 | Harriman et al. | Jul 2000 | A |
6104700 | Haddock et al. | Aug 2000 | A |
6111886 | Stewart | Aug 2000 | A |
6112016 | MacWilliams et al. | Aug 2000 | A |
6122251 | Shinohara | Sep 2000 | A |
6128669 | Moriarty et al. | Oct 2000 | A |
6134665 | Klein et al. | Oct 2000 | A |
6141677 | Hanif et al. | Oct 2000 | A |
6141689 | Yasrebi | Oct 2000 | A |
6141765 | Sherman | Oct 2000 | A |
6144669 | Williams et al. | Nov 2000 | A |
6145054 | Mehrotra et al. | Nov 2000 | A |
6157955 | Narad et al. | Dec 2000 | A |
6160562 | Chin et al. | Dec 2000 | A |
6170051 | Dowling | Jan 2001 | B1 |
6175927 | Cromer et al. | Jan 2001 | B1 |
6182177 | Harriman | Jan 2001 | B1 |
6195676 | Spix et al. | Feb 2001 | B1 |
6199133 | Schnell | Mar 2001 | B1 |
6201807 | Prasanna | Mar 2001 | B1 |
6212542 | Kahle et al. | Apr 2001 | B1 |
6212544 | Borkenhagen et al. | Apr 2001 | B1 |
6212604 | Tremblay | Apr 2001 | B1 |
6212611 | Nizar et al. | Apr 2001 | B1 |
6216220 | Hwang | Apr 2001 | B1 |
6223207 | Lucovsky et al. | Apr 2001 | B1 |
6223238 | Meyer et al. | Apr 2001 | B1 |
6223243 | Ueda et al. | Apr 2001 | B1 |
6223274 | Catthoor et al. | Apr 2001 | B1 |
6223279 | Nishimura et al. | Apr 2001 | B1 |
6247025 | Bacon | Jun 2001 | B1 |
6256713 | Audityan et al. | Jul 2001 | B1 |
6269391 | Gillespie | Jul 2001 | B1 |
6272109 | Pei et al. | Aug 2001 | B1 |
6272520 | Sharangpani et al. | Aug 2001 | B1 |
6272616 | Fernando et al. | Aug 2001 | B1 |
6275505 | O'Loughlin et al. | Aug 2001 | B1 |
6279113 | Vaidya | Aug 2001 | B1 |
6282169 | Kiremidjian | Aug 2001 | B1 |
6286083 | Chin et al. | Sep 2001 | B1 |
6289011 | Seo et al. | Sep 2001 | B1 |
6295600 | Parady | Sep 2001 | B1 |
6298370 | Tang et al. | Oct 2001 | B1 |
6307789 | Wolrich et al. | Oct 2001 | B1 |
6311261 | Chamdani et al. | Oct 2001 | B1 |
6320861 | Adam et al. | Nov 2001 | B1 |
6324624 | Wolrich et al. | Nov 2001 | B1 |
6335932 | Kadambi et al. | Jan 2002 | B2 |
6338078 | Chang et al. | Jan 2002 | B1 |
6345334 | Nakagawa et al. | Feb 2002 | B1 |
6347344 | Baker et al. | Feb 2002 | B1 |
6349331 | Andra et al. | Feb 2002 | B1 |
6356962 | Kasper | Mar 2002 | B1 |
6359911 | Movshovich et al. | Mar 2002 | B1 |
6360262 | Guenthner et al. | Mar 2002 | B1 |
6360277 | Ruckley et al. | Mar 2002 | B1 |
6366998 | Mohamed | Apr 2002 | B1 |
6373848 | Allison et al. | Apr 2002 | B1 |
6377998 | Noll et al. | Apr 2002 | B2 |
6389031 | Chao et al. | May 2002 | B1 |
6389449 | Nemirovsky et al. | May 2002 | B1 |
6393026 | Irwin | May 2002 | B1 |
6393483 | Latif et al. | May 2002 | B1 |
6404737 | Novick et al. | Jun 2002 | B1 |
6415338 | Habot | Jul 2002 | B1 |
6418488 | Chilton et al. | Jul 2002 | B1 |
6424657 | Voit et al. | Jul 2002 | B1 |
6424659 | Viswanadham et al. | Jul 2002 | B2 |
6426940 | Seo et al. | Jul 2002 | B1 |
6426943 | Spinney et al. | Jul 2002 | B1 |
6427196 | Adiletta et al. | Jul 2002 | B1 |
6430626 | Witkowski et al. | Aug 2002 | B1 |
6434145 | Opsasnick et al. | Aug 2002 | B1 |
6438132 | Vincent et al. | Aug 2002 | B1 |
6438134 | Chow et al. | Aug 2002 | B1 |
6448812 | Bacigalupo | Sep 2002 | B1 |
6453404 | Bereznyi et al. | Sep 2002 | B1 |
6457015 | Eastham | Sep 2002 | B1 |
6463035 | Moore | Oct 2002 | B1 |
6463072 | Wolrich et al. | Oct 2002 | B1 |
6463480 | Kikuchi et al. | Oct 2002 | B2 |
6463527 | Vishkin | Oct 2002 | B1 |
6466898 | Chan | Oct 2002 | B1 |
6477562 | Nemirovsky et al. | Nov 2002 | B2 |
6484224 | Robins et al. | Nov 2002 | B1 |
6501731 | Chong et al. | Dec 2002 | B1 |
6507862 | Joy et al. | Jan 2003 | B1 |
6522188 | Poole | Feb 2003 | B1 |
6526451 | Kasper | Feb 2003 | B2 |
6526452 | Petersen et al. | Feb 2003 | B1 |
6529983 | Marshall et al. | Mar 2003 | B1 |
6532509 | Wolrich et al. | Mar 2003 | B1 |
6535878 | Guedalia et al. | Mar 2003 | B1 |
6552826 | Adler et al. | Apr 2003 | B2 |
6553406 | Berger et al. | Apr 2003 | B1 |
6560667 | Wolrich et al. | May 2003 | B1 |
6570850 | Gutierrez et al. | May 2003 | B1 |
6577542 | Wolrich et al. | Jun 2003 | B2 |
6584522 | Wolrich et al. | Jun 2003 | B1 |
6587906 | Wolrich et al. | Jul 2003 | B2 |
6604125 | Belkin | Aug 2003 | B1 |
6606704 | Adiletta et al. | Aug 2003 | B1 |
6625654 | Wolrich et al. | Sep 2003 | B1 |
6628668 | Hutzli et al. | Sep 2003 | B1 |
6629147 | Grow | Sep 2003 | B1 |
6629236 | Aipperspach et al. | Sep 2003 | B1 |
6631422 | Althaus et al. | Oct 2003 | B1 |
6631430 | Wolrich et al. | Oct 2003 | B1 |
6631462 | Wolrich et al. | Oct 2003 | B1 |
6657963 | Paquette et al. | Dec 2003 | B1 |
6658551 | Berenbaum et al. | Dec 2003 | B1 |
6661774 | Lauffenburger et al. | Dec 2003 | B1 |
6661794 | Wolrich et al. | Dec 2003 | B1 |
6665699 | Hunter et al. | Dec 2003 | B1 |
6665755 | Modelski et al. | Dec 2003 | B2 |
6667920 | Wolrich et al. | Dec 2003 | B2 |
6668317 | Bernstein et al. | Dec 2003 | B1 |
6671827 | Guilford et al. | Dec 2003 | B2 |
6675190 | Schabernack et al. | Jan 2004 | B1 |
6675192 | Emer et al. | Jan 2004 | B2 |
6678746 | Russell et al. | Jan 2004 | B1 |
6680933 | Cheesman et al. | Jan 2004 | B1 |
6681300 | Wolrich et al. | Jan 2004 | B2 |
6684326 | Cromer et al. | Jan 2004 | B1 |
6694380 | Wolrich et al. | Feb 2004 | B1 |
6697379 | Jacquet et al. | Feb 2004 | B1 |
6721325 | Duckering et al. | Apr 2004 | B1 |
6724767 | Chong et al. | Apr 2004 | B1 |
6728845 | Adiletta | Apr 2004 | B2 |
6732187 | Lougheed et al. | May 2004 | B1 |
6754211 | Brown | Jun 2004 | B1 |
6754222 | Joung et al. | Jun 2004 | B1 |
6768717 | Reynolds et al. | Jul 2004 | B1 |
6775284 | Calvignac et al. | Aug 2004 | B1 |
6792488 | Wolrich et al. | Sep 2004 | B2 |
6798744 | Loewen et al. | Sep 2004 | B1 |
6826615 | Barrall et al. | Nov 2004 | B2 |
6834053 | Stacey et al. | Dec 2004 | B1 |
6850521 | Kadambi et al. | Feb 2005 | B1 |
6856622 | Calamvokis et al. | Feb 2005 | B1 |
6873618 | Weaver | Mar 2005 | B1 |
6876561 | Wolrich et al. | Apr 2005 | B2 |
6895457 | Wolrich et al. | May 2005 | B2 |
6925637 | Thomas et al. | Aug 2005 | B2 |
6931641 | Davis et al. | Aug 2005 | B1 |
6934780 | Modelski et al. | Aug 2005 | B2 |
6934951 | Wilkinson et al. | Aug 2005 | B2 |
6938147 | Joy et al. | Aug 2005 | B1 |
6944850 | Hooper et al. | Sep 2005 | B2 |
6947425 | Hooper et al. | Sep 2005 | B1 |
6959002 | Wynne et al. | Oct 2005 | B2 |
6967963 | Houh et al. | Nov 2005 | B1 |
6976095 | Wolrich et al. | Dec 2005 | B1 |
6981077 | Modelski et al. | Dec 2005 | B2 |
6983350 | Wheeler et al. | Jan 2006 | B1 |
7006495 | Hooper | Feb 2006 | B2 |
7065569 | Teraslinna | Jun 2006 | B2 |
7069548 | Kushlis | Jun 2006 | B2 |
7096277 | Hooper | Aug 2006 | B2 |
7100102 | Hooper et al. | Aug 2006 | B2 |
7111072 | Matthews et al. | Sep 2006 | B1 |
7111296 | Wolrich et al. | Sep 2006 | B2 |
7124196 | Hooper | Oct 2006 | B2 |
7126952 | Hooper et al. | Oct 2006 | B2 |
7149786 | Bohringer et al. | Dec 2006 | B1 |
7181742 | Hooper | Feb 2007 | B2 |
7191321 | Bernstein et al. | Mar 2007 | B2 |
7206858 | Hooper et al. | Apr 2007 | B2 |
7248584 | Hooper | Jul 2007 | B2 |
7305500 | Adiletta et al. | Dec 2007 | B2 |
7328289 | Wolrich et al. | Feb 2008 | B2 |
7352769 | Hooper et al. | Apr 2008 | B2 |
20010023487 | Kawamoto | Sep 2001 | A1 |
20020027448 | Bacigalupo | Mar 2002 | A1 |
20020041520 | Wolrich et al. | Apr 2002 | A1 |
20020075878 | Lee et al. | Jun 2002 | A1 |
20020118692 | Oberman et al. | Aug 2002 | A1 |
20020150047 | Knight et al. | Oct 2002 | A1 |
20020181194 | Ho et al. | Dec 2002 | A1 |
20030043803 | Hooper | Mar 2003 | A1 |
20030067934 | Hooper et al. | Apr 2003 | A1 |
20030086434 | Kloth | May 2003 | A1 |
20030105901 | Wolrich et al. | Jun 2003 | A1 |
20030105917 | Ostler et al. | Jun 2003 | A1 |
20030110166 | Wolrich et al. | Jun 2003 | A1 |
20030115347 | Wolrich et al. | Jun 2003 | A1 |
20030115426 | Rosenbluth et al. | Jun 2003 | A1 |
20030131198 | Wolrich et al. | Jul 2003 | A1 |
20030140196 | Wolrich et al. | Jul 2003 | A1 |
20030145159 | Adiletta et al. | Jul 2003 | A1 |
20030147409 | Wolrich et al. | Aug 2003 | A1 |
20030161303 | Mehrvar et al. | Aug 2003 | A1 |
20030161337 | Weinman | Aug 2003 | A1 |
20030196012 | Wolrich et al. | Oct 2003 | A1 |
20030210574 | Wolrich et al. | Nov 2003 | A1 |
20030231635 | Kalkunte et al. | Dec 2003 | A1 |
20040039895 | Wolrich et al. | Feb 2004 | A1 |
20040052269 | Hooper et al. | Mar 2004 | A1 |
20040054880 | Bernstein et al. | Mar 2004 | A1 |
20040059828 | Hooper et al. | Mar 2004 | A1 |
20040071152 | Wolrich et al. | Apr 2004 | A1 |
20040073728 | Wolrich et al. | Apr 2004 | A1 |
20040073778 | Adiletta et al. | Apr 2004 | A1 |
20040085901 | Hooper et al. | May 2004 | A1 |
20040098496 | Wolrich et al. | May 2004 | A1 |
20040109369 | Wolrich et al. | Jun 2004 | A1 |
20040148382 | Narad et al. | Jul 2004 | A1 |
20040162933 | Adiletta et al. | Aug 2004 | A1 |
20040252686 | Hooper et al. | Dec 2004 | A1 |
20050033884 | Wolrich et al. | Feb 2005 | A1 |
20050149665 | Wolrich et al. | Jul 2005 | A1 |
20060007871 | Welin | Jan 2006 | A1 |
20060069882 | Wheeler et al. | Mar 2006 | A1 |
Number | Date | Country |
---|---|---|
0 379 709 | Aug 1990 | EP |
0 464 715 | Jan 1992 | EP |
0 633 678 | Jan 1995 | EP |
0 745 933 | Dec 1996 | EP |
0 773 648 | May 1997 | EP |
0 809 180 | Nov 1997 | EP |
0 959 602 | Nov 1999 | EP |
59-111533 | Jun 1984 | JP |
WO 9415287 | Jul 1994 | WO |
WO 9738372 | Oct 1997 | WO |
WO 9820647 | May 1998 | WO |
WO 0038376 | Jun 2000 | WO |
WO 0056024 | Sep 2000 | WO |
WO 0116718 | Mar 2001 | WO |
WO 0116769 | Mar 2001 | WO |
WO 0116770 | Mar 2001 | WO |
WO 0116782 | Mar 2001 | WO |
WO 0117179 | Mar 2001 | WO |
WO 0131856 | May 2001 | WO |
WO 0148596 | Jul 2001 | WO |
WO 0148606 | Jul 2001 | WO |
WO 0148619 | Jul 2001 | WO |
WO 0150247 | Jul 2001 | WO |
WO 0150679 | Jul 2001 | WO |
WO03030461 | Apr 2003 | WO |
Number | Date | Country | |
---|---|---|---|
Parent | 09475614 | Dec 1999 | US |
Child | 09710496 | US |