# US 2026/0154202 A1 · Cache, cache management method and electronic device

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

- Number: US 2026/0154202 A1
- Document ID: US20260154202A1
- Status: Published application
- Kind: A1
- Application number: 18/724,303
- Filed: 2023-09-27
- Published: 2026-06-04
- Earliest claimed: 2023-09-27
- Assignees: VeriSilicon Microelectronics (Shanghai) Co., Ltd.
- Applicants: Verisilicon Microelectronics (Shanghai) Co., Ltd.
- Inventors: Zhangxian SONG; Brian HUTSELL; Cheng CHI; Mike CAI; Rong LU; Kui QIN; Jianbing WU; Xiaoying CHEN
- Web page: https://patentgrep.com/patent/US20260154202A1

## CPC

- G06F 12/0855: Overlapped cache accessing, e.g. pipeline (G06F12/0846 takes precedence)
- G06F 12/0859: {with reload from main memory}
- G06F 12/0868: Data transfer between cache memory and other subsystems, e.g. storage devices or host systems
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Cache, cache management method, and electronic device. The cache includes: multiple cache lines, a first read request queue and a second read request queue; a first read request queue is configured for storing and sending a first read request to a memory controller; the first read request is configured for requesting data from memory and storing the data in the memory controller; the number of the first read requests stored in the first read request queue is greater than that of the multiple cache lines; the second read request queue is configured for storing and sending a second read request to memory controller; and the second read request corresponds one-to-one with the first read request, and the second read request is used to request data corresponding to the first read request from the memory controller when a cache line corresponding to the first read request is idle

## Claims

### Claim 1

A cache, wherein the cache comprises a plurality of cache lines, a first read request queue, and a second read request queue;
the first read request queue is configured to store and send a first read request to a memory controller; the first read request is configured to request data from a memory and storing the data in the memory controller; and a number of the first read request that can be stored in the first read request queue is greater than a number of the plurality of cache lines; and
the second read request queue is configured to store and send a second read request to the memory controller; and the second read request corresponds one-to-one with the first read request, and the second read request is configured to request data corresponding to the first read request to the memory controller in an event that a cache line corresponding to the first read request is idle.

### Claim 2 (depends on 1)

The cache according to claim 1, wherein the cache further comprises:
a third read request queue, which is configured to store a cache line index corresponding to the first read request, and to store the data corresponding to the first read request in the cache line corresponding to the first read request based on the cache line index of the first read request.

### Claim 3 (depends on 1)

The cache according to claim 1, wherein the cache further comprises:
the cache controller, which is configured to allocate a cache line for a request sent by a processor, wherein the request is a request that does not hit the cache; and
a first buffer, which is configured to determine whether a read-after-write situation exists in the cache line corresponding to the request, wherein if the read-after-write situation does not exist in the cache line corresponding to the request, a first read request is generated and sent to the first read request queue; and if the read-after-write situation exists in the cache line corresponding to the request, the request is stored and whether the read-after-write situation exists in a cache line corresponding to a next request of the request is determined.

### Claim 4 (depends on 3)

The cache according to claim 3, wherein the first buffer is further configured to generate a first read request corresponding to a request when the read-after-write situation corresponding to the request saved in the first buffer is released.

### Claim 5 (depends on 3)

The cache according to claim 3, wherein the first buffer comprises a group of flip-flops with the same number as that of the cache lines, wherein each flip-flop corresponds to one cache line, the flip-flop is configured to store a request for which a read-after-write situation exists, and the cache line corresponding to the request is the same as the cache line corresponding to the flip-flop storing the request.

### Claim 6 (depends on 3)

The cache according to claim 3, wherein the cache controller is configured to allocate a cache line to a request sent by the processor from the cache lines other than that corresponding to a target request, wherein the target request is a request stored in the first buffer.

### Claim 7 (depends on 1)

The cache according to claim 1, wherein the cache further comprises: a second buffer and a send queue; and
the second buffer is configured to store a write request, a number of pending requests, and a number of completed requests for respective cache lines; and when the total number of requests corresponding to one cache line is the same as the number of completed requests corresponding to the cache line, the write request corresponding to the cache line is sent to the send queue.

### Claim 8 (depends on 7)

