WO2016115661A1 - Procédé et dispositif d'isolement de défaillance de mémoire - Google Patents

Procédé et dispositif d'isolement de défaillance de mémoire Download PDF

Info

Publication number
WO2016115661A1
WO2016115661A1 PCT/CN2015/071008 CN2015071008W WO2016115661A1 WO 2016115661 A1 WO2016115661 A1 WO 2016115661A1 CN 2015071008 W CN2015071008 W CN 2015071008W WO 2016115661 A1 WO2016115661 A1 WO 2016115661A1
Authority
WO
WIPO (PCT)
Prior art keywords
memory
physical address
block
address block
belongs
Prior art date
Application number
PCT/CN2015/071008
Other languages
English (en)
Chinese (zh)
Inventor
刘勇
Original Assignee
华为技术有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN201580011928.2A priority Critical patent/CN106133704A/zh
Priority to PCT/CN2015/071008 priority patent/WO2016115661A1/fr
Publication of WO2016115661A1 publication Critical patent/WO2016115661A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00—Accessing, addressing or allocating within memory systems or architectures
    • G06F12/02—Addressing or allocation; Relocation

Definitions

  • Embodiments of the present invention relate to computer technologies, and in particular, to a memory fault isolation method and apparatus.
  • a memory failure on the server will cause the server or board to be reset.
  • the server reset will cause the running application to be interrupted, and the server needs to be returned to the manufacturer to replace the memory. It is inconvenient to replace the memory.
  • the prior art provides an offline fault memory isolation method, which does not need to return to the manufacturer to replace the memory.
  • the method includes: first, detecting the memory through a Basic Input Output System (BIOS) before the server is running, and Obtain the address information of the faulty memory space, save the address information of the faulty memory space to a non-volatile memory (Non-Volatile Memory, NVM for short), and read the address information of the faulty memory space saved in the NVM, and the address information is obtained.
  • the corresponding fault memory space is marked as unavailable, permanently isolating the fault memory space.
  • the method provided by the above prior art can only perform fault isolation before the server is running, and a memory hardware failure occurs during the running of the server, which still causes service interruption.
  • the embodiment of the invention provides a memory fault isolation method and device, which can perform fault isolation during server operation and avoid service interruption.
  • a first aspect of the present invention provides a memory fault isolation apparatus, including:
  • An exception processing module configured to monitor a state of a memory that is identified by a physical address mapped by a virtual address of the process, where a page to which the virtual address belongs has a mapping relationship with a physical address block to which the original physical address belongs, The physical address block is used to identify a contiguous memory interval allocated to the process;
  • the exception handling module is further configured to mark a status of the physical address block to which the original physical address belongs as a fault, if the memory identified by the original physical address is faulty;
  • a memory management module for using a non-faulty memory for the page block to which the virtual address belongs Newly allocated physical address block
  • the exception processing module is further configured to synchronize data in a memory interval identified by a physical address block to which the original physical address belongs to a memory interval identified by the reallocated physical address block.
  • the exception processing module is further configured to: save the information of the physical address block marked as a fault to a nonvolatile memory in;
  • the memory management module is specifically configured to:
  • the memory management module is specifically configured to:
  • the memory management module is further configured to:
  • the initial memory is allocated to the process from the non-faulty memory.
  • the exception handling The module is also used to:
  • the status of the physical address block to which the original physical address belongs is marked as non-fault.
  • a second aspect of the present invention provides a memory fault isolation method, including:
  • the status of the physical address block to which the original physical address belongs is marked as a fault
  • the method further includes:
  • Reassigning a physical address block to the page to which the virtual address belongs from the non-faulty memory includes:
  • the The physical memory block is re-allocated in the fault memory for the page to which the virtual address belongs, including:
  • the method further includes:
  • the non-faulty memory a memory other than the fault physical address block in the memory
  • the initial memory is allocated to the process from the non-faulty memory.
  • the method further include:
  • the status of the physical address block to which the original physical address belongs is marked as non-fault.
  • the server monitors the state of the memory identified by the original physical address mapped by the virtual address of the process, and if the memory identified by the original physical address fails, the server Mark the status of the physical address block to which the original physical address belongs as a fault to isolate the faulty memory space online. And the server allocates a physical address block to the page to which the virtual address belongs, and synchronizes the data in the memory interval identified by the physical address block to which the original physical address belongs to the memory interval identified by the reallocated physical address block.
  • the virtual address of the process is unchanged during the whole process, so that the service is not interrupted, and the faulty memory space is isolated online.
  • FIG. 1 is a schematic structural diagram of a server according to an embodiment of the present invention.
  • FIG. 2 is a schematic structural diagram of a memory fault isolation device according to Embodiment 1 of the present invention.
  • FIG. 3 is a flowchart of a memory fault isolation method according to Embodiment 2 of the present invention.
  • FIG. 1 is a schematic structural diagram of a server according to an embodiment of the present invention.
  • the server includes: a memory, a processor, and an NVM.
  • the processor mainly refers to a central processing unit (CPU), and a processor. It includes a memory management module and an exception handling module.
  • Memory Management Module Implement virtual machine or process virtual address space and physical address space mapping.
  • the exception handling module is configured to perform related processing on the abnormality triggered by the CPU, and is used to process the memory fault in the embodiment of the present invention.
  • the memory and NVM are two separate physical hardware.
  • the NVM is used to store the physical address of the faulty memory space. Even if the server is powered off, the data stored in the NVM will not be lost.
  • the memory is generally a random access memory (RAM) or a dynamic random access memory (DRAM).
  • RAM random access memory
  • DRAM dynamic random access memory
  • the memory generally exists in the form of a memory stick. The size of a single memory stick in the memory of the server is 8GB, 16GB and above, the replacement cost is high, and the virtual machine or process is a business running bearer.
  • FIG. 2 is a schematic structural diagram of a memory fault isolation device according to Embodiment 1 of the present invention.
  • the memory fault isolation device provided in this embodiment may be integrated in a server. As shown in FIG. 2, the memory fault isolation device provided in this embodiment is provided.
  • the method includes an exception processing module 11 and a memory management module 12.
  • the exception processing module 11 is configured to monitor the state of the memory identified by the original physical address mapped by the virtual address of the process, where the page to which the virtual address belongs has a mapping relationship with the physical address block to which the original physical address belongs, and the physical address block Used to identify a contiguous memory interval allocated to a process.
  • the exception handling module 11 is further configured to mark the status of the physical address block to which the original physical address belongs as a fault.
  • a memory management module 12 configured to re-allocate a physical address block from a non-faulty memory for a page block to which the virtual address belongs;
  • the exception handling module 11 is further configured to synchronize data in the memory interval identified by the physical address block to which the original physical address belongs to the memory interval identified by the reallocated physical address block.
  • each page includes a virtual address interval, and each page corresponds to one physical address block, and each physical address The block is used to identify a contiguous memory interval.
  • Each virtual address in the page corresponds to a physical address in the physical address block, and the mapping relationship between the virtual address and the physical address is maintained by the memory management module 12 of the server.
  • the memory management module 12 allocates initial memory for the process, which is: first, the information of the fault physical address block saved in the NVM is read, and then, the non-fault memory is determined according to the information of the fault physical address block, and the non-fault memory is Memory in memory other than the failed physical address block; finally, the initial memory is allocated to the process from non-faulty memory.
  • the memory management module 12 implements the mapping of the virtual address and the physical address in the form of a page table, and the page table organization form is managed in a level 1 or multi-level manner, for example, the Linux kernel adopts a level 3 page table management method, and each The size of the page may be 4K, 2M or 1gbps, etc.
  • the management form of the page table is not limited.
  • the memory management module 12 can avoid the memory identified by the failed physical address block when the initial memory is allocated for the process by reading the information of the failed physical address block in the NVM.
  • the exception handling module 11 monitors the state of the memory identified by the original physical address mapped by the virtual address of the process, and the state of the memory identified by the original physical address includes: a fault state and a normal state.
  • the memory management module 12 receives the memory access request sent by the process, where the memory access request includes the virtual address of the process, and the memory management module 12 maps the virtual address to the original physical address, and the virtual address and the original physical address. The correspondence is stored in the Translation Look-aside Buffer (TLB).
  • TLB Translation Look-aside Buffer
  • the memory management module 12 sends the original physical address to the memory controller through the memory bus, and the memory controller reads the data according to the original physical address, and if the abnormality cannot read the data in the memory identified by the original physical address, the memory control
  • the device issues an exception access instruction through the memory bus, and the exception handling module 11 determines, according to the abnormal access instruction, that the memory identified by the original physical address is faulty.
  • a page table is usually used as the minimum operation unit, and a page table corresponds to a physical address block. Therefore, when the memory identified by the original physical address fails, the exception handling module 11 belongs to the original physical address. The status of the physical address block is marked as a failure, isolating the physical address block to which the original physical address belongs. Usually the information of the failed physical address block is recorded in the NVM, so that even if the server is powered down, the information of the failed physical address block stored in the NVM is also It will not be lost. After the server is powered on, the memory management module 12 can still read the information of the fault physical address block from the NVM. When the initial memory is allocated for the process, the memory interval identified by the fault physical address block can be avoided.
  • the memory management module 12 reallocates the physical address block for the page to which the virtual address belongs, and the physical address mapped by the virtual address changes before and after the allocation, but for the upper application In this case, the virtual address of the process corresponding to the application does not change. As long as the virtual address does not change, the process is not interrupted, thereby ensuring that the user's service is not interrupted.
  • the memory management module 12 specifically allocates a physical address block for the page to which the virtual address belongs by first: first, determining non-faulty memory according to the information of the failed physical address block stored in the NVM, and the non-faulty memory is the memory-depleted physical address block in the memory. Memory outside of the identified memory. Then, based on the virtual address and the process number of the process, the physical address block is reassigned from the non-faulty memory for the page to which the virtual address belongs. The memory management module 12 re-allocates the physical address block from the non-fault memory to the page to which the virtual address belongs according to the virtual address and the process ID of the process. Specifically, the virtual address belongs to the virtual address and the process ID of the process. The page is then selected from the non-faulty memory to establish a mapping relationship between the page to which the virtual address belongs and the selected physical address block.
  • the exception processing module 11 is further configured to synchronize the data in the memory interval identified by the physical address block to which the original physical address belongs to the reallocated physical unit. In the memory interval identified by the address block.
  • the memory controller when the memory identified by the original physical address fails, the memory controller generates an abnormal instruction, and the exception processing module 11 performs data recovery according to the abnormal access instruction, where the abnormal access instruction includes an operation code and an operand, and the operation code indicates the
  • the operation type of the exception access instruction is a read operation or a write operation
  • the operand includes information of a register to be accessed by a read operation or a write operation, and a physical address of data to be accessed by a read operation or a write operation. If the operation type is a write operation, the exception handling module 11 writes the data to be written in the memory identified by the original physical address into the corresponding location in the reallocated physical address block.
  • the exception processing module 11 can perform data recovery on the data to be read according to the backup data of the data to be read in the memory identified by the original physical address, and if the data to be read can be recovered according to the backup data, Then, the recovered data to be read is copied to the corresponding position in the reallocated physical address block. If you want to read If the data cannot be recovered, the exception handling module 11 resets the process. Different from the prior art, in this embodiment, only the currently monitored process needs to be reset without interrupting other processes running on the server. In the prior art, once a process has a memory failure during operation, the server needs to be reset, and all processes running on the server are interrupted, causing all services to be interrupted.
  • the status of the original physical address block is marked as a fault, in the memory interval identified by the original physical address block, only the memory identified by the original physical address is faulty, and the original physical address block is faulty.
  • the other memory in the identified memory interval is normal. Therefore, when the exception processing module 11 synchronizes the data in the memory interval identified by the physical address block to which the original physical address belongs to the memory interval identified by the reallocated physical address block, The data in the normal memory can be directly copied from the memory interval identified by the original physical address block to the memory interval identified by the reallocated physical address block.
  • the exception processing module 11 is further configured to perform fault detection on the memory, and specifically detect whether the faulty memory block in the NVM has returned to normal. If it is detected that the physical address block to which the original physical address belongs has returned to normal, Then, the exception handling module 11 marks the state of the physical address block to which the original physical address belongs as non-fault, and the memory interval identified by the original physical address block can be used for memory allocation. If the physical address block to which the original physical address belongs cannot be recovered, the exception handling module 11 permanently isolates the original physical address block, and the memory interval identified by the original physical address block cannot be used for memory allocation.
  • the exception handling module monitors the state of the memory identified by the original physical address mapped by the virtual address of the process. If the memory identified by the original physical address fails, the exception handling module will The status of the physical address block to which the physical address belongs is marked as a fault to isolate the faulty memory space online. And the exception handling module calls the memory management module to allocate a physical address block for the page to which the virtual address belongs, and synchronizes the data in the memory interval identified by the physical address block to which the original physical address belongs to the memory interval identified by the reallocated physical address block. in.
  • the virtual address of the process is unchanged during the whole process, so that the service is not interrupted, and the faulty memory space is isolated online.
  • FIG. 3 is a flowchart of a memory fault isolation method according to Embodiment 2 of the present invention.
  • the method in this embodiment is performed by a server. As shown in FIG. 2, the method in this embodiment may include the following steps:
  • Step 101 Monitor the state of the memory identified by the original physical address mapped by the virtual address of the process, where the page to which the virtual address belongs has a mapping relationship with the physical address block to which the original physical address belongs, and the physical address block is used to identify the process assigned to the process. A continuous memory interval.
  • the server's operating system creates a process for the application, and the server allocates an initial memory space for the process.
  • the server allocates initial memory for the process, which is: first, the information of the fault physical address block saved in the NVM is read, and then the non-fault memory is determined according to the information of the fault physical address block, and the non-fault memory is the fault physical address block in the memory. External memory; finally, the initial memory is allocated to the process from non-faulty memory.
  • the memory management module implements mapping of the virtual address and the physical address in the form of a page table, and the page table organization form is managed in a level 1 or multi-level manner, for example, the Linux kernel adopts a level 3 page table management method, and each The size of the page may be 4K, 2M or 1gbps, etc.
  • the management form of the page table is not limited.
  • the server can avoid the memory identified by the fault physical address block when the initial memory is allocated for the process.
  • the server monitors the state of the memory identified by the original physical address mapped by the virtual address of the process, and the state of the memory identified by the original physical address includes: a fault state and a normal state.
  • the memory management module of the server receives the memory access request sent by the process, where the memory access request includes a virtual address of the process, and the memory management module maps the virtual address to the original physical address, and the virtual address and the original physical address are The corresponding relationship is stored in the TLB.
  • the memory management module sends the original physical address to the memory controller through the memory bus, and the memory controller reads the data according to the original physical address, and if the abnormality cannot read the data in the memory identified by the original physical address, the memory controller An abnormal access instruction is issued through the memory bus, and the server determines, according to the abnormal access instruction, that the memory identified by the original physical address is faulty.
  • Step 102 If the memory identified by the original physical address fails, the status of the physical address block to which the original physical address belongs is marked as a fault.
  • the server marks the status of the physical address block to which the original physical address belongs as a fault, and isolates the physical address block to which the original physical address belongs.
  • the information of the fault physical address block is recorded in the NVM, so that even if the server is powered off, the information of the fault physical address block saved in the NVM is not lost, and the server can still read the fault physics from the NVM after power-on.
  • Address block information at the beginning of the process allocation When starting memory, you can avoid the memory interval identified by the failed physical address block.
  • Step 103 Reassign the physical address block from the non-fault memory to the page to which the virtual address belongs, and synchronize the data in the memory interval identified by the physical address block to which the original physical address belongs to the memory identified by the reallocated physical address block. In the interval.
  • the server in order to ensure that the running service is not interrupted, the server re-allocates the physical address block to the page to which the virtual address belongs, and the physical address mapped by the virtual address changes before and after the allocation, but for the upper layer application, The virtual address of the process corresponding to the application does not change. As long as the virtual address does not change, the process will not be interrupted, thereby ensuring that the user's service is not interrupted.
  • the server re-allocates the physical address block to the page to which the virtual address belongs by first: first, determining the non-faulty memory according to the information of the failed physical address block saved in the NVM, and the non-faulty memory is the block of the physical address in the memory. Memory outside of the identified memory. Then, based on the virtual address and the process number of the process, the physical address block is reassigned from the non-faulty memory for the page to which the virtual address belongs.
  • the server re-allocates the physical address block from the non-faulty memory to the page to which the virtual address belongs according to the virtual address and the process ID of the process, where: first, the page to which the virtual address belongs is obtained according to the virtual address and the process ID of the process; The physical address block is selected from the non-faulty memory to establish a mapping relationship between the page to which the virtual address belongs and the selected physical address block.
  • the server After reallocating the physical address block for the page block to which the virtual address belongs, the server synchronizes the data in the memory interval identified by the physical address block to which the original physical address belongs to the memory interval identified by the reallocated physical address block.
  • the server For the specific synchronization mode, refer to the related description of the first embodiment, and details are not described herein again.
  • the server monitors the state of the memory identified by the original physical address mapped by the virtual address of the process. If the memory identified by the original physical address fails, the server belongs to the original physical address. The status of the physical address block is marked as faulty to isolate the faulty memory space online. And the server allocates a physical address block to the page to which the virtual address belongs, and synchronizes the data in the memory interval identified by the physical address block to which the original physical address belongs to the memory interval identified by the reallocated physical address block.
  • the virtual address of the process is unchanged during the whole process, so that the service is not interrupted, and the faulty memory space is isolated online.
  • the server detects the fault of the memory, and the server specifically detects whether the faulty memory block in the NVM has returned to normal. If the server detects that the physical address block to which the original physical address belongs has returned to normal, Then, the server marks the status of the physical address block to which the original physical address belongs as non-fault, and the memory interval identified by the original physical address block can be used for memory allocation. If the physical address block to which the original physical address belongs cannot be recovered, the server permanently isolates the original physical address block, and the memory interval identified by the original physical address block cannot be used for memory allocation.
  • the foregoing program may be stored in a computer readable storage medium, and the program is executed when executed.
  • the foregoing steps include the steps of the foregoing method embodiments; and the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Techniques For Improving Reliability Of Storages (AREA)

