US11093141B2 - Method and apparatus for caching data - Google Patents
Method and apparatus for caching data Download PDFInfo
- Publication number
- US11093141B2 US11093141B2 US16/572,188 US201916572188A US11093141B2 US 11093141 B2 US11093141 B2 US 11093141B2 US 201916572188 A US201916572188 A US 201916572188A US 11093141 B2 US11093141 B2 US 11093141B2
- Authority
- US
- United States
- Prior art keywords
- data
- storage
- memory pool
- module
- response
- 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.)
- Active, expires
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/061—Improving I/O performance
- G06F3/0613—Improving I/O performance in relation to throughput
-
- 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
- G06F12/08—Addressing or allocation; Relocation in hierarchically structured memory systems, e.g. virtual memory systems
- G06F12/0802—Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches
- G06F12/0806—Multiuser, multiprocessor or multiprocessing cache systems
- G06F12/0842—Multiuser, multiprocessor or multiprocessing cache systems for multiprocessing or multitasking
-
- 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
- G06F12/08—Addressing or allocation; Relocation in hierarchically structured memory systems, e.g. virtual memory systems
- G06F12/0802—Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches
- G06F12/0806—Multiuser, multiprocessor or multiprocessing cache systems
- G06F12/0815—Cache consistency protocols
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/0614—Improving the reliability of storage systems
- G06F3/0619—Improving the reliability of storage systems in relation to data integrity, e.g. data losses, bit errors
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/0625—Power saving in storage systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0629—Configuration or reconfiguration of storage systems
- G06F3/0631—Configuration or reconfiguration of storage systems by allocating resources to storage systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0646—Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems
- G06F3/065—Replication mechanisms
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0655—Vertical data movement, i.e. input-output transfer; data movement between one or more hosts and one or more storage devices
- G06F3/0659—Command handling arrangements, e.g. command buffers, queues, command scheduling
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2212/00—Indexing scheme relating to accessing, addressing or allocation within memory systems or architectures
- G06F2212/28—Using a specific disk cache architecture
- G06F2212/283—Plural cache memories
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2212/00—Indexing scheme relating to accessing, addressing or allocation within memory systems or architectures
- G06F2212/28—Using a specific disk cache architecture
- G06F2212/285—Redundant cache memory
- G06F2212/286—Mirrored cache memory
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2212/00—Indexing scheme relating to accessing, addressing or allocation within memory systems or architectures
- G06F2212/62—Details of cache specific to multiprocessor cache arrangements
- G06F2212/621—Coherency control relating to peripheral accessing, e.g. from DMA or I/O device
Definitions
- Embodiments of the present disclosure generally relate to the field of data storage, and specifically relate to a scheme for caching data.
- a system architecture including a plurality of storage processors (SPs, also called processing nodes) attached with a shared disk is usually utilized to improve computing capability and input/output (IO) throughput of the storage product.
- SPs storage processors
- IO input/output
- the plurality of storage processors are connected via an internal communication interface and perform data synchronization with the internal communication interface.
- a cache module for caching data to be written into the shared disk.
- such cache module may be only used for caching and synchronizing (e.g., with a peer SP) user data (namely, the data written into the shared disk) and may only be used by an upper module above the cache module.
- non-user data such as mapping information of storage objects and metadata of a file system
- mapping information of storage objects and metadata of a file system is only stored in a local memory and will not be synchronized to a peer memory, which thereby might lead to inconsistent states of the processors.
- a lower module below the cache module cannot use the service provided by the cache module. Therefore, the data in the lower module cannot be cached conveniently.
- the data in the cache e.g., the data which has not been written into the shared disk yet
- Embodiments of the present disclosure provide a scheme for caching data.
- a method for caching data comprises: in response to receiving a first request for caching data from a client module running on a first processor, writing the data into a first cache module on the first processor; transmitting, to the client module, a first indication that the data has been written into the first cache module; in response to receiving from the client module a second request for synchronizing the data to a second processor, transmitting, to the second processor, a first command for causing the data to be written into a second cache module on the second processor; and transmitting, to the client module, a second indication that the data has been synchronized.
- a method for caching data comprises: transmitting, to a first cache module on a first processor, a first request for caching data; in response to receiving from the first cache module a first indication that the data has been written into the first cache module, transmitting, to the first cache module, a second request for synchronizing the data to a second processor, such that the data is written into a second cache module on the second processor; and receiving a second indication that the data has been synchronized.
- a method for caching data comprises: in response to receiving from a first processor a first command for synchronizing data cached in a first cache module on the first processor to a second processor, writing the data into a second cache module on the second processor.
- a first cache component located on a first processor and comprises a controller.
- the controller is configured to in response to receiving a first request for caching data from a client module running on a first processor, write the data into the first cache component; transmit, to the client module, a first indication that the data has been written into the first cache component; in response to receiving from the client module a second request for synchronizing the data to a second processor, transmit, to the second processor, a first command for causing the data to be written into a second cache component on the second processor; and transmit, to the client module, a second indication that the data has been synchronized.
- a client component running on a first processor and comprises a controller.
- the controller is configured to: transmit, to a first cache module on the first processor, a first request for caching data; in response to receiving from the first cache module a first indication that the data has been written into the first cache module, transmit, to the first cache module, a second request for synchronizing the data to a second processor, such that the data is written into a second cache module on the second processor; and receive a second indication that the data has been synchronized.
- a second cache component located on a second processor and comprises a controller.
- the controller is configured to, in response to receiving from a first processor a first command for synchronizing data cached in a first cache component on the first processor to a second processor, write the data into the second cache component.
- a storage system comprising a first processor and a second processor.
- the first processor and the second processing are communicatively coupled.
- the first processor at least comprises the first cache component according to the fourth aspect of the present disclosure.
- the second processor at least comprises the second cache component according to the sixth aspect of the present disclosure.
- a computer program product that is tangibly stored on a non-transient computer readable medium and includes machine-executable instructions.
- the machine-executable instructions when being executed, cause the machine to execute any step of the method according to the first aspect of the present disclosure.
- a computer program product that is tangibly stored on a non-transient computer readable medium and includes machine-executable instructions.
- the machine-executable instructions when being executed, cause the machine to execute any step of the method according to the second aspect of the present disclosure.
- a computer program product that is tangibly stored on a non-transient computer readable medium and includes machine-executable instructions.
- the machine-executable instructions when being executed, cause the machine to execute any step of the method according to the third aspect of the present disclosure.
- FIG. 1 illustrates a block diagram of an example storage system 100 having two SPs sharing one disk in a conventional scheme
- FIG. 2 illustrates a block diagram of a storage system 200 according to an embodiment of the present disclosure
- FIG. 3 illustrates a flowchart of a method 300 for caching data according to an embodiment of the present disclosure
- FIG. 4 illustrates a flowchart of a method 400 for obtaining a memory for caching data according to an embodiment of the present disclosure
- FIG. 5 illustrates a flowchart of a method 500 for performing power supply failure protection for the cached data according to an embodiment of the present disclosure
- FIG. 6 illustrates a flowchart of a method 600 for recovering data in a cache module according to an embodiment of the present disclosure
- FIG. 7 illustrates a flowchart of a method 700 for recovering data in a client module according to an embodiment of the present disclosure
- FIG. 8 illustrates a block diagram of a cache component 800 according to an embodiment of the present disclosure.
- FIG. 9 illustrates a block diagram of a computer system 900 adapted to implement exemplary embodiments of the present disclosure.
- the term “includes” and its variants are to be read as open-ended terms that mean “includes, but is not limited to.”
- the term “or” is to be read as “and/or” unless the context clearly indicates otherwise.
- the term “based on” is to be read as “based at least in part on.”
- the term “one example implementation” and “an example implementation” are to be read as “at least one example implementation.”
- the term “another implementation” is to be read as “at least one other implementation.” Terms “a first”, “a second” and others can denote different or identical objects. The following text may also contain other explicit or implicit definitions.
- FIG. 1 illustrates a block diagram of an example storage system 100 having two SPs sharing one disk in a conventional scheme.
- the storage system 100 there are two SPs sharing one disk 130 , namely, SP 110 and SP 120 .
- the two SPs may interact with each other via a command interface (CMI) 140 .
- CMI command interface
- the SP 110 includes a cache module 112 , an upper module 111 above the cache module 112 and a lower module 113 below the cache module 112 .
- the SP 120 includes a cache module 122 corresponding to the cache module 112 , an upper module 121 corresponding to the upper module 111 and a lower module 123 corresponding to the lower module 113 .
- SP 110 is taken as an example.
- the main function of the cache module 112 described here is to temporarily store user data in a dynamic random access memory (DRAM), and then write it into the disk 130 at suitable time.
- the cache module 112 may perform data synchronization with the cache module 122 via the CMI 140 . For example, when a host writes data to the SP 110 , the data will be written into the cache module 112 , and then synchronized to the cache module 122 .
- the host may read from the SP 120 the data written to the SP 110 .
- the upper module 111 described here may include, for example, a host module interfacing with the host, a user logic unit number module for providing logic storage units, and a file system module for providing a file system interface.
- the upper module 111 does not cache data directly by itself. When user data needs to be cached, the upper module 111 may need to write the user data into the cache module 112 .
- the upper module 111 may read the cached user data from the cache module 112 . Since for example the user logic unit number module and the file system module usually do not perform data synchronization with the SP 120 (namely, the upper module 121 ), the non-user data such as mapping information of logic storage units and metadata of the file system will only be stored in the SP 110 .
- the lower module 113 described here may include, for example, a flash cache module for providing data cache on a flash memory, a RAID module for providing a Redundant Arrays of Independent Disks (RAID) interface, a disk drive module and so on.
- a flash cache module for providing data cache on a flash memory
- a RAID module for providing a Redundant Arrays of Independent Disks (RAID) interface
- a disk drive module and so on.
- non-user data such as mapping information of logic storage units and metadata of a file system may only be stored in a local memory and not synchronized to a peer memory, which might lead to inconsistent states of the processors.
- the lower module below the cache module cannot use the service provided by the cache module. Therefore, the data in the lower module cannot be cached conveniently.
- the data in the cache e.g., the data which has not been written into the shared disk 130 yet
- example embodiments of the present disclosure propose a scheme for caching data.
- the scheme utilizes an independent cache module to provide cache service for other modules (hereinafter referred to as “client modules”) on the SP, so that the client modules can cache data like using an ordinary memory, without concerning how data are stored and synchronized.
- the independent cache module includes a persistent storage medium capable of providing power supply failure protection with respect to the cached data.
- FIG. 2 illustrates a block diagram of a storage system 200 according to an embodiment of the present disclosure. Similar to the storage system 100 as shown in FIG. 1 , the storage system 200 may include SP 210 and SP 220 . The two SPs share one disk 230 and interact with each other via CMI 240 .
- the SP 210 may include a client module 211 and a cache module 212 .
- the client module 211 may include the upper module 111 and the lower module 113 as shown in FIG. 1 . That is to say, the client module 211 may include but not limited to a host module, a user logic unit number module, a file system module, a volume cache module, a flash cache module, a RAID module, a disk driving module and so on. More generally, the client module 211 may include any module running on the SP 210 which needs to cache data, and the data to be cached may include user data (e.g., data to be written into the disk 230 ) and non-user data (e.g., file system metadata).
- user data e.g., data to be written into the disk 230
- non-user data e.g., file system metadata
- the SP 220 may include a client module 221 and a cache module 222 .
- the client module 221 corresponds to the client module 211
- the cache module 222 corresponds to the cache module 212 . That is, the client module 221 may include any module running on the SP 220 which needs to cache data, and the data to be cached may include user data and non-user data.
- the storage system 200 may further include a backup battery unit (BBU, not shown in FIG. 2 ).
- BBU backup battery unit
- the BBU may supply power to the SP 210 and SP 220 (e.g., including memories located thereon) in place of an external power supply.
- the BBU may be used to provide power supply failure protection to the storage system 200 . Further depictions about the power supply failure protection will be provided in the following.
- FIG. 3 illustrates a flowchart of a method 300 for caching data according to an embodiment of the present disclosure. Actions involved in the method 300 will be described in conjunction with FIG. 2 .
- the depictions of the method 300 may involve two SPs, namely, SP 210 and SP 220 . More specifically, the depictions of the method 300 involve the client module 211 , the cache module 212 , the cache module 222 and the client module 221 .
- a first column of actions may be performed by the client module 211
- a second column of actions may be performed by the cache module 212
- a third column of actions may be performed by the cache module 222
- a fourth column of actions may be performed by the client module 221 .
- the SP 210 and a “first processor” can be used interchangeably.
- the SP 220 and a “second processor” can be used interchangeably.
- the client module 211 and a “first client” can be used interchangeably.
- the cache module 212 and a “first cache module” can be used interchangeably.
- the cache module 222 and a “second cache module” can be used interchangeably.
- the client module 221 and a “second client module” can be used interchangeably. It should be appreciated that the method 300 may further include additional actions not shown and/or omit some actions as shown, and the scope of the present disclosure is not limited in this regard.
- the first client module transmits to the first cache module a first request for caching data.
- the data may be the user data to be written into the disk 230 , or the non-user data not to be written into the disk 230 , for example, the metadata of the file system, the mapping information of logic storage units or the like.
- the data may be any data that the first client module desires to cache.
- the data is written into the first cache module in response to the first request for caching the data being received from the first client module. Then, at Block 312 , a first indication that the data has been written into the first cache module is transmitted to the first client module.
- the first client module in response to receiving from the first cache module the first indication that the data has been written into the first cache module, transmits to the first cache module a second request for synchronizing the data to the second processor.
- the second request may cause the data to be written into the second cache module.
- a first command is transmitted to the second processor for causing the data to be written into the second cache module.
- the data is written into the second cache module in response to the first command being received from the first processor.
- the first cache module transmits to the first client module a second indication that the data has been synchronized. Additionally or alternatively, at Block 322 , the second cache module may transmit to the second client module a third indication that the data has been synchronized.
- the first client receives the second indication. Additionally or alternatively, at Block 331 , the second client receives the third indication.
- the actions performed by the SP 210 in FIG. 3 may also be performed by the SP 220 , while the actions performed by the SP 220 may also be performed by the SP 110 . That is, the request to cache data may also be initiated by the second client module. In this case, Blocks 301 - 303 may be performed by the second client module, Blocks 311 - 314 may be performed by the second cache module, and Blocks 321 - 322 may be performed by the first cache module, and Block 311 may be performed by the first client.
- the above depictions of the method 300 only involve two SPs, it should be appreciated that the method 300 may also be applied to the storage system having a plurality of SPs. The scope of the present disclose is not limited in this aspect.
- either the user data written into the disk or non-user data such as file system metadata can be synchronized among the plurality of SPs so that the states of the SPs can remain consistent.
- memories in the cache modules are organized in a tree structure.
- a root of the tree may be a memory pool manager which manages one or more memory pools.
- the “memory pool” used here refers to a set of memories having the same attributes and usage.
- a memory pool may only belong to a specific client module, and the client module may create a plurality of memory pools.
- the memory pool may manage one or more storage objects, and the storage objects are used to manage storage blocks and their attributes to be used by the client.
- the client module may firstly request to create a memory pool, and then request to allocate a storage object from the memory pool. After the client module obtains the allocated storage object, the client module may use the storage object to perform data cache.
- FIG. 4 illustrates a flowchart of a method 400 for obtaining a memory for caching data according to an embodiment of the present disclosure.
- the method 400 may be performed prior to the method 300 .
- the actions involved in the method 400 may be described in conjunction with FIG. 2 . Similar to FIG. 3 , the depictions of the method 400 involve the client module 211 , the cache module 212 , the cache module 222 and the client module 221 .
- a first column of actions can be performed by the client module 211
- a second column of actions can be performed by the cache module 212
- a third column of actions can be performed by the cache module 222
- a fourth column of actions can be performed by the client module 221 .
- the method 400 may further include additional actions not shown and/or omit some actions as shown, and the scope of the present disclosure is not limited in this regard.
- the first client transmits to the first cache module a third request to create mirrored memory pools on the first and second cache modules.
- the third request may designate attributes of the mirror memory pools to be created, for example, whether to activate power supply failure protection, whether to synchronize the cache data or the like.
- a first memory pool is created in the first cache module in response to the third request being received from the first client module.
- a unique identifier may be allocated to identify the first memory pool.
- the first cache module transmits to the second processor a second command for creating in the second cache module a second memory pool corresponding to the first memory pool.
- the second memory pool is created in the second cache module in response to the second command being received from the first processor.
- a unique identifier may be allocated to identify the second memory pool.
- the first cache module in response to the first memory pool being created, returns the created first memory pool (e.g., the identifier of the first memory pool) to the first client module.
- the second cache module in response to the second memory pool being created, returns the created second memory pool (e.g., the identifier of the second memory pool) to the second client module.
- the first client may obtain from the first cache module the first memory pool (e.g., the identifier of the first memory pool) in the mirrored memory pools.
- the first memory pool is created on the first cache module.
- the second client may obtain from the second cache module the second memory pool (e.g., the identifier of the second memory pool) in the mirrored memory pool.
- the second memory pool is created on the second cache module.
- the first client may transmit to the first cache module a fourth request to allocate from the mirrored memory pools mirrored storage objects for caching data.
- the first cache module allocates a first storage object from the first memory pool.
- the first cache module transmits to the second processor a third command for allocating a second storage object corresponding to the first storage object.
- the second storage object is allocated from the second memory pool in response to the third command being received from the first processor.
- the first cache module in response to the first storage object being allocated, returns the allocated first storage object to the first client module. Similarly, at Block 424 , in response to the second storage object being allocated, the second cache module returns the allocated second storage object to the second client module.
- the first client obtains from the first cache module the first storage object in the mirrored memory objects.
- the first storage object is allocated from the first memory pool.
- the second client obtains from the second cache module the second storage object in the mirrored memory objects.
- the second storage object is allocated from the second memory pool.
- the actions performed by the SP 210 in FIG. 4 may also be performed by the SP 220 , while the actions performed by the SP 220 may also be performed by the SP 110 . That is, the request to create mirrored memory pools may also be initiated by the second client module. In this case, Blocks 401 - 403 may be performed by the second client module, Blocks 411 - 416 may be performed by the second cache module, and Blocks 421 - 424 may be performed by the first cache module, and Blocks 431 - 432 may be performed by the first client.
- the above depictions of the method 400 only involve two SPs, it should be appreciated that the method 400 may also be applied to the storage system having a plurality of SPs. The scope of the present disclose is not limited in this aspect.
- the client modules can cache data like using an ordinary memory, without concerning how data are stored and synchronized.
- the method 300 may be performed. That is, the first client module may transmit a request to the first cache module to write the data into the first storage object (Block 301 ). Correspondingly, the first cache module may write the data into the first storage object (Block 311 ). Then, the first client module may transmit a request to the first cache module to synchronize data to the second processor (Block 302 ). The first cache module may transmit to the second processor a command for causing the data to be written into the second cache module (Block 313 ). Correspondingly, the second cache module may write data into the second storage object (Block 321 ).
- the cache modules 212 and 222 as shown in FIG. 2 may include a transient storage medium and a persistent storage medium.
- the transient storage medium for example may include a dynamic random access memory (DRAM) and any transient storage medium currently known or to be developed.
- the persistent storage medium for example may include a solid-state disk (SSD) and any persistent storage medium current known or to be developed.
- the data may be cached in the transient storage medium, while the persistent storage medium may be used to provide power supply failure protection to the cached data. For example, when the power supply fails, the cached data may be transferred to the persistent storage medium, and when the power supply failure recovers, the data may be transferred from the persistent memory back to the transient storage medium.
- FIG. 5 illustrates a flowchart of a method 500 for performing power supply failure protection for the cached data according to an embodiment of the present disclosure.
- the method 500 may be performed by the cache module 212 and/or 222 .
- the method 500 may be performed in parallel with the method 300 and/or 400 . It should be appreciated that the method 500 may further include additional actions not shown and/or omit some actions as shown, and the scope of the present disclosure is not limited in this regard.
- the cache module transfers the data from the transient storage medium to the persistent storage medium.
- FIG. 6 illustrates a flowchart of a method 600 for recovering data in a cache module according to an embodiment of the present disclosure.
- the method 600 may be performed as an example of the Block 502 in the method 500 .
- the memory pool is re-created in the transient storage medium.
- the memory object is re-allocated from the recreated memory pool.
- the data is transferred from the persistent storage medium to the corresponding memory object.
- the method 600 may further include additional actions not shown and/or omit some actions as shown, and the scope of the present disclosure is not limited in this regard.
- the method 600 may be performed iteratively until all memory pools and storage objects are re-created in the cache module.
- the cache module may transmit to the client an indication that the caching of the data has recovered from the power supply failure.
- the client needs to perform some corresponding actions to complete data recovery. Additionally, the client may perform the corresponding actions in response to receiving the indication that the caching of the data has recovered from the power supply failure.
- FIG. 7 illustrates a flowchart of a method 700 for recovering data in a client module according to an embodiment of the present disclosure.
- the method 700 may be performed by the client module 211 and/or 221 .
- the method 700 may be executed consecutively with the method 500 . It should be appreciated that method 700 may further include additional actions not shown and/or omit some shown actions, and the scope of the present disclosure is not limited in this regard.
- a memory pool is obtained from the cache module in response to receiving from the cache module (e.g., the cache module 212 and/or 222 ) the indication that the caching of the data has recovered from the power supply failure.
- the cache module may return the re-created memory pool (e.g., the identifier of the memory pool) to the client module.
- the client module obtains the storage object from the cache module.
- the cache module may return the re-created storage object to the client module.
- the client module can obtain the memory used by itself before the power supply failure, and then use the obtained memory to perform subsequent procedures.
- FIG. 8 illustrates a block diagram of a cache component 800 according to an embodiment of the present disclosure.
- the cache module 212 and/or 222 as shown in FIG. 2 may be implemented as the cache component 800 .
- the cache component 800 may include a controller 810 , a transient storage medium 820 and a persistent storage medium 830 .
- the controller 810 may be configured to write data into the cache component 800 (e.g., the transient storage medium 820 ) in response to receiving a first request for caching data from a client module running on a first processor.
- the controller 810 may be further configured to transmit to the client module a first indication that the data has been written into the cache component 800 .
- the controller 810 may be further configured to, in response to receiving from the client module a second request for synchronizing the data to a second processor, transmit to the second processor a first command for causing the data to be written into the second cache module on the second processor. In addition, the controller 810 may be further configured to transmit to the client module a second indication that the data has been synchronized.
- the controller 810 may be further configured to, in response to receiving a first signal indicative of occurrence of a power supply failure, transfer the data from the transient storage medium 820 to the persistent storage medium 830 .
- the controller 810 may be further configured to, in response to receiving a second signal indicative of recovery of the power supply failure, transfer the data from the persistent storage medium 830 back to the transient storage medium 820 .
- the controller 810 may be further configured to transmit to the client module an indication that the caching of the data has recovered from the power supply failure.
- any client module may conveniently implement an active-active mode, that is, states of two mirrored client modules in the two SPs stay completely consistent.
- parts of the cache component 800 are not shown in FIG. 8 .
- parts of the cache component 800 may be hardware parts or software parts.
- the cache component 800 may be partially or completely implemented using software and/or firmware, e.g., implemented as a computer program product embodied on a computer readable medium.
- the cache component 800 may be partially or completely implemented based on hardware, e.g., implemented as an integrated circuit (IC), an application-specific integrated circuit (ASIC), a system on chip (SOC), a field programmable gate array (FPGA), etc.
- IC integrated circuit
- ASIC application-specific integrated circuit
- SOC system on chip
- FPGA field programmable gate array
- Embodiments of the present disclosure further provide a client component.
- the client component runs on the first processor and comprises a controller.
- the controller is configured to: transmit, to a first cache module on the first processor, a first request for caching data; in response to receiving from the first cache module a first indication that the data has been written into the first cache module, transmit, to the first cache module, a second request for synchronizing the data to a second processor, such that the data is written into a second cache module on the second processor; and receive a second indication that the data has been synchronized.
- FIG. 9 illustrates a block diagram of an example device 900 adapted to implement an exemplary embodiment of the present disclosure.
- the device 900 comprises a central processing unit (CPU) 901 that may perform various appropriate actions and processing based on computer program instructions stored in a read-only memory (ROM) 902 or computer program instructions loaded from a memory unit 908 to a random access memory (RAM) 903 .
- ROM read-only memory
- RAM random access memory
- the CPU 901 , ROM 902 and RAM 903 are connected to each other via a bus 904 .
- An input/output (I/O) interface 905 is also connected to the bus 904 .
- Various components in the device 900 are connected to the I/O interface 905 , including: an input 909 such as a keyboard, a mouse and the like; an output unit 907 including various kinds of displays and a loudspeaker, etc.; a memory unit 908 including a magnetic disk, an optical disk, and etc.; a communication unit 909 including a network card, a modem, and a wireless communication transceiver, etc.
- the communication unit 909 allows the device 900 to exchange information/data with other devices through a computer network such as the Internet and/or various kinds of telecommunications networks.
- the methods 300 , 400 , 500 and/or 600 may be executed by the processing unit 901 .
- the methods 300 , 400 , 500 and/or 600 may be implemented as a computer software program that is tangibly embodied on a machine readable medium, e.g., the storage unit 908 .
- part or all of the computer program may be loaded and/or mounted onto the device 900 via ROM 902 and/or communication unit 909 .
- the computer program is loaded to the RAM 903 and executed by the CPU 901 , one or more steps of the at least one of the methods 300 , 400 , 500 and/or 600 as described above may be executed.
- the present disclosure may be a method, apparatus, system and/or computer program product.
- the computer program product may include a computer readable medium on which computer readable program instructions for executing various aspects of the present disclosure are embodied.
- the computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device.
- the computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing.
- a non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing.
- RAM random access memory
- ROM read-only memory
- EPROM or Flash memory erasable programmable read-only memory
- SRAM static random access memory
- CD-ROM compact disc read-only memory
- DVD digital versatile disk
- memory stick a floppy disk
- a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon
- a computer readable storage medium is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.
- Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network.
- the network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers.
- a network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.
- Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++ or the like, and conventional procedural programming languages, such as the “C” programming language or similar programming languages.
- the computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server.
- the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
- electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.
- These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
- These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.
- the computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
- each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s).
- the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Computer Security & Cryptography (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Description
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/572,188 US11093141B2 (en) | 2016-12-21 | 2019-09-16 | Method and apparatus for caching data |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201611192431.8 | 2016-12-21 | ||
CN201611192431.8A CN108388524A (en) | 2016-12-21 | 2016-12-21 | For data cached method and apparatus |
US15/848,488 US10496287B2 (en) | 2016-12-21 | 2017-12-20 | Method and apparatus for caching data |
US16/572,188 US11093141B2 (en) | 2016-12-21 | 2019-09-16 | Method and apparatus for caching data |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/848,488 Continuation US10496287B2 (en) | 2016-12-21 | 2017-12-20 | Method and apparatus for caching data |
Publications (2)
Publication Number | Publication Date |
---|---|
US20200012438A1 US20200012438A1 (en) | 2020-01-09 |
US11093141B2 true US11093141B2 (en) | 2021-08-17 |
Family
ID=62561711
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/848,488 Active US10496287B2 (en) | 2016-12-21 | 2017-12-20 | Method and apparatus for caching data |
US16/572,188 Active 2038-01-20 US11093141B2 (en) | 2016-12-21 | 2019-09-16 | Method and apparatus for caching data |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/848,488 Active US10496287B2 (en) | 2016-12-21 | 2017-12-20 | Method and apparatus for caching data |
Country Status (2)
Country | Link |
---|---|
US (2) | US10496287B2 (en) |
CN (1) | CN108388524A (en) |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108388524A (en) * | 2016-12-21 | 2018-08-10 | 伊姆西Ip控股有限责任公司 | For data cached method and apparatus |
US10902020B2 (en) | 2018-06-08 | 2021-01-26 | International Business Machines Corporation | Multiple cache processing of streaming data |
CN111124993B (en) * | 2018-10-31 | 2023-09-01 | 伊姆西Ip控股有限责任公司 | Method, apparatus and program product for reducing cache data mirror latency in I/O processing |
US11409666B2 (en) * | 2019-11-22 | 2022-08-09 | EMC IP Holding Company LLC | Techniques for providing I/O hints using I/O flags |
CN111026330B (en) * | 2019-11-25 | 2023-07-25 | 湖南博匠信息科技有限公司 | Data caching device and method based on SD card and airborne storage system |
Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040103238A1 (en) * | 2002-11-26 | 2004-05-27 | M-Systems Flash Disk Pioneers Ltd. | Appliance, including a flash memory, that is robust under power failure |
CN102346740A (en) | 2010-08-02 | 2012-02-08 | 联想(北京)有限公司 | File synchronization method, electronic equipment and synchronization system |
US20130013871A1 (en) | 2011-07-04 | 2013-01-10 | Fujitsu Limited | Information processing system and data processing method |
CN104881368A (en) | 2015-05-07 | 2015-09-02 | 北京飞杰信息技术有限公司 | Cache synchronization method and system applied to double control storage system |
CN105007307A (en) | 2015-06-18 | 2015-10-28 | 浪潮(北京)电子信息产业有限公司 | Storage control method and system |
CN105739924A (en) | 2016-01-29 | 2016-07-06 | 华为技术有限公司 | Cache cluster-based cache method and system |
US9454326B1 (en) | 2013-03-31 | 2016-09-27 | Emc Corporation | File metro cluster for site failover of data storage system |
US9753662B1 (en) * | 2016-09-26 | 2017-09-05 | International Business Machines Corporation | Using mirror indicators to determine whether to mirror tracks in a data set in a primary volume mirrored to a secondary volume |
US20180173435A1 (en) * | 2016-12-21 | 2018-06-21 | EMC IP Holding Company LLC | Method and apparatus for caching data |
Family Cites Families (42)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7233977B2 (en) | 1998-12-18 | 2007-06-19 | Emc Corporation | Messaging mechanism employing mailboxes for inter processor communications |
US7340555B2 (en) * | 2001-09-28 | 2008-03-04 | Dot Hill Systems Corporation | RAID system for performing efficient mirrored posted-write operations |
US7536495B2 (en) * | 2001-09-28 | 2009-05-19 | Dot Hill Systems Corporation | Certified memory-to-memory data transfer between active-active raid controllers |
US7171610B2 (en) * | 2002-06-12 | 2007-01-30 | International Business Machines Corporation | Method, system, and article of manufacture for preventing data loss |
US7062675B1 (en) | 2002-06-25 | 2006-06-13 | Emc Corporation | Data storage cache system shutdown scheme |
EP1426963A2 (en) * | 2002-11-15 | 2004-06-09 | Matsushita Electric Industrial Co., Ltd. | Recording apparatus and recording method with data recovery means |
US7143248B2 (en) * | 2003-01-29 | 2006-11-28 | Steven Bress | Systems and methods for restoring critical data to computer long-term memory device controllers |
US20050063216A1 (en) * | 2003-09-24 | 2005-03-24 | Wilkins Virgil V. | System and method for providing efficient redundancy mirroring communications in an n-way scalable network storage system |
JP4703959B2 (en) * | 2003-12-03 | 2011-06-15 | 株式会社日立製作所 | Storage device system and replication creation method thereof |
US8677086B2 (en) * | 2004-06-30 | 2014-03-18 | Emc Corporation | System for caching data |
US20060212644A1 (en) * | 2005-03-21 | 2006-09-21 | Acton John D | Non-volatile backup for data cache |
JP4756992B2 (en) * | 2005-10-25 | 2011-08-24 | 株式会社日立製作所 | Storage system and storage control method |
US7421552B2 (en) | 2006-03-17 | 2008-09-02 | Emc Corporation | Techniques for managing data within a data storage system utilizing a flash-based memory vault |
US7849350B2 (en) * | 2006-09-28 | 2010-12-07 | Emc Corporation | Responding to a storage processor failure with continued write caching |
US8200885B2 (en) * | 2007-07-25 | 2012-06-12 | Agiga Tech Inc. | Hybrid memory system with backup power source and multiple backup an restore methodology |
JP2009075759A (en) * | 2007-09-19 | 2009-04-09 | Hitachi Ltd | Storage device, and method for managing data in storage device |
JP2009205335A (en) * | 2008-02-27 | 2009-09-10 | Hitachi Ltd | Storage system using two kinds of memory devices for cache and method for controlling the storage system |
JP5410025B2 (en) * | 2008-03-07 | 2014-02-05 | 株式会社日立製作所 | Storage system and management method thereof |
WO2010049929A1 (en) * | 2008-10-27 | 2010-05-06 | Kaminario Tehnologies Ltd. | A mass-storage system utilizing solid-state storage and non-solid-state storage |
US8650328B1 (en) * | 2008-12-15 | 2014-02-11 | American Megatrends, Inc. | Bi-directional communication between redundant storage controllers |
US8495299B2 (en) * | 2009-11-16 | 2013-07-23 | Microsoft Corporation | Non-blocking data transfer via memory cache manipulation |
US8510598B2 (en) * | 2010-03-29 | 2013-08-13 | Dot Hill Systems Corporation | Buffer management method and apparatus for power reduction during flush operation |
US10360143B2 (en) * | 2010-07-01 | 2019-07-23 | Qualcomm Incorporated | Parallel use of integrated non-volatile memory and main volatile memory within a mobile device |
US8327080B1 (en) * | 2010-09-28 | 2012-12-04 | Emc Corporation | Write-back cache protection |
JP2012190359A (en) * | 2011-03-11 | 2012-10-04 | Toshiba Corp | Cache system and processing device |
US20120311271A1 (en) * | 2011-06-06 | 2012-12-06 | Sanrad, Ltd. | Read Cache Device and Methods Thereof for Accelerating Access to Data in a Storage Area Network |
CN103384877B (en) * | 2011-06-07 | 2016-03-23 | 株式会社日立制作所 | Comprise storage system and the storage controlling method of flash memory |
US20130007370A1 (en) * | 2011-07-01 | 2013-01-03 | Oracle International Corporation | Method and apparatus for minimizing working memory contentions in computing systems |
WO2013038465A1 (en) * | 2011-09-16 | 2013-03-21 | Hitachi, Ltd. | Storage system and method of controlling storage system |
US9298636B1 (en) * | 2011-09-29 | 2016-03-29 | Emc Corporation | Managing data storage |
US9037793B1 (en) * | 2011-09-30 | 2015-05-19 | Emc Corporation | Managing data storage |
US9122589B1 (en) * | 2013-06-28 | 2015-09-01 | Emc Corporation | Data storage system with unified system cache |
US10089037B1 (en) * | 2013-10-29 | 2018-10-02 | EMC IP Holding Company LLC | Block active/active access to data storage systems at different locations |
US9864861B2 (en) * | 2014-03-27 | 2018-01-09 | Intel Corporation | Object oriented marshaling scheme for calls to a secure region |
US9614931B2 (en) * | 2015-01-20 | 2017-04-04 | Sphere 3D Inc. | Identifying a resource set require for a requested application and launching the resource set in a container for execution in a host operating system |
US9830082B1 (en) | 2015-09-08 | 2017-11-28 | EMC IP Holding Company LLC | Hybrid hyper-converged infrastructure and storage appliance |
US9778865B1 (en) | 2015-09-08 | 2017-10-03 | EMC IP Holding Company LLC | Hyper-converged infrastructure based on server pairs |
JP2017130002A (en) * | 2016-01-20 | 2017-07-27 | 富士通株式会社 | Storage control device and control program |
CN107526535B (en) * | 2016-06-22 | 2020-07-10 | 伊姆西Ip控股有限责任公司 | Method and system for managing storage system |
US10180790B1 (en) * | 2016-09-30 | 2019-01-15 | EMC IP Holding Company LLC | Efficient cloning and migration of data objects |
CN108733506B (en) * | 2017-04-17 | 2022-04-12 | 伊姆西Ip控股有限责任公司 | Method, apparatus and computer readable medium for data synchronization |
US10445497B2 (en) * | 2017-05-03 | 2019-10-15 | International Business Machines Corporation | Offloading processing of writes to determine malicious data from a first storage system to a second storage system |
-
2016
- 2016-12-21 CN CN201611192431.8A patent/CN108388524A/en active Pending
-
2017
- 2017-12-20 US US15/848,488 patent/US10496287B2/en active Active
-
2019
- 2019-09-16 US US16/572,188 patent/US11093141B2/en active Active
Patent Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040103238A1 (en) * | 2002-11-26 | 2004-05-27 | M-Systems Flash Disk Pioneers Ltd. | Appliance, including a flash memory, that is robust under power failure |
CN102346740A (en) | 2010-08-02 | 2012-02-08 | 联想(北京)有限公司 | File synchronization method, electronic equipment and synchronization system |
US20130013871A1 (en) | 2011-07-04 | 2013-01-10 | Fujitsu Limited | Information processing system and data processing method |
US9454326B1 (en) | 2013-03-31 | 2016-09-27 | Emc Corporation | File metro cluster for site failover of data storage system |
CN104881368A (en) | 2015-05-07 | 2015-09-02 | 北京飞杰信息技术有限公司 | Cache synchronization method and system applied to double control storage system |
CN105007307A (en) | 2015-06-18 | 2015-10-28 | 浪潮(北京)电子信息产业有限公司 | Storage control method and system |
CN105739924A (en) | 2016-01-29 | 2016-07-06 | 华为技术有限公司 | Cache cluster-based cache method and system |
US9753662B1 (en) * | 2016-09-26 | 2017-09-05 | International Business Machines Corporation | Using mirror indicators to determine whether to mirror tracks in a data set in a primary volume mirrored to a secondary volume |
US20180173435A1 (en) * | 2016-12-21 | 2018-06-21 | EMC IP Holding Company LLC | Method and apparatus for caching data |
Non-Patent Citations (1)
Title |
---|
Y. Chen, Y. Lan and H. Ren, "The Research and Implement of a Dual-Controller System," 2012 Fourth International Conference on Computational and Information Sciences, Chongqing, 2012, pp. 1084-1087, doi: 10.1109/ICCIS.2012.340. (Year: 2012). * |
Also Published As
Publication number | Publication date |
---|---|
US20200012438A1 (en) | 2020-01-09 |
CN108388524A (en) | 2018-08-10 |
US10496287B2 (en) | 2019-12-03 |
US20180173435A1 (en) | 2018-06-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11093141B2 (en) | Method and apparatus for caching data | |
US11349920B2 (en) | Methods, devices and computer readable mediums for data synchronization | |
US10922177B2 (en) | Method, device and computer readable storage media for rebuilding redundant array of independent disks | |
US11126353B2 (en) | Method and apparatus for data copy | |
US11243845B2 (en) | Method and device for data backup | |
US10216592B2 (en) | Storage system and a method used by the storage system | |
US10922196B2 (en) | Method and device for file backup and recovery | |
US10073747B2 (en) | Reducing recovery time in disaster recovery/replication setup with multitier backend storage | |
US11106377B2 (en) | Storage management method, device and computer-readable medium | |
CN104412228A (en) | Live migration protocols and cluster server failover protocols | |
US10853209B2 (en) | Method, apparatus and computer program product for data synchronization | |
US10831402B2 (en) | Method and apparatus for ensuring data consistency | |
CN104750428A (en) | Block storage access and gateway module, storage system and method, and content delivery apparatus | |
US20160283118A1 (en) | Optimization of disk images for thin provisioned disks | |
US9767116B1 (en) | Optimized object status consistency within clustered file systems | |
US11137933B2 (en) | Accelerating transaction execution across geographically dispersed clusters | |
US10592523B1 (en) | Notification system and method | |
US9857979B2 (en) | Optimizing page boundary crossing in system memory using a reference bit and a change bit | |
US20140068215A1 (en) | Method and apparatus for accessing data in a data storage system | |
US10101929B2 (en) | Maintaining data consistency | |
US20200241760A1 (en) | Method, apparatus and computer program product for storing data | |
US20180173624A1 (en) | Method and apparatus for data access in storage system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
AS | Assignment |
Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., A Free format text: PATENT SECURITY AGREEMENT (NOTES);ASSIGNORS:DELL PRODUCTS L.P.;EMC IP HOLDING COMPANY LLC;WYSE TECHNOLOGY L.L.C.;AND OTHERS;REEL/FRAME:051302/0528 Effective date: 20191212 Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT, TEXAS Free format text: PATENT SECURITY AGREEMENT (NOTES);ASSIGNORS:DELL PRODUCTS L.P.;EMC IP HOLDING COMPANY LLC;WYSE TECHNOLOGY L.L.C.;AND OTHERS;REEL/FRAME:051302/0528 Effective date: 20191212 |
|
AS | Assignment |
Owner name: EMC IP HOLDING COMPANY LLC, MASSACHUSETTS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:LIU, YOUSHENG;GAO, JIAN;XU, XINLEI;AND OTHERS;REEL/FRAME:051653/0636 Effective date: 20180104 |
|
AS | Assignment |
Owner name: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, NORTH CAR Free format text: SECURITY AGREEMENT;ASSIGNORS:DELL PRODUCTS L.P.;EMC IP HOLDING COMPANY LLC;WYSE TECHNOLOGY L.L.C.;AND OTHERS;REEL/FRAME:051449/0728 Effective date: 20191230 Owner name: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, NORTH CAROLINA Free format text: SECURITY AGREEMENT;ASSIGNORS:DELL PRODUCTS L.P.;EMC IP HOLDING COMPANY LLC;WYSE TECHNOLOGY L.L.C.;AND OTHERS;REEL/FRAME:051449/0728 Effective date: 20191230 |
|
AS | Assignment |
Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., TEXAS Free format text: SECURITY AGREEMENT;ASSIGNORS:CREDANT TECHNOLOGIES INC.;DELL INTERNATIONAL L.L.C.;DELL MARKETING L.P.;AND OTHERS;REEL/FRAME:053546/0001 Effective date: 20200409 |
|
AS | Assignment |
Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT, TEXAS Free format text: SECURITY INTEREST;ASSIGNORS:DELL PRODUCTS L.P.;EMC CORPORATION;EMC IP HOLDING COMPANY LLC;REEL/FRAME:053311/0169 Effective date: 20200603 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT RECEIVED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: EMC CORPORATION, MASSACHUSETTS Free format text: RELEASE OF SECURITY INTEREST AT REEL 051449 FRAME 0728;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058002/0010 Effective date: 20211101 Owner name: SECUREWORKS CORP., DELAWARE Free format text: RELEASE OF SECURITY INTEREST AT REEL 051449 FRAME 0728;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058002/0010 Effective date: 20211101 Owner name: WYSE TECHNOLOGY L.L.C., CALIFORNIA Free format text: RELEASE OF SECURITY INTEREST AT REEL 051449 FRAME 0728;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058002/0010 Effective date: 20211101 Owner name: EMC IP HOLDING COMPANY LLC, TEXAS Free format text: RELEASE OF SECURITY INTEREST AT REEL 051449 FRAME 0728;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058002/0010 Effective date: 20211101 Owner name: DELL PRODUCTS L.P., TEXAS Free format text: RELEASE OF SECURITY INTEREST AT REEL 051449 FRAME 0728;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058002/0010 Effective date: 20211101 |
|
AS | Assignment |
Owner name: EMC IP HOLDING COMPANY LLC, TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (053311/0169);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:060438/0742 Effective date: 20220329 Owner name: EMC CORPORATION, MASSACHUSETTS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (053311/0169);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:060438/0742 Effective date: 20220329 Owner name: DELL PRODUCTS L.P., TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (053311/0169);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:060438/0742 Effective date: 20220329 Owner name: SECUREWORKS CORP., DELAWARE Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (051302/0528);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:060438/0593 Effective date: 20220329 Owner name: DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO WYSE TECHNOLOGY L.L.C.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (051302/0528);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:060438/0593 Effective date: 20220329 Owner name: EMC IP HOLDING COMPANY LLC, TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (051302/0528);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:060438/0593 Effective date: 20220329 Owner name: DELL PRODUCTS L.P., TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (051302/0528);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:060438/0593 Effective date: 20220329 |