The cache according to claim 7, wherein the second buffer comprises a group of flip-flops with the same number as that of the cache lines, wherein each flip-flop corresponds to one cache line, and the flip-flop is configured to store the write request, the total number of requests, and the number of completed requests of its corresponding cache line.

### Claim 9 (depends on 1)

The cache according to claim 1, wherein the cache further comprises: an arbitration module, wherein the arbitration module is configured to determine a pending cache line based on a state of each cache line and a preset rule; and/or
the cache further comprises: a multi-thread queue, wherein the multi-thread queue comprises a plurality of threads, wherein each thread corresponds to one cache line, and each thread is configured to store pending requests for its corresponding cache line.

### Claim 10 (depends on 1)

A cache management method, wherein the cache management method is applied the cache according to claim 1, wherein the cache comprises the plurality of cache lines, the first read request queue and the second read request queue, and the method comprises:
the first read request queue sending the first read request to the memory controller, wherein the first read request is configured to request data from the memory and store the data in the memory controller; and
the second read request queue sending the second read request to the memory controller when the cache line corresponding to the first read request is idle, wherein the second read request is configured to request data corresponding to the first read request from the memory controller.

### Claim 11 (depends on 1)

An electronic device, wherein the electronic device comprises: a processor and the cache according to claim 1.

### Claim 12 (depends on 11)

The electronic device according to claim 11, wherein the cache further comprises:
a third read request queue, which is configured to store a cache line index corresponding to the first read request, and to store the data corresponding to the first read request in the cache line corresponding to the first read request based on the cache line index of the first read request.

### Claim 13 (depends on 11)

The electronic device according to claim 11, wherein the cache further comprises:
the cache controller, which is configured to allocate a cache line for a request sent by a processor, wherein the request is a request that does not hit the cache; and
a first buffer, which is configured to determine whether a read-after-write situation exists in the cache line corresponding to the request, wherein if the read-after-write situation does not exist in the cache line corresponding to the request, a first read request is generated and sent to the first read request queue; and if the read-after-write situation exists in the cache line corresponding to the request, the request is stored and whether the read-after-write situation exists in a cache line corresponding to a next request of the request is determined.

### Claim 14 (depends on 13)

The electronic device according to claim 13, wherein the first buffer is further configured to generate a first read request corresponding to a request when the read-after-write situation corresponding to the request saved in the first buffer is released.

### Claim 15 (depends on 13)

The electronic device according to claim 13, wherein the first buffer comprises a group of flip-flops with the same number as that of the cache lines, wherein each flip-flop corresponds to one cache line, the flip-flop is configured to store a request for which a read-after-write situation exists, and the cache line corresponding to the request is the same as the cache line corresponding to the flip-flop storing the request.

### Claim 16 (depends on 13)

The electronic device according to claim 13, wherein the cache controller is configured to allocate a cache line to a request sent by the processor from the cache lines other than that corresponding to a target request, wherein the target request is a request stored in the first buffer.

### Claim 17 (depends on 11)

The electronic device according to claim 11, wherein the cache further comprises: a second buffer and a send queue; and
the second buffer is configured to store a write request, a number of pending requests, and a number of completed requests for respective cache lines; and when the total number of requests corresponding to one cache line is the same as the number of completed requests corresponding to the cache line, the write request corresponding to the cache line is sent to the send queue.

### Claim 18 (depends on 17)

The electronic device according to claim 17, wherein the second buffer comprises a group of flip-flops with the same number as that of the cache lines, wherein each flip-flop corresponds to one cache line, and the flip-flop is configured to store the write request, the total number of requests, and the number of completed requests of its corresponding cache line.

### Claim 19 (depends on 11)

The electronic device according to claim 11, wherein the cache further comprises: an arbitration module, wherein the arbitration module is configured to determine a pending cache line based on a state of each cache line and a preset rule; and/or
the cache further comprises: a multi-thread queue, wherein the multi-thread queue comprises a plurality of threads, wherein each thread corresponds to one cache line, and each thread is configured to store pending requests for its corresponding cache line.

### Claim 20 (depends on 10)

The cache management method according to claim 10, wherein the cache further comprises:
a third read request queue, which is configured to store a cache line index corresponding to the first read request, and to store the data corresponding to the first read request in the cache line corresponding to the first read request based on the cache line index of the first read request.