Abstract

L'invention concerne un procédé et un dispositif d'isolement de défaillance de mémoire. Le procédé comprend les opérations suivantes : durant le fonctionnement d'un processus, un serveur surveille l'état d'une mémoire identifiée par une adresse physique d'origine mappée par une adresse virtuelle du processus ; si la mémoire identifiée par l'adresse physique d'origine a une défaillance, le serveur marque l'état d'un bloc d'adresse physique auquel l'adresse physique d'origine appartient comme étant une défaillance, de façon à réaliser l'isolement en ligne d'un espace de mémoire défaillante ; et le serveur attribue le bloc d'adresse physique pour une page à laquelle l'adresse virtuelle appartient, et synchronise des données dans un intervalle de mémoire identifié par le bloc d'adresse physique auquel l'adresse physique d'origine appartient avec l'intervalle de mémoire identifié par le bloc d'adresse physique ré-attribué. Dans le procédé mentionné ci-dessus, l'adresse virtuelle du processus dans la totalité du processus est inchangée, de façon à garantir qu'un service est ininterrompu et à réaliser l'isolement en ligne d'un espace de mémoire défaillante.
PCT/CN2015/071008 2015-01-19 2015-01-19 Procédé et dispositif d'isolement de défaillance de mémoire WO2016115661A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201580011928.2A CN106133704A (zh) 2015-01-19 2015-01-19 内存故障隔离方法和装置
PCT/CN2015/071008 WO2016115661A1 (fr) 2015-01-19 2015-01-19 Procédé et dispositif d'isolement de défaillance de mémoire

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2015/071008 WO2016115661A1 (fr) 2015-01-19 2015-01-19 Procédé et dispositif d'isolement de défaillance de mémoire

