EP0163096B1 - Dispositif pour sauvegarder l'état du calculateur - Google Patents
Dispositif pour sauvegarder l'état du calculateur Download PDFInfo
- Publication number
- EP0163096B1 EP0163096B1 EP85104649A EP85104649A EP0163096B1 EP 0163096 B1 EP0163096 B1 EP 0163096B1 EP 85104649 A EP85104649 A EP 85104649A EP 85104649 A EP85104649 A EP 85104649A EP 0163096 B1 EP0163096 B1 EP 0163096B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- memory
- processor
- archive
- address
- computer
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/1441—Resetting or repowering
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
Definitions
- the invention is based on a device for saving a computer state according to the preamble of patent claim 1.
- This device is connected to the processor bus and tracks the bus handles with which the processor changes the state of the main memory (write cycles). Before a variable is changed in the working memory, this device, which is called the “save stack”, addresses the variable concerned, reads the previous content and saves it in a stack.
- the rescue pile is empty.
- the state of the computer at this retreat point should be able to be restored if there is a failure before the next retreat point is reached.
- the processor is reinitialized and the rescue stack is written back to the working memory. This gives all variables their previous value, namely the one they had when the rescue pile was empty, i.e. at the last retreat point, even if this value has been changed several times in the meantime.
- the invention solves the problem of improving the ratio of useful work time to rescue time.
- the present invention is also based on a storage of the changed variables, however the new value is not saved, but after the “saving of the changes”.
- a device for saving the state of a computer with a cascade memory is the subject of part-application EP-A-87110448.5 (published No. 0254247).
- Fig. 1 denotes a processor, 2 an address bus, 3 a data bus, 4 a working memory, 5 and 6 two archive memories or 5 an archive memory zone 1 and 6 an archive memory zone 2.
- 4a, 5a and 6a denote address decoders in the working memory 4 and in the archive memories 5 and 6; 4b, 5b and 6b copy areas for the processor state in the main memory 4 or in the archive memories 5 and 6 ..
- processor 1 and its working memory 4 are required for normal computer operation.
- the archive stores 5 and 6 are used for fault tolerance.
- the address bus 2 and the data bus 3 or the address and data lines were drawn separately in order to simplify the explanations. It could just as well be a multiplexed bus or a serial bus.
- the work of the processor consists of: 1. useful work, 2. state rescue and 3. restoration of the state after overcoming the failure.
- Useful work is the normal operation of processing a useful program. If a failure should occur during the useful work, the processor 1 undertakes a recovery after the repair, as will be explained below.
- the useful work is divided into steps, which are called retreat blocks or blocks for short.
- the blocks are considered to be indivisible operations: either they are completed or the computer returns to the state before the block.
- the status of the computer at any time is defined by the current status of the user program, ie by the status of its variables, by the status of the internal registers of the processor and the input and output devices, not shown, I / O devices for short .
- Register state and state of the I / O devices are referred to as processor state or context.
- the program code is not part of the state.
- Variable state and processor state together form the computer or Task status.
- the processor state is stored in the copy area 4b of the main memory 4. Overall, the working memory 4 contains the entire task status.
- retreat point i RPi
- RPi + 1 RPi + 1
- the retreat points are chosen at regular intervals or as required.
- the state at the retreat point is recorded by executing a state rescue program.
- the distance between neighboring withdrawal points is given by the application. In fast processes, the interval may not exceed a few 100 ms, in data processing applications it may be a few hours.
- the processor should abandon the aborted work and try to restore the RPi state as it was at the beginning of the block after repair in order to process the block again from there. This is the job of the recovery program.
- the state rescue can take place parallel to the work or after the work. First of all, we assume that useful work and state rescue take place in succession.
- the archive store contains the RPi status. If a block has been calculated without errors, the state of the process RP i + 1 is copied from the working memory 4 into the archive memory 5, and the next block can begin.
- the copying operation from the main memory into the archive memory can be carried out by the processor 1 itself by addressing a cell of the main memory 4 for reading and the corresponding cell of the archive memory 5 for writing.
- a control device (not shown) with direct memory access can carry out the copying work somewhat faster than the processor.
- the archive store 5 should have the same organization as the main memory, i. that is, it should have the same number of memory locations with the same division as the main memory 4. For each memory cell in the main memory 4 there is a corresponding memory cell in the archive memory 5.
- the bus addresses of the corresponding memory cells in the main memory 4 and in the archive memory 5 do not need to match, they can e.g. differentiate in the most significant bit in order to reduce the circuit complexity. However, it is advantageous if the address is the same relative to the beginning of the memory in the case of corresponding memory cells from the working memory 4 and archive memory 5.
- the archive store 5 is approximately as fast as the main memory 4.
- the archive store 5 could e.g. a buffered CMOS read / write memory, a non-volatile read / write memory RAM, as z. B. is commercially available under the name IN-TEL 2004, or a slower memory, such as a core storage.
- Non-volatile memories such as EAROM or EEPROM
- EAROM EAROM
- EEPROM EEPROM
- a diskette, optical and magnetic disk are not only problematic for reasons of speed, their organization differs considerably from the linear structure of a memory, and an appropriate illustration must first be produced.
- the restoration consists of the processor 1 being tested for reliability in a self-test or external test after it has been repaired. Then the processor or the control unit with direct memory access loads the task state, which was stored in the archive memory 5, back into the main memory 4. Then the I / O devices and the processor 1 are loaded with their internal state (processor state). Finally, the program counter of processor 1 is set, and useful work can begin again at the last retreat point.
- the archive store 5 While copying the retreat point into the archive store 5, the archive store 5 is inconsistent, it contains parts from the RP i and parts from the RP i + 1.
- the copy operation should be indivisible, i.e., it is either fully executed or not at all. Since the copy operation takes a finite time, the probability of failure during that time is not negligible.
- the archive store 5 does not lose any information in the event of a failure, but the zone or the storage area which was being processed or updated at the time of the failure is inconsistent and is considered lost.
- the archive store is divided into two identical halves, the archive store areas 5 and 6.
- the processor 1 can write in both areas of the archive memory 5, 6, but not at the same time. No failure should cause processor 1 to change the part of the archive memory with which it is not currently working.
- both areas 5 and 6 of the archive memory contain the same content, namely one copy of the main memory 4 (process status on RP i). Both archive stores or archive storage areas are updated one after the other, ie brought from RP i + 1. As a convention, we assume that the archive store 5 is updated first and then the archive store 6.
- the copies can be provided with the physical or with a logical time to mark their validity.
- the storage area of the archive store that is currently being processed is referred to as the “dirty” area and the other as the “clean” area.
- the processor 1 first carries out the state rescue with the archive memory 5. Then the roles of the dirty and clean areas are reversed. The processor 1 then carries out the same operation with the archive memory 6.
- processor 1 If a failure occurs during the first copy, then the processor returns to the last retreat point RP i, if it occurs during the second copy, then processor 1 starts with the new retreat point RP i + 1. If both copies are valid and contain the same RP, then processor 1 takes any copy.
- a recovery program checks which half of the archive memory contains a valid RP after the repair has been completed, and if this applies to both halves, the younger RP is selected. Then the task will resume from that point.
- Simplification of state rescue The state rescue described above is time-consuming, especially with a large memory. So that there is a reasonable relationship between useful work and the rescue period, the retreat blocks should be at least as long as twice the rescue period, which is not always tolerable in time-critical applications.
- the rescue time can be reduced significantly with the methods described below. Instead of processor 1 writing both memory areas individually, one of the memory areas can already be updated during useful work. This happens because the dirty archive storage area tracks activity on the bus and updates accordingly.
- the state of the main memory 4 is changed in accordance with the program progress. Any change in the working memory 4 is due to a write operation on the processor bus.
- the dirty part of the archive store follows this activity on the bus, in principle without disturbing the traffic.
- the dirty archive memory makes the same change in its copy of that memory cell.
- the clean part of the archive store is not changed.
- the processor writes its state and e.g. the time in the main memory (and thus also in the archive memory 5) and reports its status as valid.
- the dirty archive memory now contains the state of the main memory 4 and the processor 1 at the end of block RP i + 1.
- both storage areas of the archive storage again contain a consistent state, namely that at the beginning (RP i, clean storage area 6) and that at the end of the block (RP i + 1, formerly dirty storage area 5).
- This method also allows a slower memory to be used for the archive memory than for the main memory, since the archive memory is only used for the write cycles. It is generally assumed that there is an average of one write cycle per 9 read cycles.
- the rescue time is reduced by half, in our example from 262 ms to 131 ms.
- the archive memory can be about 9 times slower than the main memory.
- Fig. 4 shows an embodiment in which a stack memory 8 with an address memory area 8 a and a data memory area 8 b is provided between the working memory 4 and the archive memories 5 and 6 and is connected to the same address bus 2 and data bus 3.
- data memory 8 is empty. All changes to the working memory 4 are simultaneously entered in the stack memory 8 and in one of the archive memories (dirty zone). Without using the processor, the associated address / data pair is registered and entered in the stack 8 for each write access to the bus.
- the stack can be organized as a FIFO (first-in, firstout) or STACK (first-in, last-out).
- All address / data pairs are entered in the order in which they occur, and a counter or a stack pointer records the respective fill level of the memory and assigns its place to the new value pairs.
- the stack contains all the data that have changed since the beginning of the block.
- the first archive store 5 has already been updated, either by listening as described above or using the same method as the archive store 6.
- the stack memory 8 reduces the time period for the state rescue, since it contains all the information necessary for the state rescue in an ordered form. It is no longer necessary to transfer the entire contents of the working memory to the archive memory 6, but only the part that has been changed since the last retreat point.
- Fig. 5 shows an embodiment with such a cache memory 7.
- the first archive memory 5 can e.g. be updated by listening.
- the stack 8 occurs as a background memory. It is e.g. organized as a FIFO or STACK.
- the operating mode of the cache memory which is referred to as restoring, is again best suited.
- restoring In order to save the entire computer state at the retreat point, however, it is necessary to write out the contents of the cache memory.
- Various methods for this method has already been described. The efficiency of this method depends on the application and is best suited if the addresses of the variables form groups. This is e.g. the case with all modern programming languages.
- the rescue time can be shortened by a different organization of the stack, as will be shown with reference to FIG. 6.
- the stack 8 was previously organized as a linear memory (FIFO or STACK). There it happens that the same address appears several times because of a variable, for example a run variable in a loop that has been changed several times. The number of entries in the stack 8 could be reduced if only the last value of the variable were kept. Then it would be possible to use an archive store that is much slower than the stack store.
- FIFO linear memory
- the stack 8 is provided with an associative memory which has an associative address memory 8 a ', an associative data memory area 8 b and a counter 8 c.
- the stack reads the address on each write cycle on the processor bus. He compares them with the entries in his address table by creating the address at the so-called key input of the associative memory. If the address is not found, it is read into the associative memory as a new entry. The counter 8 c assigns it its position, it is then increased by one digit. From now on, the address is considered to be present. If the address already exists or has just been entered, the position of this address appears on the so-called position output to the data storage area 8 b. The position address has the same width as the counter 8 c. The associated date is then recorded in the data storage area 8b.
- the data memory is a normal semiconductor memory.
- processor 1 When the stack memory 8 is saved in the archive memory 6, the processor 1 addresses the counter 8 c and thus forces a position address on the position lines and on the address lines. In this mode, processor 1 does not drive the address lines, but rather lets them float.
- the processor 1 is z. B. buffered by a three-state gate.
Claims (6)
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CH205384 | 1984-04-26 | ||
CH2053/84 | 1984-04-26 |
Related Child Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP87110448A Division EP0254247A3 (fr) | 1984-04-26 | 1985-04-17 | Dispositif pour sauvegarder le contexte d'un calculateur |
EP87110448.5 Division-Into | 1985-04-17 |
Publications (2)
Publication Number | Publication Date |
---|---|
EP0163096A1 EP0163096A1 (fr) | 1985-12-04 |
EP0163096B1 true EP0163096B1 (fr) | 1988-11-17 |
Family
ID=4224825
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP85104649A Expired EP0163096B1 (fr) | 1984-04-26 | 1985-04-17 | Dispositif pour sauvegarder l'état du calculateur |
EP87110448A Withdrawn EP0254247A3 (fr) | 1984-04-26 | 1985-04-17 | Dispositif pour sauvegarder le contexte d'un calculateur |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP87110448A Withdrawn EP0254247A3 (fr) | 1984-04-26 | 1985-04-17 | Dispositif pour sauvegarder le contexte d'un calculateur |
Country Status (4)
Country | Link |
---|---|
US (1) | US4905196A (fr) |
EP (2) | EP0163096B1 (fr) |
JP (1) | JPH0619722B2 (fr) |
DE (1) | DE3566314D1 (fr) |
Families Citing this family (44)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0228559A1 (fr) * | 1985-12-17 | 1987-07-15 | BBC Brown Boveri AG | Agencement multi-calculateurs tolérant des défauts |
US5832202A (en) * | 1988-12-28 | 1998-11-03 | U.S. Philips Corporation | Exception recovery in a data processing system |
US5257359A (en) * | 1989-02-08 | 1993-10-26 | Hitachi Microsystems, Inc. | Instruction cache buffer with program-flow control |
US5115506A (en) * | 1990-01-05 | 1992-05-19 | Motorola, Inc. | Method and apparatus for preventing recursion jeopardy |
JPH0772866B2 (ja) * | 1990-01-26 | 1995-08-02 | インターナショナル・ビジネス・マシーンズ・コーポレイション | エキスパート・システムの状態を巻戻す方法及びシステム |
JPH0437935A (ja) * | 1990-06-01 | 1992-02-07 | Hitachi Ltd | キャッシュメモリを有する計算機 |
US5341493A (en) * | 1990-09-21 | 1994-08-23 | Emc Corporation | Disk storage system with write preservation during power failure |
US5829030A (en) * | 1990-11-05 | 1998-10-27 | Mitsubishi Denki Kabushiki Kaisha | System for performing cache flush transactions from interconnected processor modules to paired memory modules |
JP2641819B2 (ja) * | 1990-11-05 | 1997-08-20 | 三菱電機株式会社 | キャッシュ・コントローラ並びにフォールト・トレラント・コンピュータ及びそのデータ転送方式 |
US5291600A (en) * | 1991-10-23 | 1994-03-01 | At&T Bell Laboratories | Recovery of in-core disk data |
US5363503A (en) * | 1992-01-22 | 1994-11-08 | Unisys Corporation | Fault tolerant computer system with provision for handling external events |
US5386563A (en) * | 1992-10-13 | 1995-01-31 | Advanced Risc Machines Limited | Register substitution during exception processing |
US5568380A (en) * | 1993-08-30 | 1996-10-22 | International Business Machines Corporation | Shadow register file for instruction rollback |
US6101421A (en) * | 1993-09-10 | 2000-08-08 | Motorola, Inc. | Reset recovery in a microprocessor controlled device |
GB2307072B (en) | 1994-06-10 | 1998-05-13 | Advanced Risc Mach Ltd | Interoperability with multiple instruction sets |
JPH10506483A (ja) * | 1994-06-10 | 1998-06-23 | テキサス・マイクロ・インコーポレーテッド | フォールト・トレラントなコンピュータ・システムのためのメイン・メモリ・システム及びチェックポイント用プロトコル |
US5557777A (en) * | 1994-09-30 | 1996-09-17 | Apple Computer, Inc. | Method and apparatus for system recovery from power loss |
JP3086779B2 (ja) * | 1995-06-19 | 2000-09-11 | 株式会社東芝 | メモリ状態復元装置 |
JP3020833B2 (ja) * | 1995-06-19 | 2000-03-15 | 株式会社東芝 | チェックポイント取得システム |
JPH096546A (ja) * | 1995-06-19 | 1997-01-10 | Toshiba Corp | ディスク制御システム |
US5864657A (en) * | 1995-11-29 | 1999-01-26 | Texas Micro, Inc. | Main memory system and checkpointing protocol for fault-tolerant computer system |
US5745672A (en) * | 1995-11-29 | 1998-04-28 | Texas Micro, Inc. | Main memory system and checkpointing protocol for a fault-tolerant computer system using a read buffer |
US5751939A (en) * | 1995-11-29 | 1998-05-12 | Texas Micro, Inc. | Main memory system and checkpointing protocol for fault-tolerant computer system using an exclusive-or memory |
US5737514A (en) * | 1995-11-29 | 1998-04-07 | Texas Micro, Inc. | Remote checkpoint memory system and protocol for fault-tolerant computer system |
US5805929A (en) * | 1996-01-29 | 1998-09-08 | International Business Machines Corporation | Multiple independent I/O functions on a PCMCIA card share a single interrupt request signal using an AND gate for triggering a delayed RESET signal |
US5923887A (en) * | 1996-05-20 | 1999-07-13 | Advanced Micro Devices, Inc. | Interrupt request that defines resource usage |
US5953742A (en) * | 1996-07-01 | 1999-09-14 | Sun Microsystems, Inc. | Memory management in fault tolerant computer systems utilizing a first and second recording mechanism and a reintegration mechanism |
TW379298B (en) * | 1996-09-30 | 2000-01-11 | Toshiba Corp | Memory updating history saving device and memory updating history saving method |
FR2773234B1 (fr) * | 1997-12-31 | 2003-07-25 | Sgs Thomson Microelectronics | Memoire a double acces pour processeur de signal numerique |
US6256714B1 (en) | 1998-09-02 | 2001-07-03 | Sharp Laboratories Of America, Inc. | Computer system with efficient memory usage for managing multiple application programs |
US6233627B1 (en) * | 1998-08-10 | 2001-05-15 | Micron Technology, Inc. | Processor with internal register for peripheral status |
JP2000099277A (ja) * | 1998-09-18 | 2000-04-07 | Fujitsu Ltd | ファイルユニット間のリモート転送方法 |
US6332199B1 (en) | 1998-10-29 | 2001-12-18 | International Business Machines Corporation | Restoring checkpointed processes including adjusting environment variables of the processes |
US7281040B1 (en) * | 2000-03-07 | 2007-10-09 | Cisco Technology, Inc. | Diagnostic/remote monitoring by email |
US7110440B2 (en) * | 2001-03-14 | 2006-09-19 | Mercury Computer Systems, Inc. | Wireless communications systems and methods for multiple processor based multiple user detection |
US6854038B2 (en) * | 2002-06-06 | 2005-02-08 | International Business Machines Corporation | Global status journaling in NVS |
US7058849B2 (en) * | 2002-07-02 | 2006-06-06 | Micron Technology, Inc. | Use of non-volatile memory to perform rollback function |
US7130997B2 (en) * | 2003-05-29 | 2006-10-31 | International Business Machines Corporation | Method of registering a portion of RAM with firmware to preserve the portion during reboot |
CN100437500C (zh) * | 2005-09-28 | 2008-11-26 | 联想(北京)有限公司 | 用于软件系统保护的软件系统保护点还原方法和装置 |
US7689868B2 (en) * | 2007-06-22 | 2010-03-30 | Sony Computer Entertainment Inc. | Memory handling techniques to facilitate debugging |
US20110181780A1 (en) * | 2010-01-25 | 2011-07-28 | Barton James M | Displaying Content on Detected Devices |
US20110183654A1 (en) | 2010-01-25 | 2011-07-28 | Brian Lanier | Concurrent Use of Multiple User Interface Devices |
IL208641A0 (en) | 2010-10-12 | 2010-12-30 | Eci Telecom Ltd | Method for accelerating start up of a computerized system |
US20120117497A1 (en) * | 2010-11-08 | 2012-05-10 | Nokia Corporation | Method and apparatus for applying changes to a user interface |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE2163162A1 (de) * | 1970-12-23 | 1972-07-13 | Ibm | Schaltungsanordnung zur Kanalfehlerkorrektur |
DE2240432A1 (de) * | 1971-08-18 | 1973-03-01 | Ibm | Datenverarbeitungsanlage |
Family Cites Families (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3533082A (en) * | 1968-01-15 | 1970-10-06 | Ibm | Instruction retry apparatus including means for restoring the original contents of altered source operands |
FR2268306A1 (en) * | 1974-04-17 | 1975-11-14 | Nat Res Dev | Data processing unit with programme modules - modules permit repeated cycle operation without increase in main memory capacity |
GB1509193A (en) * | 1974-04-17 | 1978-05-04 | Nat Res Dev | Computer systems |
US3974480A (en) * | 1974-05-08 | 1976-08-10 | Francois Gernelle | Data processing system, specially for real-time applications |
US4044337A (en) * | 1975-12-23 | 1977-08-23 | International Business Machines Corporation | Instruction retry mechanism for a data processing system |
US4014005A (en) * | 1976-01-05 | 1977-03-22 | International Business Machines Corporation | Configuration and control unit for a heterogeneous multi-system |
JPS5311181A (en) * | 1976-07-19 | 1978-02-01 | Katsumi Hirakawa | Fireeand waterrresistant reinforcing agents |
JPS53121427A (en) * | 1977-03-31 | 1978-10-23 | Toshiba Corp | Electronic computer |
JPS53133338A (en) * | 1977-04-27 | 1978-11-21 | Nec Corp | Sharing system for auxiliary unit |
US4254477A (en) * | 1978-10-25 | 1981-03-03 | Mcdonnell Douglas Corporation | Reconfigurable memory circuit |
US4291388A (en) * | 1978-12-20 | 1981-09-22 | Allen-Bradley Company | Programmable controller with data archive |
JPS561726A (en) * | 1979-06-15 | 1981-01-09 | Tokyo Electric Power Co | Device for settling protective control unit |
US4300060A (en) * | 1979-12-10 | 1981-11-10 | General Motors Corporation | Signal programmable multiple function flip-flop |
US4513367A (en) * | 1981-03-23 | 1985-04-23 | International Business Machines Corporation | Cache locking controls in a multiprocessor |
US4459658A (en) * | 1982-02-26 | 1984-07-10 | Bell Telephone Laboratories Incorporated | Technique for enabling operation of a computer system with a consistent state of a linked list data structure after a main memory failure |
JPS592151A (ja) * | 1982-06-29 | 1984-01-07 | Fujitsu Ltd | チエツクポイント・リカバリ方式 |
JPS5913783A (ja) * | 1982-07-15 | 1984-01-24 | Taiho Yakuhin Kogyo Kk | ジテルペノイド |
DE3382152D1 (de) * | 1982-12-09 | 1991-03-07 | Sequoia Systems Inc | Sicherstellungsspeichersystem. |
-
1985
- 1985-04-17 DE DE8585104649T patent/DE3566314D1/de not_active Expired
- 1985-04-17 EP EP85104649A patent/EP0163096B1/fr not_active Expired
- 1985-04-17 EP EP87110448A patent/EP0254247A3/fr not_active Withdrawn
- 1985-04-26 JP JP60089150A patent/JPH0619722B2/ja not_active Expired - Lifetime
-
1987
- 1987-10-05 US US07/105,448 patent/US4905196A/en not_active Expired - Fee Related
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE2163162A1 (de) * | 1970-12-23 | 1972-07-13 | Ibm | Schaltungsanordnung zur Kanalfehlerkorrektur |
DE2240432A1 (de) * | 1971-08-18 | 1973-03-01 | Ibm | Datenverarbeitungsanlage |
Non-Patent Citations (1)
Title |
---|
"Proceedings of the 12th International Conference on Fault Tolerant Computing FTSC-12", 1982, Seiten 127-132; * |
Also Published As
Publication number | Publication date |
---|---|
US4905196A (en) | 1990-02-27 |
JPH0619722B2 (ja) | 1994-03-16 |
EP0254247A3 (fr) | 1988-08-10 |
EP0254247A2 (fr) | 1988-01-27 |
DE3566314D1 (en) | 1988-12-22 |
EP0163096A1 (fr) | 1985-12-04 |
JPS60235246A (ja) | 1985-11-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP0163096B1 (fr) | Dispositif pour sauvegarder l'état du calculateur | |
DE4220198C2 (de) | Transaktionsverarbeitungsverfahren für einen digitalen Computer und Transaktionsverarbeitungssystem | |
DE69817696T2 (de) | Warmaustausch von gespiegeltem Nachschreib-Cachespeicher | |
EP0013737B1 (fr) | Hiérarchie de mémoire à plusieurs étages pour un système de traitement des données | |
DE69133302T2 (de) | Registerabbildung in einem einzigen Taktzyklus | |
DE3803759C2 (fr) | ||
DE602005000819T2 (de) | Aufrechterhaltung der konsistenz einer fernkopie unter verwendung von virtualisierung | |
DE2428348C2 (de) | Verfahren zur Weiterbenutzung eines fehlerhaften Datenspeichers und Einrichtung zur Durchführung dieses Verfahrens | |
EP0228559A1 (fr) | Agencement multi-calculateurs tolérant des défauts | |
DE10238566A1 (de) | Fenster-basierendes Flashspeicher-Speichersystem und Management und Zugriffsverfahren darauf | |
DE1901036A1 (de) | Anordnung fuer die wiederholte Ausfuehrung fehlerhaft ausgefuehrter Funktionen | |
DE2619159A1 (de) | Fehlererkennungs- und korrektureinrichtung | |
EP1952239A1 (fr) | Dispositif et procédé d élimination de défauts dans un système présentant au moins deux unités d exécution avec registres | |
DE3151745A1 (de) | Multitasking-datenverarbeitungsanlage | |
DE2617408B2 (de) | Speichermodul für ein Datenverarbeitungsgerät mit Speicherhierarchie | |
DE4423559A1 (de) | Datenverbindungsverfahren und Vorrichtung für Multiprozessor-Computersysteme mit gemeinsamem Speicher | |
DE602004007925T2 (de) | Verwalten einer beziehung zwischen einem zielvolumen und einem quellenvolumen | |
DE60222891T2 (de) | Nichtflüchtige Speichervorrichtung und Selbstreparatur-Verfahren | |
DE3045609C2 (fr) | ||
DE4335061C2 (de) | Mehrspeichervorrichtung | |
DE2106731A1 (de) | Diagnoseeinrichtung fur elektronische Datenverarbeitungsanlagen | |
DE2823457C2 (de) | Schaltungsanordnung zur Fehlerüberwachung eines Speichers einer digitalen Rechenanlage | |
DE102022108212A1 (de) | Vereinfachte Raid-Implementierung für Byte-adressierbaren Speicher | |
DE2902477A1 (de) | Datenverarbeitungsanordnung | |
DE1966991A1 (de) | Ausfallgesicherte datenverarbeitungsanlage |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
AK | Designated contracting states |
Designated state(s): CH DE FR GB LI |
|
17P | Request for examination filed |
Effective date: 19851003 |
|
17Q | First examination report despatched |
Effective date: 19870126 |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: BBC BROWN BOVERI AG |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): CH DE FR GB LI |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: FR Free format text: THE PATENT HAS BEEN ANNULLED BY A DECISION OF A NATIONAL AUTHORITY Effective date: 19881117 |
|
REF | Corresponds to: |
Ref document number: 3566314 Country of ref document: DE Date of ref document: 19881222 |
|
GBT | Gb: translation of ep patent filed (gb section 77(6)(a)/1977) | ||
EN | Fr: translation not filed | ||
PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
26N | No opposition filed | ||
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: CH Payment date: 19900720 Year of fee payment: 6 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 19910318 Year of fee payment: 7 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LI Effective date: 19910430 Ref country code: CH Effective date: 19910430 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 19910626 Year of fee payment: 7 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: GB Effective date: 19920417 |
|
GBPC | Gb: european patent ceased through non-payment of renewal fee | ||
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DE Effective date: 19930101 |