JP2006164077A - Memory system, control method therefor and method for maintaining data coherency - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To improve the efficiency of memory access including write access while maintaining data coherency. <P>SOLUTION: This memory system has: buses 10, 11; and a first device 13 and a second device 15 each having a memory 17 connected to the bus, a memory controller 16, and a cache. The memory controller includes a buffer 20 for temporarily storing write data when data of the cache and the second device perform write access to the memory. By temporarily storing the write data when data of the cache and the second device perform the write access to the memory in the buffer of the memory controller, the data coherency can be maintained simultaneously while eliminating the write access retrial of the second device. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

The present invention generally relates to a memory system and a control method thereof, and more particularly to a method for improving the efficiency of write access to a memory via a bus while maintaining data coherency.

In a system such as a personal computer (PC), devices such as a CPU and a memory (DRAM and the like) are connected to each other via a bus. Each device becomes a master device (bus master) and accesses a memory in which data is stored. A memory such as a DRAM (system memory) has a large storage capacity, but its access speed is slow. In order to increase the speed of access to frequently used data, the CPU uses a cache memory (hereinafter simply referred to as “cache”) such as SRAM. The cache has a small storage capacity, but can be accessed at a higher speed than a system memory such as a DRAM.

In a system having a cache, it is necessary to maintain coherency (data identity) between the cache and the main memory. As a method (algorithm) for maintaining this data coherency, there is a snoop method. FIG. 1 is a diagram for explaining a conventional snoop operation. In FIG. 1, the CPU bus 1 and the system bus 2 are connected by a bus bridge 3. CPU # 0 and CPU # 2 are connected to the CPU bus 1. The two CPUs have a cache. Device # 2, a memory controller, and a memory are connected to the system bus 2.

In the snoop method, the CPU # 0 having a cache monitors (snoop 5) the address of the data access 4 from another device # 2 (master device) (FIG. 1A). The CPU # 0 issues a retry request 6 when the access address matches the address of the data in its own cache and the data state has been changed (updated) by the standard MESI protocol or the like (FIG. 1B). )). In response to the retry request 6, the ongoing access of the master device # 2 is interrupted (FIG. 1 (b)). Further, a cache line composed of a plurality of data of consecutive addresses including the matched addresses in the cache is written back to the memory first (FIGS. 1C and 1D). Thereafter, the master device # 2 accesses the memory again to transfer the data, so that the coherency of the data is maintained (FIGS. 1E and 1F).

As is apparent from the operation of FIG. 1, when a retry request from a monitored (snoop) device occurs, the device in the middle of transfer needs to interrupt access and then access again. That is, overhead due to a snoop hit in write access occurs. This operation causes a decrease in bus utilization and an increase in device waiting time.

For example, Japanese Patent Laid-Open Publication No. 06-222993 discloses a conventional technique for speeding up memory access in a multiprocessor system using a snoop method. However, this publication does not disclose a technique for improving an operation delay or a decrease in bus utilization due to an access retry when a snoop hit occurs.
Published Patent Publication 06-222993

An object of the present invention is to improve the efficiency of memory access including write access while maintaining data coherency.

An object of the present invention is to solve a problem (operation delay, a decrease in bus utilization, etc.) due to an overhead at the time of access retry when a cache hit (snoop hit) occurs in write access in the snoop mode. It is to reduce.

The present invention comprises a bus, a memory connected to the bus, a memory controller, a first device having a cache, and a second device, wherein the memory controller has write access to the data in the cache and the second device. A memory system is provided that includes a buffer for temporarily storing write data in a case.

The present invention eliminates the write access retry of the second device by temporarily storing the cache data and the write data when the second device performs write access to the memory in the buffer of the memory controller. Data coherency can be maintained.

Since the present invention can eliminate the write access retry, it is possible to reduce problems caused by overhead (such as an operation delay and a decrease in bus utilization).

The present invention will be described with reference to the drawings. FIG. 2 is a diagram for explaining the outline of the method (operation) of the present invention. In FIG. 2, the CPU bus 10 and the system bus 12 are connected by a bus bridge 13. CPU # 0 (13) and CPU # 2 (14) are connected to the CPU bus 10. The two CPUs have a cache. Device # 2 (15), a memory controller (16), and a memory (17) are connected to the system bus 12. The memory (17) is a system memory such as a DRAM. The memory controller (16) has a buffer 20 for temporary storage of data. Although FIG. 2 shows a configuration in which two buses, the CPU bus 10 and the system bus 12, exist, a configuration in which each device is connected to one system bus may be used. Further, the number of devices to be connected may be any number as long as there are at least two master devices that can occupy the bus.