Publications (1)

Publication Number Publication Date
WO2016115661A1 true WO2016115661A1 (fr) 2016-07-28

Family

ID=56416247

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/071008 WO2016115661A1 (fr) 2015-01-19 2015-01-19 Procédé et dispositif d'isolement de défaillance de mémoire

Country Status (2)

Country Link
CN (1) CN106133704A (fr)
WO (1) WO2016115661A1 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110532124A (zh) * 2019-09-06 2019-12-03 西安易朴通讯技术有限公司 内存隔离方法及装置
WO2021185279A1 (fr) * 2020-03-20 2021-09-23 华为技术有限公司 Procédé de traitement de défaillance de mémoire et dispositif associé
CN113515405A (zh) * 2021-07-09 2021-10-19 维沃移动通信有限公司 地址管理方法和装置
CN114020525A (zh) * 2021-10-21 2022-02-08 苏州浪潮智能科技有限公司 故障隔离方法、装置、设备及存储介质
CN114461436A (zh) * 2022-04-08 2022-05-10 苏州浪潮智能科技有限公司 一种内存故障处理方法、装置及计算机可读存储介质
CN115617274A (zh) * 2022-10-27 2023-01-17 亿铸科技(杭州)有限责任公司 一种具备坏块管理功能的存内计算装置及操作方法

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108579093B (zh) * 2018-05-10 2023-11-03 腾讯科技（上海）有限公司 目标进程的运行保护方法、装置及可读介质
CN110858167B (zh) * 2018-08-22 2023-06-27 阿里巴巴集团控股有限公司 一种内存故障隔离方法、装置及设备
CN109522122B (zh) * 2018-11-14 2021-12-17 郑州云海信息技术有限公司 一种内存管理方法、系统、装置及计算机可读存储介质
CN109753378A (zh) * 2019-01-02 2019-05-14 浪潮商用机器有限公司 一种内存故障的隔离方法、装置、系统及可读存储介质
CN112667422A (zh) * 2019-10-16 2021-04-16 华为技术有限公司 内存故障处理方法及装置、计算设备、存储介质
CN114780473A (zh) * 2022-05-18 2022-07-22 长鑫存储技术有限公司 内存条热插拔方法及装置、内存条
KR20230161864A (ko) 2022-05-18 2023-11-28 창신 메모리 테크놀로지즈 아이엔씨 메모리 핫 플러그 방법 및 장치, 메모리
CN115686901B (zh) * 2022-10-25 2023-08-04 超聚变数字技术有限公司 内存故障分析方法及计算机设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090307563A1 (en) * 2008-06-05 2009-12-10 Ibm Corporation (Almaden Research Center) Replacing bad hard drive sectors using mram
CN102541676A (zh) * 2011-12-22 2012-07-04 福建新大陆通信科技股份有限公司 一种nand flash的状态检测及映射方法
CN103064804A (zh) * 2012-12-13 2013-04-24 华为技术有限公司 磁盘数据的访问控制方法及装置
CN103186471A (zh) * 2011-12-30 2013-07-03 深圳市共进电子股份有限公司 存储设备中坏块的管理方法及系统
CN103778065A (zh) * 2012-10-25 2014-05-07 北京兆易创新科技股份有限公司 一种闪速存储器及其进行坏块管理的方法

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103631721A (zh) * 2012-08-23 2014-03-12 华为技术有限公司 一种隔离内存中坏块的方法及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090307563A1 (en) * 2008-06-05 2009-12-10 Ibm Corporation (Almaden Research Center) Replacing bad hard drive sectors using mram
CN102541676A (zh) * 2011-12-22 2012-07-04 福建新大陆通信科技股份有限公司 一种nand flash的状态检测及映射方法
CN103186471A (zh) * 2011-12-30 2013-07-03 深圳市共进电子股份有限公司 存储设备中坏块的管理方法及系统
CN103778065A (zh) * 2012-10-25 2014-05-07 北京兆易创新科技股份有限公司 一种闪速存储器及其进行坏块管理的方法
CN103064804A (zh) * 2012-12-13 2013-04-24 华为技术有限公司 磁盘数据的访问控制方法及装置

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110532124A (zh) * 2019-09-06 2019-12-03 西安易朴通讯技术有限公司 内存隔离方法及装置
WO2021185279A1 (fr) * 2020-03-20 2021-09-23 华为技术有限公司 Procédé de traitement de défaillance de mémoire et dispositif associé
CN113495799A (zh) * 2020-03-20 2021-10-12 华为技术有限公司 一种内存故障处理方法及相关设备
CN113495799B (zh) * 2020-03-20 2024-04-12 华为技术有限公司 一种内存故障处理方法及相关设备
CN113515405A (zh) * 2021-07-09 2021-10-19 维沃移动通信有限公司 地址管理方法和装置
CN114020525A (zh) * 2021-10-21 2022-02-08 苏州浪潮智能科技有限公司 故障隔离方法、装置、设备及存储介质
CN114020525B (zh) * 2021-10-21 2024-04-19 苏州浪潮智能科技有限公司 故障隔离方法、装置、设备及存储介质
CN114461436A (zh) * 2022-04-08 2022-05-10 苏州浪潮智能科技有限公司 一种内存故障处理方法、装置及计算机可读存储介质
CN115617274A (zh) * 2022-10-27 2023-01-17 亿铸科技(杭州)有限责任公司 一种具备坏块管理功能的存内计算装置及操作方法

