US8255634B2 - Apparatus and methods for look-ahead virtual volume meta-data processing in a storage controller - Google Patents
Apparatus and methods for look-ahead virtual volume meta-data processing in a storage controller Download PDFInfo
- Publication number
- US8255634B2 US8255634B2 US12/854,800 US85480010A US8255634B2 US 8255634 B2 US8255634 B2 US 8255634B2 US 85480010 A US85480010 A US 85480010A US 8255634 B2 US8255634 B2 US 8255634B2
- Authority
- US
- United States
- Prior art keywords
- data
- meta
- virtual volume
- request
- memory
- 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
- 238000000034 method Methods 0.000 title claims abstract description 50
- 238000012545 processing Methods 0.000 title claims description 61
- 238000013507 mapping Methods 0.000 claims abstract description 38
- 230000015654 memory Effects 0.000 claims description 60
- 238000013500 data storage Methods 0.000 claims description 3
- 230000001360 synchronised effect Effects 0.000 abstract description 9
- 238000010586 diagram Methods 0.000 description 6
- 238000007726 management method Methods 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 238000013461 design Methods 0.000 description 3
- 239000003999 initiator Substances 0.000 description 3
- 239000004065 semiconductor Substances 0.000 description 3
- 101001076732 Homo sapiens RNA-binding protein 27 Proteins 0.000 description 2
- 102100025873 RNA-binding protein 27 Human genes 0.000 description 2
- 230000010076 replication Effects 0.000 description 2
- 101100465393 Homo sapiens PSMA1 gene Proteins 0.000 description 1
- 102100036042 Proteasome subunit alpha type-1 Human genes 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000013479 data entry Methods 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000012005 ligant binding assay Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/2053—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant
- G06F11/2056—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant by mirroring
- G06F11/2071—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant by mirroring using a plurality of controllers
- G06F11/2076—Synchronous techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
- G06F2201/815—Virtual
Definitions
- the invention relates generally to storage controllers of storage systems and more specifically relates to apparatus and methods for improved efficiency in processing of virtual to physical mapping meta-data in a storage controller.
- Virtualized storage systems define one or more virtual volumes for use by attached host systems.
- Each virtual volume comprises a range of contiguous logical addresses (e.g., logical block addresses or LBAs) that are mapped to some physical storage locations on storage devices associated with the storage system.
- a storage controller of the storage system is coupled with the attached host systems and with physical storage devices associated with the storage system.
- the storage controller receives I/O requests from attached host systems and/or from storage related services provided within the storage system.
- the storage controller then translates or maps the logical addresses affected by the I/O request into corresponding physical storage locations.
- the mapping meta-data structure for a simple logical/virtual volume is typically a relatively simple table structure that maps logical addresses to corresponding physical storage locations. Such a relatively simple meta-data structure may typically be stored in a cache memory or other high speed memory for rapid access to thus reduce overhead processing of the storage controller. Use of such mapping meta-data structures is often referred to as “walking” the mapping meta-data structure. A “walk” of the mapping structure for a simple read or write access to a simple virtual volume is relatively rapid and uses relatively little CPU and memory bandwidth of the storage controller—thus, imposing a relatively small overhead processing burden on the storage controller as it may impact overall storage system performance.
- the storage controller of the storage system may provide various enhanced data services within the storage system.
- These enhanced data services provide a number of data services beyond simple read and write access to data stored on a simply logical/virtual volume.
- some virtualized storage systems provide data services within the storage system for automated synchronous mirroring (e.g., mirroring of data to another volume such as for reliability or for remote replication of data).
- Still other exemplary enhanced data services may provide for automated snapshot generation (i.e., to create shadow or snapshot copies of the contents of a virtual volume such as for replication or backup data services).
- mapping meta-data and other meta-data pertaining to accessing the virtual volume for the enhanced services may involve far more complexity in their respective access to mapping meta-data and other meta-data pertaining to accessing the virtual volume for the enhanced services.
- access to a synchronous mirrored volume of a virtual volume may, at a minimum, involve accessing mapping meta-data for two virtual/logical volumes.
- access to automatically generated snapshots may entail accessing significantly more meta-data to identify a particular point in time snapshot of the contents of a logical/virtual volume.
- This added complexity in providing virtual to physical mapping where a volume is utilizing enhanced data services can add significant overhead to the processing of the storage controller in “walking” the mapping and other meta-data structures associated with the virtual volumes. This added overhead processing can rise to a level that notably, negatively impacts overall performance of the storage system.
- the present invention solves the above and other problems, thereby advancing the state of the useful arts, by providing apparatus and methods and systems for improved efficiency in accessing meta-data in a storage controller of a virtualized storage system.
- Features and aspects hereof walk/retrieve meta-data for one or more other I/O requests when retrieving meta-data for a first I/O request.
- the meta-data may include mapping information for mapping logical addresses of the virtual volume.
- Meta-data may also include meta-data associated with higher level, enhanced data services provide by or in conjunction with the storage system.
- Enhanced data services may include features for synchronous mirroring of a volume and/or management of time-based snapshots of the content of a virtual volume.
- a storage controller within a virtualized storage system comprises a virtual volume, the virtual volume comprising a portion of one or more physical storage devices coupled with the storage controller.
- the controller is adapted for processing I/O requests directed to the virtual volume.
- the controller comprises a memory for storing meta-data regarding the virtual volume and an I/O processor, coupled with the memory, operable to receive a first I/O request associated with first meta-data and operable to receive a second I/O request associated with second meta-data.
- the I/O processor is adapted to process the first I/O request.
- the processing of the first I/O request comprises retrieving the first and second meta-data.
- the I/O processor is further adapted to process the second I/O request using the previously retrieved second meta-data.
- Another aspect hereof provides a method operable in a storage controller in a storage system for accessing meta-data associated with a virtual volume of the storage system and provides a computer readable medium storing programmed instructions to implement the method.
- the virtual volume comprises portions of one or more physical storage devices associated with the storage system.
- the method comprises receiving in the storage controller a first I/O request directed to the virtual volume.
- the first I/O request is associated with first meta-data stored in a memory of the storage controller.
- the method also comprises receiving a second I/O request directed to the virtual volume.
- the second I/O request associated with second meta-data stored in the memory.
- the method also comprises processing the first I/O request in the storage controller to access the virtual volume based on the first meta-data.
- the step of processing the first I/O request comprises retrieving the first and second meta-data from the memory.
- the method also comprises processing the second I/O request in the storage controller to access the virtual volume based on the previously retrieved second meta-data.
- FIG. 1 is a block diagram of an exemplary virtualized storage system including a storage controller enhanced in accordance with features hereof to more efficiently process meta-data associated with access to virtual volumes of the system.
- FIG. 2 is a block diagram of exemplary hierarchical meta-data structures walked by systems and methods in accordance with features and aspects hereof.
- FIG. 3 is a flowchart describing an exemplary method in accordance with features and aspects hereof to efficiently process meta-data associated with accessing a virtual volume of a storage system by looking ahead to subsequent I/O requests when accessing meta-data for a first I/O request.
- FIG. 4 is a flow chart describing another exemplary method in accordance with features and aspects hereof to efficiently process meta-data associated with accessing a virtual volume of a storage system by looking ahead to subsequent I/O requests when accessing meta-data for a first I/O request.
- FIG. 5 is a block diagram of an exemplary computing device adapted to receive a computer readable medium embodying methods for efficient access to meta-data associated with virtual volume access in accordance with features and aspects hereof.
- FIG. 1 is a block diagram of a virtualized storage system 150 comprising a storage controller 100 enhanced in accordance with features and aspects hereof for improved efficiency in accessing and utilizing meta-data associated with access to one or more virtual volumes.
- Enhanced storage controller 100 may be coupled with any number of virtual volumes 160 .
- Virtual volume 160 may comprise portions of one or more physical storage devices such as rotating optical or magnetic disk drives as well as semiconductor storage devices (e.g., RAMdisks or flash memory disks).
- Enhanced storage controller 100 includes one or more I/O processors 102 .
- Each of one or more of the I/O processors 102 may comprise a general or special purpose programmable processor (CPU) and associated program memory from which programmed instructions are fetched and executed. Additionally or in the alternative, each of one or more of the I/O processors 102 may comprise customized circuitry adapted for rapidly executing common I/O requests such as read and write I/O requests directed to a virtual volume 160 .
- enhanced storage controller 100 may include both a CPU based I/O processor 102 (sometimes referred to as a “software” or “soft-path” I/O processor) as well as a custom circuitry I/O processor 102 (sometimes referred to as a “hard-path” or “fast-path” I/O processor).
- a CPU based I/O processor 102 sometimes referred to as a “software” or “soft-path” I/O processor
- custom circuitry I/O processor 102 sometimes referred to as a “hard-path” or “fast-path” I/O processor.
- meta-data in memory 104 comprises mapping information used to map logical addresses of a virtual volume 160 into corresponding physical storage locations on one or more physical storage devices. Processing of such mapping information in the meta-data of memory 104 may consume significant processing capability of I/O processor 102 .
- enhanced storage controller 100 may include look-ahead logic 110 adapted to look ahead when processing a first I/O request to determine if a subsequent I/O request may utilize meta-data stored in relatively close proximity to the meta-data associated with the first I/O request.
- Such logic 110 may be integral within one or more of the I/O processors 102 or, as a matter of design choice, may be implemented as circuits external to any of the I/O processors 102 . Further, where an I/O processor 102 is implemented with a CPU and programmed instructions, logic 110 may be similarly implemented as programmed instructions. Where an I/O processor 102 is implemented as customized I/O processing circuits, logic 110 may be integrated as custom logic circuits within the processor 102 . Thus, I/O processor 102 is operable to access meta-data associated with a first I/O request and with one or more other I/O requests as an aspect of processing the first I/O request.
- the requisite meta-data for such other requests may be accessed without again referencing complex data structures in meta-data memory 104 . Rather, the previously retrieved meta-data for the other I/O requests may be more conveniently stored for rapid access by I/O processor 102 . In one exemplary embodiment, the previously retrieved meta-data for other I/O requests may be temporarily saved in a meta-data cache memory 108 . Meta-data cache memory 108 may be any suitable memory component for saving meta-data previously retrieved.
- Enhanced data services 106 comprise higher-level data management functions provided by storage controller 100 (or, as a matter of design choice, provided by another computational device within the storage system 150 or otherwise associated with storage system 150 ).
- Enhanced data services 106 may include, for example, synchronous mirroring of a virtual volume 160 . Such synchronous mirroring of virtual volume 160 may automatically duplicate or replicate all data of virtual volume 160 onto one or more mirrored virtual volumes 162 . Simple localized mirroring may entail well known RAID level 1 storage management provided by storage controller 100 .
- synchronous mirroring data services 106 may also include mirroring or duplication of data of virtual volume 160 to a physically remote or even geographically remote mirrored virtual volume 162 (unlike localized mirroring as performed by RAID level 1 management using locally attached storage devices).
- Enhanced data services 106 may also include snapshot management for providing a plurality of time-based snapshots of the contents of virtual volume 160 .
- snapshot-related enhanced data services upon request by a user or based on an automated schedule, a point in time snapshot of the contents of virtual volume 160 may be created and stored as virtual volume snapshot 164 . Any number of such snapshots may be managed by enhanced data services 106 depending on the needs of a particular application and the snapshots 164 .
- Meta-data in memory 104 associates each snapshot 164 with the virtual volume 160 from which it is derived.
- I/O requests to be processed that reference a virtual volume including such enhanced data services may entail substantially more processing of meta-data in memory 104 .
- simply identifying a volume to be accessed in an I/O request may entail determining from meta-data in memory 104 which of a plurality of mirrored virtual volumes 162 and/or which of a plurality of virtual volume snapshots 164 is identified by the I/O request.
- the meta-data access to make such a volume identification determination may be substantial in addition to the further meta-data access required to map logical addresses to physical addresses for the specific volume snapshot or mirror identified.
- I/O processor 102 of enhanced storage controller 100 provides enhancements as look-ahead logic 110 to access meta-data in memory 104 when processing any number of subsequent I/O requests while processing a first received I/O request.
- Look-ahead logic 110 may be implemented as suitably designed custom logic circuits (optionally integrated with a hard-path I/O processor 102 ) or as programmed instructions to be executed by a CPU of a soft-path I/O processor 102 .
- FIG. 2 is a block diagram of exemplary hierarchical meta-data structures that may be efficiently walked by methods and systems in accordance with features and aspects hereof.
- FIG. 2 exhibits one exemplary implementation of the meta-data structures that typifies the hierarchical complexity required to identify physical storage locations corresponding to logical addresses used to access a virtual volume.
- FIG. 2 also exhibits the added complexity when data services implemented within the storage system (such as mirroring).
- a typical configuration 200 is shown representing hierarchical meta-data for a simple virtual volume.
- Multiple initiators may access the same virtual volume each using a different virtual volume identifier (e.g., a virtual target identifier) corresponding to its nexus (a particular initiator ID connecting to a particular virtual volume target ID or an “I_T nexus”).
- a “KDISK” meta-data structure is first used to map the I_T nexus to a particular virtual volume based on the initiator and target identifiers. Therefore, either KDISK 1 202 structure or KDISK 2 204 structure is first selected based on the I_T nexus of a received I/O request to locate the volume meta-data structure 206 .
- the volume meta-data structure 206 represents the addressed virtual volume and points to the base of a plurality of KMAP structures—one for each of potentially multiple segments of the virtual volume. For example, in one exemplary embodiment, a different KMAP structure may exist for each 2 terabyte segment of the virtual volume's total storage capacity. Thus, volume structure 206 and the logical addresses accessed by the I/O request will identify the specific KMAP 1 meta-data structure 208 to be used for the segment to be accessed. Each KMAP data structure may point to yet another hierarchical layer of physical data meta-data structures. Each physical data meta-data structure may be used to map still smaller granularity of pages of the segment from virtual/logical addresses to corresponding physical addresses. Thus, the KMAP 1 structure 208 and the logical address of the I/O request locate a particular PSC 1 meta-data structure 210 to locate the mapping data for a specific page of logical addresses of the I/O request.
- a number of hierarchical layers of meta-data may be traversed or walked to determine the physical addresses corresponding to a range of logical addresses of an I/O request.
- methods and structures hereof extend the range of logical addresses to be translated to include one or more other I/O requests also queued for processing by the storage system.
- the meta-data so obtained from the extended range of logical addresses may then be saved (e.g., “cached”) for later use when the subsequent I/O requests are unqueued and processed.
- the mirror configuration 250 comprises KMAP 3 258 , KMAP 2 260 , and FORK 262 structures layered in front of the original KMAP 1 208 and PSC 1 210 structures.
- the hierarchy is extended with KMAP 4 266 and PSC 2 170 once the user adds a mirrored volume (e.g., RAID level 1 ) capability to the typical configuration.
- the user could create third and fourth copies (under the FORK 262 ) for additional redundancy.
- Services such as “snapshot” or thinly provisioned volumes may be implemented in “page tables” referenced by a KMAP structure. For example, each page of a segment may present 1 megabyte of storage and a page table pointing to a plurality of such physical pages may present 1 gigabyte of storage.
- the segment state for all segments may be set to “Read Only” to thereby cause a map fault on subsequent write I/O.
- a copy of the segment Prior to issuing the write command to the target, a copy of the segment may be copied to a different target (thus creating another tree of mapped structures using a FORK meta-data structure. Once completed, the pending write command is issued and updates the newly generated mapping structures for the snapshot.
- Thin provision volume services may handled by setting segment states to “Zero on Read” causing the system to return data full of zeros responsive to a read request.
- the write command is queued then segments are automatically provisioned from a pool of free storage and the mapping structures are updated accordingly. After provisioning the data storage to be written, the pending command is issued to the newly provisioned storage.
- Storage services such as snapshots or thin provisioning applied to a mirror configuration also requires a KMAP and associated page tables. Since there are more (e.g., two or more) KMAP structures underneath the FORK structure, a KMAP structure may also be layered in front the FORK structure to provide a Common State Table (CST) for the services (e.g., KMAP 2 260 ). Still further, snapshot services, thin provisioning services, etc. are applied to segments in the KMAP 2 260 CST.
- the top level of the mirror configuration is a Global Dirty Table (GDT) in KMAP 3 structure 258 . The GDT may be used for system crash recovery and during mirror creation. When the meta-data structures are created, the GDT state is set to fault read or write I/O requests prior to issuing the command. This state causes the parallel mirror segments to resynchronize and become clean again allowing pending commands to that segment to continue processing on successive maps.
- GDT Global Dirty Table
- FIG. 2 is intended to exhibit one possible design choice that reflects the complexity of hierarchical meta-data structures used to access virtual volumes.
- a wide variety of other possible meta-data structures will be readily apparent to those of ordinary skill in the art having more or less hierarchical complexity and reflecting the requirements of other forms of data services.
- FIG. 3 is a flowchart describing an exemplary method in accordance with features and aspects hereof to more efficiently manage access to meta-data associated with I/O requests directed to a virtual volume of a storage system.
- the method of FIG. 3 may be operable in, for example, enhanced storage controller 100 of FIG. 1 or any other suitable computational/electronic device used by a virtualized storage system to process I/O requests received by the storage system. More specifically, the method of FIG. 3 may be operable in one or more I/O processors of a storage controller such as I/O processors 102 of FIG. 1 .
- Step 300 receives a first I/O request from an attached host or from data services provided in association with the storage system. The first I/O request is associated with first meta-data.
- the first meta-data may include, at a minimum, mapping information used for mapping logical addresses of the identified virtual volume to corresponding physical storage locations of one or more physical storage devices.
- the first meta-data may include data services information associated with higher-level data services provided by the storage controller of the storage system or provided by other computational components associated with the storage system or external to the storage system.
- a second I/O request is received.
- the second I/O request is associated with second meta-data.
- Second meta-data as above with respect to first meta-data, may include mapping information meta-data for mapping logical to physical addresses as well as data services information used to identify features of higher-level data services functionality.
- higher-level data services may include, for example, synchronous mirroring of the contents of a virtual volume to provide one or more mirrored copies of the virtual volume data contents either locally or remotely.
- data services may include features to generate and manage one or more time-based snapshots of the contents of a virtual volume. Such time-based snapshot may be used, for example, in providing backup services for data stored on the virtual volume and for other purposes.
- an I/O processor of a storage controller will eventually commence processing of the first I/O request.
- the I/O processor will retrieve both the first and second meta-data associated with the first and second I/O requests, respectively.
- the retrieved first meta-data will be used directly in step 304 for processing of the first I/O request.
- the first meta-data may be retrieved to aid in processing the first I/O request by mapping logical addresses of an identified volume to corresponding physical storage location.
- the I/O processor in retrieving the first meta-data, the I/O processor will detect that the second meta-data is physically nearby the memory location containing the first meta-data.
- Access to the first meta-data may also retrieve the second meta-data corresponding to the second I/O request. More generally, in accessing the first meta-data, any nearby meta-data associated with one or more other I/O requests received subsequent to receipt of the first I/O request may be retrieved. Thus, the method “looks ahead” to reduce overhead processing of the I/O processor of the enhanced storage controller in retrieving and manipulating meta-data stored in a meta-data memory of the storage controller.
- the I/O controller processor commences processing of the second I/O request at step 306 , the previously retrieved second meta-data is utilized for processing of the second I/O request. Thus, processing of the second I/O request does not require a new access to meta-data memory to retrieve the second meta-data.
- the enhanced method may therefore avoid “walking” complex hierarchical meta-data structures (such as exemplified in FIG. 2 ) for the second and other subsequent I/O requests by accessing meta-data for other requests during the “walking” of the meta-data for the first I/O request.
- FIG. 4 is a flowchart describing another exemplary method enhanced in accordance with features and aspects hereof to more efficiently manage meta-data associated with processing of I/O requests in a storage controller of a virtualized storage system.
- the method of FIG. 4 may be operable, for example, in an enhanced storage controller such as storage controller 100 of FIG. 1 . More specifically, the method of FIG. 4 may be operable, for example, in I/O processor 102 of enhanced storage controller 100 of FIG. 1 .
- a new I/O request is received and at step 402 , the newly received I/O request may be added to a queue of pending requests to be processed by the I/O processor. Steps 400 and 402 are then repeated for each newly received I/O request.
- steps 410 through 424 represent aspects of processing an I/O request previously received and queued by operation of steps 400 and 402 .
- Step 410 unqueues a next queued I/O request to be processed by the I/O processor.
- the I/O processor determines the range of logical addresses and virtual volume(s) identified for access in the newly unqueued I/O request.
- Step 414 determines whether the meta-data required to process the newly unqueued I/O request (e.g., a first I/O request) is already available. As discussed herein, the required meta-data may have been previously retrieved in the processing of a prior I/O request. If the required meta-data is already available (previously retrieved), step 416 gets the previously retrieved meta-data from a meta-data cache memory. Step 424 then completes processing of the newly unqueued I/O request using the previously retrieved meta-data.
- step 418 computationally extends the range of meta-data to be accessed in processing of the newly unqueued I/O request.
- the extended range of meta-data to be accessed may include meta-data associated with one or more other queued I/O requests directed to the same virtual volume (e.g., directed to the same mirrored copy and/or time-based snapshot volume, etc.).
- the extended range of meta-data to be accessed may be determined by a fixed additional offset from the starting logical block address of the newly unqueued I/O request.
- the meta-data to be retrieved from the meta-data memory may start with the meta-data for the range of logical block addresses for the virtual volume identified in the unqueued I/O request.
- the range of meta-data to be retrieved may then be computationally extended from that starting point through a pre-determined fixed number of additional meta-data entries or through a predetermined fixed range of meta-data memory addresses.
- step 418 may inspect the queue of other I/O requests awaiting processing. The range of meta-data may then be computationally extended to assure retrieval of meta-data for one or more other I/O requests presently in the queue of pending I/O requests.
- the extended range of meta-data is retrieved by “walking” the meta-data structures.
- the walk of the structures for the extended range retrieves meta-data associated with the newly unqueued I/O request and retrieves meta-data associated with any other pending I/O requests whose meta-data lies in the extended range of meta-data.
- the meta-data is “walked” in the sense that any data structures associated with the logical to physical mapping may be accessed as well as data structures relating to any higher-level data services associated with the I/O request.
- Such data structures may include complex indirect pointers, object handles, hierarchical structures, etc.
- the data structures for the meta-data include, for example, hierarchical layers of data structures or other indirection complexity
- the complexity of accessing (walking) the meta-data structures for the presently unqueued (e.g., first) I/O request need not be duplicated for accessing meta-data associated with other queued I/O requests utilizing meta-data stored nearby the first meta-data.
- Step 420 stores in a meta-data cache memory any retrieved meta-data within the extended range of retrieved meta-data that corresponds with other I/O requests.
- the meta-data for such other I/O requests is thereby accessible for use in processing the other requests without repeating the overhead processing associated with walking the meta-data structures in the meta-data memory (as discussed above with reference to steps 414 and 416 ). That overhead processing may be performed when processing the first I/O request and need not be repeated for the meta-data in the extended range for other I/O requests.
- step 424 processes the unqueued I/O request using the retrieved meta-data for that request.
- Embodiments of the invention can take the form of an entirely hardware (i.e., circuits) embodiment, an entirely software embodiment or an embodiment containing both hardware and software elements.
- the invention is implemented in software, which includes but is not limited to firmware, resident software, microcode, etc.
- FIG. 5 is a block diagram depicting a storage controller computer 500 adapted to provide features and aspects hereof by executing programmed instructions and accessing data stored on a computer readable storage medium 512 .
- embodiments of the invention can take the form of a computer program product accessible from a computer-usable or computer-readable medium 512 providing program code for use by, or in connection with, a computer or any instruction execution system.
- a computer-usable or computer readable medium can be any apparatus that can contain, store, communicate, propagate, or transport the program for use by or in connection with the computer, instruction execution system, apparatus, or device.
- the medium can be an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system (or apparatus or device) or a propagation medium.
- Examples of a computer-readable medium include a semiconductor or solid-state memory, magnetic tape, a removable computer diskette, a random access memory (RAM), a read-only memory (ROM), a rigid magnetic disk and an optical disk.
- Current examples of optical disks include compact disk-read only memory (CD-ROM), compact disk-read/write (CD-R/W) and DVD.
- a storage controller computer 500 suitable for storing and/or executing program code will include at least one processor 502 coupled directly or indirectly to memory elements 504 through a system bus 550 .
- the memory elements 504 can include local memory employed during actual execution of the program code, bulk storage, and cache memories that provide temporary storage of at least some program code in order to reduce the number of times code must be retrieved from bulk storage during execution.
- Meta-data memory 510 may be accessed by processor 502 via bus 550 to retrieve meta-data for processing of I/O requests.
- Input/output interface 506 couples the controller to I/O devices to be controlled (e.g., storage devices, etc.). Host system interface 508 may also couple the computer 500 to other data processing systems.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Description
Claims (21)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/854,800 US8255634B2 (en) | 2010-08-11 | 2010-08-11 | Apparatus and methods for look-ahead virtual volume meta-data processing in a storage controller |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/854,800 US8255634B2 (en) | 2010-08-11 | 2010-08-11 | Apparatus and methods for look-ahead virtual volume meta-data processing in a storage controller |
Publications (2)
Publication Number | Publication Date |
---|---|
US20120042115A1 US20120042115A1 (en) | 2012-02-16 |
US8255634B2 true US8255634B2 (en) | 2012-08-28 |
Family
ID=45565614
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/854,800 Active 2030-11-25 US8255634B2 (en) | 2010-08-11 | 2010-08-11 | Apparatus and methods for look-ahead virtual volume meta-data processing in a storage controller |
Country Status (1)
Country | Link |
---|---|
US (1) | US8255634B2 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140052691A1 (en) * | 2012-08-17 | 2014-02-20 | International Business Machines Corporation | Efficiently storing and retrieving data and metadata |
US20150347430A1 (en) * | 2014-05-30 | 2015-12-03 | International Business Machines Corporation | Techniques for enabling coarse-grained volume snapshots for virtual machine backup and restore |
US10733153B2 (en) | 2016-02-29 | 2020-08-04 | Red Hat, Inc. | Snapshot management in distributed file systems |
Families Citing this family (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060167838A1 (en) * | 2005-01-21 | 2006-07-27 | Z-Force Communications, Inc. | File-based hybrid file storage scheme supporting multiple file switches |
US9195500B1 (en) | 2010-02-09 | 2015-11-24 | F5 Networks, Inc. | Methods for seamless storage importing and devices thereof |
US9286298B1 (en) | 2010-10-14 | 2016-03-15 | F5 Networks, Inc. | Methods for enhancing management of backup data sets and devices thereof |
US9020912B1 (en) | 2012-02-20 | 2015-04-28 | F5 Networks, Inc. | Methods for accessing data in a compressed file system and devices thereof |
KR20140042428A (en) * | 2012-09-28 | 2014-04-07 | 삼성전자주식회사 | Computing system and data management method thereof |
US9519501B1 (en) | 2012-09-30 | 2016-12-13 | F5 Networks, Inc. | Hardware assisted flow acceleration and L2 SMAC management in a heterogeneous distributed multi-tenant virtualized clustered system |
US10375155B1 (en) | 2013-02-19 | 2019-08-06 | F5 Networks, Inc. | System and method for achieving hardware acceleration for asymmetric flow connections |
US9554418B1 (en) | 2013-02-28 | 2017-01-24 | F5 Networks, Inc. | Device for topology hiding of a visited network |
US9335932B2 (en) * | 2013-03-15 | 2016-05-10 | Bracket Computing, Inc. | Storage unit selection for virtualized storage units |
US9733867B2 (en) | 2013-03-15 | 2017-08-15 | Bracket Computing, Inc. | Multi-layered storage administration for flexible placement of data |
US10834065B1 (en) | 2015-03-31 | 2020-11-10 | F5 Networks, Inc. | Methods for SSL protected NTLM re-authentication and devices thereof |
US10404698B1 (en) | 2016-01-15 | 2019-09-03 | F5 Networks, Inc. | Methods for adaptive organization of web application access points in webtops and devices thereof |
US10235248B1 (en) | 2017-04-27 | 2019-03-19 | EMC IP Holding Company LLC | Processing I/O operations in parallel while maintaining read/write consistency using range and priority queues in a data protection system |
US11531478B1 (en) * | 2021-06-07 | 2022-12-20 | Dell Products L.P. | Optimizing memory usage to enable larger-sized deployments and client servicing |
Citations (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5148538A (en) * | 1989-10-20 | 1992-09-15 | International Business Machines Corporation | Translation look ahead based cache access |
US5586289A (en) | 1994-04-15 | 1996-12-17 | David Sarnoff Research Center, Inc. | Method and apparatus for accessing local storage within a parallel processing computer |
US20030225993A1 (en) * | 2002-05-29 | 2003-12-04 | Hitachi, Ltd. | Computer system |
US6763375B1 (en) | 2000-04-11 | 2004-07-13 | International Business Machines Corporation | Method for defining and controlling the overall behavior of a network processor device |
US20050172067A1 (en) * | 2004-02-04 | 2005-08-04 | Sandisk Corporation | Mass storage accelerator |
US7191304B1 (en) * | 2002-09-06 | 2007-03-13 | 3Pardata, Inc. | Efficient and reliable virtual volume mapping |
US20070113044A1 (en) * | 2004-01-16 | 2007-05-17 | Day Michael N | Method and Apparatus for Preloading Translation Buffers |
US20070208885A1 (en) * | 2006-02-22 | 2007-09-06 | Sony Computer Entertainment Inc. | Methods And Apparatus For Providing Independent Logical Address Space And Access Management |
US20070214325A1 (en) * | 2006-03-13 | 2007-09-13 | Kabushiki Kaisha Toshiba | Data storage device and method thereof |
US7330961B2 (en) * | 2002-11-21 | 2008-02-12 | Fujitsu Limited | Cache control method and processor system |
US20080282047A1 (en) * | 2007-05-08 | 2008-11-13 | Hitachi, Ltd. | Methods and apparatus to backup and restore data for virtualized storage area |
US20100228650A1 (en) | 2007-08-27 | 2010-09-09 | Correlsense Ltd. | Apparatus and Method for Tracking Transaction Related Data |
US20110138390A1 (en) | 2009-12-07 | 2011-06-09 | Sony Corporation | Information processing device, information processing method and program |
US20110258404A1 (en) * | 2010-04-14 | 2011-10-20 | Hitachi, Ltd. | Method and apparatus to manage groups for deduplication |
-
2010
- 2010-08-11 US US12/854,800 patent/US8255634B2/en active Active
Patent Citations (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5148538A (en) * | 1989-10-20 | 1992-09-15 | International Business Machines Corporation | Translation look ahead based cache access |
US5586289A (en) | 1994-04-15 | 1996-12-17 | David Sarnoff Research Center, Inc. | Method and apparatus for accessing local storage within a parallel processing computer |
US6763375B1 (en) | 2000-04-11 | 2004-07-13 | International Business Machines Corporation | Method for defining and controlling the overall behavior of a network processor device |
US20030225993A1 (en) * | 2002-05-29 | 2003-12-04 | Hitachi, Ltd. | Computer system |
US7191304B1 (en) * | 2002-09-06 | 2007-03-13 | 3Pardata, Inc. | Efficient and reliable virtual volume mapping |
US7330961B2 (en) * | 2002-11-21 | 2008-02-12 | Fujitsu Limited | Cache control method and processor system |
US20070113044A1 (en) * | 2004-01-16 | 2007-05-17 | Day Michael N | Method and Apparatus for Preloading Translation Buffers |
US20050172067A1 (en) * | 2004-02-04 | 2005-08-04 | Sandisk Corporation | Mass storage accelerator |
US20100211752A1 (en) * | 2006-02-22 | 2010-08-19 | Sony Computer Entertainment Inc. | Methods and apparatus for providing independent logical address space and access management |
US7610464B2 (en) * | 2006-02-22 | 2009-10-27 | Sony Computer Entertainment Inc. | Methods and apparatus for providing independent logical address space and access management |
US20070208885A1 (en) * | 2006-02-22 | 2007-09-06 | Sony Computer Entertainment Inc. | Methods And Apparatus For Providing Independent Logical Address Space And Access Management |
US20070214325A1 (en) * | 2006-03-13 | 2007-09-13 | Kabushiki Kaisha Toshiba | Data storage device and method thereof |
US20080282047A1 (en) * | 2007-05-08 | 2008-11-13 | Hitachi, Ltd. | Methods and apparatus to backup and restore data for virtualized storage area |
US20100228650A1 (en) | 2007-08-27 | 2010-09-09 | Correlsense Ltd. | Apparatus and Method for Tracking Transaction Related Data |
US20110138390A1 (en) | 2009-12-07 | 2011-06-09 | Sony Corporation | Information processing device, information processing method and program |
US20110258404A1 (en) * | 2010-04-14 | 2011-10-20 | Hitachi, Ltd. | Method and apparatus to manage groups for deduplication |
Cited By (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140052691A1 (en) * | 2012-08-17 | 2014-02-20 | International Business Machines Corporation | Efficiently storing and retrieving data and metadata |
US20140059004A1 (en) * | 2012-08-17 | 2014-02-27 | International Business Machines Corporation | Efficiently storing and retrieving data and metadata |
US8805855B2 (en) * | 2012-08-17 | 2014-08-12 | International Business Machines Corporation | Efficiently storing and retrieving data and metadata |
US9043341B2 (en) * | 2012-08-17 | 2015-05-26 | International Business Machines Corporation | Efficiently storing and retrieving data and metadata |
US9569518B2 (en) | 2012-08-17 | 2017-02-14 | International Business Machines Corporation | Efficiently storing and retrieving data and metadata |
US20150347430A1 (en) * | 2014-05-30 | 2015-12-03 | International Business Machines Corporation | Techniques for enabling coarse-grained volume snapshots for virtual machine backup and restore |
US20150363413A1 (en) * | 2014-05-30 | 2015-12-17 | International Business Machines Corporation | Techniques for enabling coarse-grained volume snapshots for virtual machine backup and restore |
US9477683B2 (en) * | 2014-05-30 | 2016-10-25 | International Business Machines Corporation | Techniques for enabling coarse-grained volume snapshots for virtual machine backup and restore |
US9575991B2 (en) * | 2014-05-30 | 2017-02-21 | International Business Machines Corporation | Enabling coarse-grained volume snapshots for virtual machine backup and restore |
US10733153B2 (en) | 2016-02-29 | 2020-08-04 | Red Hat, Inc. | Snapshot management in distributed file systems |
US11797494B2 (en) | 2016-02-29 | 2023-10-24 | Red Hat, Inc. | Snapshot management in distributed file systems |
Also Published As
Publication number | Publication date |
---|---|
US20120042115A1 (en) | 2012-02-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8255634B2 (en) | Apparatus and methods for look-ahead virtual volume meta-data processing in a storage controller | |
US11099769B1 (en) | Copying data without accessing the data | |
US11442640B1 (en) | Utilizing unmapped and unknown states in a replicated storage system | |
US10430282B2 (en) | Optimizing replication by distinguishing user and system write activity | |
US9454317B2 (en) | Tiered storage system, storage controller and method of substituting data transfer between tiers | |
US20050138312A1 (en) | Method for acquiring snapshot | |
CN108885589B (en) | Method of flash-friendly caching for CDM workloads | |
US9727278B2 (en) | System and methods for mitigating write emulation on a disk device using cache memory | |
JP2008090657A (en) | Storage system and control method | |
US11099768B2 (en) | Transitioning from an original device to a new device within a data storage array | |
JP4398464B2 (en) | System, method, and program for managing point-in-time copy relationships between one target volume and one source volume | |
US11579983B2 (en) | Snapshot performance optimizations | |
WO2011121590A1 (en) | Log structure array | |
US10936243B2 (en) | Storage system and data transfer control method | |
US11561720B2 (en) | Enabling access to a partially migrated dataset | |
US11074003B2 (en) | Storage system and restoration method | |
US9864761B1 (en) | Read optimization operations in a storage system | |
US8825970B1 (en) | System and method for mounting a storage volume utilizing a block reference list | |
US11194760B1 (en) | Fast object snapshot via background processing | |
JP6266767B2 (en) | Consistent and efficient mirroring of non-volatile memory state within a virtual environment | |
US9460010B1 (en) | Method, data storage system and computer program product for managing copy on first write data for snapshot purposes |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: LSI CORPORATION, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:YOUNG, HOWARD;REEL/FRAME:024826/0255 Effective date: 20100714 |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: DEUTSCHE BANK AG NEW YORK BRANCH, AS COLLATERAL AG Free format text: PATENT SECURITY AGREEMENT;ASSIGNORS:LSI CORPORATION;AGERE SYSTEMS LLC;REEL/FRAME:032856/0031 Effective date: 20140506 |
|
AS | Assignment |
Owner name: AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:LSI CORPORATION;REEL/FRAME:035390/0388 Effective date: 20140814 |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
AS | Assignment |
Owner name: AGERE SYSTEMS LLC, PENNSYLVANIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS (RELEASES RF 032856-0031);ASSIGNOR:DEUTSCHE BANK AG NEW YORK BRANCH, AS COLLATERAL AGENT;REEL/FRAME:037684/0039 Effective date: 20160201 Owner name: LSI CORPORATION, CALIFORNIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS (RELEASES RF 032856-0031);ASSIGNOR:DEUTSCHE BANK AG NEW YORK BRANCH, AS COLLATERAL AGENT;REEL/FRAME:037684/0039 Effective date: 20160201 |
|
AS | Assignment |
Owner name: BANK OF AMERICA, N.A., AS COLLATERAL AGENT, NORTH CAROLINA Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD.;REEL/FRAME:037808/0001 Effective date: 20160201 Owner name: BANK OF AMERICA, N.A., AS COLLATERAL AGENT, NORTH Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD.;REEL/FRAME:037808/0001 Effective date: 20160201 |
|
AS | Assignment |
Owner name: AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD., SINGAPORE Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;REEL/FRAME:041710/0001 Effective date: 20170119 Owner name: AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;REEL/FRAME:041710/0001 Effective date: 20170119 |
|
AS | Assignment |
Owner name: AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE. LIMITE Free format text: MERGER;ASSIGNOR:AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD.;REEL/FRAME:047230/0133 Effective date: 20180509 |
|
AS | Assignment |
Owner name: AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE. LIMITE Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE EFFECTIVE DATE OF MERGER TO 09/05/2018 PREVIOUSLY RECORDED AT REEL: 047230 FRAME: 0133. ASSIGNOR(S) HEREBY CONFIRMS THE MERGER;ASSIGNOR:AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD.;REEL/FRAME:047630/0456 Effective date: 20180905 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |