# US 2026/0300187 A1 · Methods and apparatus for eviction in dual datapath victim cache system

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

- Number: US 2026/0300187 A1
- Document ID: US20260300187A1
- Status: Published application
- Kind: A1
- Application number: 19/706,191
- Filed: 2026-06-12
- Published: 2026-10-01
- Earliest claimed: 2019-05-24
- Applicants: Texas Instruments Incorporated
- Inventors: Naveen Bhoria; Timothy David Anderson; Pete Michael Hippleheuser
- Web page: https://patentgrep.com/patent/US20260300187A1

## 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
- 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
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G11C: STATIC STORES (semiconductor memory devices H10B)

## Abstract

Methods, apparatus, systems and articles of manufacture are disclosed to evict in a dual datapath victim cache system. An example apparatus includes a cache storage, a cache controller operable to receive a first memory operation and a second memory operation concurrently, comparison logic operable to identify if the first and second memory operations missed in the cache storage, and a replacement policy component operable to, when at least one of the first and second memory operations corresponds to a miss in the cache storage, reserve an entry in the cache storage to evict based on the first and second memory operations.

## Claims

### Claim 1

A system, comprising:
at least one processor core configured to produce a first memory operation and a second memory operation;
a main cache;
a victim cache that includes a set of entries configured into a set of ways; and
a cache controller coupled to the main cache, to the victim cache, the cache controller configured to:
receive, via a first interface, the first memory operation via a first data path;
determine that the first memory operation is associated with data eviction from the main cache to the victim cache;
determine, based on a pointer value, a first way of the set of ways for the data eviction;
receive, via a second interface, the second memory operation via a second data path;
determine whether the second memory operation conflicts with the data eviction; and
based on a determination that the second memory operation conflicts with the data eviction, determine a second way of the set of ways for the data eviction; and
increment the pointer value.

### Claim 2 (depends on 1)

The system of claim 1, wherein the cache controller is configured to determine that the second memory operation conflicts with the data eviction based on the second memory operation being associated with a read of data stored in the first way.

### Claim 3 (depends on 1)

The system of claim 1, wherein the data eviction is based on a write miss in the main cache.

### Claim 4 (depends on 1)

The system of claim 1, further comprising:
a register configured to store the pointer value.

### Claim 5 (depends on 1)

The system of claim 1, wherein the first data path is a scalar data path and the second data path is a vector data path, or vice versa.

### Claim 6 (depends on 1)

The system of claim 1, wherein to increment the pointer value, the cache controller is configured to increment the pointer value twice.

### Claim 7 (depends on 1)

The system of claim 1, wherein the cache controller is further configured to:
based on a determination that the second memory operation does not conflict with the data eviction:
perform the data eviction based on the first way of the set of ways; and
increment the pointer value once.

### Claim 8 (depends on 1)

The system of claim 1, wherein the pointer value indicates a way based on a least recently used policy.

### Claim 9

An apparatus comprising:
a victim cache;
a cache controller coupled to the victim cache, the cache controller comprising:
a first interface configured to receive a first memory operation for the victim cache;
a second interface configured to receive a second memory operation for the victim cache;
comparison logic coupled to the first interface and to the second interface, the comparison logic configured to identify whether the first memory operation corresponds to a miss in the victim cache and whether the second memory operation corresponds to a miss in the victim cache; and
replacement policy logic coupled to the comparison logic, the replacement policy logic configured to:
determine whether to evict a first entry in the victim cache o a second entry in the victim cache based on the first memory operation corresponding to a miss or second memory operation corresponding to a miss; and
lock the first entry and the second entry for eviction.

### Claim 10 (depends on 9)

The apparatus of claim 9, wherein the replacement policy logic is further configured to:
store an indicator of a first way of the victim cache to be replaced; and
in response to the first memory operation missing in the victim cache and the second memory operation hitting in the victim cache:
determine whether the second memory operation is directed to the first way of the victim cache indicated by the indicator;
increment the indicator to indicate a second way of the victim cache based on the second memory operation being directed to the first way of the victim cache; and
cause the second way of the victim cache to be evicted based on the first memory operation and the incremented indicator.