Also Published As

Publication number Publication date
CN106133704A (zh) 2016-11-16

Similar Documents

Publication Publication Date Title
WO2016115661A1 (fr) Procédé et dispositif d'isolement de défaillance de mémoire
CN106776159B (zh) 具有故障转移的快速外围元件互连网络系统与操作方法
US8135985B2 (en) High availability support for virtual machines
US7644252B2 (en) Multi-processor system and memory accessing method
US9501231B2 (en) Storage system and storage control method
WO2013081616A1 (fr) Migration et réargenture de mémoire fondées sur le matériel
US10235282B2 (en) Computer system, computer, and method to manage allocation of virtual and physical memory areas
WO2022193768A1 (fr) Procédé d'exécution d'une instruction de lecture-écriture en mémoire, et dispositif informatique
JP2008269142A (ja) ディスクアレイ装置
US9646721B1 (en) Solid state drive bad block management
JP6165964B2 (ja) 計算機
US20170277632A1 (en) Virtual computer system control method and virtual computer system
JP2011227766A (ja) 記憶手段の管理方法、仮想計算機システムおよびプログラム
JP6540334B2 (ja) システム、情報処理装置、および情報処理方法
US11822419B2 (en) Error information processing method and device, and storage medium
US11182252B2 (en) High availability state machine and recovery
CN109558068B (zh) 数据迁移方法及迁移系统
US11256585B2 (en) Storage system
JP6677021B2 (ja) 情報処理装置、情報処理方法、プログラム
EP2921965B1 (fr) Dispositif de traitement d'informations et procédé de gestion de mémoire partagée
JP2017033375A (ja) 並列計算システム、マイグレーション方法、及びマイグレーションプログラム
WO2014024279A1 (fr) Dispositif, procédé et programme de récupération après une défaillance mémoire
JP6175566B2 (ja) ストレージシステム及び記憶制御方法
JP6682897B2 (ja) 通信設定方法、通信設定プログラム、情報処理装置および情報処理システム
US20160259695A1 (en) Storage and control method of the same

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15878339

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15878339

Country of ref document: EP

Kind code of ref document: A1