# US 6,732,242 B2 · External bus transaction scheduling system

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

- Number: US 6,732,242 B2
- Document ID: US6732242B2
- Status: Granted
- Kind: B2
- Application number: 10/113,546
- Filed: 2002-03-28
- Published: 2003-10-02
- Granted: 2004-05-04
- Earliest claimed: 2002-03-28
- Assignees: Intel Corporation
- Inventors: David L. Hill; Paul D. Breuder; Robert J. Greiner; Derek T. Bachand
- Web page: https://patentgrep.com/patent/US6732242B2

## CPC

- G06F 13/161: {with latency improvement}
- G06F 9/383: {Operand prefetching (cache prefetching G06F12/0862)}
- G06F 12/0862: with prefetch
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A transaction management system is described for scheduling requests on an external bus. The system includes a number of queue registers to store requests and a controller coupled to queue registers to schedule external bus transactions for an agent that processes read requests, prefetch requests and write requests. The controller posts at least one write request to an external bus every defined number of transactions if at least one non-posted write request is stored in the queue registers.

## Claims

### Claim 1

A processor comprising:
an execution core to process read requests and write requests;
a prefetch unit to process prefetch requests; and
a transaction management system coupled to said execution core and said prefetch unit to schedule read, prefetch and write requests generated thereby, said transaction management system including a plurality of queue registers to store a plurality of requests, and a controller to post at least one write request to an external bus every defined number of transactions if at least one non-posted write request is stored in the queue registers.

### Claim 2 (depends on 1)

The processor of claim 1, wherein said controller schedules external bus transaction such that two consecutive write requests are posted to the external bus after four read requests have been posted to the external bus if at least two non-posted write requests are stored in the queue registers.

### Claim 3 (depends on 1)

The processor of claim 1, wherein said controller schedules external bus transactions such that at least one write request is posted to the external bus every eight transactions if at least one non-posted write request is stored in the queue registers.

### Claim 4 (depends on 1)

The processor of claim 1, wherein said controller posts at least one write request to the external bus after eight read requests have been posted to the external bus if at least one non-posted write request is stored in the queue registers.

### Claim 5 (depends on 1)

The processor of claim 1, wherein said controller comprises a priority generating logic to generates a relative priority for each type of request and a selection logic to schedules requests to be posted to the external bus based on said relative priority.

### Claim 6 (depends on 5)

The processor of claim 5, wherein said controller further comprises an age matrix to maintain an account of the ages of requests stored in the queue registers and masks to permit the age matrix to prioritize among those requests based upon request types.

### Claim 7 (depends on 6)

The processor of claim 6, wherein said age matrix is embodied in the form of a triangular age matrix.

### Claim 8 (depends on 6)

The processor of claim 6, wherein said controller generates priority based on (1) past history of request transactions posted to the external bus and (2) type of requests stored in the queue registers.

### Claim 9 (depends on 1)

The processor of claim 1, wherein each request causes a cacheline of data to transfer via the external bus.

### Claim 10

A system comprising:
a main memory to store a plurality of data elements; and
a processor coupled to said main memory via an external bus, said processor including an execution core to process read requests and write requests and a plurality of queue registers to store a plurality of requests, said processor including a controller coupled to said plurality of queue registers to schedule external bus transactions requesting data to be written to said main memory or requesting data to be read from said main memory, wherein said controller posts at least one write request to said external bus every defined number of transactions if at least one non-posted write request is stored in the queue registers.

### Claim 11 (depends on 10)

The system of claim 10, wherein said processor further comprises a prefetch unit to process prefetch requests.

### Claim 12 (depends on 10)

The system of claim 10, wherein said controller schedules external bus transactions such that at least one write request is posted to the external bus every eight transactions if at least one non-posted write request is stored in the queue registers.

### Claim 13 (depends on 10)

The system of claim 10, wherein said controller posts at least two consecutive write requests to the external bus after four read requests have been posted to the external bus if at least two non-posted write requests are stored in the queue registers.

### Claim 14 (depends on 10)

The system of claim 10, wherein said controller posts at least one write request to the external bus after eight read requests have been posted to the external bus if at least one non-posted write request is stored in the queue registers.

### Claim 15 (depends on 10)

The system of claim 10, wherein said controller comprises a priority generating logic to generates a relative priority for each type of request and a selection logic to schedules requests to be posted to the external bus based on said relative priority.

### Claim 16 (depends on 15)

The system of claim 15, wherein said controller further comprises an age matrix to maintain an account of the ages of requests stored in the queue registers and masks to permit the age matrix to identify the oldest request among those requests chosen based upon request types.

### Claim 17 (depends on 15)

The system of claim 15, wherein said controller generates priority based on (1) past history of request transactions posted to the external bus and (2) type of requests stored in the queue registers.

### Claim 18 (depends on 15)

The system of claim 15, wherein said controller periodically assigns priority to write requests to prevent write requests from accumulating in the queue registers.

### Claim 19 (depends on 10)

The system of claim 10, wherein each request causes a cacheline of data to transfer via the external bus.

### Claim 20

A method comprising:
storing a plurality of requests;
scheduling external bus transactions for an agent that processes read requests, prefetch requests and write requests such that at least one write request is posted to an external bus every defined number of transactions if at least one write request is stored.

### Claim 21 (depends on 20)

The method of claim 20, wherein said external bus transactions are scheduled such that at least one write request is posted to an external bus every eight transactions if at least one non-posted write request is stored in the queue registers.

### Claim 22 (depends on 20)

The method of claim 20, further comprising posting at least two consecutive write requests to the external bus after four read requests have been posted to the external bus if at least two non-posted write requests are stored in queue registers.

### Claim 23 (depends on 20)

The method of claim 20, further comprising posting at least one write request to the external bus after eight read requests have been posted to the external bus if at least one non-posted write request is stored in queue registers.

### Claim 24 (depends on 20)

The method of claim 20, further comprising generating a relative priority for each type of request and scheduling requests to be posted to the external bus based on said relative priority.

### Claim 25 (depends on 24)

The method of claim 24, wherein said priority for each type of request is generated based on (1) past history of request transactions posted to the external bus and (2) type of requests stored in the queue registers.

### Claim 26 (depends on 20)

The method of claim 20, wherein each request causes a cacheline of data to transfer via the external bus.