### Claim 11 (depends on 9)

The apparatus of claim 9, wherein the replacement policy logic is further configured to:
store an indicator of a second way of the victim cache to be replaced; and
in response to the second memory operation missing in the victim cache and the first memory operation hitting in the victim cache:
determine whether the first memory operation is directed to the second way of the victim cache indicated by the indicator;
decrement the indicator to indicate a first way of the victim cache based on the first memory operation being directed to the second way of the victim cache; and
cause the first way of the victim cache to be evicted based on the second memory operation and the indicator.

### Claim 12 (depends on 9)

The apparatus of claim 9, wherein the replacement policy logic is further configured to:
store a first indicator of a first way and a second indicator of a second way of the victim cache to be replaced; and
in response to the first memory operation missing in the victim cache and the second memory operation missing in the victim cache, cause the first way of the victim cache to be evicted based on the first memory operation and the second way of the victim cache to be evicted based on the second memory operation.

### Claim 13 (depends on 12)

The apparatus of claim 12, wherein the replacement policy logic is further configured to increment the first indicator by two locations and the second indicator by two locations after the first way and the second way of the victim cache are evicted.

### Claim 14 (depends on 9)

The apparatus of claim 9, wherein the first interface is a vector interface and the second interface is a scalar interface.

### Claim 15

A system comprising:
at least one processor core configured to produce a first memory operation and a second memory operation;
a victim cache;
a cache controller coupled to the victim cache and to the at least one processor, the cache controller comprising:
a first interface configured to receive a first memory operation for the victim cache;
a second interface configured to receive a second memory operation for the victim cache;
comparison logic coupled to the first interface and to the second interface, the comparison logic configured to identify whether the first memory operation corresponds to a miss in the victim cache and whether the second memory operation corresponds to a miss in the victim cache; and
replacement policy logic coupled to the comparison logic, the replacement policy logic configured to:
determine whether to evict a first entry in the victim cache o a second entry in the victim cache based on the first memory operation corresponding to a miss or second memory operation corresponding to a miss; and
lock the first entry and the second entry for eviction.

### Claim 16 (depends on 15)

The system of claim 15, wherein the replacement policy logic is further configured to:
store an indicator of a first way of the victim cache to be replaced; and
in response to the first memory operation missing in the victim cache and the second memory operation hitting in the victim cache:
determine whether the second memory operation is directed to the first way of the victim cache indicated by the indicator;
increment the indicator to indicate a second way of the victim cache based on the second memory operation being directed to the first way of the victim cache; and
cause the second way of the victim cache to be evicted based on the first memory operation and the incremented indicator.

### Claim 17 (depends on 15)

The system of claim 15, wherein the replacement policy logic is further configured to:
store an indicator of a second way of the victim cache to be replaced; and
in response to the second memory operation missing in the victim cache and the first memory operation hitting in the victim cache:
determine whether the first memory operation is directed to the second way of the victim cache indicated by the indicator;
decrement the indicator to indicate a first way of the victim cache based on the first memory operation being directed to the second way of the victim cache; and
cause the first way of the victim cache to be evicted based on the second memory operation and the indicator.

### Claim 18 (depends on 15)

The system of claim 15, wherein the replacement policy logic is further configured to:
store a first indicator of a first way and a second indicator of a second way of the victim cache to be replaced; and
in response to the first memory operation missing in the victim cache and the second memory operation missing in the victim cache, cause the first way of the victim cache to be evicted based on the first memory operation and the second way of the victim cache to be evicted based on the second memory operation.

### Claim 19 (depends on 18)

The system of claim 18, wherein the replacement policy logic is further configured to increment the first indicator by two locations and the second indicator by two locations after the first way and the second way of the victim cache are evicted.

### Claim 20 (depends on 15)

The system of claim 15, wherein the first interface is a vector interface and the second interface is a scalar interface.