In the snoop method, the CPU # 0 (13) having a cache monitors (snoop 19) the address of the data access 18 from the other master device # 2 (15) (FIG. 2A). The CPU # 0 (13) issues a retry request 6 when the access address matches the address of the data in its own cache and the data state has been changed (updated) by the standard MESI protocol or the like. Master device # 2 (15) does not interrupt ongoing access. Device # 2 (15) writes the write data to the buffer 20 in the memory controller (FIG. 2 (b)). The data at the matched address in the cache of CPU # 0 is written back to the buffer 20 (FIGS. 2C and 2D). Thereafter, the write data and cache data in the buffer 20 are written into the memory (17) as one continuous data (FIG. 1 (d)).

Thus, in the present invention, it is not necessary to interrupt bus access corresponding to a retry request due to a snoop hit at the time of write access. Data coherency is maintained by postponing the cache data write-back process and temporarily storing it in a buffer in the memory controller. As a result, the arbitration and address phase on the system bus 11 can be reduced as compared with the conventional method of FIG. Further, in the memory bus between the memory controller 16 and the memory 17, three RAS address transfers, two CAS address transfers, and two data transfer periods (when continuous data transfer is counted as one period), Can be reduced once. When considering from the start to the completion of the write access, the access time can be reduced by about 20 to 30%, depending on the bus configuration and the memory speed.

FIG. 3 is a functional block diagram showing the configuration of the present invention. FIG. 3 includes a retry control circuit 101, an arbitration circuit 102, a memory controller 104, a tag control circuit 106, and a buffer 108. The tag control circuit 106 and the buffer 108 are actually built in the memory controller 104, but are illustrated as different blocks for the sake of explanation. Both of these circuits are connected to the system bus (11 in FIG. 2).

The retry control circuit 101 is a circuit that monitors an address retry signal and distributes it to other devices. When there is a retry signal input due to a snoop hit at the time of write access, the retry output is not asserted but the Retry-Hold signal and the corresponding Priority signal are asserted. The retry input other than the snoop hit at the time of write access is used as the retry output as it is. The arbitration circuit 102 has a function of making the request from the device the highest priority in response to the priority signal from the retry control circuit 101. If there is no Priority signal, normal arbitration is performed. The memory controller 104 controls the timing of the memory. This corresponds to a normal DRAM control circuit. Outputs an Access Complete signal when access is completed.

The tag control circuit 106 records the write data position in the buffer 108 for the write data at the time of the snoop hit. The buffer 108 has the same size as the cache line size (for example, 32 bytes) as a unit. Therefore, for example, in the case of a 32-byte cache line, the corresponding position of the lower 5 bits (2 5 = 32) is recorded as the data position. Further, the tag control circuit 106 generates a Write Strobe signal for writing subsequent data (cache-out data) from the cache other than the write data in the buffer 108. In addition, the tag control circuit 106 latches the cache-out data in the buffer 108 and then generates an Output Select signal for writing to the memory. The buffer 108 latches data (write data, cache-out data) on the bus according to the Write Strobe signal of the tag control circuit 106. Further, the buffer 108 outputs the latched data to the memory in response to the Output Select signal.

A description of each signal in FIG. 3 is given below.
-Retry-Hold: Indicates that a retry for write access has been accepted.
Cleared when cache-out access ends.
・ Priority-X: When a retry for write access is accepted, the next action
Set the device-X so that the
Signal to maximize priority ・ Access Complete: Signal indicating the end of memory access cycle ・ Data Strobe: Data input from the bus and data output to the memory
Timing signal • Data DIR: Signal indicating the data transfer direction • Write Strobe: Which byte is racked by address and byte enable
Signal to specify whether to output ・ Output Select: Specify which data is output during memory write
Signals-Bus Request: Bus request signal from each device-Bus Grant: Bus grant signal to each device-Retry from X: Retry signal from cached device-X-Retry to X: Retry signal to device-X

