|Publication number||US7941585 B2|
|Application number||US 11/015,343|
|Publication date||May 10, 2011|
|Filing date||Dec 17, 2004|
|Priority date||Sep 10, 2004|
|Also published as||CN100533372C, CN101036117A, CN101036117B, CN101040256A, CN101053234A, CN101053234B, CN101069170A, CN101069170B, CN101128804A, CN101128804B, US9141548, US20060059286, US20060059310, US20060059316, US20140317353|
|Publication number||015343, 11015343, US 7941585 B2, US 7941585B2, US-B2-7941585, US7941585 B2, US7941585B2|
|Inventors||David H. Asher, David A. Carlson, Richard E. Kessler|
|Original Assignee||Cavium Networks, Inc.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (96), Non-Patent Citations (7), Referenced by (7), Classifications (30), Legal Events (5)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This application claims the benefit of U.S. Provisional Application No. 60/609,211, filed on Sep. 10, 2004. The entire teachings of the above application are incorporated herein by reference.
The use of a cache memory with a processor is well known in the computer art. A primary purpose of utilizing cache memory is to bring the data closer to the processor in order for the processor to operate on that data. It is generally understood that memory devices closer to the processor have faster data access times than memory devices farther away on the data path from the processor. However, there is a cost trade-off in utilizing faster memory devices. The faster the data access, the higher the cost to store a bit of data. Accordingly, a cache memory tends to be much smaller in storage capacity than main memory, but is faster in accessing the data.
A characteristic common to most Reduced Instruction Set Computer (RISC) architectures is the use of a load/store architecture. That is, memory can only be accessed by load and store instructions. All other operations are performed on data stored in processor registers (register file). This approach separates the accessing of memory from data manipulation operation, thereby allowing the complier to schedule loads to the processor registers to avoid pipeline stalls.
Typically, a RISC processor includes a simple instruction issue and register dependency logic that only allows one outstanding cache miss. A cache miss is a request to read from memory which cannot be satisfied from the cache, for which the main memory has been consulted. This logic reduces the area, cost, and power consumption of the processor. An outstanding cache miss means the cache memory can continue to be accessed by other instructions until a second miss occurs. That is, all further accesses to the cache memory are stalled until the first outstanding cache miss has been resolved.
Another characteristic common to most RISC architectures is the use of virtual memory (addresses) to access memory. The virtual memory addresses are translated (mapped) to physical (real) addresses for example, through a memory management unit. The purpose of virtual memory is to enlarge the address space, the set of addresses a processor can utilize.
The present invention provides a mechanism for dynamically partitioning an internal data cache in a processor to provide a scratchpad/local memory within the data cache. The scratchpad/local memory can be used to extend the processor's register set or provide addressable local memory.
An embodiment includes a processor having a main register file and a data cache. The data cache can be partitioned to include a local memory, the size of which can be dynamically changed on a cache block basis while the processor is executing instructions that use the main register file. The local memory can act as an additional register file to the processor, and it resides at a virtual address. A load/store instruction can access the virtual address of the local memory when the load/store instruction's effective virtual address matches the virtual address of the local memory. Data can be moved from the local memory to the main register file using only a single (load) instruction. Data can be moved from the main register file to the local memory using only a single (store) instruction. These single instructions are loads/stores that can use a constant base address, together with a (possibly negative) offset. In one embodiment, the capability (input output bridge direct memory access or IOBDMA) to fetch data into the local memory is provided. IOBDMA may also execute in a single instruction.
In another embodiment, the RISC processor can use register base +16-bit signed constant offset addressing, and can include a register (r0) that gives a zero base address. The data transfers between the local memory and the scratchpad may be signed or unsigned, and can be any width allowed by the loads/stores in the instruction set: 8-bits (byte), 16 bits (half-word), 32-bits (word), or 64-bits (double-word).
In another embodiment, the processor can include a plurality of processors, wherein the plurality of processors can comprise a network processor.
The foregoing and other objects, features and advantages of the invention will be apparent from the following more particular description of preferred embodiments of the invention, as illustrated in the accompanying drawings in which like reference characters refer to the same parts throughout the different views. The drawings are not necessarily to scale, emphasis instead being placed upon illustrating the principles of the invention.
A description of preferred embodiments of the invention follows.
A processor is a central processing unit (CPU) that interprets and executes instructions.
The processor 100 includes an Execution Unit 102, an Instruction dispatch unit 104, an instruction fetch unit 106, a Memory Management Unit (MMU) 108, a system interface 110, a load/store unit 118, a write buffer 122, and security accelerators 124. The processor core also includes an EJTAG interface 120 allowing debug operations to be performed. The system interface 110 controls access to external memory, that is, memory external to the processor 100 such as, external (L2) cache memory 132.
The Execution unit 102 includes a multiply unit 114 and at least one register file (main register file) 116. The multiply unit 114 has a 64-bit register-direct multiply. The Instruction fetch unit 106 includes instruction cache (ICache) 126. The load/store unit 118 includes a data cache 128. A portion of the data cache 128 can be reserved as scratchpad/local memory 130. In one embodiment, the instruction cache 126 is 32K bytes, the data cache 128 is 8 K bytes and the write buffer 122 is 2 K bytes. The Memory Management Unit 108 includes a Translation Lookaside Buffer (TLB) 112.
In one embodiment, the processor 100 includes a crypto acceleration module (security accelerators) 124 that include cryptography acceleration for Triple Data Encryption standard (3DES), Advanced Encryption Standard (AES), Secure Hash Algorithm (SHA-1), Message Digest Algorithm #5 (MD5). The crypto acceleration module 124 communicates by moves to and from the main register file 116 in the Execution unit 102. RSA and the Diffie-Hellman (DH) algorithm are performed in the multiplier unit 114.
A superscalar processor has a superscalar instruction pipeline that allows more than one instruction to be completed each clock cycle by allowing multiple instructions to be issued simultaneously and dispatched in parallel to multiple execution units. The RISC-type processor 100 has an instruction set architecture that defines instructions by which the programmer interfaces with the RISC-type processor. Only load and store instructions access external memory; that is, memory external to the processor 100. In one embodiment, the external memory is accessed over a coherent memory bus 134. All other instructions operate on data stored in the register file 116 in the processor 100. In one embodiment, the processor is a superscalar dual issue processor.
The register file in a 64-bit processor typically includes thirty-two 64-bit registers; one write port, and two read ports. The instruction pipeline is divided into stages, each stage taking one clock cycle to complete. Thus, in a five stage pipeline, it takes five clock cycles to process each instruction and five instructions can be processed concurrently with each instruction being processed by a different stage of the pipeline in any given clock cycle. Typically, a five stage pipeline includes the following stages: fetch, decode, execute, memory and write back.
During the fetch-stage, the instruction fetch unit 106 fetches an instruction from instruction cache 126 in data cache 128 at a location identified by a memory address stored in a program counter. During the decode-stage, the instruction fetched from instruction cache 126 in the fetch-stage is decoded by the instruction dispatch unit 104 and the address of the next instruction to be fetched for the issuing context is computed. During the execute-stage, the Integer Execution unit 102 performs an operation dependent on the type of instruction. For example, the Integer Execution Unit 102 begins the arithmetic or logical operation for a register-to-register instruction, calculates the virtual address for a load or store operation or determines whether the branch condition is true for a branch instruction. During the memory-stage, data is aligned by the load/store unit 118 and transferred to its destination in external memory. During the write back-stage, the result of a register-to-register or load instruction is written back to the register file 116.
The system interface 110 is coupled via the Coherent Memory Bus 134 to external memory, such as L2 cache 132. All store data is sent to L2 cache 132, 136 over the coherent memory bus 134 via a write buffer entry in the write buffer 122.
During a load instruction, if a specified address is not in the data cache 128, then the processor 100 looks for the specified address in an external cache, also called an L2 cache 132. If the address is not in the L2 cache 132 (a cache miss), then the primary/main memory 136 is searched for the address. If the address is not in primary/main memory 136, then the processor 100 searches secondary memory (not shown) through an input/output controller. Examples of secondary memory are hard disks, CD ROMs, etc.
The foregoing discussion of a typical memory hierarchy in a processor makes apparent the desirability of finding an address within the data cache 128. In the absence of a “hit” in the data cache, the address must be located in the external memory (L2 cache 132 or other external memory). Therefore, it is highly desirable to have a high “hit” rate in the internal data cache 128 of a processor 100.
The present invention uniquely addresses the problem of accessing external memory by providing a scratchpad/local memory using a portion of the data cache 128 to extend the size of the register file 116. The scratchpad 130 accelerates packet-processing because data can be stored locally (without being stored in external memory) inside the processor 100 and accessed quickly. Also, the scratchpad memory 130 eliminates all coherent-bus 134 bandwidth for these locations.
There are several features that make the scratch/local 130 memory unique. Unlike past local memories, the size of the scratchpad 130 can vary dynamically on a cache block basis and the size can be dynamically changed based on the type of application being executed. The size of the scratchpad 130 is changed by software by modifying a value stored in a configuration register 133 which can be located in the load/store unit 118. The scratchpad/local memory 130 can be accessed by an ordinary virtual address, yet can always also be accessed as an extended register set, with no more than a single instruction (store/load) ever required to move data between the main register file 116 and the local memory 130. Also, no new instructions are added to the processor's instruction set, to use the local memory 130 as an extended register set, and no registers need be reserved in the main register file 116 to store base addresses.
In an embodiment, the starting (virtual address) of the local memory 130 is 0xFFFFFFFFFFFF8000 and the ending address is 0xFFFFFFFFFFFFBFFF. These addresses are selected for reasons that will be explained below with reference to
The scratchpad memory 130 is accessed using regular load and store instructions. For example, the LD (load) instruction performs an aligned load of a doubleword (64-bits) and the SD (store) instruction performs an aligned store of a double word (64-bits). For the extended register file usage, single LD and SD memory instructions are used to move data between the main register file 116 and the scratchpad 130 without using a register in the main register file 116 to store a base address.
The instruction mnemonics for a typical RISC load/store instruction is:
In the instruction as shown with reference to
As shown in
Similarly, a store instruction can be used to move data from a register in the main register file 116 into the local scratchpad 130. For example, the instruction:
In the preceding example, the offset value (0x8008) is sign extended to provide 0xFFFFFFFFFFFF8008 and this sign extended value is added to the base register value in register r0, which is zero, producing a resulting virtual address of 0xFFFFFFFFFFFF8008. Thus, this instruction references the second (64-bit) location in the scratchpad (at byte offset 8). To complete the execution of the example SD instruction, the processor 100 copies the contents of register 3 (r3) in the main register file 116 (
The RISC-type processor includes load/store instructions for multiple data widths and signed/unsigned data. Therefore, any load/store instructions can be used, and thus the available registers or memory locations can be 8-bits (byte), 16-bits (Halfword), 32-bits (word), or 64-bits (Double-word) bits, either signed or unsigned because load and store instructions are used to access the scratchpad memory 130.
The size of the scratchpad 130 is a configuration variable stored within the configuration register 133 in the load/store unit 118. Software can change the size of the scratchpad by changing the configuration variable at any time. This is advantageous as different applications may require more or less scratchpad space. For example, general packet processing might require only about 48 double-words, while an application that computes a large modular exponentiation may require about 496 double-words. Software can dynamically adjust the configuration variable to provide the scratchpad size appropriate to the particular application, yet maximize the space available for the data cache 128, to improve the performance of the application.
In many RISC type processors the number of outstanding loads that can be in progress is limited. For example, some processors can only have one outstanding load to the main register file. To increase the number of loads that can be outstanding (i.e., in progress), the scratchpad 130 can be further partitioned to provide an area of data cache for storing prefetched data. This allows data to be prefetched and stored in the scratchpad 130. These prefetches, such as Input Output Bridge Direct Memory Access (IOBDMA) instructions, queue data waiting to be loaded into the register file 116 in the scratchpad 130. Essentially an IOBDMA instruction is an “I/O prefetch” that returns its results into scratchpad/local memory 130.
The present invention allows multiple outstanding loads via IOBDMAs. The IOBDMAs places the result into the local scratchpad 130. The present invention allows the processor (core) to have many outstanding loads, each of which can be a vector load, while not impacting the core's simple instruction issue and register dependency logic. This is because the extra registers in local memory 130 are not scoreboarded like the registers in the main register file 116 registers are. Scoreboarding is a technique for allowing instructions to be executed out of order when these are sufficient resources and no data dependencies. After an IOBDMA instruction is issued (i.e. in response to executing a store instruction that references an IOBDMA address), a SYNCIOBDMA (or SYNC) instruction is executed before using the result of the IOBDMA instruction to guarantee that the IOBDMA results have been deposited into scratchpad/local memory 130. An SYNCIOBDMA instruction essentially delays execution until the results have been deposited into scratchpad/local memory 130. The SYNCIOBDMA (and SYNC) instructions are the only instructions that need to scoreboard the CVMSEG LM locations, so the multiple outstanding loads can be added without adding any complexity to the issue logic of the processor core.
The IOBDMA instruction allows the execution unit 102 (
An IOBDMA store causes an I/O Bus transaction using the Major DID 306 and offset 312. This transaction is similar to a transaction created to service an I/O load. The IOBDMA does not stall the processor and can return a vector of 64-bit words.
The “SD $9, 0xA200($0)” initiates the IOBDMA to the I/O address stored in register 9 ($9). When the processor 100 receives a store instruction to this 0xFFFFFFFFFFFFA200 virtual address, it executes an IOBDMA. The store data (stored in r9) contains the address to reference (major did 306, sub did 308, rsvd 310, offset 312;
The security appliance 402 is a standalone system that can switch packets received at one Ethernet port (Gig E) to another Ethernet port (Gig E) and perform a plurality of security functions on received packets prior to forwarding the packets. For example, the security appliance 402 can be used to perform security processing on packets received on a Wide Area Network prior to forwarding the processed packets to a Local Area Network.
The network services processor 400 includes hardware packet processing, buffering, work scheduling, ordering, synchronization, and coherence support to accelerate all packet processing tasks. The network services processor 400 processes Open System Interconnection network L2-L7 layer protocols encapsulated in received packets.
The network services processor 400 receives packets from the Ethernet ports (Gig E) through the physical interfaces PHY 404 a, 404 b, performs L7-L2 network protocol processing on the received packets and forwards processed packets through the physical interfaces 404 a, 404 b or through the PCI bus 406. The network protocol processing can include processing of network security protocols such as Firewall, Application Firewall, Virtual Private Network (VPN) including IP Security (IPSEC) and/or Secure Sockets Layer (SSL), Intrusion detection System (IDS) and Anti-virus (AV).
A Dynamic Random Access Memory (DRAM) controller in the network services processor 400 controls access to an external DRAM 408 that is coupled to the network services processor 400. The DRAM 408 is external to the network services processor 400. The DRAM 408 stores data packets received from the PHYs interfaces 404 a, 404 b or the Peripheral Component Interconnect Extended (PCI-X) interface 406 for processing by the network services processor 400.
The network services processor 400 includes another memory controller for controlling Low latency DRAM 418. The low latency DRAM 418 is used for Internet Services and Security applications allowing fast lookups, including the string-matching that may be required for Intrusion Detection System (IDS) or Anti Virus (AV) applications.
A packet is received for processing by any one of the GMX/SPX units 510 a, 510 b through an SPI-4.2 or RGM II interface. A packet can also be received by the PCI interface 524. The GMX/SPX unit performs pre-processing of the received packet by checking various fields in the L2 network protocol header included in the received packet and then forwards the packet to the packet input unit 514.
The packet input unit 514 performs further pre-processing of network protocol headers (L3 and L4) included in the received packet. The pre-processing includes checksum checks for Transmission Control Protocol (TCP)/User Datagram Protocol (UDP) (L3 network protocols).
A Free Pool Allocator (FPA) 536 maintains pools of pointers to free memory in level 2 cache memory 132 and DRAM. The input packet processing unit 514 uses one of the pools of pointers to store received packet data in level 2 cache memory 132 or DRAM and another pool of pointers to allocate work queue entries for the processor cores.
The packet input unit 514 then writes packet data into buffers in Level 2 cache 132 or DRAM in a format that is convenient to higher-layer software executed in at least one processor core 100 for further processing of higher level network protocols.
The network services processor 100 also includes application specific co-processors that offload the processor cores 100 so that the network services processor achieves high-throughput. The compression/decompression co-processor 508 is dedicated to performing compression and decompression of received packets. The DFA module 544 includes dedicated DFA engines to accelerate pattern and signature match necessary for anti-virus (AV), Intrusion Detection Systems (IDS) and other content processing applications at up to 4 Gbps.
The I/O Bridge (IOB) 532 manages the overall protocol and arbitration and provides coherent I/O partitioning. The IOB 532 includes a bridge 538 and a Fetch and Add Unit (FAU) 540. Registers in the FAU 540 are used to maintain lengths of the output queues that are used for forwarding processed packets through the packet output unit 518. The bridge 538 includes buffer queues for storing information to be transferred between the I/O bus, coherent memory bus, the packet input unit 514 and the packet output unit 518.
The Packet order/work (POW) module 528 queues and schedules work for the processor cores 100. Work is queued by adding a work queue entry to a queue. For example, a work queue entry is added by the packet input unit 514 for each packet arrival. The timer unit 542 is used to schedule work for the processor cores.
Processor cores 100 request work from the POW module 528. The POW module 528 selects (i.e. schedules) work for a processor core 100 and returns a pointer to the work queue entry that describes the work to the processor core 100.
The processor core 100 includes instruction cache 126, Level 1 data cache 128 and crypto acceleration 124. In one embodiment, the network services processor 100 includes sixteen superscalar RISC (Reduced Instruction Set Computer)-type processor cores. In one embodiment, each superscalar RISC-type processor core is an extension of the MIPS64 version 2 processor core.
Level 2 cache memory 132 and DRAM memory is shared by all of the processor cores 100 and I/O co-processor devices. Each processor core 100 is coupled to the Level 2 cache memory 132 by a coherent memory bus 134. The coherent memory bus 134 is the communication channel for all memory and I/O transactions between the processor cores 100, the I/O Bridge (IOB) 532 and the Level 2 cache and controller 132. In one embodiment, the coherent memory bus 134 is scalable to 16 processor cores, supports fully coherent Level 1 data caches 128 with write through, is highly buffered and can prioritize I/O.
The level 2 cache memory controller 132 maintains memory reference coherence. It returns the latest copy of a block for every fill request, whether the block is stored in the L2 cache, in DRAM or is in-flight. It also stores a duplicate copy of the tags for the data cache 128 in each processor core 100. It compares the addresses of cache block store requests against the data cache tags, and invalidates (both copies) a data cache tag for a processor core 100 whenever a store instruction is from another processor core or from an I/O component via the I/O Bridge 532.
After the packet has been processed by the processor cores 100, a packet output unit (PKO) 518 reads the packet data from memory, performs L4 network protocol post-processing (e.g., generates a TCP/UDP checksum), forwards the packet through the GMX/SPC unit 510 a, 510 b and frees the L2 cache/DRAM used by the packet. The invention has been described for a processor core that is included in a security appliance. However, the invention is not limited to a processor core in a security appliance. The invention applies to ordering of store instructions in any pipelined processor.
While this invention has been particularly shown and described with references to preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the scope of the invention encompassed by the appended claims.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US4415970||Nov 14, 1980||Nov 15, 1983||Sperry Corporation||Cache/disk subsystem with load equalization|
|US4755930||Jun 27, 1985||Jul 5, 1988||Encore Computer Corporation||Hierarchical cache memory system and method|
|US4780815||Feb 17, 1987||Oct 25, 1988||Hitachi, Ltd.||Memory control method and apparatus|
|US5091846||Oct 30, 1989||Feb 25, 1992||Intergraph Corporation||Cache providing caching/non-caching write-through and copyback modes for virtual addresses and including bus snooping to maintain coherency|
|US5119485||May 15, 1989||Jun 2, 1992||Motorola, Inc.||Method for data bus snooping in a data processing system by selective concurrent read and invalidate cache operation|
|US5155831||Apr 24, 1989||Oct 13, 1992||International Business Machines Corporation||Data processing system with fast queue store interposed between store-through caches and a main memory|
|US5276852||Mar 15, 1993||Jan 4, 1994||Digital Equipment Corporation||Method and apparatus for controlling a processor bus used by multiple processor components during writeback cache transactions|
|US5404483||Jun 22, 1992||Apr 4, 1995||Digital Equipment Corporation||Processor and method for delaying the processing of cache coherency transactions during outstanding cache fills|
|US5408644||Jun 5, 1992||Apr 18, 1995||Compaq Computer Corporation||Method and apparatus for improving the performance of partial stripe operations in a disk array subsystem|
|US5590368||Jul 27, 1995||Dec 31, 1996||Intel Corporation||Method and apparatus for dynamically expanding the pipeline of a microprocessor|
|US5619680||Nov 25, 1994||Apr 8, 1997||Berkovich; Semyon||Methods and apparatus for concurrent execution of serial computing instructions using combinatorial architecture for program partitioning|
|US5623627 *||Dec 9, 1993||Apr 22, 1997||Advanced Micro Devices, Inc.||Computer memory architecture including a replacement cache|
|US5737547||Jun 7, 1995||Apr 7, 1998||Microunity Systems Engineering, Inc.||System for placing entries of an outstanding processor request into a free pool after the request is accepted by a corresponding peripheral device|
|US5737750 *||Dec 9, 1996||Apr 7, 1998||Hewlett-Packard Company||Partitioned single array cache memory having first and second storage regions for storing non-branch and branch instructions|
|US5742840 *||Aug 16, 1995||Apr 21, 1998||Microunity Systems Engineering, Inc.||General purpose, multiple precision parallel operation, programmable media processor|
|US5754819||Jul 28, 1994||May 19, 1998||Sun Microsystems, Inc.||Low-latency memory indexing method and structure|
|US5794060 *||Nov 22, 1996||Aug 11, 1998||Microunity Systems Engineering, Inc.||General purpose, multiple precision parallel operation, programmable media processor|
|US5794061 *||Nov 22, 1996||Aug 11, 1998||Microunity Systems Engineering, Inc.||General purpose, multiple precision parallel operation, programmable media processor|
|US5809321 *||Nov 22, 1996||Sep 15, 1998||Microunity Systems Engineering, Inc.||General purpose, multiple precision parallel operation, programmable media processor|
|US5822603 *||Nov 22, 1996||Oct 13, 1998||Microunity Systems Engineering, Inc.||High bandwidth media processor interface for transmitting data in the form of packets with requests linked to associated responses by identification data|
|US5860158||Nov 15, 1996||Jan 12, 1999||Samsung Electronics Company, Ltd.||Cache control unit with a cache request transaction-oriented protocol|
|US5890217||Feb 7, 1996||Mar 30, 1999||Fujitsu Limited||Coherence apparatus for cache of multiprocessor|
|US5893141||Mar 6, 1997||Apr 6, 1999||Intel Corporation||Low cost writethrough cache coherency apparatus and method for computer systems without a cache supporting bus|
|US5895485||Feb 24, 1997||Apr 20, 1999||Eccs, Inc.||Method and device using a redundant cache for preventing the loss of dirty data|
|US5897656||Sep 16, 1996||Apr 27, 1999||Corollary, Inc.||System and method for maintaining memory coherency in a computer system having multiple system buses|
|US5991855||Jul 2, 1997||Nov 23, 1999||Micron Electronics, Inc.||Low latency memory read with concurrent pipe lined snoops|
|US6009263 *||Jul 28, 1997||Dec 28, 1999||Institute For The Development Of Emerging Architectures, L.L.C.||Emulating agent and method for reformatting computer instructions into a standard uniform format|
|US6018792||Jul 2, 1997||Jan 25, 2000||Micron Electronics, Inc.||Apparatus for performing a low latency memory read with concurrent snoop|
|US6021473||Aug 27, 1996||Feb 1, 2000||Vlsi Technology, Inc.||Method and apparatus for maintaining coherency for data transaction of CPU and bus device utilizing selective flushing mechanism|
|US6026475 *||Nov 26, 1997||Feb 15, 2000||Digital Equipment Corporation||Method for dynamically remapping a virtual address to a physical address to maintain an even distribution of cache page addresses in a virtual address space|
|US6065092||Oct 24, 1997||May 16, 2000||Hitachi Micro Systems, Inc.||Independent and cooperative multichannel memory architecture for use with master device|
|US6070227||Oct 31, 1997||May 30, 2000||Hewlett-Packard Company||Main memory bank indexing scheme that optimizes consecutive page hits by linking main memory bank address organization to cache memory address organization|
|US6125421||May 6, 1998||Sep 26, 2000||Hitachi Micro Systems, Inc.||Independent multichannel memory architecture|
|US6134634||Dec 19, 1997||Oct 17, 2000||Texas Instruments Incorporated||Method and apparatus for preemptive cache write-back|
|US6188624||Jul 12, 1999||Feb 13, 2001||Winbond Electronics Corporation||Low latency memory sensing circuits|
|US6226715||May 6, 1999||May 1, 2001||U.S. Philips Corporation||Data processing circuit with cache memory and cache management unit for arranging selected storage location in the cache memory for reuse dependent on a position of particular address relative to current address|
|US6279080||Jun 9, 1999||Aug 21, 2001||Ati International Srl||Method and apparatus for association of memory locations with a cache location having a flush buffer|
|US6408365||Feb 1, 1999||Jun 18, 2002||Nec Corporation||Multiprocessor system having means for arbitrating between memory access request and coherency maintenance control|
|US6438658||Jun 30, 2000||Aug 20, 2002||Intel Corporation||Fast invalidation scheme for caches|
|US6526481||Apr 27, 2000||Feb 25, 2003||Massachusetts Institute Of Technology||Adaptive cache coherence protocols|
|US6546471||Feb 18, 2000||Apr 8, 2003||Hitachi, Ltd.||Shared memory multiprocessor performing cache coherency|
|US6560680||Nov 26, 2001||May 6, 2003||Micron Technology, Inc.||System controller with Integrated low latency memory using non-cacheable memory physically distinct from main memory|
|US6563818||May 20, 1999||May 13, 2003||Advanced Micro Devices, Inc.||Weighted round robin cell architecture|
|US6571320||Nov 7, 2000||May 27, 2003||Infineon Technologies Ag||Cache memory for two-dimensional data fields|
|US6587920||Nov 30, 2000||Jul 1, 2003||Mosaid Technologies Incorporated||Method and apparatus for reducing latency in a memory system|
|US6598136 *||Oct 22, 1997||Jul 22, 2003||National Semiconductor Corporation||Data transfer with highly granular cacheability control between memory and a scratchpad area|
|US6622214||Jan 12, 1999||Sep 16, 2003||Intel Corporation||System and method for maintaining memory coherency in a computer system having multiple system buses|
|US6622219||Apr 26, 2002||Sep 16, 2003||Sun Microsystems, Inc.||Shared write buffer for use by multiple processor units|
|US6643745||Mar 31, 1998||Nov 4, 2003||Intel Corporation||Method and apparatus for prefetching data into cache|
|US6647456||Feb 23, 2001||Nov 11, 2003||Nvidia Corporation||High bandwidth-low latency memory controller|
|US6654858||Aug 31, 2000||Nov 25, 2003||Hewlett-Packard Development Company, L.P.||Method for reducing directory writes and latency in a high performance, directory-based, coherency protocol|
|US6665768||Oct 12, 2000||Dec 16, 2003||Chipwrights Design, Inc.||Table look-up operation for SIMD processors with interleaved memory systems|
|US6718457||Dec 3, 1998||Apr 6, 2004||Sun Microsystems, Inc.||Multiple-thread processor for threaded software applications|
|US6725336 *||Apr 20, 2001||Apr 20, 2004||Sun Microsystems, Inc.||Dynamically allocated cache memory for a multi-processor unit|
|US6754810 *||Apr 10, 2002||Jun 22, 2004||I.P.-First, L.L.C.||Instruction set for bi-directional conversion and transfer of integer and floating point data|
|US6757784||Sep 28, 2001||Jun 29, 2004||Intel Corporation||Hiding refresh of memory and refresh-hidden memory|
|US6785677||May 2, 2001||Aug 31, 2004||Unisys Corporation||Method for execution of query to search strings of characters that match pattern with a target string utilizing bit vector|
|US6924810 *||Nov 18, 2002||Aug 2, 2005||Advanced Micro Devices, Inc.||Hierarchical texture cache|
|US7055003 *||Apr 25, 2003||May 30, 2006||International Business Machines Corporation||Data cache scrub mechanism for large L2/L3 data cache structures|
|US7093153 *||Oct 30, 2002||Aug 15, 2006||Advanced Micro Devices, Inc.||Method and apparatus for lowering bus clock frequency in a complex integrated data processing system|
|US7209996||Oct 16, 2002||Apr 24, 2007||Sun Microsystems, Inc.||Multi-core multi-thread processor|
|US7558925||Jan 18, 2006||Jul 7, 2009||Cavium Networks, Inc.||Selective replication of data structures|
|US7594081||Dec 28, 2004||Sep 22, 2009||Cavium Networks, Inc.||Direct access to low-latency memory|
|US20010037406||Mar 9, 2001||Nov 1, 2001||Philbrick Clive M.||Intelligent network storage interface system|
|US20010054137 *||Jun 10, 1998||Dec 20, 2001||Richard James Eickemeyer||Circuit arrangement and method with improved branch prefetching for short branch instructions|
|US20020032827 *||Mar 14, 1997||Mar 14, 2002||De H. Nguyen||Structure and method for providing multiple externally accessible on-chip caches in a microprocessor|
|US20020099909||Nov 26, 2001||Jul 25, 2002||Meyer James W.||System controller with integrated low latency memory using non-cacheable memory physically distinct from main memory|
|US20020112129||Feb 12, 2001||Aug 15, 2002||International Business Machines Corporation||Efficient instruction cache coherency maintenance mechanism for scalable multiprocessor computer system with store-through data cache|
|US20030056061||Aug 20, 2002||Mar 20, 2003||Alpine Microsystems, Inc.||Multi-ported memory|
|US20030065884||Sep 28, 2001||Apr 3, 2003||Lu Shih-Lien L.||Hiding refresh of memory and refresh-hidden memory|
|US20030067913||Oct 5, 2001||Apr 10, 2003||International Business Machines Corporation||Programmable storage network protocol handler architecture|
|US20030105793 *||Apr 9, 2002||Jun 5, 2003||Guttag Karl M.||Long instruction word controlling plural independent processor operations|
|US20030110208||Jan 24, 2003||Jun 12, 2003||Raqia Networks, Inc.||Processing data across packet boundaries|
|US20030115238 *||Jan 17, 2003||Jun 19, 2003||Sun Microsystems, Inc.||Method frame storage using multiple memory circuits|
|US20030115403||Dec 19, 2001||Jun 19, 2003||Bouchard Gregg A.||Dynamic random access memory system with bank conflict avoidance feature|
|US20030172232||Mar 6, 2002||Sep 11, 2003||Samuel Naffziger||Method and apparatus for multi-core processor integrated circuit having functional elements configurable as core elements and as system device elements|
|US20030212874 *||Mar 24, 2003||Nov 13, 2003||Sun Microsystems, Inc.||Computer system, method, and program product for performing a data access from low-level code|
|US20040010782 *||Jul 9, 2002||Jan 15, 2004||Moritz Csaba Andras||Statically speculative compilation and execution|
|US20040012607 *||Jul 16, 2003||Jan 22, 2004||Witt Sarah Elizabeth||Video processing|
|US20040059880||Sep 23, 2002||Mar 25, 2004||Bennett Brian R.||Low latency memory access method using unified queue mechanism|
|US20040073778||Jul 8, 2003||Apr 15, 2004||Adiletta Matthew J.||Parallel processor architecture|
|US20040250045||Jul 2, 2004||Dec 9, 2004||Dowling Eric M.||Split embedded dram processor|
|US20050114606 *||Nov 21, 2003||May 26, 2005||International Business Machines Corporation||Cache with selective least frequently used or most frequently used cache line replacement|
|US20050138276||Dec 17, 2003||Jun 23, 2005||Intel Corporation||Methods and apparatus for high bandwidth random access using dynamic random access memory|
|US20050138297 *||Dec 23, 2003||Jun 23, 2005||Intel Corporation||Register file cache|
|US20050166038 *||Apr 10, 2002||Jul 28, 2005||Albert Wang||High-performance hybrid processor with configurable execution units|
|US20050267996 *||Mar 30, 2005||Dec 1, 2005||O'connor James M||Method frame storage using multiple memory circuits|
|US20050273605 *||May 20, 2004||Dec 8, 2005||Bratin Saha||Processor extensions and software verification to support type-safe language environments running with untrusted code|
|US20060059314||Dec 28, 2004||Mar 16, 2006||Cavium Networks||Direct access to low-latency memory|
|US20060059316||Jan 5, 2005||Mar 16, 2006||Cavium Networks||Method and apparatus for managing write back cache|
|US20060143396||Dec 29, 2004||Jun 29, 2006||Mason Cabot||Method for programmer-controlled cache line eviction policy|
|US20070038798||Jan 18, 2006||Feb 15, 2007||Bouchard Gregg A||Selective replication of data structures|
|US20100306510 *||Jun 2, 2009||Dec 2, 2010||Sun Microsystems, Inc.||Single cycle data movement between general purpose and floating-point registers|
|GB2378779A||Title not available|
|WO2006031462A1||Sep 1, 2005||Mar 23, 2006||Cavium Networks||Direct access to low-latency memory|
|WO2006031551A2||Sep 9, 2005||Mar 23, 2006||Cavium Networks||Selective replication of data structure|
|1||"Double Data Rate SDRAMs operate at 400 MHz" (Oct. 14, 2003).|
|2||*||"Microsoft Computer Dictionary," 2002. Microsoft Press, Fifth Edition, p. 466.|
|3||Gharachorloo, Kourosh, et al., "Architecture and Design of AlphaServer GS320." Ninth International Conference on Architectural Support for Programming Languages and Operating Systems (ASPLOS-IX) (2000).|
|4||*||Handy, Jim. "The Cache Memory Book." 1998. Academic Press, Inc. Second Edition. pp. 85-86.|
|5||Jouppi, Norman P., "Cache Write Policies and Performance," WRL Research Report 91/12 (1991).|
|6||Stokes, Jon, "A Look at Centrino's Core: The Pentium M" "Instruction decoding and micro-op fusion," http://arstechnica.com/articles/paedia/cpu/pentium-m.ars/4, pp. 1-4, Feb. 25, 2004.|
|7||van Riel, Rik, "Page replacement in Linux 2.4 memory management," Conectiva Inc., pp. 1-10, Retrieved from the Internet, http://web.archive.org/web/20010821013232/http://surriel.com/lectures/linux24-vm.html [retrieved on Jun. 5, 2007].|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US8898244 *||Oct 20, 2011||Nov 25, 2014||Allen Miglore||System and method for transporting files between networked or connected systems and devices|
|US8947817||Apr 28, 2014||Feb 3, 2015||Seagate Technology Llc||Storage system with media scratch pad|
|US9372800||Mar 7, 2014||Jun 21, 2016||Cavium, Inc.||Inter-chip interconnect protocol for a multi-chip system|
|US9411644||Mar 7, 2014||Aug 9, 2016||Cavium, Inc.||Method and system for work scheduling in a multi-chip system|
|US9443553||Apr 28, 2014||Sep 13, 2016||Seagate Technology Llc||Storage system with multiple media scratch pads|
|US9529532||Mar 7, 2014||Dec 27, 2016||Cavium, Inc.||Method and apparatus for memory allocation in a multi-node system|
|US20130103786 *||Oct 20, 2011||Apr 25, 2013||Allen Miglore||System and method for transporting files between networked or connected systems and devices|
|U.S. Classification||711/101, 711/129, 711/E12.046, 711/130, 711/E12.001|
|International Classification||G06F13/00, G06F13/28, G06F12/00|
|Cooperative Classification||G06F2212/6022, G06F11/3632, G06F12/0875, G06F13/24, G06F9/383, G06F12/0891, G06F2212/6012, G06F9/30138, G06F9/30014, G06F12/0835, G06F12/0804, G06F12/084, G06F12/0815, G06F12/0813|
|European Classification||G06F9/38D2, G06F12/08B14, G06F12/08B4P4P, G06F9/30A1A1, G06F12/08B20, G06F11/36B4, G06F13/24, G06F9/30R5X|
|Oct 31, 2005||AS||Assignment|
Owner name: CAVIUM NETWORKS, CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ASHER, DAVID H.;CARLSON, DAVID A.;KESSLER, RICHARD E.;REEL/FRAME:017158/0111
Effective date: 20050914
|Mar 14, 2007||AS||Assignment|
Owner name: CAVIUM NETWORKS, INC., A DELAWARE CORPORATION, CAL
Free format text: MERGER;ASSIGNOR:CAVIUM NETWORKS, A CALIFORNIA CORPORATION;REEL/FRAME:019014/0174
Effective date: 20070205
|Jul 21, 2011||AS||Assignment|
Owner name: CAVIUM, INC., CALIFORNIA
Free format text: MERGER;ASSIGNOR:CAVIUM NETWORKS, INC.;REEL/FRAME:026632/0672
Effective date: 20110617
|Oct 15, 2014||FPAY||Fee payment|
Year of fee payment: 4
|Aug 17, 2016||AS||Assignment|
Owner name: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT, IL
Free format text: SECURITY AGREEMENT;ASSIGNORS:CAVIUM, INC.;CAVIUM NETWORKS LLC;REEL/FRAME:039715/0449
Effective date: 20160816