IE911094A1 - A Data Processing Method - Google Patents
A Data Processing MethodInfo
- Publication number
- IE911094A1 IE911094A1 IE109491A IE109491A IE911094A1 IE 911094 A1 IE911094 A1 IE 911094A1 IE 109491 A IE109491 A IE 109491A IE 109491 A IE109491 A IE 109491A IE 911094 A1 IE911094 A1 IE 911094A1
- Authority
- IE
- Ireland
- Prior art keywords
- memory
- stable
- bank
- intra
- stable memory
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11C—STATIC STORES
- G11C29/00—Checking stores for correct operation ; Subsequent repair; Testing stores during standby or offline operation
- G11C29/70—Masking faults in memories by using spares or by reconfiguring
- G11C29/74—Masking faults in memories by using spares or by reconfiguring using duplex memories, i.e. using dual copies
-
- G—PHYSICS
- G09—EDUCATION; CRYPTOGRAPHY; DISPLAY; ADVERTISING; SEALS
- G09G—ARRANGEMENTS OR CIRCUITS FOR CONTROL OF INDICATING DEVICES USING STATIC MEANS TO PRESENT VARIABLE INFORMATION
- G09G5/00—Control arrangements or circuits for visual indicators common to cathode-ray tube indicators and other visual indicators
- G09G5/36—Control arrangements or circuits for visual indicators common to cathode-ray tube indicators and other visual indicators characterised by the display of a graphic pattern, e.g. using an all-points-addressable [APA] memory
- G09G5/39—Control of the bit-mapped memory
- G09G5/393—Arrangements for updating the contents of the bit-mapped memory
Landscapes
- Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a method of operation of a stable memory circuit having two stable memory banks (bank 0, bank 1). Each bank may comprise one or more VRAMs (1). A stable memory operation involves writing from a source location (6) in a VRAM to a temporary location (5) in the same VRAM and subsequently writing the data from the temporary location (5) to a destination location (10) in the same VRAM. This allows stable memory operations to be carried out very quickly because communication between memory devices is not required.
Description
Stable Memory Operations
The invention relates to stable memory operations carried out in a stable memory circuit comprising at least two memory banks which may be interconnected by a stable data path.
European Patent Specification No. EP 0418030A2 (TCD, Coghlan, Jones) describes such a circuit.
An object of the invention is to provide stable memory operations which may be carried out much more quickly than heretofore. Another object is to minimise the delay to host processor operations. A still further object is to provide deterministic stable memory operations, (i.e. the duration of which may be predicted in advance), and in which the duration is independent of memory size.
According to the invention, there is provided a stable memory operation carried out in a stable memory circuit comprising at least two memory banks each comprising at least one memory device, the stable memory operation comprising the steps of writing data from a source location of a memory device to a temporary location in the same device, and subsequently writing the data to a destination location in the same device to complete an intra-bank transfer.
- 2 In one embodiment, temporary location is in an auxiliary memory area of the device. The auxiliary memory area may be a register.
In another embodiment, the device is a video random access 5 memory, and the temporary location is the serial access register of the video random access memory. In this latter embodiment, the video random access memory has a plurality of serial access registers, one of which is used for the intrabank transfer, another serial access register being for use in another stable memory operation carried out simultaneously.
In one embodiment, the stable memory operation also includes an inter-bank copy, logical operation time of a host processor being reduced by performing the intra-bank transfer in advance. In this embodiment, the intra-bank transfer may be carried out on a copy-on-write basis.
In another embodiment, the intra-bank transfer is carried out simultaneously in at least two memory devices being replicates of each other. The intra-bank transfer may be carried out simultaneously in all devices, resulting in data in each memory device being checkpointed in a deterministic time, independently of memory size.
The invention will be more clearly understood from the following description of some preferred embodiments thereof,
- 3 given by way of example only with reference to the accompanying drawings, in which:Fig. 1 is a diagram showing a memory chip for use in a stable memory circuit; and
Figs. 2 to 6 inclusive are diagrams showing stable memory circuits at various stages of stable memory operations being carried out.
Referring to the drawings, and initially to Fig. 1 there is illustrated a memory device, namely, a video random access memory (VRAM) indicated generally by the reference numeral 1 for use in a memory bank of a stable memory circuit. The VRAM 1 comprises a conductor 2 for communication with a host processor and a stable memory manager circuit, and a conductor 3 for a stable data path connecting the bank in which the VRAM
1 is located with another stable memory bank. The VRAM 1 also includes a 512 x 512 x 4 bit memory array 4 and a 512 x 4 bit serial access register 5.
As stated above, the VRAM 1 forms part of a stable memory bank, there being two banks interconnected by a stable data path in a stable memory circuit. Each bank would generally comprise many VRAMs 1, however, it is possible that a bank may have only one VRAM 1.
- 4 A stable memory operation may be carried out within the VRAM 1. This operation involves writing data from a source location in the memory array 4 to a temporary location in the serial access register 5. Subsequently, the data is written from the temporary location to a destination location within the memory array 4. This operation is hereinafter referred to as an intra-bank transfer because it occurs within a single memory device of a bank.
In many cases, it would be more practical to carry out the 10 intra-bank transfer for a block (row) of locations of the memory array 4 at once. This is particularly true where the memory device is a VRAM, as the serial access register is wide. Further, in many situations it would be suitable to carry out the intra-bank transfer for a memory address space comprising several blocks.
Because communication between memory devices is not required for the intra-bank transfer, the transfer may be carried out extremely quickly and results in stable memory operations including this transfer being carried out quickly. In practice, the transfer minimises the delay to host processor operations after it has requested a stable memory operation. Examples are given below.
The VRAM 1 may have more than one serial access register 5, in which case one register may be used for an intra-bank transfer, and another for a different stable memory operation.
- 5 Referring now to Fig. 2, a stable memory operation including an intra-bank transfer involving a VRAM 1 is illustrated. A host write access is attempted to a memory block 6 of the VRAM 1 as indicated by the arrow 7 shown in Fig. 2(a). However, if this block is marked (M) for copy-on-write, then before the host write is carried out, a separate stable memory manager circuit connected to the VRAM 1 via the host conductor 2 copies the contents of the memory block 6 temporarily to the serial access register 5 as indicated by the arrow 8 of Fig.
2(b). As indicated by the arrow 9 of Fig. 2(c), the contents are then written from the serial access register 5 to another memory block 10 within the same VRAM 1. As shown in Fig. 2(d), the host memory write may then take place to the memory block 6 as indicated by the arrow 11. This operation is referred to as copy-on-write and may be used in memory management, stable memory capability management, transaction processing, or persistent storage management.
Marking for copy-on-write may be carried out either by the host processor or by the stable memory manager circuit. If the host processor does this within its memory management unit, then the host processor's write fault handler would have to request the intra-bank transfers from the manager circuit. If the manager circuit does the marking, then it would have to schedule the intra-bank transfers.
- 6 For some stable memory operations, for example, atomic actions, checkpoints or transactions, it is necessary that host writes do not occur to those areas of memory involved until the stable memory operation has been completed. This restriction may be removed by marking those areas of memory for copy-on-write at the start of the stable memory operation. When a host write access is attempted to the relevant memory location, the manager circuit may very rapidly transfer the contents of that source location using an intra-bank transfer as described above, after which the host write may be allowed to the source location. The advantage is that copies are taken only if necessary, and space for copying to is only allocated on demand. Further, because of the speed with which an intra-bank transfer may take place, the delay to the host processor after a stable memory operation has been requested is very short.
Referring now to Fig. 3, there are illustrated two stable memory banks, namely bank 0 and bank 1 interconnected by a stable data path 3, and each bank comprising a single VRAM 1.
With reference to Fig. 3, there is now described an atomic commit operation, referred to as a FAST commit. This operation involves the sequence of actions below:(a) allocate a stable space SO in bank 0, and a stable space SI in bank 1 (Fig. 3(a)),
- Ί (b) the host processor carries out work in the space SO (Fig. 3(b)), (c) the space SO is marked (M) for copy-on-write (Fig. 3(c)), (d) carrying out an inter-bank copy from space SO to space SI via the stable data path 3 and continue to work in the space SO (Fig. 3(d)), (e) if required, compare the contents of spaces SO and SI via the stable data path 3 (Fig. 3(e)), (f) the host processor continuing work in the space SO (Fig. 3(f)), (g) if, as shown in Fig. 3(g), a host write access is attempted to space SO during the physical commit (steps (d) and (e) above) the manager circuit may allocate an extra space S2 in bank 0 and then very rapidly copy-on-write SO to S2 using an intra-bank transfer (Figs. 3(h) and 3(i)). After the intrabank transfer, the host write may be allowed to proceed .
Referring to the above operation, it will be noted that only a single memory space SO is committed and is thus marked for
- 8 copy-on-write at the start of the stable memory operation in step (c). After step (c), the commit is logically complete (but not physically complete), and the host processor may continue to work in the space SO while the physical commit proceeds. The commit is physically complete after step (e).
If, after the copy-on-write, the attempted host write proceeds to the source space SO of the intra-bank transfer (Fig. 3(j), then at the end of the stable memory operation, the manager circuit may need to perform post-processing to cater for the copy-on-write. If, however, the host write proceeds to the destination space S2 of the intra-bank transfer (Fig. 3(k)), then no post-processing will be necessary, but after the stable memory operation, the host work will have to continue to this destination space rather than to the source space.
Alternatively, any restrictions on writes to locations involved in stable memory operations may be removed by performing a 3-way stable memory operation, where the primary locations of memory are first copied to secondary locations of memory via intra-bank transfers, then the stable memory operation is conducted between one of these and further tertiary locations of memory. Once the intra-bank transfers are complete, the host processor may continue its operations within the other memory locations (those not involved in the stable memory operation). The advantage here is that the host processor is delayed only for the time taken by the intra-bank
- 9 transfer, possibly as short as two manager circuit memory accesses .
The following are some examples of 3-way atomic commit operations described with reference to Figs. 4 and 5. In
Figs. 4 and 5, there are again two memory banks, bank 0 and bank 1, each of which, for clarity and simplicity, simply has a single VRAM 1. The following stable memory operation, referred to as a CLASSICAL commit is described with reference to Fig. 4.
(a) The host processor allocates spaces SO and SI in bank 0 and bank 1 respectively as being for stable memory operations (Fig. 4(a)).
(b) The host processor carries out work in a memory space A of bank 0 (Fig. 4(b)).
(c) & (d) An intra-bank transfer is carried out between space
A and space SO in bank 0 (Figs. 4(c) and 4(d)).
(e) The processor continues to work in the space A while an inter-bank transfer takes place between the spaces SO and SI (Fig. 4(e)).
(f) If required, the contents of spaces SO and SI are compared (Fig. 4(f)).
- 10 (g) Finally, the host processor continues to work in the space A of bank 0 (Fig. 4(g)).
Here, for simplicity only, a single space A has been committed. After step (b) above, a primary space to be committed (space A) is copied to a secondary area of memory (space SO), via an intra-bank transfer. After step (d), the commit is logically complete (but not physically complete), and the host processor may continue to work in the location A while the physical commit proceeds between the secondary location SO and a further tertiary location SI of the stable memory circuit. In this specification, the term logically complete is intended to mean that the step is complete to the extent that the host processor may continue.
The commit is physically complete after step (f). If a host processor write access is attempted to location A during the physical commit, there will be no effect upon the physical commit process and no action need be taken. Hence, the host processor is delayed only for the time taken for the intrabank transfer, but unnecessary transfers may take place, and three locations (A, SO and SI) will always have to be allocated. It will be appreciated that the commit need not be constrained to a single memory location.
- 11 Alternatively, another stable memory commit operation, referred to as an IN-PLACE commit would require the following sequence of actions with reference to Fig. 5.
(a)
The host processor allocates stable spaces SO and SI in bank 0 and bank 1, respectively (Fig. 5(a)).
(b) The host processor carries out work in the space SO (Fig. 5(b)).
(c) & (d) An intra-bank transfer is carried out between the spaces SO and location A, (Figs. 5(c) and 5(d)).
(e) & (f) The host processor continues to work in the location
A, while simultaneously an inter-bank copy operation takes place between the space SO and the space Si (Fig. 5(e)), and if required the contents of the spaces SO and SI are compared (Fig. 5(f)).
(g) The host processor continues to work in the space A, (Fig. 5(g)).
Again, for simplicity only, a single space A is to be committed. After step (b) above, the primary area to be committed (space SO) is copied to a secondary area of memory (space A) via an intra-bank transfer. After step (d) the commit is logically complete (but not physically complete) and
- 12 the host may continue to work in the secondary space A while the physical commit proceeds between the primary space SO and a further tertiary space SI of memory. The commit is physically complete after step (f). If a host write access is attempted to the space A during the physical commit, there will be no effect upon the physical commit process and no action may be taken. Again, the host processor is delayed only for the time taken by the intra-bank transfer, but unnecessary transfers may take place and three spaces (A, SO and SI) will always have to be allocated. Again, it will be appreciated that the commit need not be constrained to a single block.
If the stable memory operation is likely to occur frequently, it may be implemented with a FOUR-WAY operation by declaring two pairs of spaces and alternatively continuing host processor work in one space of one pair, whilst the stable memory operation proceeds between the other pair, and vice versa. For example, a FOUR-WAY variant of the atomic commit operation, here called a FOUR-WAY commit requires the sequence of actions below.
(a) The host processor allocates stable spaces SO, S2 and in bank 0 and spaces SI and S3 in bank 1.
(b) The host processor carries out work in the space SO.
- 13 (c) An intra-bank transfer operation takes place between space SO and space S2.
(d) The host processor continues work in space S2, while simultaneously an inter-bank copy operation takes place between the spaces SO and SI and subsequently if so required the contents of the spaces SO and SI are compared.
(e) The host processor continues work in the space S2.
(f) An intra-bank transfer operation takes place between the space S2 and the space SO.
(g) The host processor continues work in the space SO and simultaneously an inter-bank copy operation takes place between the space S2 and the space S3 and subsequently, if so required, the contents of these spaces are compared.
(h) The host processor continues work in SO.
Again, for simplicity only, a single memory space is committed. After step (b), the primary area to be committed (space SO) is copied to a tertiary area of memory (space S2) via an intra-bank transfer. After step (c) the commit is logically complete and the host may continue to work in the
- 14 tertiary space S2 while the physical commit proceeds between the primary space SO and the secondary space SI. The commit is physically complete after step (d) . If a host write access is attempted to the space S2 during the physical commit, there will be no effect on the physical commit process, and no action need by taken. The next commit will take place in the opposite direction, with an intra-bank transfer of space S2 back to space SO where host work can then continue while the physical commit is conducted between the spaces S2 and S3.
An advantage is that the procedure gains some symmetry, and in particular memory allocation is more symmetric. Again, the host processor is delayed only for the time taken by the intra-bank transfer, but unnecessary transfers may still take place and four spaces (SO, SI, S2 and S3) will always have to be allocated.
A further important advantage of the FOUR-WAY commit relates to protection. When using VRAMs, an intra-bank transfer occurs entirely within the VRAMs so that error detection and correction of the intra-bank transfer by an external circuit is not possible. This reduces the level of protection afforded by error detection and correction codes unless a new generation of VRAMs is designed which expressly perform these functions internally. However, protection would be possible using other forms of dual-ported memory, provided that all of the data within the memory location is available externally for simultaneous error detection and correction.
- 15 For all of the above commit operations, the error detection and correction occurs on the stable data paths during the physical commit. If an uncorrectable error is found, then all but the FOUR-WAY commit are in error. For the FOUR-WAY commit there is always a full back-up in at least one of the four locations of memory involved.
Fig. 6 shows a stable memory circuit 20 having two banks, namely bank 0 and bank 1 which are not interconnected by a stable data path. Each bank comprises four VRAMs 1 so that the VRAMs in one bank are replicated in the other bank. Accordingly, in the event of a fault within one VRAM, the data may be accessed from a replicate device. Inter-bank copying is not required for a commit operation - data can be committed within the VRAM that holds the data using intra-bank transfers only, provided the operations are performed simultaneously on its replicate devices.
In Fig. 6(a), writes take place to the source block SO in two of the VRAMs 1, being replicates of each other so that the writes are effectively broadcast. In Figs. 6(b) and 6(c) an intra-bank transfer takes place between the source block SO and the destination block SI in each of the VRAMs 1. In Fig. 6(d) reads take place from the source block SO in two of the VRAMs 1. Any errors are detected using a voting circuit 21 which compares the contents of the block SO in different VRAMs
1. The important point is that because the operations are
- 16 performed simultaneously on replicate VRAMs, inter-bank copying need not take place. In particular, the stable memory operations described above will allow all the memory to be checkpointed extremely rapidly by performing the commits for all VRAMs 1 simultaneously. The checkpointing will take place with a time Tchk equal to:TChk = 2* (VRAM capacity/serial access register capacity) *(transfer cycle time)
Thus all of memory may be checkpointed in a deterministic time, independent of the total memory capacity. For modern VRAMs Tchk is of the order of 100 microseconds. The significance of this can be seen when used in a real-time system where deadlines must be met:- checkpointing of all of memory can be undertaken regularly, each checkpoint taking just 100 microseconds. On a fault, backward error recovery to the previous checkpoint state can be accomplished (for all of memory) in another 100 microseconds. For the first time, this allows checkpointing with backward error recovery to become the basis for fault-tolerance for both hardware and software in hard-real-time systems. Normally this would be assumed to apply just to hard-real-time recovery from hardware faults.
The invention has been described in use with VRAMs as the memory devices. However, any memory device within which there is an auxiliary memory area which can provide a temporary
- 17 location may be used. Registers in devices such as VRAMs have been found to be particularly suitable. With minor modifications the sense amplifiers in DRAMs could also serve this purpose. As shown in Fig. 6, it is not essential that the memory banks be interconnected by a stable data path. The intra-bank transfer may be used with advantage whether or not inter-bank operations also take place.
Although not shown in the specific embodiments, it is envisaged that a processing operation may take place on the data between being written to the temporary location and to the destination location.
The invention is not limited to the embodiments hereinbefore described, but may be varied in construction and detail.
Claims (9)
1. A stable memory operation carried out in a stable memory circuit comprising at least two memory banks each comprising at least one memory device, the stable memory 5 operation comprising the steps of writing data from a source location of a memory device to a temporary location in the same device, and subsequently writing the data to a destination location in the same device to complete an intra-bank transfer. 10
2. A stable memory operation as claimed in Claim 1, wherein the temporary location is in an auxiliary memory area of the device.
3. A stable memory operation as claimed in Claim 2, wherein the auxiliary memory area is a register. 15
4. A stable memory operation as claimed in any preceding claim, wherein the device is a video random access memory, and the temporary location is the serial access register of the video random access memory.
5. A stable memory operation as claimed in Claim 4, wherein 20 the video random access memory has a plurality of serial access registers, one of which is used for the intra-bank transfer, another serial access register being for use in - 19 another stable memory operation carried out simultaneously.
6. A stable memory operation as claimed in any preceding claim, wherein the stable memory operation also includes 5 an inter-bank copy, logical operation time of a host processor being reduced by performing the intra-bank transfer in advance.
7. A stable memory operation as claimed in Claim 6 wherein the intra-bank transfer is carried out on a copy-on-write 10 basis.
8. A stable memory operation as claimed in any of Claims 1 to 5, wherein the intra-bank transfer is carried out simultaneously in at least two memory devices being replicates of each other. 15
9. A stable memory operation as claimed in Claim 8, wherein the intra-bank transfer is carried out simultaneously in all devices, resulting in data in each memory device being checkpointed in a deterministic time, independently of memory size.
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
IE109491A IE911094A1 (en) | 1991-04-03 | 1991-04-03 | A Data Processing Method |
ZA922466A ZA922466B (en) | 1991-04-03 | 1992-04-03 | Stable memory operations |
PCT/GB1992/000608 WO1992017842A1 (en) | 1991-04-03 | 1992-04-03 | Stable memory operations |
AU14506/92A AU1450692A (en) | 1991-04-03 | 1992-04-03 | Stable memory operations |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
IE109491A IE911094A1 (en) | 1991-04-03 | 1991-04-03 | A Data Processing Method |
Publications (1)
Publication Number | Publication Date |
---|---|
IE911094A1 true IE911094A1 (en) | 1992-11-04 |
Family
ID=11021834
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
IE109491A IE911094A1 (en) | 1991-04-03 | 1991-04-03 | A Data Processing Method |
Country Status (4)
Country | Link |
---|---|
AU (1) | AU1450692A (en) |
IE (1) | IE911094A1 (en) |
WO (1) | WO1992017842A1 (en) |
ZA (1) | ZA922466B (en) |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7496787B2 (en) | 2004-12-27 | 2009-02-24 | Stratus Technologies Bermuda Ltd. | Systems and methods for checkpointing |
US9251002B2 (en) | 2013-01-15 | 2016-02-02 | Stratus Technologies Bermuda Ltd. | System and method for writing checkpointing data |
EP3090344B1 (en) | 2013-12-30 | 2018-07-18 | Stratus Technologies Bermuda Ltd. | Dynamic checkpointing systems and methods |
US9760442B2 (en) | 2013-12-30 | 2017-09-12 | Stratus Technologies Bermuda Ltd. | Method of delaying checkpoints by inspecting network packets |
US9588844B2 (en) | 2013-12-30 | 2017-03-07 | Stratus Technologies Bermuda Ltd. | Checkpointing systems and methods using data forwarding |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3866182A (en) * | 1968-10-17 | 1975-02-11 | Fujitsu Ltd | System for transferring information between memory banks |
FR2591775B1 (en) * | 1985-12-12 | 1988-03-04 | Inst Nat Rech Inf Automat | ELECTRONIC DEVICE FORMING IMPROVED FAST STABLE MEMORY |
IE63461B1 (en) * | 1989-09-11 | 1995-04-19 | Jeremy Owen Jones | Improvements in and relating to stable memory circuits |
-
1991
- 1991-04-03 IE IE109491A patent/IE911094A1/en unknown
-
1992
- 1992-04-03 ZA ZA922466A patent/ZA922466B/en unknown
- 1992-04-03 AU AU14506/92A patent/AU1450692A/en not_active Abandoned
- 1992-04-03 WO PCT/GB1992/000608 patent/WO1992017842A1/en active Application Filing
Also Published As
Publication number | Publication date |
---|---|
ZA922466B (en) | 1992-12-30 |
WO1992017842A1 (en) | 1992-10-15 |
AU1450692A (en) | 1992-11-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US5574874A (en) | Method for implementing a checkpoint between pairs of memory locations using two indicators to indicate the status of each associated pair of memory locations | |
US4905196A (en) | Method and storage device for saving the computer status during interrupt | |
JPS62186349A (en) | Maintaining of data usability in data base system | |
US5200963A (en) | Self-checking on-line testable static ram | |
EP0432359A2 (en) | Method and apparatus for performing memory protection operations in a parallel processor system | |
JPS6218057B2 (en) | ||
IE911094A1 (en) | A Data Processing Method | |
EP0418030A2 (en) | Improvements in and relating to stable memory circuits | |
US5168558A (en) | Apparatus and method for providing distributed control in a main memory unit of a data processing system | |
US5204964A (en) | Method and apparatus for resetting a memory upon power recovery | |
JPH06149485A (en) | Data completion guarantee processing method | |
JP2513060B2 (en) | Failure recovery type computer | |
US4954946A (en) | Apparatus and method for providing distribution control in a main memory unit of a data processing system | |
JP3009168B2 (en) | Data processing device | |
JPH0233175B2 (en) | ||
IE930844A1 (en) | Memory checkpointing | |
JPH02118745A (en) | Memory back-up device | |
JP2001175422A (en) | Disk array device | |
JPH04181331A (en) | Instruction retry system | |
IES59752B2 (en) | Memory checkpointing | |
JPH0273420A (en) | Semiconductor disk device | |
JPS59109961A (en) | Main storage controlling system | |
JPS61843A (en) | Resource status holding system | |
Chau et al. | Self-checking on-line testable static RAM | |
JPS62151950A (en) | Action history memory system |