Next, the operation of the present invention in the configuration of FIG. 3 will be described.
(A) The device C (Device # 2) outputs the Bus Request C signal (110) to the arbitration circuit 102 and receives the Bus Grant C signal (112) as a reply. Further, the device C (Device # 2) outputs an address (Bus Address 114) to the bus in order to write to the memory.
(B) Each cache such as device A (CPU # 0) monitors (snoops) an address (Bus Address 114) on the bus.
(C) Here, assuming that the address in the cache of device A (CPU # 0) hits (snoop hit), device A (CPU # 0) sends a Retry from A signal (116) to the retry control circuit 101. Activate.
(D) The retry control circuit 101 receives from the memory controller 104 a Write Access signal (118) indicating that the access from the device C (Device # 2) is a write access. In this case, even if the retry control circuit 101 receives the Retry from A signal (116), it does not activate the Retry to C signal (120) that is a signal for interrupting the write access of the device C.
(E) The retry control circuit 101 activates the Retry Hold signal (122) to the tag control circuit 106. Further, the retry control circuit 101 sends (activates) a Priority-A signal (124) corresponding to the device A (CPU # 0) that has received the Retry from A signal (116) to the arbitration circuit 102.

(F) The device C (Device # 2) uses the Bus Address signal (114), the Byte Enable signal (126), and the Bus Control signal (128) to control the memory controller 104 and to perform Bus Data In (130). The above write data is written into the buffer 108. The write position is designated by the Write Strobe signal (136) output from the tag control circuit 106 that has received the Data Strobe signal and Data DIR signal (134) from the memory controller 104. Specifically, the write position depends on the lower 5 bits of the Bus Address (138) (in the case of a 32-byte cache line) and the data width of the Byte Enable signal (140). At this time, the byte position information written in the tag control circuit 106 is recorded.
(G) Since the memory controller 104 receives the Retry Hold signal (122), the memory controller 104 waits for cache (data) out from the cache without writing to the memory. Further, when the writing to the buffer 108 by the device C (Device # 2) is completed, the memory controller 104 sets the Access Complete signal (144) to Active.
(H) The device A (CPU # 0) that has requested Retry requests cache-out. The arbitration circuit 102 that has received the Priority-A signal (124) sets the priority of the Bus Request A (146) from the device A (CPU # 0) to the highest priority. The cache-out of device A (CPU # 0) is accepted immediately after the access of device C (Device # 2).

(I) The device A (CPU # 0) caches the snoop hit data out to the buffer 108. At this time, the write position is determined by the Write Strobe signal 136 so that the data previously written by the device C is not overwritten.
(J) When the writing to the buffer 108 by the device A (CPU # 0) is completed, the memory controller 104 outputs an Access Complete signal (144) to the retry control circuit 101.
(K) The retry control circuit 101 deactivates the activated Retry-Hold signal (122) and Priority-A signal (124).
(L) The memory controller 104 writes the data latched in the buffer 108 (write access data and cache-out data) to the memory as a series of data based on the address (TAG) information of the tag control circuit 106. . This completes the write access operation while maintaining data coherency.

It is a figure for demonstrating the conventional snoop operation | movement. It is a figure for demonstrating the outline | summary of the method (operation | movement) of this invention. It is a functional block diagram which shows the structure of this invention.

Explanation of symbols

1, 10 CPU bus 2, 12 System bus 3, 13 Bus bridge 4 Data access 5 Snoop 6 Retry request 13 CPU # 0
14 CPU # 2
15 Device # 2
16 Memory Controller 17 Memory 20 Buffer 101 Retry Control Circuit 102 Arbitration Circuit 104 Memory Controller 106 Tag Control Circuit 108 Buffer

Claims (10)

With bus,
A memory connected to the bus, a memory controller, a first device having a cache, and a second device;
The memory controller includes a buffer for temporarily storing cache data and write data when the second device performs write access to the memory. The memory system according to claim 1, further comprising a control circuit for temporarily storing the write data in the buffer when the write data hits the cache data. The memory according to claim 2, wherein the control circuit includes a retry control circuit for preventing the second device from retrying in response to an access retry request from the first device in the case of the cache hit. system. And a tag control circuit for storing a write position of the write data in the buffer and temporarily storing the cache data in the buffer without overwriting the write data at the write position. The memory system of claim 3. 5. The memory system of claim 4, wherein the cache data temporarily stored in the buffer is data that has already been updated in the cache. 6. The memory system according to claim 5, wherein the tag control circuit causes the write data and the cache data stored in the buffer to be written to the memory as continuous data. 2. The memory system of claim 1, wherein the bus includes a CPU local bus and a system bus, the two buses are connected by a bus bridge, and the first device includes a CPU connected to the CPU local bus. . In a memory system comprising a bus, a memory connected to the bus, a memory controller, a first device having a cache, and a second device, the memory controller having a buffer,
A method for controlling a memory system when a second device has write access to a memory, comprising:
(A) comparing the address of the write data in the write access with the address of the data in the cache;
(B) a step of confirming whether or not there is a data change of the matched address in the cache when the two addresses match;
(C) temporarily storing the write data in a buffer without causing the second device to retry access when the data is changed;
(D) temporarily storing the changed data in the cache in a buffer without overwriting the temporarily stored write data;
(E) writing the change data and the write data temporarily stored in the buffer to the memory as continuous data;
A method comprising: 9. The method of claim 8, wherein the comparing step (a) comprises the first device cache monitoring the second device write access. A method for maintaining data coherency in a snoop manner in a system in which a memory, a memory controller having a buffer, a plurality of bus masters, and a cache memory are connected to each other via a bus,
When a bus master write access is snoop hit and the cache memory data hit is updated, the bus master write data and A method comprising: writing cache memory update data into the memory as continuous data after temporarily storing the update data in the buffer.

Images