# US 2021/0342270 A1 · Victim cache that supports draining write-miss entries

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0342270 A1
- Document ID: US20210342270A1
- Status: Published application
- Kind: A1
- Application number: 17/377,509
- Filed: 2021-07-16
- Published: 2021-11-04
- Earliest claimed: 2019-05-24
- Assignees: Texas Instruments Incorporated
- Applicants: Texas Instruments Incorporated
- Inventors: Naveen BHORIA; Timothy David ANDERSON; Pete HIPPLEHEUSER
- Web page: https://patentgrep.com/patent/US20210342270A1

## CPC

- G06F 12/128: adapted to multidimensional cache systems, e.g. set-associative, multicache, multiset or multilevel
- G06F 9/3001: {Arithmetic instructions}
- G06F 9/30043: {LOAD or STORE instructions; Clear instruction}
- G06F 9/30047: {Prefetch instructions; cache control instructions}
- G06F 9/546: {Message passing systems or structures, e.g. queues}
- G06F 11/1064: {in cache or content addressable memories}
- G06F 12/0215: {with look ahead addressing means}
- G06F 12/0238: {Memory management in non-volatile memory, e.g. resistive RAM or ferroelectric memory}
- G06F 12/0292: {using tables or multilevel address translation means (G06F12/023 takes precedence; address translation in virtual memory systems G06F12/10)}
- G06F 12/0802: Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches
- G06F 12/0804: with main memory updating (G06F12/0806 takes precedence)
- G06F 12/0806: Multiuser, multiprocessor or multiprocessing cache systems
- G06F 12/0811: with multilevel cache hierarchies
- G06F 12/0815: Cache consistency protocols
- G06F 12/082: {Associative directories (G06F12/0822 takes precedence)}
- G06F 12/0853: Cache with multiport tag or data arrays
- G06F 12/0855: Overlapped cache accessing, e.g. pipeline (G06F12/0846 takes precedence)
- G06F 12/0864: using pseudo-associative means, e.g. set-associative or hashing
- G06F 12/0884: Parallel mode, e.g. in parallel with main memory or CPU
- G06F 12/0888: using selective caching, e.g. bypass
- G06F 12/0891: using clearing, invalidating or resetting means
- G06F 12/0895: of parts of caches, e.g. directory or tag array
- G06F 12/0897: with two or more cache hierarchy levels (with multilevel cache hierarchies G06F12/0811)
- G06F 12/1027: using associative or pseudo-associative address translation means, e.g. translation look-aside buffer [TLB]
- G06F 12/12: Replacement control
- G06F 12/121: using replacement algorithms
- G06F 12/126: with special data handling, e.g. priority of data or instructions, handling errors or pinning
- G06F 12/127: using additional replacement algorithms
- G06F 13/1605: {based on arbitration (arbitration in handling access to a common bus or bus system G06F13/36)}
- G06F 13/1642: {with request queuing}
- G06F 13/1673: {using buffers}
- G06F 13/1689: {Synchronisation and timing concerns (synchronisation on a memory bus G06F13/4234)}
- G06F 15/8069: {using a cache}
- G11C 5/066: {Means for reducing external access-lines for a semiconductor memory clip, e.g. by multiplexing at least address and data signals}
- G11C 7/10: Input/output [I/O] data interface arrangements, e.g. I/O data control circuits, I/O data buffers
- G11C 7/1015: {Read-write modes for single port memories, i.e. having either a random port or a serial port}
- G11C 7/106: {Data output latches}
- G11C 7/1075: {for multiport memories each having random access ports and serial ports, e.g. video RAM}
- G11C 7/1078: {Data input circuits, e.g. write amplifiers, data input buffers, data input registers, data input level conversion circuits}
- G11C 7/1087: {Data input latches}
- G11C 7/222: {Clock generating, synchronizing or distributing circuits within memory device}
- G11C 29/42: using error correcting codes [ECC] or parity check
- G11C 29/44: Indication or identification of errors, e.g. for repair
- G11C 29/52: Protection of memory contents; Detection of errors in memory contents
- G11C 29/72: {with optimized replacement algorithms}
- G11C 29/76: {using address translation or modifications}
- G06F 2212/1016: Performance improvement
- G06F 2212/1021: Hit rate improvement
- G06F 2212/1024: Latency reduction
- G06F 2212/1041: Resource optimization
- G06F 2212/1044: Space efficiency improvement
- G06F 2212/301: In special purpose processing node, e.g. vector processor
- G06F 2212/454: Vector or matrix data
- G06F 2212/603: of operating mode, e.g. cache mode or local memory mode
- G06F 2212/6032: Way prediction in set-associative cache
- G06F 2212/6042: Allocation of cache space to multiple users or processors
- G06F 2212/608: Details relating to cache mapping
- G06F 2212/62: Details of cache specific to multiprocessor cache arrangements
- G11C 29/4401: {for self repair}
- G11C 2029/0409: {Online test}
- G11C 2029/0411: {Online error correction}
- Y02D 10/00: Energy efficient computing, e.g. low power processors, power management or thermal management
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G11C: STATIC STORES (semiconductor memory devices H10B)
- Y02D: CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE

## Abstract

A caching system including a first sub-cache and a second sub-cache in parallel with the first sub-cache, wherein the second sub-cache includes a set of cache lines, line type bits configured to store an indication that a corresponding cache line of the set of cache lines is configured to store write-miss data, and an eviction controller configured to flush stored write-miss data based on the line type bits.

## Claims

### Claim 1

An eviction method, comprising:
detecting an idle activity on a processor interface; and
in response to detecting the idle activity on the processor interface:
determining a write-miss entry inside a victim cache; and
draining the write-miss entry from the victim cache.

### Claim 2 (depends on 1)

The eviction method of claim 1, wherein:
the idle activity is detected when a processor has not issued a command on the processor interface for N number of clock cycles.

### Claim 3 (depends on 2)

The eviction method of claim 2, wherein:
the N number of clock cycles is predetermined.

### Claim 4 (depends on 2)

The eviction method of claim 2, wherein:
the N number of clock cycles is configurable.

### Claim 5 (depends on 1)

The eviction method of claim 1, wherein:
the determining the write-miss entry includes examining each line of the victim cache in logical order for the write-miss entry.

### Claim 6 (depends on 1)

The eviction method of claim 1, wherein:
the write-miss entry is a plurality of write-miss entries;
each of the plurality of write-miss entries is stored in respective lines of the victim cache; and
the draining the write-miss entry includes draining the plurality of write-miss entries in one of a first in first out, least recently used, or random basis.

### Claim 7 (depends on 1)

The eviction method of claim 1, wherein:
the determining the write-miss entry inside the victim cache includes sending an eviction trigger request to a victim cache controller for a selected line of the victim cache associated with the write-miss entry.

### Claim 8 (depends on 7)

The eviction method of claim 7, wherein:
in response to receiving the eviction trigger request, the victim cache controller determines if an entry exists on the selected line of the victim cache; and
and in response to determining the entry does not exist, the victim cache controller drains the selected line of the victim cache.

### Claim 9 (depends on 1)

The eviction method of claim 1, further comprising:
storing the write-miss entry in a drain buffer until the write-miss entry is accepted by a memory.

### Claim 10 (depends on 1)

The eviction method of claim 1, wherein:
the draining the write-miss entry from the victim cache is in response to a processor writing out half of the write-miss entry.

### Claim 11

A device, comprising:
a victim cache; and
a victim cache controller configured to detect an idle activity on a processor interface;
wherein in response to detecting the idle activity on the processor interface, the victim cache controller is configured to:
determine a write-miss entry inside the victim cache; and
flush the write-miss entry from the victim cache.

### Claim 12 (depends on 11)

The device of claim 11, wherein:
the idle activity is detected when a processor has not issued a command on the processor interface for N number of clock cycles.

### Claim 13 (depends on 12)

The device of claim 12, wherein:
the N number of clock cycles is predetermined.

### Claim 14 (depends on 12)

The device of claim 12, wherein:
the N number of clock cycles is configurable.

### Claim 15 (depends on 11)

The device of claim 11, wherein:
the victim cache controller is configured to determine the write-miss entry by examining each line of the victim cache in logical order for the write-miss entry.

### Claim 16 (depends on 11)

The device of claim 11, wherein:
the write-miss entry is a plurality of write-miss entries;
each of the plurality of write-miss entries is stored in respective lines of the victim cache; and
the victim cache controller is configured to flush the write-miss entry by flushing the plurality of write-miss entries in one of a first in first out, least recently used, or random basis.

### Claim 17 (depends on 11)

The device of claim 11, wherein:
the victim cache controller is configured to determine the write-miss entry inside the victim cache in response to an eviction trigger request for a selected line of the victim cache associated with the write-miss entry.

### Claim 18 (depends on 17)

The device of claim 17, wherein:
in response to the eviction trigger request, the victim cache controller is configured to determine if an entry exists on the selected line of the victim cache; and
and in response to determining the entry does not exist, the victim cache controller is configured to flush the selected line of the victim cache.

### Claim 19 (depends on 11)

The device of claim 11, wherein:
the victim cache controller is configured to store the write-miss entry in a drain buffer until the write-miss entry is accepted by a memory.

### Claim 20 (depends on 11)

The device of claim 11, wherein:
the victim cache controller is configured to flush the write-miss entry from the victim cache is in response to a processor writing out half of the write-miss entry.
