This application is based upon and claims the benefit of priority of the prior Japanese Patent Application No. 2017-050471, filed on Mar. 15, 2017, the entire contents of which are incorporated herein by reference.
The embodiments discussed herein are related to a memory controller, an information processor, and a memory control method.
In the case where product development is carried out based on a memory trend assumed at the time of the system development planning, there is a risk that memory operation in a specific case or at a specific timing is unknown at the time of actually designing details of the system because the specification of the memory to be used is not fixed yet.
A related art is disclosed in Japanese Laid-open Patent Publication No. 10-149318.
According to an aspect of the embodiments, a memory controller includes: a memory access control circuit which receives a write command and write data from a processor and controls a writing operation to a memory; and a number-of-writing-operations control circuit which performs control to execute the writing operation to the memory multiple times, based on the write command and the write data.
The object and advantages of the invention will be realized and attained by means of the elements and combinations particularly pointed out in the claims.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are not restrictive of the invention, as claimed.
For example, a memory into which a memory chip and a memory interface converter are integrated is developed for Hybrid Memory Cube (HMC) and the like. For example, since a memory interface converter includes complicated logic circuits, sometimes the fix of the specification delays. For this reason, there is a case where the operation of the memory in a certain case or at certain timing is unknown, or a case where an unclear part in the specification, which had not been noticed at a design stage, is found at an evaluation stage after the production.
For example, there is a case where a delay of memory development causes insufficient evaluation at the memory manufacturer. For example, there is a possibility that a memory in which memory chips are stacked and densely packaged, such as HMC, may potentially have a new problem factor, such as a crosstalk noise caused by the stacking.
To prepare for such cases, for example, a memory controller is provided with functions which makes it possible to follow an actual behavior of the memory, by including various risk avoidance functions for unclear parts in the specification of the memory, problems which are not removed before shipping, and the like.
For example, a memory controller receives a write command and write data from a computation unit (for example, a micro processing unit (MPU)) and controls the writing operation to a memory.
As described above, for example, for memories such as HMC, there may be a case where write processing to the memory is not reliably executed with various factors, such as specification of a memory interface converter, a crosstalk noise resulted from stacking memory chips, or a timing problem.
For example, the read-modify-write command is a command to read data from a memory, replace a part of the data with other data, and write back the data to the memory. There is a possibility that a problem occurs when the read-modify-write operation is executed. It is caused because, for example, specification for the read-modify-write operation is unclear, or data to be substituted (written back to the memory) are dropped at a specific timing, which is resulted from the inside of the memory chip, the memory interface converter, or the memory access control circuit side.
Occurrence of such a dropout of write data to a memory is not limited to memories such as HMC or at the time of executing the read-modify-write command, but it is possible that a dropout occurs in writing data to various memories.
For example, to re-execute write processing, a special circuit is provided to be implemented in the computation unit, or software processing is added. For example, whether data were written to a memory correctly is checked when the written data are read, and a data error is detected by a checkpoint set by software. For example, data written to a memory are not read soon in some cases. Hence, in the case where the writing operation is not executed properly, it may be difficult to investigate when and in what write data an error occurred if the symptom is not easily reproduced.
As illustrated in
The memory controller 50, for example, receives a write command Cmd and write data Wd from the computation unit 1 and controls writing operations to the memory 2. Although the memory controller 50 executes not only writing operations from the computation unit 1 to the memory 2, but reading operation from the memory 2 and others, descriptions are provided mainly for the writing operation and the read-modify-write operation.
The memory controller 50 includes a command queue (Cmd-Q) 54 to store commands Cmd from the computation unit 1 and a valid queue (Valid-Q) 53 to store valid signals indicating whether commands are valid or invalid. The memory controller 50 includes a command multiplexer 54a to select a command stored in the command queue 54, and a valid signal multiplexer 53a to select a valid signal stored in the valid queue 53.
The memory controller 50 includes a write data queue (Data-Q) 55 to store write data Wd from the computation unit 1, a read data queue 56 to store read data Rd read from the memory 2, and an AND gate 42. The memory controller 50 includes a write data multiplexer 55a to select write data stored in the write data queue 55 and a top of queue (TOQ) 51 to specify a head queue in each of the multiplexers 53a, 54a, and 55a.
The top of queue 51, for example, increments a number by +1 (52) one after another to control the multiplexers 53a, 54a, and 55a. The AND gate 42 performs a logical AND between the outputs of the multiplexers 53a and 54a, generates an acknowledgement (response signal) Ack, and outputs it to the computation unit 1. The acknowledgement Ack is also inputted to the top of queue 51. The top of queue 51 receives the acknowledgement Ack, controls the multiplexers 53a, 54a, and 55a with the incremented signal, for example, and executes the next processing.
In the information processor illustrated in
For example, there may be a case where write processing to the memory 2 is not reliably executed with various factors, such as specification of the memory 2, a noise, or a timing problem. For example, in the case where the memory 2 is HMC or the like, there may be the occurrence of a crosstalk noise due to stacking memory chips or a timing problem at the memory interface converter, and problems often occur when the read-modify-write command is executed. The problem of a dropout of data written to a memory like this is not limited to memories such as HMC, or not limited at the time when the read-modify-write command is executed. The problem also may occur at the time of writing data to various memories.
As illustrated in
The memory 2, which is HMC or the like, includes a memory interface converter 21 and a memory chip 22 formed of stacked multiple memory chips (dice: DRAM chips). This embodiment is not limited to HMC, but may be widely applied to various memories. This also applies to other embodiments to be described later.
The memory access control circuit 3 includes a command queue (Cmd-Q) 34 to store write commands Cmd from the computation unit 1 and a valid queue (Valid-Q) 33 to store valid signals indicating whether commands are valid or invalid. The memory access control circuit 3 also includes a command multiplexer 34a to select a command stored in the command queue 34 and a valid signal multiplexer 33a to select a valid signal stored in the valid queue 33.
The memory access control circuit 3 further includes a write data queue (Data-Q) 35 to store write data Wd from the computation unit 1 and a read data queue 36 to store read data Rd read from the memory 2. The memory access control circuit 3 includes a write data multiplexer 35a to select write data stored in the write data queue 35 and a top of queue (TOQ) 31 to specify a head queue in each of the multiplexers 33a, 34a, and 35a. The top of queue 31, for example, increments a number by +1 (32) one after another to control the multiplexers 33a, 34a, and 35a.
The number-of-writing-operations control circuit 4 includes a number-of-writing-operations setting circuit 41 to set the number of writing operations to the memory 2, and an AND gate 42. Here, the AND gate 42 corresponds to the AND gate 42 in the memory controller 50 illustrated in
The number-of-writing-operations setting circuit 41, for example, sets the number of writing operations to the memory 2 for a single memory write command, based on an initial setting by the BIOS 6. The number-of-writing-operations setting circuit 41 includes a register (num) 411 for setting the number of writing operations specified by the BIOS 6, a counter (cnt) 414 to count the number of writing operations to the memory 2, and a comparator 413. Here, the counter 414, for example, is incremented by +1 (412) one after another every time a writing operation to the memory 2 is executed.
When the output (count value) of the counter 414 agrees to the value set in the register 411, the comparator 413 outputs to the top of queue 31, an end signal Se indicating that a specified number of writing operations have been executed. The top of queue 31, receiving the end signal Se, for example, controls the multiplexers 33a, 34a, and 35a with the incremented signal to execute the next processing.
In the information processor illustrated in
The computation unit 1 outputs the write command Cmd and the write data Wd to the memory controller 5 (memory access control circuit 3). The write command Cmd and the write data Wd stored in the queues 34 and 35, respectively, are selected by the multiplexers 34a and 35a based on the signal from the top of queue 31, and outputted to the memory 2. Here, the outputs of the multiplexers 34a and 35a are outputted continuously and used in the n writing operations.
When the top of queue 31 selects a memory write instruction, the memory write instruction is given to the memory interface converter 21 and a writing operation to the memory chip 22 is executed, for example. In this case, every time a memory write instruction is given to the memory interface converter 21, the count value (cnt) in the counter 414 is incremented by +1. Then, until the count value reaches the set value (num) in the register 411, the same memory write instruction is repeatedly given to the built-in memory in the memory interface converter 21.
For example, as illustrated in
As illustrated in
For example, in the case where num=4 is set as an initial setting by the BIOS 6, the memory write instruction is given four times. Note that since memory write processing may be throw-off type processing, it is possible to make the response (Ack) to the computation unit 1 at the first memory write instruction.
As described above, in the information processor (memory controller 5), dropout of write processing to the memory may be avoided and, for example, therefore, an isolation at a failure may be performed quickly and the reliability of the system may be improved. The quick isolation at a failure and the improvement of the system reliability described above may be achieved without changing a circuit of the computation unit or adding software processing. This effect is also obtained from the later-described embodiments.
For example, as illustrated in
The multiplexer 44 selects the write command from the command queue 34 (command multiplexer 34a) or the read command (Read Cmd) to output it to the memory 2, and is controlled by the output of the comparator 413. The comparator 46 compares write data Mwd to the memory 2 and read data Mrd from the memory 2. If these two data equal, the comparator 46 outputs a high level “H”. The AND gate 45 receives the output of the comparator 46 and the output of the timing adjuster 47 which delays the output of the comparator 413. When both are “H”, the AND gate 45 outputs an agreement signal (match) of “H” to the computation unit 1.
As illustrated in
The divide-write control circuit 48 includes a least-significant-bit detector 481, a divide-write processor 482, and multiplexers (selection circuits) 483 and 484. The least-significant-bit detector 481 determines the higher half write data Wd1 and the lower half write data Wd2 based on the least significant bit of the counter 414, and controls the multiplexer 483. The divide-write processor 482 controls the multiplexer 484 which switches the outputs of the multiplexer 483 and the AND gate 42 to output one of these outputs to the memory 2.
As illustrated in
In the target setting unit 495, for example, a target command described above for which multiple writing operations are executed for a single write command is set by the initial setting of the BIOS 6. The comparator 491 compares the outputs of the target setting unit 495 and the command multiplexer 34a. If a command is the target command for the processing, multiple writing operations are performed using the number-of-writing-operations setting circuit 41 and the like. Note that if the outputs of the target setting unit 495 and the command multiplexer 34a do not agree to each other, an ordinary writing operation (single writing operation) is executed. It goes without saying that the target-command setting circuit 49 illustrated in
As described above, the information processor (memory controller 5) illustrated in
According to the foregoing embodiments, when a writing operation to the memory 2 is instructed to the memory controller 5, it is possible to execute the writing operation to the memory multiple times for a single write instruction. Writing the same data to the same address in a memory multiple times does not cause any problem. Since the same writing operation is executed multiple times, even in the case where a dropout of writing occurs during the writing operations for some reason, if the data are written correctly at least once, the write processing is successful.
However, since the writing operation to the memory 2 is executed multiple times for a single write instruction, although the memory write is throw-off type processing, if the data queue runs out, influence on the performance occurs. For this reason, for example, it is preferable that this function may be enabled by the initial setting from the BIOS or the like in the case where the evaluation does not progress because a writing of data occurs during writing operations for some reason at the time of evaluation before shipment, or in a similar case. By providing a function in the memory controller 5 (number-of-writing-operations control circuit 4) to compare write data and the read data, it is possible to judge whether the written data are correct, immediately after the memory write operation, which facilitates investigation in the case where the written data are not correct. Further, in the case where a problem is found after the evaluation is completed and it is impossible to fix the problem before the shipment, for example, it is possible to take the foregoing measures for a minimum number of commands.
All examples and conditional language recited herein are intended for pedagogical purposes to aid the reader in understanding the invention and the concepts contributed by the inventor to furthering the art, and are to be construed as being without limitation to such specifically recited examples and conditions, nor does the organization of such examples in the specification relate to a showing of the superiority and inferiority of the invention. Although the embodiments of the present invention have been described in detail, it should be understood that the various changes, substitutions, and alterations could be made hereto without departing from the spirit and scope of the invention.
Number | Date | Country | Kind |
---|---|---|---|
2017-050471 | Mar 2017 | JP | national |
Number | Name | Date | Kind |
---|---|---|---|
5559956 | Sukegawa | Sep 1996 | A |
6324624 | Wolrich | Nov 2001 | B1 |
6490642 | Thekkath | Dec 2002 | B1 |
7315915 | Fukuda | Jan 2008 | B2 |
8320067 | Tsai | Nov 2012 | B1 |
8725975 | Moyer | May 2014 | B2 |
9672882 | Jeter | Jun 2017 | B1 |
9911478 | Peddu | Mar 2018 | B1 |
20020174310 | Ueyama | Nov 2002 | A1 |
20020174392 | Chang | Nov 2002 | A1 |
20020188816 | Johnson | Dec 2002 | A1 |
20060018162 | Kawai | Jan 2006 | A1 |
20080028177 | Bartley | Jan 2008 | A1 |
20080313387 | Shibata | Dec 2008 | A1 |
20090161453 | Giovannini | Jun 2009 | A1 |
20130339320 | Noda | Dec 2013 | A1 |
20140059280 | Im | Feb 2014 | A1 |
20140237205 | Takefman | Aug 2014 | A1 |
20140258606 | Nakanishi | Sep 2014 | A1 |
20160267975 | Takeuchi | Sep 2016 | A1 |
20160313917 | Xu | Oct 2016 | A1 |
20160322074 | Niu | Nov 2016 | A1 |
20170093597 | Ranck | Mar 2017 | A1 |
20170148501 | Son | May 2017 | A1 |
20180136851 | Batra | May 2018 | A1 |
20180267745 | Sakurai | Sep 2018 | A1 |
Number | Date | Country |
---|---|---|
10-149318 | Jun 1998 | JP |
Number | Date | Country | |
---|---|---|---|
20180267745 A1 | Sep 2018 | US |