WO2008070173A1 - Apparatus, system, and method for solid-state storage as cache for high-capacity, non-volatile storage - Google Patents

Apparatus, system, and method for solid-state storage as cache for high-capacity, non-volatile storage Download PDF

Info

Publication number
WO2008070173A1
WO2008070173A1 PCT/US2007/025049 US2007025049W WO2008070173A1 WO 2008070173 A1 WO2008070173 A1 WO 2008070173A1 US 2007025049 W US2007025049 W US 2007025049W WO 2008070173 A1 WO2008070173 A1 WO 2008070173A1
Authority
WO
WIPO (PCT)
Prior art keywords
storage
data
solid
module
state storage
Prior art date
Application number
PCT/US2007/025049
Other languages
French (fr)
Inventor
David Flynn
John Strasser
Jonathan Thatcher
Michael Zappe
Original Assignee
Fusion Multisystems, Inc. (Dba Fusion-Io)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Family has litigation
First worldwide family litigation filed litigation Critical https://patents.darts-ip.com/?family=39223046&utm_source=google_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=WO2008070173(A1) "Global patent litigation dataset” by Darts-ip is licensed under a Creative Commons Attribution 4.0 International License.
Application filed by Fusion Multisystems, Inc. (Dba Fusion-Io) filed Critical Fusion Multisystems, Inc. (Dba Fusion-Io)
Priority to JP2009540309A priority Critical patent/JP5523835B2/en
Priority to EP07867661.6A priority patent/EP2109822B1/en
Priority to CN200780050973.4A priority patent/CN101622606B/en
Priority to KR1020147028326A priority patent/KR101532951B1/en
Priority to ES07867661.6T priority patent/ES2507072T3/en
Priority to CA002672100A priority patent/CA2672100A1/en
Publication of WO2008070173A1 publication Critical patent/WO2008070173A1/en

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00—Accessing, addressing or allocating within memory systems or architectures
    • G06F12/02—Addressing or allocation; Relocation
    • G06F12/08—Addressing or allocation; Relocation in hierarchically structured memory systems, e.g. virtual memory systems
    • G06F12/12—Replacement control
    • G06F12/121—Replacement control using replacement algorithms
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F15/00—Digital computers in general; Data processing equipment in general
    • G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/16—Constructional details or arrangements
    • G06F1/18—Packaging or power distribution
    • G06F1/183—Internal mounting support structures, e.g. for printed circuit boards, internal connecting means
    • 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/08—Error detection or correction by redundancy in data representation, e.g. by using checking codes
    • G06F11/10—Adding special bits or symbols to the coded information, e.g. parity check, casting out 9's or 11's
    • 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/08—Error detection or correction by redundancy in data representation, e.g. by using checking codes
    • G06F11/10—Adding special bits or symbols to the coded information, e.g. parity check, casting out 9's or 11's
    • G06F11/1076—Parity data used in redundant arrays of independent storages, e.g. in RAID systems
    • G06F11/108—Parity data distribution in semiconductor storages, e.g. in SSD
    • 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/0223—User address space allocation, e.g. contiguous or non contiguous base addressing
    • G06F12/023—Free address space management
    • G06F12/0238—Memory management in non-volatile memory, e.g. resistive RAM or ferroelectric memory
    • G06F12/0246—Memory management in non-volatile memory, e.g. resistive RAM or ferroelectric memory in block erasable memory, e.g. flash memory
    • 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/0804—Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches with main memory updating
    • 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/0866—Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches for peripheral storage systems, e.g. disk cache
    • G06F12/0868—Data transfer between cache memory and other subsystems, e.g. storage devices or host systems
    • 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/12—Replacement control
    • 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/12—Replacement control
    • G06F12/121—Replacement control using replacement algorithms
    • G06F12/123—Replacement control using replacement algorithms with age lists, e.g. queue, most recently used [MRU] list or least recently used [LRU] list
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/14—Handling requests for interconnection or transfer
    • G06F13/20—Handling requests for interconnection or transfer for access to input/output bus
    • G06F13/28—Handling requests for interconnection or transfer for access to input/output bus using burst mode transfer, e.g. direct memory access DMA, cycle steal
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38—Information transfer, e.g. on bus
    • G06F13/40—Bus structure
    • G06F13/4004—Coupling between buses
    • G06F13/4022—Coupling between buses using switching circuits, e.g. switching matrix, connection or expansion network
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38—Information transfer, e.g. on bus
    • G06F13/42—Bus transfer protocol, e.g. handshake; Synchronisation
    • G06F13/4247—Bus transfer protocol, e.g. handshake; Synchronisation on a daisy chain bus
    • G06F13/426—Bus transfer protocol, e.g. handshake; Synchronisation on a daisy chain bus using an embedded synchronisation, e.g. Firewire bus, Fibre Channel bus, SSA bus
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F15/00—Digital computers in general; Data processing equipment in general
    • G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
    • G06F15/163—Interprocessor communication
    • G06F15/173—Interprocessor communication using an interconnection network, e.g. matrix, shuffle, pyramid, star, snowflake
    • 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
    • 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/0604—Improving or facilitating administration, e.g. storage management
    • 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/0608—Saving storage space on 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/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
    • 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/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0638—Organizing or formatting or addressing of data
    • G06F3/0643—Management of files
    • 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/0646—Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems
    • G06F3/0652—Erasing, e.g. deleting, data cleaning, moving of data to a wastebasket
    • 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/0656—Data buffering arrangements
    • 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
    • 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/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
    • G06F3/0671—In-line storage system
    • G06F3/0673—Single storage device
    • G06F3/0679—Non-volatile semiconductor memory device, e.g. flash memory, one time programmable memory [OTP]
    • 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/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
    • G06F3/0671—In-line storage system
    • G06F3/0683—Plurality of storage devices
    • G06F3/0685—Hybrid storage combining heterogeneous device types, e.g. hierarchical storage, hybrid arrays
    • 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/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
    • G06F3/0671—In-line storage system
    • G06F3/0683—Plurality of storage devices
    • G06F3/0688—Non-volatile semiconductor memory arrays
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/52—Program synchronisation; Mutual exclusion, e.g. by means of semaphores
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H05—ELECTRIC TECHNIQUES NOT OTHERWISE PROVIDED FOR
    • H05K—PRINTED CIRCUITS; CASINGS OR CONSTRUCTIONAL DETAILS OF ELECTRIC APPARATUS; MANUFACTURE OF ASSEMBLAGES OF ELECTRICAL COMPONENTS
    • H05K7/00—Constructional details common to different types of electric apparatus
    • H05K7/14—Mounting supporting structure in casing or on frame or rack
    • H05K7/1438—Back panels or connecting means therefor; Terminals; Coding means to avoid wrong insertion
    • H05K7/1439—Back panel mother boards
    • H05K7/1444—Complex or three-dimensional-arrangements; Stepped or dual mother boards
    • H—ELECTRICITY
    • H05—ELECTRIC TECHNIQUES NOT OTHERWISE PROVIDED FOR
    • H05K—PRINTED CIRCUITS; CASINGS OR CONSTRUCTIONAL DETAILS OF ELECTRIC APPARATUS; MANUFACTURE OF ASSEMBLAGES OF ELECTRICAL COMPONENTS
    • H05K7/00—Constructional details common to different types of electric apparatus
    • H05K7/14—Mounting supporting structure in casing or on frame or rack
    • H05K7/1485—Servers; Data center rooms, e.g. 19-inch computer racks
    • H05K7/1487—Blade assemblies, e.g. blade cases or inner arrangements within a blade
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2211/00—Indexing scheme relating to details of data-processing equipment not covered by groups G06F3/00 - G06F13/00
    • G06F2211/002—Bus
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2211/00—Indexing scheme relating to details of data-processing equipment not covered by groups G06F3/00 - G06F13/00
    • G06F2211/10—Indexing scheme relating to G06F11/10
    • G06F2211/1002—Indexing scheme relating to G06F11/1076
    • G06F2211/103—Hybrid, i.e. RAID systems with parity comprising a mix of RAID types
    • 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/10—Providing a specific technical effect
    • G06F2212/1032—Reliability improvement, data loss prevention, degraded operation etc
    • 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/10—Providing a specific technical effect
    • G06F2212/1041—Resource optimization
    • G06F2212/1044—Space efficiency improvement
    • 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/20—Employing a main memory using a specific memory technology
    • G06F2212/202—Non-volatile memory
    • G06F2212/2022—Flash 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/22—Employing cache memory using specific memory technology
    • G06F2212/222—Non-volatile 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/70—Details relating to dynamic memory management
    • 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/72—Details relating to flash memory management
    • G06F2212/7203—Temporary buffering, e.g. using volatile buffer or dedicated buffer blocks
    • 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/72—Details relating to flash memory management
    • G06F2212/7205—Cleaning, compaction, garbage collection, erase control
    • 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/72—Details relating to flash memory management
    • G06F2212/7208—Multiple device management, e.g. distributing data over multiple flash devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Definitions

  • This invention relates to managing data and more particularly relates to using solid-state storage as cache for high-capacity, non-volatile storage devices.
  • DESCRIPTION OF THE RELATED ART cache is advantageous because data that is accessed often or that is loaded as part of an application or operating system may be stored in cache with subsequent access much quicker than when the data must be accessed through a high-capacity, non-volatile (“HCNV”) storage device, such as a hard disk drive (“HDD”), an optical drive, tape storage, etc.
  • HCNV high-capacity, non-volatile
  • HDD hard disk drive
  • tape storage etc.
  • Cache is typically included in a computer.
  • Some storage devices and systems include cache in HCNV storage devices.
  • Some HCNV storage devices contain non-volatile solid state cache; these provide benefit in reducing access times, but can only deliver performance consistent with the usually limited capability of the HCNV storage device interface.
  • Some non-volatile solid-state cache storage devices exist that are typically placed on a motherboard; these devices cannot be used in multi-client environments as no cache coherence is provided.
  • Some controllers of HCNV devices also include cache. Where redundant HCNV cache controllers are shared between multiple clients, sophisticated cache coherency algorithms are required to ensure that data is not corrupted.
  • caches are implemented in DRAM, making cache capacity a premium, and requiring relatively high power per performance. If power supporting the volatile cache is lost, data stored in the cache is lost. Typically, some battery backup is used to avoid data loss in case of power failure, with sufficient capability to flush the cache to non-volatile memory prior to failure of the batter backup. In addition, battery backup systems consume power, require redundancy, negatively impact reliability and consume space. Batteries must also be serviced on a regular basis and battery backup can be relatively expensive.
  • the present invention has been developed in response to the present state of the art, and in particular, in response to the problems and needs in the art that have not yet been fully solved by currently available systems for managing data storage. Accordingly, the present invention has been developed to provide an apparatus, system, and method for managing the storage of data on one or more high capacity, non-volatile (“HCNV”) storage devices that overcome many or all of the above-discussed shortcomings in the art.
  • HCNV high capacity, non-volatile
  • the apparatus is provided, in one embodiment, with a plurality of modules including a cache front-end module and a cache back-end module.
  • the cache front-end module manages data transfers associated with a storage request. The data transfers are between a requesting device and solid-state storage function as cache for one or more HCNV storage devices, and the data transfers may include one or more of data, metadata, and metadata indexes.
  • the solid-state storage may include an array of non-volatile, solid-state data storage elements.
  • the cache back- end module manages data transfers between the solid-state storage and the one or more HCNV storage devices.
  • the cache front-end module and the cache back-end module are co-located with a solid-state storage controller that manages the solid-state storage.
  • the cache front-end module, the cache back-end module, and the solid- state storage controller may operate autonomously from the requesting device.
  • the apparatus includes an HCNV RAID module that stores data cached in the solid-state storage in two or more HCNV storage devices in redundant array of independent drives (“RAID") consistent with a RAID level.
  • the data may appear to a requesting device as a whole.
  • the solid-state storage and the one or more HCNV storage devices may include a hybrid storage device within a hybrid storage device set that is configured as a RAID group.
  • a data segment cached in the solid-state storage and later stored on an HCNV device may include one of N data segments of a stripe or a parity data segment of the stripe.
  • the hybrid storage device typically receives storage requests from one or more clients independent of data segments of a RAID stripe.
  • the hybrid storage device may be a storage device of a shared, front-end distributed RAID group that receives two or more simultaneous storage requests from two or more clients.
  • the HCNV storage device may be a hard disk drive ("HDD"), an optical drive, or a tape storage.
  • the solid-state storage and the one or more HCNV storage devices may be a hybrid storage device.
  • the apparatus may also include a standard device emulation module that provides access to the hybrid storage device by emulating a standard device attached to one or more requesting devices prior to loading the one or more requesting devices with code specific to the operation of the hybrid storage device.
  • the standard device typically may be supported by an industry standard BIOS.
  • the solid-state storage device may be partitioned into two or more regions, wherein one or more partitions may be used as solid-state storage independent of the solid-state storage functioning as cache for the HCNV storage devices.
  • one or more clients send cache control messages to the cache front-end module and the cache back-end module to manage a state of one or more of files or objects stored within the solid-state storage device and the one or more HCNV storage devices.
  • the cache control messages may include one or more control messages.
  • Various embodiments of the control messages may include a control message that causes the cache back-end module to pin a portion of an object or file in the solid- state storage or a control message that causes the cache back-end module to unpin a portion of an object or file in the solid-state storage.
  • Other embodiments of the control messages may include a control message that causes the cache back-end module to flush a portion of an object or file from the solid-state storage to the one or more HCVN storage devices or a control message causes the cache back-end module to preload a portion of an object or file to the solid-state storage from the one or more HCVN storage devices.
  • a control message may be a control message that causes the cache back-end module to offload one or more portions of one or more objects or files from the solid-state storage to the one or more HCVN storage devices in order to free up a determined amount of storage space in the solid-state storage.
  • the cache control messages are communicated through metadata ("cache control metadata") for the object or file.
  • the cache control metadata may be persistent.
  • the cache control metadata may be established through attributes set at a time of creation of the file or object.
  • the cache control metadata may be obtained from a file or object management system.
  • the apparatus may include a volatile cache storage element wherein the cache front-end module and the cache back-end module store data in the volatile cache storage element and manage data stored in the solid-state storage and volatile cache storage element.
  • the back-end storage module may further manage data transfers between the volatile cache storage element, the solid state storage, and the HCVN storage devices.
  • metadata and/or index metadata for objects and files stored in the HCVN storage devices may be maintained within the solid-state storage device and the volatile cache storage element.
  • metadata and/or index metadata for objects and files stored in the HCVN storage devices may be maintained within the solid-state storage device.
  • the solid-state storage and the one or more HCNV storage devices may include a storage device such that the HCNV storage devices are hidden from view of a client connected to the storage device.
  • a system of the present invention is also presented.
  • the system substantially includes the modules and embodiments described above with regard to the apparatus.
  • the system includes a solid-state storage that includes an array of non-volatile, solid-state data storage elements.
  • the system also includes one or more HCNV storage devices and a storage controller.
  • the storage controller in one embodiment, may include a solid-state storage controller and an HCNV storage device controller.
  • the storage controller may also include a cache front-end module and a cache back-end module.
  • the cache front-end module manages data transfers associated with a storage request. The data transfers are typically between a requesting device and the solid-state storage functioning as cache for the one or more HCNV storage devices.
  • the data transfers may include one or more of data, metadata, and metadata indexes.
  • the cache back-end module manages data transfers between the solid-state storage and the one or more HCNV storage devices.
  • the system includes a network interface connected to the storage controller, wherein the network interface facilitates data transfers between the requesting device and the solid-state storage controller through a computer network.
  • the system includes a server that includes the solid-state storage, the one or more HCNV storage devices, and the storage controller.
  • the one or more HCNV storage devices are connected to the storage controller through a storage area network ("SAN").
  • SAN storage area network
  • a method of the present invention is also presented for sharing a device between multiple hosts.
  • the method in the disclosed embodiments substantially includes the steps necessary to carry out the functions presented above with respect to the operation of the described apparatus and system.
  • the method includes managing data transfers associated with a storage request, wherein the data transfers are between a requesting device and solid-state storage functioning as cache for one or more HCNV storage devices.
  • the data transfers may include one or more of data, metadata, and metadata indexes.
  • the solid-state storage may include an array of non-volatile, solid-state data storage elements.
  • the method may also include managing data transfers between the solid-state storage and the one or more HCNV storage devices.
  • Figure IA is a schematic block diagram illustrating one embodiment of a system for data management in a solid-state storage device in accordance with the present invention
  • Figure IB is a schematic block diagram illustrating one embodiment of a system for object management in a storage device in accordance with the present invention
  • Figure 1C is a schematic block diagram illustrating one embodiment of a system for an in-server storage area network in accordance with the present invention
  • Figure 2A is a schematic block diagram illustrating one embodiment of an apparatus for object management in a storage device in accordance with the present invention
  • Figure 2B is a schematic block diagram illustrating one embodiment of a solid-state storage device controller in a solid-state storage device in accordance with the present invention
  • Figure 3 is a schematic block diagram illustrating one embodiment of a solid-state storage controller with a write data pipeline and a read data pipeline in a solid-state storage device in accordance with the present invention
  • Figure 4A is a schematic block diagram illustrating one embodiment of a bank interleave controller in the solid-state storage controller in accordance with the present invention
  • Figure 4B is a schematic block diagram illustrating an alternate embodiment of a bank interleave controller in the solid-state storage controller in accordance with the present invention
  • Figure 5A is a schematic flow chart diagram illustrating one embodiment of a method for managing data in a solid-state storage device using a data pipeline in accordance with the present invention
  • Figure 5B is a schematic flow chart diagram illustrating one embodiment of a method for in-server SAN in accordance with the present invention
  • Figure 6 is a schematic flow chart diagram illustrating another embodiment of a method for managing data in a solid-state storage device using a data pipeline in accordance with the present invention
  • Figure 7 is a schematic flow chart diagram illustrating an embodiment of a method for managing data in a solid-state storage device using a bank interleave in accordance with the present invention
  • Figure 8 is a schematic block diagram illustrating one embodiment of an apparatus for garbage collection in a solid-state storage device in accordance with the present invention
  • Figure 9 is a schematic flow chart diagram illustrating one embodiment of a method for garbage collection in a solid state storage device in accordance with the present invention.
  • Figure 10 is a schematic block diagram illustrating one embodiment of a system for progressive RAID, front-end distributed RAID, and shared, front-end distributed RAID in accordance with the present inventions;
  • Figure 11 is a schematic block diagram illustrating one embodiment of an apparatus for front-end distributed RAID in accordance with the present invention
  • Figure 12 is a schematic flow chart diagram illustrating an embodiment of a method for front-end distributed RAID in accordance with the present invention
  • Figure 13 is a schematic block diagram illustrating one embodiment of an apparatus for shared, front-end distributed RAID in accordance with the present invention
  • Figure 14 is a schematic flow chart diagram illustrating an embodiment of a method for shared, front-end distributed RAID in accordance with the present invention
  • Figure 15 is a schematic block diagram illustrating one embodiment of a system with solid-state storage as cache for a high-capacity, non-volatile storage device in accordance with the present invention
  • Figure 16 is a schematic block diagram illustrating one embodiment of an apparatus with solid-state storage as cache for a high-capacity, non-volatile storage device in accordance with the present invention.
  • Figure 17 is a schematic flow chart diagram illustrating one embodiment of a method with solid-state storage as cache for a high-capacity, non-volatile storage device in accordance with the present invention.
  • modules may be implemented as a hardware circuit comprising custom VLSI circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components.
  • a module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.
  • Modules may also be implemented in software for execution by various types of processors.
  • An identified module of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.
  • a module of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices.
  • operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network.
  • the software portions are stored on one or more computer readable media.
  • Reference to a signal bearing medium may take any form capable of generating a signal, causing a signal to be generated, or causing execution of a program of machine-readable instructions on a digital processing apparatus.
  • a signal bearing medium may be embodied by a transmission line, a compact disk, digital-video disk, a magnetic tape, a Bernoulli drive, a magnetic disk, a punch card, flash memory, integrated circuits, or other digital processing apparatus memory device.
  • an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted method. Additionally, the order in which a particular method occurs may or may not strictly adhere to the order of the corresponding steps shown.
  • Figure IA is a schematic block diagram illustrating one embodiment of a system 100 for data management in a solid-state storage device in accordance with the present invention.
  • the system 100 includes a solid-state storage device 102, a solid-state storage controller 104, a write data pipeline 106, a read data pipeline 108, a solid-state storage 110, a computer 112, a client 114, and a computer network 116, which are described below.
  • the system 100 includes at least one solid-state storage device 102.
  • the system 100 includes two or more solid-state storage devices 102.
  • Each solid- state storage device 102 may include non- volatile, solid-state storage 110, such as flash memory, nano random access memory (“nano RAM or NRAM”), magneto-resistive RAM (“MRAM”), dynamic RAM (“DRAM”), phase change RAM (“PRAM”), etc.
  • NRAM nano random access memory
  • MRAM magneto-resistive RAM
  • DRAM dynamic RAM
  • PRAM phase change RAM
  • the solid-state storage device 102 is described in more detail with respect to Figures 2 and 3.
  • the solid-state storage device 102 is depicted in a computer 112 connected to a client 114 through a computer network 116.
  • the solid-state storage device 102 is internal to the computer 112 and is connected using a system bus, such as a peripheral component interconnect express (“PCI-e”) bus, a Serial Advanced Technology Attachment (“serial ATA”) bus, or the like.
  • PCI-e peripheral component interconnect express
  • serial ATA Serial Advanced Technology Attachment
  • the solid-state storage device 102 is external to the computer 112 and is connected, a universal serial bus (“USB”) connection, an Institute of Electrical and Electronics Engineers (“IEEE”) 1394 bus (“FireWire”), or the like.
  • the solid-state storage device 102 is connected to the computer 112 using a peripheral component interconnect ("PCI") express bus using external electrical or optical bus extension or bus networking solution such as Infiniband or PCI Express Advanced Switching (“PCIe-AS”), or the like.
  • PCIe-AS Peripheral Component Interconnect
  • the solid-state storage device 102 may be in the form of a dual- inline memory module ("DEvIM"), a daughter card, or a micro-module.
  • the solid-state storage device 102 is an element within a rack-mounted blade.
  • the solid state storage device 102 is contained within a package that is integrated directly onto a higher level assembly (e.g. mother board, lap top, graphics processor).
  • individual components comprising the solid-state storage device 102 are integrated directly onto a higher level assembly without intermediate packaging.
  • the solid-state storage device 102 includes one or more solid-state storage controllers 104, each may include a write data pipeline 106 and a read data pipeline 108 and each includes a solid-state storage 110, which are described in more detail below with respect to Figures 2 and 3.
  • the system 100 includes one or more computers 112 connected to the solid-state storage device 102.
  • a computer 112 may be a host, a server, a storage controller of a storage area network ("SAN"), a workstation, a personal computer, a laptop computer, a handheld computer, a supercomputer, a computer cluster, a network switch, router, or appliance, a database or storage appliance, a data acquisition or data capture system, a diagnostic system, a test system, a robot, a portable electronic device, a wireless device, or the like.
  • a computer 112 may be a client and the solid-state storage device 102 operates autonomously to service data requests sent from the computer 112.
  • the computer 112 and solid-state storage device 102 may be connected using a computer network, system bus, or other communication means suitable for connection between a computer 112 and an autonomous solid-state storage device 102.
  • the system 100 includes one or more clients 114 connected to one or more computer 112 through one or more computer networks 116.
  • a client 114 may be a host, a server, a storage controller of a SAN, a workstation, a personal computer, a laptop computer, a handheld computer, a supercomputer, a computer cluster, a network switch, router, or appliance, a database or storage appliance, a data acquisition or data capture system, a diagnostic system, a test system, a robot, a portable electronic device, a wireless device, or the like.
  • the computer network 116 may include the Internet, a wide area network ("WAN”), a metropolitan area network (“MAN”), a local area network (“LAN”), a token ring, a wireless network, a fiber channel network, a SAN, network attached storage (“NAS”), ESCON, or the like, or any combination of networks.
  • the computer network 116 may also include a network from the IEEE 802 family of network technologies, such Ethernet, token ring, WiFi, WiMax, and the like.
  • the computer network 116 may include servers, switches, routers, cabling, radios, and other equipment used to facilitate networking computers 112 and clients 114.
  • the system 100 includes multiple computers 112 that communicate as peers over a computer network 116.
  • the system 100 includes multiple solid-state storage devices 102 that communicate as peers over a computer network 116.
  • One of skill in the art will recognize other computer networks 116 comprising one or more computer networks 116 and related equipment with single or redundant connection between one or more clients 114 or other computer with one or more solid-state storage devices 102 or one or more solid-state storage devices 102 connected to one or more computers 112.
  • the system 100 includes two or more solid-state storage devices 102 connected through the computer network 118 to a client 116 without a computer 1 12.
  • Figure IB is a schematic block diagram illustrating one embodiment of a system 101 for object management in a storage device in accordance with the present invention.
  • the system
  • An object request may be a request to create an object, a request to write data to an object, a request to read data from an object, a request to delete an object, a request to checkpoint an object, a request to copy an object, and the like.
  • An object request may be a request to create an object, a request to write data to an object, a request to read data from an object, a request to delete an object, a request to checkpoint an object, a request to copy an object, and the like.
  • the storage controller 152 and data storage device 154 are separate devices. In another embodiment, the storage controller 152 and data storage device 154 are integrated into one storage device 150. In another embodiment, a data storage device 154 is a solid-state storage 110 and the storage controller is a solid-state storage device controller 202. In other embodiments, a data storage device 154 may be a hard disk drive, an optical drive, tape storage, or the like. In another embodiment, a storage device 150 may include two or more data storage devices 154 of different types. In one embodiment, the data storage device 154 is a solid-state storage 1 10 and is arranged as an array of solid-state storage elements 216, 218, 220. In another embodiment, the solid-state storage 110 is arranged in two or more banks 214a-n. Solid-state storage 110 is described in more detail below with respect to Figure 2B.
  • the storage devices 150a-n may be networked together and act as a distributed storage device.
  • the storage device 150a coupled to the requesting device 155 controls object requests to the distributed storage device.
  • the storage devices 150 and associated storage controllers 152 manage objects and appear to the requesting device(s) 155 as a distributed object file system.
  • a parallel object file system is an example of a type of distributed object file system.
  • the storage devices 150 and associated storage controllers 152 manage objects and appear to the requesting device(s) 155 as distributed object file servers.
  • a parallel object file server is an example of a type of distributed object file server.
  • the requesting device 155 may exclusively manage objects or participate in managing objects in conjunction with storage devices 150; this typically does not limit the ability of storage devices 150 to fully manage objects for other clients 114.
  • each distributed storage device, distributed object file system and distributed object file server can operate independently as a single device.
  • the networked storage devices 150a-n may operate as distributed storage devices, distributed object file systems, distributed object file servers, and any combination thereof having images of one or more of these capabilities configured for one or more requesting devices 155.
  • the storage devices 150 may be configured to operate as distributed storage devices for a first requesting device 155a, while operating as distributed storage devices and distributed object file systems for requesting devices 155b.
  • the storage controller 152a of the storage device 150a manages objects may appear to the requesting device(s) 155 as an object file system or an object file server.
  • the storage devices 150 serve as a redundant array of independent drives (“RAID") managed by one or more distributed storage controllers 152.
  • RAID redundant array of independent drives
  • a request to write a data segment of an object results in the data segment being stripped across the data storage devices 154a-n with a parity stripe, depending upon the RAID level.
  • One benefit of such an arrangement is that such an object management system may continue to be available when a single storage.
  • device 150 has a failure, whether of the storage controller 152, the data storage device 154, or other components of storage device 150.
  • a system 101 with a single storage device 150a may also include multiple data storage devices 154a and the storage controller 152a of the storage device 150a may act as a RAID controller and stripe the data segment across the data storage devices 154a of the storage device 150a and may include a parity stripe, depending upon the RAID level.
  • the solid- state storage device(s) 102 may be configured in a DIMM configuration, daughter card, micromodule, etc. and reside in a computer 112.
  • the computer 112 may be a server or similar device with the solid-state storage devices 102 networked together and acting as distributed RAID controllers.
  • the storage devices 102 may be connected using PCI-e, PCIe-AS, Infiniband or other high-performance bus, switched bus, networked bus, or network and may provide a very compact, high performance RAID storage system with single or distributed solid- state storage controllers 202 autonomously striping a data segment across solid-state storage 110a-n.
  • the same network used by the requesting device 155 to communicate with storage devices 150 may be used by the peer storage device 150a to communicate with peer storage devices 150b-n to accomplish RAID functionality.
  • a separate network may be used between the storage devices 150 for the purpose of RAIDing.
  • the requesting devices 155 may participate in the RAIDing process by sending redundant requests to the storage devices 150. For example, requesting device 155 may send a first object write request to a first storage device 150a and a second object write request with the same data segment to a second storage device 150b to achieve simple mirroring.
  • the storage controller(s) 152 With the ability for object handling within the storage device(s) 102, the storage controller(s) 152 uniquely have the ability to store one data segment or object using one RAID level while another data segment or object is stored using a different RAID level or without RAID striping. These multiple RAID groupings may be associated with multiple partitions within the storage devices 150. RAID 0, RAID 1, RAID5, RAID6 and composite RAID types 10, 50, 60, can be supported simultaneously across a variety of RAID groups comprising data storage devices 154a-n. One skilled in the art will recognize other RAID types and configurations that may also be simultaneously supported.
  • the storage controller(s) 152 operate autonomously as " RAID controllers
  • the RAID controllers can perform progressive RAIDing and can transform objects or portions of objects striped across data storage devices 154 with one RAID level to another RAID level without the requesting device 155 being affected, participating or even detecting the change in RAID levels.
  • progressing the RAID configuration from one level to another level may be accomplished autonomously on an object or even a packet bases and is initiated by a distributed RAID control module operating in one of the storage devices 150 or the storage controllers 152.
  • RAID progression will be from a higher performance and lower efficiency storage configuration such as RAIDl to a lower performance and higher storage efficiency configuration such as RAID5 where the transformation is dynamically initiated based on the frequency of access.
  • SOLID-STATE STORAGE DEVICE WITH IN-SERVER SAN Figure 1C is a schematic block diagram illustrating one embodiment of a system 103 for an in-server storage area network ("SAN") in accordance with the present invention.
  • the system 103 includes a computer 112 typically configured as a server ("server 112").
  • Each server 112 includes one or more storage devices 150 where the server 112 and storage devices 150 are each connected to a shared network interface 156.
  • Each storage device 150 includes a storage controller 152 and corresponding data storage device 154.
  • the system 103 includes clients 114, 114a, 114b that are either internal or external to the servers 112.
  • the clients 114, 114a, 114b may communicate with each server 112 and each storage device 150 through over one or more computer networks 116, which are substantially similar to those described above.
  • the storage device 150 includes a DAS module 158, a NAS module 160, a storage communication module 162, an in-server SAN module 164, a common interface module 166, a proxy module 170, a virtual bus module 172, a front-end RAID module 174, and back-end RAID module 176, which are described below. While the modules 158-176 are shown in a storage device 150, all or a portion of each module 158-176 may be in the storage device 150, server 112, storage controller 152, or other location.
  • a server 112 as used in conjunction with in-server SAN, is a computer functioning as a server.
  • the server 112 includes at least one server function, such as a file server function, but may also include other server functions as well.
  • the servers 112 may be part of a server farm and may service other clients 114. In other embodiments, the server 112 may also be a personal computer, a workstation, or other computer that houses storage devices 150.
  • a server 112 may access one or more storage devices 150 in the server 112 as direct attached storage ("DAS"), SAN attached storage or network attached storage ("NAS").
  • DAS direct attached storage
  • NAS network attached storage
  • Storage controllers 150 participating in an in-server SAN or NAS may be internal or external to the server 112.
  • the in-server SAN apparatus includes a DAS module 158 that configures at least a portion of the at least one data storage device 154 controlled by a storage controller 152 in a server 112 as a DAS device attached to the server 112 for servicing storage requests from at least one client 114 to the server 112.
  • a first data storage device 154a is configured as a DAS to the first server 112a while also being configured as an in- server SAN storage device to the first server 112a.
  • the first data storage device 154a is partitioned so one partition is a DAS and the other is an in-server SAN.
  • the in-server SAN apparatus includes a NAS module 160 that configures a storage controller 152 as a NAS device for at least one client 114 and services file requests from the client 114.
  • the storage controller 152 may be also configured as an in-server SAN device for the first server 112a.
  • the storage devices 150 may directly connect to the computer network 116 through the shared network interface 156 independent from the server 112 in which the storage device 150 resides.
  • an apparatus for in-server SAN includes a first storage controller 152a within a first server 112a where the first storage controller 152a controls at least one storage device 154a.
  • the first server 112a includes a network interface 156 shared by the first server 112a and the first storage controller 152a.
  • the in-server SAN apparatus includes a storage communication module 162 that facilitates communication between the first storage controller 152a and at least one device external to the first server 112asuch that the communication between the first storage controller 152a and the external device is independent from the first server 112a.
  • the storage communication module 162 may allow the first storage controller 152a to independently access the network interface 156a for external communication.
  • the storage communication module 162 accesses a switch in the network interface 156a to direct network traffic between the first storage controller 152a and external devices.
  • the in-server SAN apparatus also includes an in-server SAN module 164 that services a storage request using one or both of a network protocol and a bus protocol.
  • the in-server SAN module 164 services the storage request independent from the first server 112a and the service request is received from an internal or external client 114, 114a.
  • the device external to the first server 112a is a second storage controller 152b.
  • the second storage controller 152b controls at least one data storage device 154b.
  • the in-server SAN module 164 services the storage request using communication through the network interface 156a and between the first and second storage controllers 152a, 152b independent of the first server 112a.
  • the second storage controller 152b may be within a second server 112b or within some other device.
  • the device external to the first server 112a is a client 114 and the storage request originates with the external client 114 where the first storage controller is configured as at least part of a SAN and the in-server SAN module 164 services the storage request through the network interface 156a independent of the first server 112a.
  • the external client 114 may be in the second server 112b or may be external to the second server 112b.
  • the in-server SAN module 164 can service storage requests from the external client 114 even when the first server 112a is unavailable.
  • the client 114a originating the storage request is internal to the first server 112a where the first storage controller 152a is configured as at least part of a SAN and the in-server SAN module 164 services the storage request through one or more of the network interface 156a and system bus.
  • Traditional SAN configurations allow a storage device remote from a server 1 12 to be accessed as if the storage device resides within the server 112 as direct attached storage (“DAS”) so that the storage device appears as a block storage device.
  • DAS direct attached storage
  • a storage device connected as a SAN requires a SAN protocol, such as fiber channel, Internet small computer system interface (“iSCSI"), HyperSCSI, Fiber Connectivity (“FICON”), Advanced Technology Attachment ("ATA”) over Ethernet, etc.
  • In-server SAN includes a storage controller 152 inside a server 112 while still allowing network connection between the storage controller 152a and a remote storage controller 152b or an external client 114 using a network protocol and/or a bus protocol.
  • SAN protocols are a form of network protocol and more network protocols are emerging, such as Infiniband that would allow a storage controller 150a, and associated data storage devices 154a, to be configured as a SAN and communicate with an external client 114 or second storage controller 152b.
  • a first storage controller 152a may communicate with an external client 114 or second storage controller 152b using Ethernet.
  • a storage controller 152 may communicate over a bus with internal storage controllers 152 or clients 114a.
  • a storage controller 152 may communicate over a bus using PCI-e that may support PCI Express Input/Output Virtualization ("PCIe-IOV").
  • PCIe-IOV PCI Express Input/Output Virtualization
  • Other emerging bus protocols allow a system bus to extend outside a computer or server 112 and would allow a storage controller 152a to be configured as a SAN.
  • One such bus protocol is PCIe-AS.
  • the present invention is not limited to simply SAN protocols, but may also take advantage of the emerging network and bus protocols to service storage requests.
  • An external device either in the form of a client 114 or external storage controller 152b, may communicate over an extended system bus or a computer network 1 16.
  • a storage request includes requests to write data, read data, erase data, query data, etc. and may include object data, metadata, and management requests as well as block data requests.
  • a traditional server 1 12 typically has a root complex that controls access to devices within the server 1 12. Typically, this root complex of the server 112 owns the network interface 156 such so any communication through the network interface 156 is controlled by the server 112.
  • the storage controller 152 is able to access the network interface 156 independently so that clients 114 may communicate directly with one or more of the storage controllers 152a in the first server 112a forming a SAN or so that one or more first storage controllers 152a may be networked together with a second storage controller 152b or other remote storage controllers 152 to form a SAN.
  • devices remote from the first server 112a may access the first server 112a or the first storage controller 152a through a single, shared network address.
  • the in-server SAN apparatus includes a common interface module 166 that configures the network interface 156, the storage controller 152, and the server 112 such that the server 112 and the storage controller 152 are accessible using a shared network address.
  • the server 1 12 includes two or more network interfaces 156.
  • the server 112 may communicate over one network interface 156 while the storage device 150 may communicate over another interface.
  • the server 112 includes multiple storage devices 150, each with a network interface 156.
  • One of skill in the art will recognize other configurations of a server 1 12 with one or more storage devices 150 and one or more network interfaces 156 where one or more of the storage devices 150 access a network interface 156 independent of the server 112.
  • One of skill in the art will also recognize how these various configurations may be extended to support network redundancy and improve availability.
  • the in-server SAN apparatus eliminates much of the complexity and expense of a traditional SAN.
  • a typical SAN requires servers 112 with external storage controllers 152 and associated data storage devices 154. This takes up additional space in a rack and requires cabling, switches, etc. The cabling, switching, another other overhead required to configure a traditional SAN take space, degrade bandwidth, and are expensive.
  • the in-server SAN apparatus allows the storage controllers 152 and associated storage 154 to fit in a server 112 form factor, thus reducing required space and costing less.
  • In-server SAN also allows connection using relatively fast communication over internal and external high-speed data buses.
  • the storage device 150 is a solid-state storage device 102
  • the storage controller 152 is a solid-state storage controller 104
  • the data storage device 154 is a solid- state storage 110.
  • the solid-state storage device 102 may be configured in a DIMM which may conveniently fit in a server 112 and require a small amount of space.
  • the one or more internal clients 114a in the server 112 may also connect to the computer network 116 through the server's network interface 156 and the client's connection is typically controlled by the server 1 12. This has several advantages. Clients 114a may locally and remotely access the storage devices 150 directly and may initiate a local or remote direct memory access (“DMA,” "RDMA”) data transfer between the memory of a client 114a and a storage device 150.
  • DMA local or remote direct memory access
  • clients 114, 114a within or external to a server 112 may act as file servers to clients 114 through one or more networks 1 16 while utilizing locally attached storage devices 150 as DAS devices, network attached storage devices 150, network attached solid-state storages 102 devices participating as part of in-server SANs, external SANs, and hybrid SANs.
  • a storage device 150 may participate in a DAS, in-server-SAN, SAN, NAS, etc, simultaneously and in any combination.
  • each storage device 150 may be partitioned in such a way that a first partition makes the storage device 150 available as a DAS, a second partition makes the storage device 150 available as an element in an in-server-SAN, a third partition makes the storage device 150 available as a NAS, a fourth partition makes the storage device 150 available as an element in a SAN, etc.
  • the storage device 150 may be partitioned consistent with security and access control requirements.
  • any number of combinations and permutations of storage devices, virtual storage devices, storage networks, virtual storage networks, private storage, shared storage, parallel file systems, parallel object file systems, block storage devices, object storage devices, storage appliances, network appliances, and the like may be constructed and supported.
  • the storage devices 150 can communicate with each other and can act as an in-server SAN.
  • Clients 114a in the servers 112 and clients 114 connected through the computer network 116 may access the storage devices 150 as a SAN.
  • the server 112/storage device 150 combination eliminates the need in conventional SANs for dedicated storage controllers, fiber channel networks, and other equipment.
  • the in-server SAN system 103 has the advantage of enabling the storage device 150 to share common resources such as power, cooling, management, and physical space with the client 114 and computer 112.
  • storage devices 150 may fill empty slots of servers 1 12 and provide all the performance capabilities, reliability and availability of a SAN or NAS.
  • storage devices 150 may fill empty slots of servers 1 12 and provide all the performance capabilities, reliability and availability of a SAN or NAS.
  • One of skill in the art will recognize other features and benefits of an in-server SAN system 103.
  • multiple in-server-SAN storage devices 150a are collocated within a single server 112a infrastructure.
  • the server 112a is comprised of one or more internal bladed server clients 114a interconnected using PCI-express IO V without an external network interface 156, external client 114, 114b or external storages device 150b.
  • in-server SAN storage device 150 may communicate through one or more computer networks 116 with peer storage devices 150 that are located in a computer 1 12 (per Figure IA), or are connected directly to the computer network 116 without a computer 112 to form a hybrid SAN which has all the capabilities of both SAN and in-server SAN.
  • This flexibility has the benefit of simplifying extensibility and migration between a variety of possible solid-state storage network implementations.
  • One skilled in the art will recognize other combinations, configurations, implementations, and architectures for locating and interconnecting solid-state controllers 104.
  • a link setup module 168 operating within that agent can set up communication paths between internal clients 114a and storage devices 150a/first storage controllers 152a through network interface 156a to external storage devices 150b and clients 114, 114b.
  • the individual internal storage devices 150a and internal clients 114a are able to establish and manage their own command queues and transfer both commands and data through network interface 156a to external storage devices 150b and clients 114, 114b in either direction, directly and through RDMA independent of the proxy or agent controlling the network interface 156a.
  • the link setup module 168 establishes the communication links during an initialization process, such as a startup or initialization of hardware.
  • a proxy module 170 directs at least a portion of commands used in servicing a storage request through the first server 112a while at least data, and possibly other commands, associated with the storage request are communicated between the first storage controller and the external storage device independent of the first server.
  • the proxy module 170 forwards commands or data in behalf of the internal storage devices 150a and clients 114a.
  • the first server 112a includes one or more servers within the first server 112a and includes a virtual bus module 172 that allows the one or more servers in the first server 112a to independently access one or more storage controllers 152a through separate virtual buses.
  • the virtual buses may be established using an advanced bus protocol such as PCIe-IOV.
  • Network interfaces 156a supporting IOV may allow the one or more servers and the one or more storage controllers to independently control the one or more network interfaces 156a.
  • the in-server SAN apparatus allows two or more storage devices 150 to be configured in a RAID.
  • the in-server SAN apparatus includes a front-end RAID module 174 that configures two or more storage controllers 152 as a RAID. Where a storage request from a client 114, 114a includes a request to store data, the front-end RAID module 174 services the storage request by writing the data to the RAID consistent with the particular implemented RAID level.
  • a second storage controller 152 may be located either in the first server 112a or external to the first server 112a.
  • the front-end RAID module 174 allows RAIDing of storage controllers 152 such that the storage controllers 152 are visible to the client 114, 114a sending the storage request. This allows striping and parity information to be managed by a storage controller 152 designated as master or by the client 114, 114a.
  • the in-server SAN apparatus includes a back-end RAID module 176 that configures two or more data storage devices 154 controlled by a storage controller as a RAID.
  • the back-end RAID module 176 services the storage request by writing the data to the RAID consistent with an implemented RAID level such that the storage devices 154 configured as a RAID are accessed by the client 114, 114a as a single data storage device 154 controlled by the first storage controller 152.
  • This RAID implementation allows RAIDing of the data storage devices 154 controlled by a storage controller 152 in a way that the RAIDing is transparent to any client 114, 114a accessing the data storage devices 154.
  • both front-end RAID and back-end RAID are implemented to have multi-level RAID.
  • One of skill in the art will recognize other ways to RAID the storage devices 152 consistent with the solid-state storage controller 104 and associated solid-state storage 110 described herein.
  • FIG. 2A is a schematic block diagram illustrating one embodiment of an apparatus 200 for object management in a storage device in accordance with the present invention.
  • the apparatus 200 includes a storage controller 152 with an object request receiver module 260, a parsing module 262, a command execution module 264, an object index module 266, an object request queuing module 268, a packetizer 302 with a messages module 270, and an object index reconstruction module 272, which are described below.
  • the storage controller 152 is substantially similar to the storage controller 152 described in relation to the system 102 of Figure IB and may be a solid-state storage device controller 202 described in relation to Figure 2.
  • the apparatus 200 includes an object request receiver module 260 that receives an object request from one or more requesting devices 155.
  • the storage controller 152 stores the data segment as a data packet in a data storage device 154 coupled to the storage controller 152.
  • the object request is typically directed at a data segment stored or to be stored in one or more object data packets for an object managed by the storage controller.
  • the object request may request that the storage controller 152 create an object to be later filled with data through later object request which may utilize a local or remote direct memory access ("DMA,” "RDMA”) transfer.
  • DMA local or remote direct memory access
  • the object request is a write request to write all or part of an object to a previously created object.
  • the write request is for a data segment of an object.
  • the other data segments of the object may be written to the storage device 150 or to other storage devices 152.
  • the write request is for an entire object.
  • the object request is to read data from a data segment managed by the storage controller 152.
  • the object request is a delete request to delete a data segment or object.
  • the storage controller 152 can accept write requests that do more than write a new object or append data to an existing object.
  • a write request received by the object request receiver module 260 may include a request to add data ahead of data stored by the storage controller 152, to insert data into the stored data, or to replace a segment of data.
  • the object index maintained by the storage controller 152 provides the flexibility required for these complex write operations that is not available in other storage controllers, but is currently available only outside of storage controllers in file systems of servers and other computers.
  • the apparatus 200 includes a parsing module 262 that parses the object request into one or more commands.
  • the parsing module 262 parses the object request into one or more buffers. For example, one or more commands in the object request may be parsed into a command buffer.
  • the parsing module 262 prepares an object request so that the information in the object request can be understood and executed by the storage controller 152.
  • One of skill in the art will recognize other functions of a parsing module 262 that parses an object request into one or more commands.
  • the apparatus 200 includes a command execution module 264 that executes the command(s) parsed from the object request. In one embodiment, the command execution module 264 executes one command. In another embodiment, the command execution module 264 executes multiple commands.
  • the command execution module 264 interprets a command parsed from the object request, such as a write command, and then creates, queues, and executes subcommands.
  • a write command parsed from an object request may direct the storage controller 152 to store multiple data segments.
  • the object request may also include required attributes such as encryption, compression, etc.
  • the command execution module 264 may direct the storage controller 152 to compress the data segments, encrypt the data segments, create one or more data packets and associated headers for each data packet, encrypt the data packets with a media encryption key, add error correcting code, and store the data packets a specific location. Storing the data packets at a specific location and other subcommands may also be broken down into other lower level subcommands.
  • One of skill in the art will recognize other ways that the command execution module 264 can execute one or more commands parsed from an object request.
  • the apparatus 200 includes an object index module 266 that creates an object entry in an object index in response to the storage controller 152 creating an object or storing the data segment of the object.
  • the storage controller 152 creates a data packet from the data segment and the location of where the data packet is stored is assigned at the time the data segment is stored.
  • Object metadata received with a data segment or as part of an object request may be stored in a similar way.
  • the object index module 266 creates an object entry into an object index at the time the data packet is stored and the physical address of the data packet is assigned.
  • the object entry includes a mapping between a logical identifier of the object and one or more physical addresses corresponding to where the storage controller 152 stored one or more data packets and any object metadata packets.
  • the entry in the object index is created before the data packets of the object are stored. For example, if the storage controller 152 determines a physical address of where the data packets are to be stored earlier, the object index module 266 may create the entry in the object index earlier.
  • the object index module 266 updates an entry in the object index corresponding the modified object.
  • the object index creates a new object and a new entry in the object index for the modified object.
  • the object includes modified data packets and some data packets that remain unchanged.
  • the new entry includes a mapping to the unchanged data packets as where they were originally written and to the modified objects written to a new location.
  • the storage controller 152 may store at least one packet such as an erase packet that includes information including a reference to the object, relationship to the object, and the size of the data block erased. Additionally, it may further indicate that the erased object elements are filled with zeros.
  • the erase object request can be used to emulate actual memory or storage that is erased and actually has a portion of the appropriate memory/storage actually stored with zeros in the cells of the memory/storage.
  • creating an object index with entries indicating mapping between data segments and metadata of an object allows the storage controller 152 to autonomously handle and manage objects. This capability allows a great amount of flexibility for storing data in the storage device 150. Once the index entry for the object is created, subsequent object requests regarding the object can be serviced efficiently by the storage controller 152.
  • the storage controller 152 includes an object request queuing module that queues one or more object requests received by the object request receiver module 260 prior to parsing by the parsing module 262.
  • the object request queuing module 268 allows flexibility between when an object request is received and when it is executed.
  • the storage controller 152 includes a packetizer 302 that creates one or more data packets from the one or more data segments where the data packets are sized for storage in the data storage device 154.
  • the packetizer 302 is described below in more detail with respect to Figure 3.
  • the packetizer 302 includes, in one embodiment, a messages module 270 that creates a header for each packet.
  • the header includes a packet identifier and a packet length.
  • the packet identifier relates the packet to the object for which the packet was formed.
  • each packet includes a packet identifier that is self-contained in that the packet identifier contains adequate information to identify the object and relationship within the object of the object elements contained within the packet.
  • a more efficient preferred embodiment is to store packets in containers.
  • a container is a data construct that facilitates more efficient storage of packets and helps establish relationships between an object and data packets, metadata packets, and other packets related to the object that are stored within the container.
  • the storage controller 152 typically treats object metadata received as part of an object and data segments in a similar manner.
  • packet may refer to a data packet comprising data, a metadata packet comprising metadata, or another packet of another packet type.
  • An object may be stored in one or more containers and a container typically includes packets for no more than one unique object.
  • An object may be distributed between multiple containers.
  • a container is stored within a single logical erase block (storage division) and is typically never split between logical erase blocks.
  • a container in one example, may be split between two or more logical/virtual pages.
  • a container is identified by a container label that associates that container with an object.
  • a container may contain zero to many packets and the packets within a container are typically from one object.
  • a packet may be of many object element types, including object attribute elements, object data elements, object index elements, and the like. Hybrid packets may be created that include more than one object element type. Each packet may contain zero to many elements of the same element type.
  • Each packet within a container typically contains a unique identifier that identifies the relationship to the object.
  • Each packet is associated with one container.
  • containers are limited to an erase block so that at or near the beginning of each erase block a container packet can be found. This helps limit data loss to an erase block with a corrupted packet header.
  • the object index is unavailable and a packet header within the erase block is corrupted, the contents from the corrupted packet header to the end of the erase block may be lost because there is possibly no reliable mechanism to determine the location of subsequent packets.
  • a more reliable approach is to have a container limited to a page boundary. This embodiment requires more header overhead.
  • containers can flow across page and erase block boundaries. This requires less header overhead but a larger portion of data may be lost if a packet header is corrupted. For these several embodiments it is expected that some type of RAID is used to further ensure data integrity.
  • the apparatus 200 includes an object index reconstruction module 272 that that reconstructs the entries in the object index using information from packet headers stored in the data storage device 154.
  • the object index reconstruction module 272 reconstructs the entries of the object index by reading headers to determine the object to which each packet belongs and sequence information to determine where in the object the data or metadata belongs.
  • the object index reconstruction module 272 uses physical address information for each packet and timestamp or sequence information to create a mapping between the physical locations of the packets and the object identifier and data segment sequence. Timestamp or sequence information is used by the object index reconstruction module 272 to replay the sequence of changes made to the index and thereby typically reestablish the most recent state.
  • the object index reconstruction module 272 locates packets using packet header information along with container packet information to identify physical locations of the packets, object identifier, and sequence number of each packet to reconstruct entries in the object index.
  • erase blocks are time stamped or given a sequence number as packets are written and the timestamp or sequence information of an erase block is used along with information gathered from container headers and packet headers to reconstruct the object index.
  • timestamp or sequence information is written to an erase block when the erase block is recovered.
  • the object index reconstruction module 272 allows the object index to be stored in volatile memory allowing the advantages of volatile memory, such as fast access.
  • the object index reconstruction module 272 allows quick reconstruction of the object index autonomously without dependence on a device external to the storage device 150.
  • the object index in volatile memory is stored periodically in a data storage device 154.
  • the object index, or "index metadata,” is stored periodically in a solid-state storage 110.
  • the index metadata is stored in a solid-state storage HOn separate from solid-state storage l lOa-i lOn-1 storing packets.
  • the index metadata is managed independently from data and object metadata transmitted from a requesting device 155 and managed by the storage controller 152/solid-state storage device controller 202. Managing and storing index metadata separate from other data and metadata from an object allows efficient data flow without the storage controller 152/solid-state storage device controller 202 unnecessarily processing object metadata.
  • the storage controller 152 receives one or more data segments of an object from memory of a requesting device 155 as a local or remote direct memory access (“DMA," "RDMA") operation.
  • the storage controller 152 pulls data from the memory of the requesting device 155 in one or more DMA or RDMA operations.
  • the requesting device 155 pushes the data segment(s) to the storage controller 152 in one or more DMA or RDMA operations.
  • the storage controller 152 transmits one or more data segments of an object to the memory of the requesting device 155 in one or more DMA or RDMA operations.
  • the storage controller 152 pushes data to the memory of the requesting device 155 in one or more DMA or RDMA operations.
  • the requesting device 155 pulls data from the storage controller 152 in one or more DMA or RDMA operations.
  • the storage controller 152 pulls object command request sets from the memory of the requesting device 155 in one or more DMA or RDMA operations.
  • the requesting device 155 pushes object command request sets to the storage controller 152 in one or more DMA or RDMA operations.
  • the storage controller 152 emulates block storage and an object communicated between the requesting device 155 and the storage controller 152 comprises one or more data blocks.
  • the requesting device 155 includes a driver so that the storage device 150 appears as a block storage device.
  • the requesting device 152 may send a block of data of a certain size along with a physical address of where the requesting device 155 wants the data block stored.
  • the storage controller 152 receives the data block and uses the physical block address transmitted with the data block or a transformation of the physical block address as an object identifier.
  • the storage controller 156 then stores the data block as an object or data segment of an object by packetizing the data block and storing the data block at will.
  • the object index module 266 then creates an entry in the object index using the physical block-based object identifier and the actual physical location where the storage controller 152 stored the data packets comprising the data from the data block.
  • the storage controller 152 emulates block storage by accepting block objects.
  • a block object may include one or more data blocks in a block structure.
  • the storage controller 152 treats the block object as any other object.
  • an object may represent an entire block device, partition of a block device, or some other logical or physical sub-element of a block device including a track, sector, channel, and the like.
  • an object may represent an entire block device, partition of a block device, or some other logical or physical sub-element of a block device including a track, sector, channel, and the like.
  • RAID group an object supporting a different RAID construction such as progressive RAID.
  • One skilled in the art will recognize other mappings of traditional or future block devices to objects.
  • FIG. 2B is a schematic block diagram illustrating one embodiment 201 of a solid-state storage device controller 202 that includes a write data pipeline 106 and a read data pipeline 108 in a solid-state storage device 102 in accordance with the present invention.
  • the solid-state storage device controller 202 may include a number of solid-state storage controllers 0-N 104a-n, each controlling solid-state storage 110.
  • solid-state controller 0 104a and solid-state storage controller N 104n two solid-state controllers are shown: solid-state controller 0 104a and solid-state storage controller N 104n, and each controls solid-state storage 110a-n.
  • solid-state storage controller 0 104a controls a data channel so that the attached solid-state storage 110a stores data.
  • Solid-state storage controller N 104n controls an index metadata channel associated with the stored data and the associated solid-state storage 11On stores index metadata.
  • the solid-state storage device controller 202 includes a single solid-state controller 104a with a single solid-state storage 110a.
  • At least one solid-state controller 104 is field-programmable gate array ("FPGA") and controller functions are programmed into the FPGA.
  • the FPGA is a Xilinx® FPGA.
  • the solid-state storage controller 104 comprises components specifically designed as a solid-state storage controller 104, such as an application-specific integrated circuit ("ASIC") or custom logic solution.
  • ASIC application-specific integrated circuit
  • Each solid-state storage controller 104 typically includes a write data pipeline 106 and a read data pipeline 108, which are describe further in relation to Figure 3.
  • at least one solid-state storage controller 104 is made up of a combination FPGA, ASIC, and custom logic components.
  • the solid state storage 110 is an array of non- volatile solid-state storage elements 216, 218, 220, arranged in banks 214, and accessed in parallel through a bi-directional storage input/output ("I/O") bus 210.
  • the storage I/O bus 210 in one embodiment, is capable of unidirectional communication at any one time. For example, when data is being written to the solid-state storage 110, data cannot be read from the solid-state storage 110. In another embodiment, data can flow both directions simultaneously.
  • bi-directional as used herein with respect to a data bus, refers to a data pathway that can have data flowing in only one direction at a time, but when data flowing one direction on the bi-directional data bus is stopped, data can flow in the opposite direction on the bi-directional data bus.
  • a solid-state storage element (e.g. SSS 0.0 216a) is typically configured as a chip (a package of one or more dies) or a die on a circuit board. As depicted, a solid-state storage element (e.g. 216a) operates independently or semi-independently of other solid-state storage elements (e.g. 218a) even if these several elements are packaged together in a chip package, a stack of chip packages, or some other package element. As depicted, a column of solid-state storage elements 216, 218, 220 is designated as a bank 214.
  • a solid-state storage HOa includes twenty solid-state storage elements 216, 218, 220 per bank 214 with eight banks 214 and a solid-state storage 11On includes 2 solid-state storage elements 216, 218 per bank 214 with one bank 214.
  • each solid-state storage element 216, 218, 220 is comprised of a single-level cell (“SIX:”) devices.
  • SIX: single-level cell
  • each solid-state storage element 216, 218, 220 is comprised of multi-level cell (“MLC”) devices.
  • solid-state storage elements for multiple banks that share a common storage I/O bus 210a row are packaged together.
  • a solid-state storage element 216, 218, 220 may have one or more dies per chip with one or more chips stacked vertically and each die may be accessed independently.
  • a solid-state storage element e.g. SSS 0.0216a
  • SSS 0.0 216a may have one or more virtual dies per die and one or more dies per chip and one or more chips stacked vertically and each virtual die may be accessed independently.
  • a solid-state storage element SSS 0.0 216a may have one or more virtual dies per die and one or more dies per chip with some or all of the one or more dies stacked vertically and each virtual die may be accessed independently.
  • two dies are stacked vertically with four stacks per group to form eight storage elements (e.g. SSS O.O-SSS 0.8) 216a-220a, each in a separate bank 214a-n.
  • 20 storage elements (e.g. SSS O.O-SSS 20.0) 216 form a virtual bank 214a so that each of the eight virtual banks has 20 storage elements (e.g. SSSO.O-SSS 20.8) 216, 218, 220.
  • Data is sent to the solid-state storage 110 over the storage I/O bus 210 to all storage elements of a particular group of storage elements (SSS O.O-SSS 0.8) 216a, 218a, 220a.
  • the storage control bus 212a is used to select a particular bank (e.g. Bank-0 214a) so that the data received over the storage I/O bus 210 connected to all banks 214 is written just to the selected bank 214a.
  • the storage I/O bus 210 is comprised of one or more independent I/O buses (" ⁇ OBa-m" comprising 210a.a-m, 210n.a-m) wherein the solid-state storage elements within each row share one of the independent I/O buses accesses each solid- state storage element 216, 218, 220 in parallel so that all banks 214 are accessed simultaneously.
  • ⁇ OBa-m independent I/O buses
  • one channel of the storage I/O bus 210 may access a first solid-state storage element 216a, 218a, 220a of each bank 214a-n simultaneously.
  • a second channel of the storage I/O bus 210 may access a second solid-state storage element 216b, 218b, 220b of each bank 214a-n simultaneously.
  • Each row of solid-state storage element 216, 218, 220 is accessed simultaneously.
  • solid-state storage elements 216, 218, 220 are multi- level (physically stacked)
  • all physical levels of the solid-state storage elements 216, 218, 220 are accessed simultaneously.
  • "simultaneously” also includes near simultaneous access where devices are accessed at slightly different intervals to avoid switching noise. Simultaneously is used in this context to be distinguished from a sequential or serial access wherein commands and/or data are sent individually one after the other.
  • banks 214a-n are independently selected using the storage control bus 212.
  • a bank 214 is selected using a chip enable or chip select.
  • the storage control bus 212 may select one level of a multilevel solid-state storage element 216, 218, 220. In other embodiments, other commands are used 5 by the storage control bus 212 to individually select one level of a multi-level solid-state storage element 216, 218, 220. Solid-state storage elements 216, 218, 220 may also be selected through a combination of control and of address information transmitted on storage I/O bus 210 and the storage control bus 212.
  • each solid-state storage element 216, 218, 220 is partitioned into0 erase blocks and each erase block is partitioned into pages.
  • a typical page is 2000 bytes
  • a solid-state storage element (e.g. SSSO.O) includes two registers and can program two pages so that a two-register solid-state storage element 216, 218, 220 has a capacity of 4kB.
  • a bank 214 of 20 solid-state storage elements 216, 218, 220 would then have an 8OkB capacity of pages accessed with the same address going out the channels of the storage5 I/O bus 210.
  • This group of pages in a bank 214 of solid-state storage elements 216, 218, 220 of 8OkB may be called a virtual page.
  • an erase block of each storage element 216a-m of a bank 214a may be grouped to form a virtual erase block.
  • an erase block of ' pages within a solid-state storage element 216, 218, 220 is erased when an erase command is ⁇ 0 received within a solid-state storage element 216, 218, 220.
  • the physical address contains enough information for the solid-state storage element 216, 218,0 220 to direct the packet to the designated location within the page. Since all storage elements in a row of storage elements (e.g. SSS 0.0-SSS 0.N 216a, 218a, 220a) are accessed simultaneously by the appropriate bus within the storage I/O bus 210a.a, to reach the proper page and to avoid writing the data packet to similarly addressed pages in the row of storage elements (SSS 0.0-SSS 0.N 216a, 218a, 220a), the bank 214a that includes the solid-state storage element SSS 0.0 216a with the correct page where the data packet is to be written is simultaneously selected by the storage control bus 212.
  • SSS 0.0-SSS 0.N 216a, 218a, 220a the bank 214a that includes the solid-state storage element SSS 0.0 216a with the correct page where the data packet is to be written is simultaneously selected by the storage control bus 212.
  • a read command traveling on the storage I/O bus 212 requires a simultaneous command on the storage control bus 212 to select a single bank 214a and the appropriate page within that bank 214a.
  • a read command reads an entire page, and because there are multiple solid-state storage elements 216, 218, 220 in parallel in a bank 214, an entire virtual page is read with a read command.
  • the read command may be broken into subcommands, as will be explained below with respect to bank interleave.
  • a virtual page may also be accessed in a write operation.
  • An erase block erase command may be sent out to erase an erase block over the storage
  • I/O bus 210 with a particular erase block address to erase a particular erase block.
  • an erase block erase command may be sent over the parallel paths of the storage I/O bus 210 to erase a virtual erase block, each with a particular erase block address to erase a particular erase block.
  • a particular bank e.g. bank-0 214a
  • Other commands may also be sent to a particular location using a combination of the storage I/O bus 210 and the storage control bus 212.
  • packets are written sequentially to the solid-state storage 110. For example, packets are streamed to the storage write buffers of a bank 214a of storage elements 216 and when the buffers are full, the packets are programmed to a designated virtual page. Packets then refill the storage write buffers and, when full, the packets are written to the next virtual page. The next virtual page may be in the same bank 214a or another bank (e.g. 214b). This process continues, virtual page after virtual page, typically until a virtual erase block is filled. In another embodiment, the streaming may continue across virtual erase block boundaries with the process continuing, virtual erase block after virtual erase block.
  • data packets associated with the object are located and read in a read operation.
  • Data segments of the modified object that have been modified are not written to the location from which they are read. Instead, the modified data segments are again converted to data packets and then written to the next available location in the virtual page currently being written.
  • the object index entries for the respective data packets are modified to point to the packets that contain the modified data segments.
  • the entry or entries in the object index for data packets associated with the same object that have not been modified will include pointers to original location of the unmodified data packets.
  • the original object will have pointers in the object index to all data packets as originally written.
  • the new object will have pointers in the object index to some of the original data packets and pointers to the modified data packets in the virtual page that is currently being written.
  • the object index includes an entry for the original object mapped to a number of packets stored in the solid-state storage 110.
  • a new object is created and a new entry is created in the object index mapping the new object to the original packets.
  • the new object is also written to the solid-state storage 110 with its location mapped to the new entry. in the object index.
  • the new object packets may be used to identify the packets within the original object that are referenced in case changes have been made in the original object that have not been propagated to the copy and the object index is lost or corrupted.
  • sequentially writing packets facilitates a more even use of the solid-state storage 110 and allows the solid-storage device controller 202 to monitor storage hot spots and level usage of the various virtual pages in the solid-state storage 110. Sequentially writing packets also facilitates a powerful, efficient garbage collection system, which is described in detail below. One of skill in the art will recognize other benefits of sequential storage of data packets.
  • the solid-state storage device controller 202 also includes a data bus 204, a local bus 206, a buffer controller 208, buffers 0-N 222a-n, a master controller 224, a direct memory access (“DMA") controller 226, a memory controller 228, a dynamic memory array 230, a static random memory array 232, a management controller 234, a management bus 236, a bridge 238 to a system bus 240, and miscellaneous logic 242, which are described below.
  • DMA direct memory access
  • the system bus 240 is coupled to one or more network interface cards (“NICs”) 244, some of which may include remote DMA (“RDMA”) controllers 246, one or more central processing unit (“CPU”) 248, one or more external memory controllers 250 and associated external memory arrays 252, one or more storage controllers 254, peer controllers 256, and application specific processors 258, which are described below.
  • NICs network interface cards
  • RDMA remote DMA
  • CPU central processing unit
  • external memory controllers 250 and associated external memory arrays 252 one or more storage controllers 254, peer controllers 256, and application specific processors 258, which are described below.
  • the components 244- 258 connected to the system bus 240 may be located in the computer 112 or may be other devices.
  • the solid-state storage controller(s) 104 communicate data to the solid-state storage 1 10 over a storage I/O bus 210.
  • the storage I/O bus 210 is an array of busses, one for each row of storage elements 216, 218, 220 spanning the banks 214.
  • the term "storage I/O bus” may refer to one storage I/O bus 210 or an array of data independent busses 204.
  • each storage I/O bus 210 accessing a row of storage elements (e.g.
  • 216a, 218a, 220a may include a logical-to-physical mapping for storage divisions (e.g. erase blocks) accessed in a row of storage elements 216a, 218a, 220a.
  • This mapping allows a logical address mapped to a physical address of a storage division to be remapped to a different storage division if the first storage division fails, partially fails, is inaccessible, or has some other problem. Remapping is explained further in relation to the remapping module 314 of Figure 3.
  • Data may also be communicated to the solid-state storage controller(s) 104 from a requesting device 155 through the system bus 240, bridge 238, local bus 206, buffer(s) 22, and finally over a data bus 204.
  • the data bus 204 typically is connected to one or more buffers 222a- n controlled with a buffer controller 208.
  • the buffer controller 208 typically controls transfer of data from the local bus 206 to the buffers 222 and through the data bus 204 to the pipeline input buffer 306 and output buffer 330 .
  • the buffer controller 222 typically controls how data arriving from a requesting device can be temporarily stored in a buffer 222 and then transferred onto a data bus 204, or vice versa, to account for different clock domains, to prevent data collisions, etc.
  • the buffer controller 208 typically works in conjunction with the master controller 224 to coordinate data flow. As data arrives, the data will arrive on the system bus 240, be transferred to the local bus 206 through a bridge 238.
  • the data is transferred from the local bus 206 to one or more data buffers 222 as directed by the master controller 224 and the buffer controller 208.
  • the data then flows out of the buffer(s) 222 to the data bus 204, through a solid-state controller 104, and on to the solid- state storage 110 such as NAND flash or other storage media.
  • data and associated out-of-band metadata (“object metadata”) arriving with the data is communicated using one or more data channels comprising one or more solid-state storage controllers 104a- 104n-l and associated solid-state storage 11 Oa- 11 On-I while at least one channel (solid-state storage controller 104n, solid-state storage 11 On) is dedicated to in-band metadata, such as index information and other metadata generated internally to the solid-state storage device 102.
  • the local bus 206 is typically a bidirectional bus or set of busses that allows for communication of data and commands between devices internal to the solid-state storage device controller 202 and between devices internal to the solid-state storage device 102 and devices 244-258 connected to the system bus 240.
  • the bridge 238 facilitates communication between the local bus 206 and system bus 240.
  • One of skill in the art will recognize other embodiments such as ring structures or switched star configurations and functions of buses 240, 206, 204, 210 and bridges 238.
  • the system bus 240 is typically a bus of a computer 112 or other device in which the solid-state storage device 102 is installed or connected.
  • the system bus 240 may be a PCI-e bus, a Serial Advanced Technology Attachment ("serial ATA") bus, parallel ATA, or the like.
  • the system bus 240 is an external bus such as small computer system interface ("SCSI"), FireWire, Fiber Channel, USB, PCIe-AS, or the like.
  • the solid-state storage device 102 may be packaged to fit internally to a device or as an externally connected device.
  • the solid-state storage device controller 202 includes a master controller 224 that controls higher-level functions within the solid-state storage device 102.
  • the master controller 224 controls data flow by interpreting object requests and other requests, directs creation of indexes to map object identifiers associated with data to physical locations of associated data, coordinating DMA requests, etc. Many of the functions described herein are controlled wholly or in part by the master controller 224.
  • the master controller 224 uses embedded controller(s). In another embodiment, the master controller 224 uses local memory such as a dynamic memory array 230 (dynamic random access memory "DRAM"), a static memory array 323 (static random access memory “SRAM”), etc. In one embodiment, the local memory is controlled using the master controller 224. In another embodiment, the master controller accesses the local memory via a memory controller 228. In another embodiment, the master controller runs a Linux server and may support various common server interfaces, such as the World Wide Web, hyper-text markup language (“HTML”), etc. In another embodiment, the master controller 224 uses a nano- processor. The master controller 224 may be constructed using programmable or standard logic, or any combination of controller types listed above. One skilled in the art will recognize many embodiments for the master controller.
  • DRAM dynamic random access memory
  • SRAM static memory array 323
  • the local memory is controlled using the master controller 224.
  • the master controller accesses the local memory via a memory controller 228.
  • the master controller runs a Linux
  • the master controller 224 divides the work load among internal controllers, such as the solid-state storage controllers 104a- n.
  • the master controller 224 may divide an object to be written to the data storage devices (e.g. solid-state storage 110a-n) so that a portion of the object is stored on each of the attached data storage devices. This feature is a performance enhancement allowing quicker storage and access to an object.
  • the master controller 224 is implemented using an FPGA.
  • the firmware within the master controller 224 may be updated through the management bus 236, the system bus 240 over a network connected to a NIC 244 or other device connected to the system bus 240.
  • the master controller 224 which manages objects, emulates block storage such that a computer 102 or other device connected to the storage device 152/solid-state storage device 102 views the storage device 152/solid-state storage device 102 as a block storage device and sends data to specific physical addresses in the storage device 152/solid-state storage device 102.
  • the master controller 224 then divides up the blocks and stores the data blocks as it would objects.
  • the master controller 224 then maps the blocks and physical address sent with the block to the actual locations determined by the master controller 224. The mapping is stored in the object index.
  • a block device application program interface is provided in a driver in the computer 112, client 114, or other device wishing to use the storage device 152/solid-state storage device 102 as a block storage device.
  • API block device application program interface
  • the master controller 224 coordinates with NIC controllers 244 and embedded RDMA controllers 246 to deliver just-in-time RDMA transfers of data and command sets.
  • NIC controller 244 may be hidden behind a non-transparent port to enable the use of custom drivers.
  • a driver on a client 114 may have access to the computer network 118 through an I/O memory driver using a standard stack API and operating in conjunction with NICs 244.
  • the master controller 224 is also a redundant array of independent drive (“RAID") controller. Where the data storage device/solid-state storage device 102 is networked with one or more other data storage devices/solid-state storage devices 102, the master controller 224 may be a RAID controller for single tier RAID, multi-tier RAID, progressive RAID, etc. The master controller 224 also allows some objects to be stored in a RAID array and other objects to be stored without RAID. In another embodiment, the master controller 224 may be a distributed RAID controller element. In another embodiment, the master controller 224 may comprise many RAID, distributed RAID, and other functions as described elsewhere.
  • RAID redundant array of independent drive
  • the master controller 224 coordinates with single or redundant network managers (e.g. switches) to establish routing, to balance bandwidth utilization, failover, etc.
  • the master controller 224 coordinates with integrated application specific logic (via local bus 206) and associated driver software.
  • the master controller 224 coordinates with attached application specific processors 258 or logic (via the external system bus 240) and associated driver software.
  • the master controller 224 coordinates with remote application specific logic (via the computer network 118) and associated driver software.
  • the master controller 224 coordinates with the local bus 206 or external bus attached hard disk drive (“HDD”) storage controller.
  • HDD hard disk drive
  • the master controller 224 communicates with one or more storage controllers 254 where the storage device/solid-state storage device 102 may appear as a storage device connected through a SCSI bus, Internet SCSI ("iSCSI"), fiber channel, etc. Meanwhile the storage device/solid-state storage device 102 may autonomously manage objects and may appear as an object file system or distributed object file system.
  • the master controller 224 may also be accessed by peer controllers 256 and/or application specific processors 258.
  • the master controller 224 coordinates with an autonomous integrated management controller to periodically validate FPGA code and/or controller software, validate FPGA code while running (reset) and/or validate controller software during power on (reset), support external reset requests, support reset requests due to watchdog timeouts, and support voltage, current, power, temperature, and other environmental measurements and setting of threshold interrupts.
  • the master controller 224 manages garbage collection to free erase blocks for reuse.
  • the master controller 224 manages wear leveling.
  • the master controller 224 allows the data storage device/solid-state storage device 102 to be partitioned into multiple virtual devices and allows partition-based media encryption.
  • the master controller 224 supports a solid-state storage controller 104 with advanced, multi-bit ECC correction.
  • a master controller 224 in a storage controller 152, or more specifically in a solid-state storage device 102.
  • the solid-state storage device controller 202 includes a memory controller 228 which controls a dynamic random memory array 230 and/or a static random memory array 232.
  • the memory controller 228 may be independent or integrated with the master controller 224.
  • the memory controller 228 typically controls volatile memory of some type, such as DRAM (dynamic random memory array 230) and SRAM (static random memory array 232).
  • the memory controller 228 also controls other memory types such as electrically erasable programmable read only memory (“EEPROM”), etc.
  • EEPROM electrically erasable programmable read only memory
  • the memory controller 228 controls two or more memory types and the memory controller 228 may include more than one controller.
  • the memory controller 228 controls as much SRAM 232 as is feasible and by DRAM 230 to supplement the SRAM 232.
  • the object index is stored in memory 230, 232 and then periodically off-loaded to a channel of the solid-state storage 11On or other non- volatile memory.
  • the memory controller 228, dynamic memory array 230, and static memory array 232 are examples of the memory controller 228, dynamic memory array 230, and static memory array 232.
  • the solid-state storage device controller 202 includes a DMA controller 226 that controls DMA operations between the storage device/solid-state storage device 102 and one or more external memory controllers 250 and associated external memory arrays 252 and CPUs 248.
  • the external memory controllers 250 and external memory arrays 252 are called external because they are external to the storage device/solid-state storage device 102.
  • the DMA controller 226 may also control RDMA operations with requesting devices through a NIC 244 and associated RDMA controller 246. DMA and RDMA are explained in more detail below.
  • the solid-state storage device controller 202 includes a management controller 234 connected to a management bus 236.
  • the management controller 234 manages environmental metrics and status of the storage device/solid-state storage device 102.
  • the management controller 234 may monitor device temperature, fan speed, power supply settings, etc. over the management bus 236.
  • the management controller may support the reading and programming of erasable programmable read only memory ("EEPROM”) for storage of FPGA code and controller software.
  • EEPROM erasable programmable read only memory
  • the management bus 236 is connected to the various components within the storage device/solid-state storage device 102.
  • the management controller 234 may communicate alerts, interrupts, etc. over the local bus 206 or may include a separate connection to a system bus 240 or other bus.
  • the management bus 236 is an Inter-Integrated Circuit ("I 2 C") bus.
  • I 2 C Inter-Integrated Circuit
  • the solid-state storage device controller 202 includes miscellaneous logic 242 that may be customized for a specific application. Typically where the solid-state device controller 202 or master controller 224 is/are configured using a FPGA or other configurable controller, custom logic may be included based on a particular application, customer requirement, storage requirement, etc.
  • DATA PIPELINE Figure 3 is a schematic block diagram illustrating one embodiment 300 of a solid-state storage controller 104 with a write data pipeline 106 and a read data pipeline 108 in a solid-state storage device 102 in accordance with the present invention.
  • the embodiment 300 includes a data bus 204, a local bus 206, and buffer control 208, which are substantially similar to those described in relation to the solid-state storage device controller 202 of Figure 2.
  • the write data pipeline includes a packetizer 302 and an error-correcting code (“ECC”) generator 304.
  • ECC error-correcting code
  • the write data pipeline includes an input buffer 306, a write synchronization buffer
  • the read data pipeline 108 includes a read synchronization buffer 328, an ECC correction module 322, a depacketizer 324, an alignment module 326, and an output buffer 330.
  • the read data pipeline 108 may include a media decryption module 332, a portion of the garbage collector bypass 316, a decryption module 334, a decompression module 336, and a read program module 338.
  • the solid-state storage controller 104 may also include control and status registers 340 and control queues 342, a bank interleave controller 344, a synchronization buffer 346, a storage bus controller 348, and a multiplexer ("MUX") 350.
  • the components of the solid-state controller 104 and associated write data pipeline 106 and read data pipeline 108 are described below.
  • synchronous solid-state storage 110 may be used and synchronization buffers 308 328 may be eliminated.
  • the write data pipeline 106 includes a packetizer 302 that receives a data or metadata segment to be written to the solid-state storage, either directly or indirectly through another write data pipeline 106 stage, and creates one or more packets sized for the solid-state storage 110.
  • the data or metadata segment is typically part of an object, but may also include an entire object. In another embodiment, the data segment is part of a block of data, but may also include an entire block of data.
  • an object is received from a computer 112, client 114, or other computer or device and is transmitted to the solid-state storage device 102 in data segments streamed to the solid-state storage device 102 or computer 112.
  • a data segment may also be known by another name, such as data parcel, but as referenced herein includes all or a portion of an object or data block.
  • Each object is stored as one or more packets.
  • Each object may have one or more container packets.
  • Each packet contains a header.
  • the header may include a header type field. Type fields may include data, object attribute, metadata, data segment delimiters (multi-packet), object structures, object linkages, and the like.
  • the header may also include information regarding the size of the packet, such as the number of bytes of data included in the packet. The length of the packet may be established by the packet type.
  • the header may include information that establishes the relationship of the packet to the object. An example might be the use of an offset in a data packet header to identify the location of the data segment within the object.
  • One of skill in the art will recognize other information that may be included in a header added to data by a packetizer 302 and other information that may be added to a data packet.
  • Each packet includes a header and possibly data from the data or metadata segment.
  • the header of each packet includes pertinent information to relate the packet to the object to which the packet belongs.
  • the header may include an object identifier and offset that indicates the data segment, object, or data block from which the data packet was formed.
  • the header may also include a logical address used by the storage bus controller 348 to store the packet.
  • the header may also include information regarding the size of the packet, such as the number of bytes included in the packet.
  • the header may also include a sequence number that identifies where the data segment belongs with respect to other packets within the object when reconstructing the data segment or object.
  • the header may include a header type field.
  • Type fields may include data, object attributes, metadata, data segment delimiters (multi-packet), object structures, object linkages, and the like.
  • data segment delimiters multi-packet
  • object structures object linkages, and the like.
  • packetizer 302 One of skill in the art will recognize other information that may be included in a header added to data or metadata by a packetizer 302 and other information that may be added to a packet.
  • the write data pipeline 106 includes an ECC generator 304 that generates one or more error-correcting codes ("ECC") for the one or more packets received from the packetizer 302.
  • ECC error-correcting codes
  • the ECC generator 304 typically uses an error correcting algorithm to generate ECC which is stored with the packet.
  • the ECC stored with the packet is typically used to detect and correct errors introduced into the data through transmission and storage.
  • packets are streamed into the ECC generator 304 as un-encoded blocks of length N.
  • a syndrome of length S is calculated, appended and output as an encoded block of length N+S.
  • the value of N and S are dependent upon the characteristics of the algorithm which is selected to achieve specific performance, efficiency, and robustness metrics.
  • the packet may comprise more than one ECC block; the ECC block may comprise more than one packet; and a first packet may end anywhere within the ECC block and a second packet may begin after the end of the first packet within the same ECC block.
  • ECC algorithms are not dynamically modified.
  • the ECC stored with the data packets is robust enough to correct errors in more than two bits.
  • the solid-state storage 110 may comprise less reliable storage such as multi-level cell (“MLC”) flash in order to increase capacity, which storage may not be sufficiently reliable without more robust ECC algorithms.
  • MLC multi-level cell
  • the write pipeline 106 includes an input buffer 306 that receives a data segment to be written to the solid-state storage 110 and stores the incoming data segments until the next stage of the write data pipeline 106, such as the packetizer 302 (or other stage for a more complex write data pipeline 106) is ready to process the next data segment.
  • the input buffer 306 typically allows for discrepancies between the rate data segments are received and processed by the write data pipeline 106 using an appropriately sized data buffer.
  • the input buffer 306 also allows the data bus 204 to transfer data to the write data pipeline 106 at rates greater than can be sustained by the write data pipeline 106 in order to improve efficiency of operation of the data bus 204.
  • a buffering function is performed elsewhere, such as in the solid-state storage device 102 but outside the write data pipeline 106, in the computer 112, such as within a network interface card (“NIC”), or at another device, for example when using remote direct memory access (“RDMA").
  • NIC network interface card
  • RDMA remote direct memory access
  • the write data pipeline 106 also includes a write synchronization buffer 308 that buffers packets received from the ECC generator 304 prior to writing the packets to the solid-state storage 110.
  • the write synch buffer 308 is located at a boundary between a local clock domain and a solid-state storage clock domain and provides buffering to account for the clock domain differences.
  • synchronous solid-state storage 110 may be used and synchronization buffers 308 328 may be eliminated.
  • the write data pipeline 106 also includes a media encryption module 318 that receives the one or more packets from the packetizer 302, either directly or indirectly, and encrypts the one or more packets using an encryption key unique to the solid-state storage device 102 prior to sending the packets to the ECC generator 304.
  • the entire packet is encrypted, including the headers.
  • headers are not encrypted.
  • encryption key is understood to mean a secret encryption key that is managed externally from an embodiment that integrates the solid-state storage 110 and where the embodiment requires encryption protection.
  • the media encryption module 318 and corresponding media decryption. module 332 provide a level of security for data stored in the solid-state storage 110.
  • solid-state storage 110 is connected to a different solid-state storag ' e controller 104, solid-state storage device 102, or computer 112
  • the contents of the solid-state storage 110 typically could not be read without use of the same encryption key used during the write of the data to the solid-state storage 110 without significant effort.
  • the solid-state storage device 102 does not store the encryption key in non-volatile storage and allows no external access to the encryption key.
  • the encryption key is provided to the solid-state storage controller 104 during initialization.
  • the solid-sate storage device 102 may use and store a non-secret cryptographic nonce that is used in conjunction with an encryption key. A different nonce may be stored with every packet. Data segments may be split between multiple packets with unique nonces for the purpose of improving protection by the encryption algorithm.
  • the encryption key may be received from a client 114, a computer 112, key manager, or other device that manages the encryption key to be used by the solid-state storage controller 104.
  • the solid-state storage 110 may have two or more partitions and the solid-state storage controller 104 behaves as though it were two or more solid-state storage controllers 104, each operating on a single partition within the solid-state storage 110.
  • a unique media encryption key may be used with each partition.
  • the write data pipeline 106 also includes an encryption module 314 that encrypts a data or metadata segment received from the input buffer 306, either directly or indirectly, prior sending the data segment to the packetizer 302, the data segment encrypted using an encryption key received in conjunction with the data segment.
  • the encryption module 314 differs from the media encryption module 318 in that the encryption keys used by the encryption module 318 to encrypt data may not be common to all data stored within the solid- state storage device 102 but may vary on an object basis and received in conjunction with receiving data segments as described below. For example, an encryption key for a data segment to be encrypted by the encryption module 318 may be received with the data segment or may be received as part of a command to write an object to which the data segment belongs.
  • the solid- sate storage device 102 may use and store a non-secret cryptographic nonce in each object packet that is used in conjunction with the encryption key.
  • a different nonce may be stored with every packet.
  • Data segments may be split between multiple packets with unique nonces for the purpose of improving protection by the encryption algorithm.
  • the nonce used by the media encryption module 318 is the same as that used by the encryption module 314.
  • the encryption key may be received from a client 114, a computer 112, key manager, or other device that holds the encryption key to be used to encrypt the data segment.
  • encryption keys are transferred to the solid-state storage controller 104 from one of a solid-state storage device 102, computer 1 12, client 114, or other external agent which has the ability to execute industry standard methods to securely transfer and protect private and public keys.
  • the encryption module 318 encrypts a first packet with a first encryption key received in conjunction with the packet and encrypts a second packet with a second encryption key received in conjunction with the second packet. In another embodiment, the encryption module 318 encrypts a first packet with a first encryption key received in conjunction with the packet and passes a second data packet on to the next stage without encryption. Beneficially, the encryption module 318 included in the write data pipeline 106 of the solid-state storage device 102 allows object-by-object or segment-by-segment data encryption without a single file system or other external system to keep track of the different encryption keys used to store corresponding objects or data segments.
  • the write data pipeline 106 includes a compression module 312 that compresses the data for metadata segment prior to sending the data segment to the packetizer 302.
  • the compression module 312 typically compresses a data or metadata segment using a compression routine known to those of skill in the art to reduce the storage size of the segment. For example, if a data segment includes a string of 512 zeros, the compression module 312 may replace the 512 zeros with code or token indicating the 512 zeros where the code is much more compact than the space taken by the 512 zeros.
  • the compression module 312 compresses a first segment with a first compression routine and passes along a second segment without compression. In another embodiment, the compression module 312 compresses a first segment with a first compression routine and compresses the second segment with a second compression routine. Having this flexibility within the solid-state storage device 102 is beneficial so that clients 114 or other devices writing data to the solid-state storage device 102 may each specify a compression routine or so that one can specify a compression routine while another specifies no compression. Selection of compression routines may also be selected according to default settings on a per object type or object class basis.
  • the write data pipeline 106 includes a garbage collector bypass 316 that receives data segments from the read data pipeline 108 as part of a data bypass in a garbage collection system.
  • a garbage collection system typically marks packets that are no longer valid, typically because the packet is marked for deletion or has been modified and the modified data is stored in a different location. At some point, the garbage collection system determines that a particular section of storage may be recovered.
  • This determination may be due to a lack of available storage capacity, the percentage of data marked as invalid reaching a threshold, a consolidation of valid data, an error detection rate for that section of storage reaching a threshold, or improving performance based on data distribution, etc. Numerous factors may be considered by a garbage collection algorithm to determine when a section of storage is to be recovered.
  • the garbage collector bypass 316 allows packets to be read into the read data pipeline 108 and then transferred directly to the write data pipeline 106 without being routed out of the solid-state storage controller 104.
  • the garbage collector bypass 316 is part of an autonomous garbage collector system that operates within the solid-state storage device 102. This allows the solid-state storage device 102 to manage data so that data is systematically spread throughout the solid-state storage 110 to improve performance, data reliability and to avoid overuse and underuse of any one location or area of the solid-state storage 110 and to lengthen the useful life of the solid-state storage 110.
  • the garbage collector bypass 316 coordinates insertion of segments into the write data pipeline 106 with other segments being written by clients 116 or other devices.
  • the garbage collector bypass 316 is before the packetizer 302 in the write data pipeline 106 and after the depacketizer 324 in the read data pipeline 108, but may also be located elsewhere in the read and write data pipelines 106, 108.
  • the garbage collector bypass 316 may be used during a flush of the write pipeline 106 to fill the remainder of the virtual page in order to improve the efficiency of storage within the Solid-State Storage 110 and thereby reduce the frequency of garbage collection.
  • the write data pipeline 106 includes a write buffer 320 that buffers data for efficient write operations.
  • the write buffer 320 includes enough capacity for packets to fill at least one virtual page in the solid-state storage 110. This allows a write operation to send an entire page of data to the solid-state storage 110 without interruption.
  • the solid-state storage 110 may be used for other read operations. This is advantageous because other solid-state devices with a smaller write buffer or no write buffer may tie up the solid-state storage when data is written to a storage write buffer and data flowing into the storage write buffer stalls. Read operations will be blocked until the entire storage write buffer is filled and programmed.
  • Another approach for systems without a write buffer or a small write buffer is to flush the storage write buffer that is not full in order to enable reads. Again this is inefficient because multiple write/program cycles are required to fill a page.
  • a single write command which includes numerous subcommands, can then be followed by a single program command to transfer the page of data from the storage write buffer in each solid-state storage element 216, 218, 220 to the designated page within each solid-state storage element 216, 218, 220.
  • This technique has the benefits of eliminating partial page programming, which is known to reduce data reliability and durability and freeing up the destination bank for reads and other commands while the buffer fills.
  • the write buffer 320 is a ping-pong buffer where one side of the buffer is filled and then designated for transfer at an appropriate time while the other side of the ping-pong buffer is being filled.
  • the write buffer 320 includes a first-in first-out ("FIFO") register with a capacity of more than a virtual page of data segments.
  • FIFO first-in first-out
  • the write buffer 320 is sized smaller than a virtual page so that less than a page of information could be written to a storage write buffer in the solid-state storage 110.
  • data is queued using the garbage collection system that needs to be moved from one location to another as part of the garbage collection process.
  • the data can be fed through the garbage collector bypass 316 to the write buffer 320 and then on to the storage write buffer in the solid-state storage 110 to fill the pages of a virtual page prior to programming the data. In this way a data stall in the write data pipeline 106 would not stall reading from the solid-state storage device 106.
  • the write data pipeline 106 includes a write program module 310 with one or more user-definable functions within the write data pipeline 106.
  • the write program module 310 allows a user to customize the write data pipeline 106.
  • a user may customize the write data pipeline 106 based on a particular data requirement or application.
  • the solid- state storage controller 104 is an FPGA
  • the user may program the write data pipeline 106 with custom commands and functions relatively easily.
  • a user may also use the write program module 310 to include custom functions with an ASIC, however, customizing an ASIC may be more difficult than with an FPGA.
  • the write program module 310 may include buffers and bypass mechanisms to allow a first data segment to execute in the write program module 310 while a second data segment may continue through the write data pipeline 106.
  • the write program module 310 may include a processor core that can be programmed through software.
  • the write program module 310 is shown between the input buffer 306 and the compression module 312, however, the write program module 310 could be anywhere in the write data pipeline 106 and may be distributed among the various stages 302-320. In addition, there may be multiple write program modules 310 distributed among the various states 302-320 that are programmed and operate independently. In addition, the order of the .stages 302-320 may be altered. One of skill in the art will recognize workable alterations to the order of the stages 302-320 based on particular user requirements.
  • the read data pipeline 108 includes an ECC correction module 322 that determines if a data error exists in ECC blocks a requested packet received from the solid-state storage 110 by using ECC stored with each ECC block of the requested packet.
  • the ECC correction module 322 then corrects any errors in the requested packet if any error exists and the errors are correctable using the ECC. For example, if the ECC can detect an error in six bits but can only correct three bit errors, the ECC correction module 322 corrects ECC blocks of the requested packet with up to three bits in error. The ECC correction module 322 corrects the bits in error by changing the bits in error to the correct one or zero state so that the requested data packet is identical to when it was written to the solid-state storage 110 and the ECC was generated for the packet. If the ECC correction module 322 determines that the requested packets contains more bits in error than the ECC can correct, the ECC correction module 322 cannot correct the errors in the corrupted ECC blocks of the requested packet and sends an interrupt.
  • the ECC correction module 322 sends an interrupt with a message indicating that the requested packet is in error.
  • the message may include information that the ECC correction module 322 cannot correct the errors or the inability of the ECC correction module 322 to correct the errors may be implied.
  • the ECC correction module 322 sends the corrupted ECC blocks of the requested packet with the interrupt and/or the message.
  • a corrupted ECC block or portion of a corrupted ECC block of the requested packet that cannot be corrected by the ECC correction module 322 is read by the master controller 224, corrected, and returned to the ECC correction module 322 for further processing by the read data pipeline 108.
  • a corrupted ECC block or portion of a corrupted ECC block of the requested packet is sent to the device requesting the data.
  • the requesting device 155 may correct the ECC block or replace the data using another copy, such as a backup or mirror copy, and then may use the replacement data of the requested data packet or return it to the read data pipeline 108.
  • the requesting device 155 may use header information in the requested packet in error to identify data required to replace the corrupted requested packet or to replace the object to which the packet belongs.
  • the solid- state storage controller 104 stores data using some type of RAID and is able to recover the corrupted data.
  • the ECC correction module 322 sends and interrupt and/or message and the receiving device fails the read operation associated with the requested data packet.
  • One of skill in the art will recognize other options and actions to be taken as a result of the ECC correction module 322 determining that one or more ECC blocks of the requested packet are corrupted and that the ECC correction module 322 cannot correct the errors.
  • the read data pipeline 108 includes a depacketizer 324 that receives ECC blocks of the requested packet from the ECC correction module 322, directly or indirectly, and checks and removes one or more packet headers.
  • the depacketizer 324 may validate the packet headers by checking packet identifiers, data length, data location, etc. within the headers.
  • the header includes a hash code that can be used to validate that the packet delivered to the read data pipeline 108 is the requested packet.
  • the depacketizer 324 also removes the headers from the requested packet added by the packetizer 302.
  • the depacketizer 324 may directed to not operate on certain packets but pass these forward without modification.
  • An example might be a container label that is requested during the course of a rebuild process where the header information is required by the object index reconstruction module 272. Further examples include the transfer of packets of various types destined for use within the solid-state storage device 102. In another embodiment, the depacketizer 324 operation may be packet type dependent.
  • the read data pipeline 108 includes an alignment module 326 that receives data from the depacketizer 324 and removes unwanted data.
  • a read command sent to the solid-state storage 110 retrieves a packet of data.
  • a device requesting the data may not require all data within the retrieved packet and the alignment module 326 removes the unwanted data. If all data within a retrieved page is requested data, the alignment module 326 does not remove any data.
  • the alignment module 326 re-formats the data as data segments of an object in a form compatible with a device requesting the data segment prior to forwarding the data segment to the next stage.
  • the size of data segments or packets changes at various stages.
  • the alignment module 326 uses received data to format the data into data segments suitable to be sent to the requesting device 155 and joined to form a response. For example, data from a portion of a first data packet may be combined with data from a portion of a second data packet. If a data segment is larger than a data requested by the requesting device, the alignment module 326 may discard the unwanted data.
  • the read data pipeline 108 includes a read synchronization buffer 328 that buffers one or more requested packets read from the solid-state storage 110 prior to processing by the read data pipeline 108.
  • the read synchronization buffer 328 is at the boundary between the solid-state storage clock domain and the local bus clock domain and provides buffering to account for the clock domain differences.
  • the read data pipeline 108 includes an output buffer 330 that receives requested packets from the alignment module 326 and stores the packets prior to transmission to the requesting device.
  • the output buffer 330 accounts for differences between when data segments are received from stages of the read data pipeline 108 and when the data segments are transmitted to other parts of the solid-state storage controller 104 or to the requesting device.
  • the output buffer 330 also allows the data bus 204 to receive data from the read data pipeline 108 at rates greater than can be sustained by the read data pipeline 108 in order to improve efficiency of operation of the data bus 204.
  • the read data pipeline 108 includes a media decryption module 332 that receives one or more encrypted requested packets from the ECC correction module 322 and decrypts the one or more requested packets using the encryption key unique to the solid-state storage device 102 prior to sending the one or more requested packets to the depacketizer 324.
  • the encryption key used to decrypt data by the media decryption module 332 is identical to the encryption key used by the media encryption module 318.
  • the solid-state storage 110 may have two or more partitions and the solid-state storage controller 104 behaves as though it were two or more solid-state storage controllers 104 each operating on a single partition within the solid-state storage 110. In this embodiment, a unique media encryption key may be used with each partition.
  • the read data pipeline 108 includes a decryption module 334 that decrypts a data segment formatted by the depacketizer 324 prior to sending the data segment to the output buffer 330.
  • the data segment decrypted using an encryption key received in conjunction with the read request that initiates retrieval of the requested packet received by the read synchronization buffer 328.
  • the decryption module 334 may decrypt a first packet with an encryption key received in conjunction with the read request for the first packet and then may decrypt a second packet with a different encryption key or may pass the second packet on to the next stage of the read data pipeline 108 without decryption.
  • the decryption module 334 uses a different encryption key to decrypt a data segment than the media decryption module 332 uses to decrypt requested packets.
  • the nonce is used in conjunction with an encryption key to decrypt the data packet.
  • the encryption key may be received from a client 114, a computer 112, key manager, or other device that manages the encryption key to be used by the solid-state storage controller 104.
  • the read data pipeline 108 includes a decompression module 336 that decompresses a data segment formatted by the depacketizer 324.
  • the decompression module 336 uses compression information stored in one or both of the packet header and the container label to select a complementary routine to that used to compress the data by the compression module 312.
  • the decompression routine used by the decompression module 336 is dictated by the device requesting the data segment being decompressed.
  • the decompression module 336 selects a decompression routine according to default settings on a per object type or object class basis. A first packet of a first object may be able to override a default decompression routine and a second packet of a second object of the same object class and object type may use the default decompression routine and a third packet of a third object of the same object class and object type may use no decompression.
  • the read data pipeline 108 includes a read program module 338 that includes one or more user-definable functions within the read data pipeline 108.
  • the read program module 338 has similar characteristics to the write program module 310 and allows a user to provide custom functions to the read data pipeline 108.
  • the read program module 338 may be located as shown in Figure 3, may be located in another position within the read data pipeline 108, or may include multiple parts in multiple locations within the read data pipeline 108. Additionally, there may be multiple read program modules 338 within multiple locations within the read data pipeline 108 that operate independently.
  • One of skill in the art will recognize other forms of a read program module 338 within a read data pipeline 108.
  • the stages of the read data pipeline 108 may be rearranged and one of skill in the art will recognize other orders of stages within the read data pipeline 108.
  • the solid-state storage controller 104 includes control and status registers 340 and corresponding control queues 342.
  • the control and status registers 340 and control queues 342 facilitate control and sequencing commands and subcommands associated with data processed in the write and read data pipelines 106, 108.
  • a data segment in the packetizer 302 may have one or more corresponding control commands or instructions in a control queue 342 associated with the ECC generator. As the data segment is packetized, some of the instructions or commands may be executed within the packetizer 302. Other commands or instructions may be passed to the next control queue 342 through the control and status registers 340 as the newly formed data packet created from the data segment is passed to the next stage.
  • Commands or instructions may be simultaneously loaded into the control queues 342 for a packet being forwarded to the write data pipeline 106 with each pipeline stage pulling the appropriate command or instruction as the respective packet is executed by that stage.
  • commands or instructions may be simultaneously loaded into the control queues 342 for a packet being requested from the read data pipeline 108 with each pipeline stage pulling the appropriate command or instruction as the respective packet is executed by that stage.
  • One of skill in the art will recognize other features and functions of control and status registers 340 and control queues 342.
  • the solid-state storage controller 104 and or solid-state storage device 102 may also include a bank interleave controller 344, a synchronization buffer 346, a storage bus controller 348, and a multiplexer (“MUX") 350, which are described in relation to Figures 4A and 4B.
  • BANK INTERLEAVE Figure 4A is a schematic block diagram illustrating one embodiment 400 of a bank interleave controller 344 in the solid-state storage controller 104 in accordance with the present invention.
  • the bank interleave controller 344 is connected to the control and status registers 340 and to the storage I/O bus 210 and storage control bus 212 through the MUX 350, storage bus controller 348, and synchronous buffer 346, which are described below.
  • the bank interleave controller includes a read agent 402, a write agent 404, an erase agent 406, a management agent 408, read queues 410a-n, write queues 412a-n, erase queues 414a-n, and management queues 416a-n for the banks 214 in the solid-state storage 110, bank controllers 418a-n, a bus arbiter 420, and a status MUX 422, which are described below.
  • the storage bus controller 348 includes a mapping module 424 with a remapping module 430, a status capture module 426, and a NAND bus controller 428, which are described below.
  • the bank interleave controller 344 directs one or more commands to two or more queues in the bank interleave controller 344 and coordinates among the banks 214 of the solid-state storage 110 execution of the commands stored in the queues, such that a command of a first type executes on one bank 214a while a command of a second type executes on a second bank 214b.
  • the one or more commands are separated by command type into the queues.
  • Each bank 214 of the solid-state storage 110 has a corresponding set of queues within the bank interleave controller 344 and each set of queues includes a queue for each command type.
  • the bank interleave controller 344 coordinates among the banks 214 of the solid-state storage 110 execution of the commands stored in the queues. For example, a command of a first type executes on one bank 214a while a command of a second type executes on a second bank 214b.
  • the command types and queue types include read and write commands and queues 410, 412, but may also include other commands and queues that are storage media specific.
  • erase and management queues 414, 416 are included and would be appropriate for flash memory, NRAM, MRAM, DRAM, PRAM, etc.
  • solid-state storage 110 For other types of solid-state storage 110, other types of commands and corresponding queues may be included without straying from the scope of the invention.
  • the flexible nature of an FPGA solid-state storage controller 104 allows flexibility in storage media. If flash memory were changed to another solid-state storage type, the bank interleave controller 344, storage bus controller 348, and MUX 350 could be altered to accommodate the media type without significantly affecting the data pipelines 106, 108 and other solid-state storage controller 104 functions.
  • the bank interleave controller 344 includes, for each bank 214, a read queue 410 for reading data from the solid-state storage 110, a write queue 412 for write commands to the solid-state storage 110, an erase queue 414 for erasing an erase block in the solid-state storage, an a management queue 416 for management commands.
  • the bank interleave controller 344 also includes corresponding read, write, erase, and management agents 402, 404, 406, 408.
  • the control and status registers 340 and control queues 342 or similar components queue commands for data sent to the banks 214 of the solid-state storage 110 without a bank interleave controller 344.
  • the agents 402, 404, 406, 408, in one embodiment, direct commands of the appropriate type destined for a particular bank 214a to the correct queue for the bank 214a.
  • the read agent 402 may receive a read command for bank-1 214b and directs the read command to the bank-1 read queue 410b.
  • the write agent 404 may receive a write command to write data to a location in bank-0 214a of the solid-state storage 110 and will then send the write command to the bank-0 write queue 412a.
  • the erase agent 406 may receive an erase command to erase an erase block in bank-1 214b and will then pass the erase command to the bank-1 erase queue 414b.
  • the management agent 408 typically receives management commands, status requests, and the like, such as a reset command or a request to read a configuration register of a bank 214, such as bank-0 214a.
  • the management agent 408 sends the management command to the bank-0 management queue 416a.
  • the agents 402, 404, 406, 408 typically also monitor status of the queues 410, 412, 414, 416 and send status, interrupt, or other messages when the queues 410, 412, 414, 416 are full, nearly full, non-functional, etc.
  • the agents 402, 404, 406, 408 receive commands and generate corresponding sub-commands.
  • the agents 402, 404, 406, 408 receive commands through the control & status registers 340 and generate corresponding sub-commands which are forwarded to the queues 410, 412, 414, 416.
  • One of skill in the art will recognize other functions of the agents 402, 404, 406, 408.
  • the queues 410, 412, 414, 416 typically receive commands and store the commands until required to be sent to the solid-state storage banks 214.
  • the queues 410, 412, 414, 416 are first-in, first-out ("FIFO") registers or a similar component that operates as a FIFO.
  • the queues 410, 412, 414, 416 store commands in an order that matches data, order of importance, or other criteria.
  • the bank controllers 418 typically receive commands from the queues 410, 412, 414, 416 and generate appropriate subcommands.
  • the bank-0 write queue 412a may receive a command to write a page of data packets to bank-0 214a.
  • the bank-0 controller 418a may receive the write command at an appropriate time and may generate one or more write subcommands for each data packet stored in the write buffer 320 to be written to the page in bank-0 214a.
  • bank-0 controller 418a may generate commands to validate the status of bank 0 214a and the solid-state storage array 216, select the appropriate location for writing one or more data packets, clear the input buffers within the solid-state storage memory array 216, transfer the one or more data packets to the input buffers, program the input buffers into the selected location, verify that the data was correctly programmed, and if program failures occur do one or more of interrupting the master controller, retrying the write to the same physical location, and retrying the write to a different physical location.
  • the storage bus controller 348 will cause the one or more commands to multiplied to each of the each of the storage I/O buses 210a-n with the logical address of the command mapped to a first physical addresses for storage I/O bus 210a, and mapped to a second physical address for storage I/O bus 210b, and so forth as further described below.
  • bus arbiter 420 selects from among the bank controllers 418 and pulls subcommands from output queues within the bank controllers 418 and forwards these to the Storage Bus Controller 348 in a sequence that optimizes the performance of the banks 214.
  • the bus arbiter 420 may respond to a high level interrupt and modify the normal selection criteria.
  • the master controller 224 can control the bus arbiter 420 through the control and status registers 340.
  • One of skill in the art will recognize other means by which the bus arbiter 420 may control and interleave the sequence of commands from the bank controllers 418 to the solid-state storage 110.
  • the bus arbiter 420 typically coordinates selection of appropriate commands, and corresponding data when required for the command type, from the bank controllers 418 and sends the commands and data to the storage bus controller 348.
  • the bus arbiter 420 typically also sends commands to the storage control bus 212 to select the appropriate bank 214.
  • only one command (control information) or set of data can be transmitted at a time.
  • write commands or data are being transmitted to the solid-state storage 110 on the storage I/O bus 210
  • read commands, data being read, erase commands, management commands, or other status commands cannot be transmitted on the storage I/O bus 210.
  • data cannot be written to the solid-state storage 110.
  • the bus arbiter 420 selects the bank-0 controller 418a which may have a write command or a series of write sub-commands on the top of its queue which cause the storage bus controller 348 to execute the following sequence.
  • the bus arbiter.420 forwards the write command to the storage bus controller 348, which sets up a write command by selecting bank-0 214a through the storage control bus 212, sending a command to clear the input buffers of the solid-state storage elements 110 associated with the bank-0 214a, and sending a command to validate the status of the solid-state storage elements 216, 218, 220 associated with the bank-0 214a.
  • the storage bus controller 348 then transmits a write subcommand on the storage I/O bus 210, which contains the physical addresses including the address of the logical erase block for each individual physical erase solid-stage storage element 216a-m as mapped from the logical erase block address.
  • the storage bus controller 348 then muxes the write buffer 320 through the write sync buffer 308 to the storage I/O bus 210 through the MUX 350 and streams write data to the appropriate page.
  • storage bus controller 348 causes the solid-state storage elements 216a-m associated with the bank-0 214a to program the input buffer to the memory cells within the solid-state storage elements 216a-m.
  • the storage bus controller 348 validates the status to ensure that page was correctly programmed.
  • a read operation is similar to the write example above.
  • the bus arbiter 420 or other component of the bank interleave controller 344, receives data and corresponding status information and sends the data to the read data pipeline 108 while sending the status information on to the control and status registers 340.
  • a read data command forwarded from bus arbiter 420 to the storage bus controller 348 will cause the MUX 350 to gate the read data on storage I/O bus 210 to the read data pipeline 108 and send status information to the appropriate control and status registers 340 through the status MUX 422.
  • the bus arbiter 420 coordinates the various command types and data access modes so that only an appropriate command type or corresponding data is on the bus at any given time. If the bus arbiter 420 has selected a write command, and write subcommands and corresponding data are being written to the solid-state storage 110, the bus arbiter 420 will not allow other command types on the storage I/O bus 210. Beneficially, the bus arbiter 420 uses timing information, such as predicted command execution times, along with status information received concerning bank 214 status to coordinate execution of the various commands on the bus with the goal of minimizing or eliminating idle time of the busses.
  • the master controller 224 through the bus arbiter 420 typically uses expected completion times of the commands stored in the queues 410, 412, 414, 416, along with status information, so that when the subcommands associated with a command are executing on one bank 214a, other subcommands of other commands are executing on other banks 214b-n.
  • the bus arbiter 420 directs another command to the bank 214a.
  • the bus arbiter 420 may also coordinate commands stored in the queues 410, 412, 414, 416 with other commands that are not stored in the queues 410, 412, 414, 416.
  • an erase command may be sent out to erase a group of erase blocks within the solid-state storage 1 10.
  • An erase command may take 10 to 1000 times more time to execute than a write or a read command or 10 to 100 times more time to execute than a program command.
  • the bank interleave controller 344 may split the erase command into N commands, each to erase a virtual erase block of a bank 214a. While bank-0 214a is executing an erase command, the bus arbiter 420 may select other commands for execution on the other banks 214b-n.
  • the bus arbiter 420 may also work with other components, such as the storage bus controller 348, the master controller 224, etc., to coordinate command execution among the buses.
  • the solid-state controller 104 includes one bank interleave controller
  • the solid-state controller 104 includes a bank interleave controller 344 for each row of storage elements 216a-m, 218a-m, 220a-m.
  • a bank interleave controller 344 serves one row of storage elements SSS 0.0-SSS 0.N 216a, 218a, 220a
  • a second bank interleave controller 344 serves a second row of storage elements SSS 1.0-SSS l.N 216b, 218b, 220b, etc.
  • FIG. 4B is a schematic block diagram illustrating an alternate embodiment 401 of a bank interleave controller in the solid-state storage controller in accordance with the present invention.
  • the components 210, 212, 340, 346, 348, 350, 402-430 depicted in the embodiment shown in Figure 4B are substantially similar to the bank interleave apparatus 400 described in relation to Figure 4 A except that each bank 214 includes a single queue 432a-n and the read commands, write commands, erase commands, management commands, etc. for a bank (e.g. Bank-0 214a) are directed to a single queue 432a for the bank 214a.
  • the queues 432 in one embodiment, are FIFO.
  • the queues 432 can have commands pulled from the queues 432 in an order other than the order they were stored.
  • the read agent 402, write agent 404, erase agent 406, and management agent 408 may be combined into a single agent assigning commands to the appropriate queues 432a-n.
  • commands are stored in a single queue where the commands may be pulled from the queue in an order other than how they are stored so that the bank interleave controller 344 can execute a command on one bank 214a while other commands are executing on the remaining banks 214b-n.
  • the bank interleave controller 344 can execute a command on one bank 214a while other commands are executing on the remaining banks 214b-n.
  • One of skill in the art will easily recognize other queue configurations and types to enable execution of a command on one bank 214a while other commands are executing on other banks 214b-n.
  • the solid-state storage controller 104 includes a synchronization buffer 346 that buffers commands and status messages sent and received from the solid-state storage 110.
  • the synchronization buffer 346 is located at the boundary between the solid-state storage clock domain and the local bus clock domain and provides buffering to account for the clock domain differences.
  • the synchronization buffer 346, write synchronization buffer 308, and read synchronization buffer 328 may be independent or may act together to buffer data, commands, status messages, etc.
  • the synchronization buffer 346 is located where there are the fewest number of signals crossing the clock domains.
  • synchronization between clock domains may be arbitrarily moved to other locations within the solid-state storage device 102 in order to optimize some aspect of design implementation.
  • the solid-state storage controller 104 includes a storage bus controller 348 that interprets and translates commands for data sent to and read from the solid-state storage 110 and status messages received from the solid-state storage 110 based on the type of solid-state storage 110.
  • the storage bus controller 348 may have different timing requirements for different types of storage, storage with different performance characteristics, storage from different manufacturers, etc.
  • the storage bus controller 348 also sends control commands to the storage control bus 212.
  • the solid-state storage controller 104 includes a MUX 350 that comprises an array of multiplexers 350a-n where each multiplexer is dedicated to a row in the solid-state storage array 110.
  • multiplexer 350a is associated with solid-state storage elements 216a, 218a, 220a.
  • MUX 350 routes the data from the write data pipeline 106 and commands from the storage bus controller 348 to the solid-state storage 110 via the storage I/O bus 210 and routes data and status messages from the solid-state storage 110 via the storage I/O bus 210 to the read data pipeline 106 and the control and status registers 340 through the storage bus controller 348, synchronization buffer 346, and bank interleave controller 344.
  • the solid-state storage controller 104 includes a MUX 350 for each row of solid-state storage elements (e.g. SSS 0.1 216a, SSS 0.2 218a, SSS 0.N 220a).
  • a MUX 350 combines data from the write data pipeline 106 and commands sent to the solid-state storage 1 10 via the storage I/O bus 210 and separates data to be processed by the read data pipeline 108 from commands.
  • Packets stored in the write buffer 320 are directed on busses out of the write buffer 320 through a write synchronization buffer 308 for each row of solid-state storage elements (SSS x.O to SSS x.N 216, 218, 220) to the MUX 350 for each row of solid-state storage elements (SSS x.O to SSS x.N 216, 218, 220).
  • the commands and read data are received by the MUXes 350 from the storage I/O bus 210.
  • the MUXes 350 also direct status messages to the storage bus controller 348.
  • the storage bus controller 348 includes a mapping module 424.
  • the mapping module 424 maps a logical address of an erase block to one or more physical addresses of an erase block.
  • a solid-state storage 110 with an array of twenty storage elements (e.g. SSS 0.0 to SSS M.O 216) per block 214a may have a logical address for a particular erase block mapped to twenty physical addresses of the erase block, one physical address per storage element. Because the storage elements are accessed in parallel, erase blocks at the same position in each storage element in a row of storage elements 216a, 218a, 220a will share a physical address.
  • one bank in this case bank-0 214a is selected.
  • the remapping module 430 changes a mapping of a logical address of an erase block to one or more physical addresses of a virtual erase block (spread over the array of storage elements).
  • virtual erase block 1 may be mapped to erase block 1 of storage element SSS 0.0 216a, to erase block 1 of storage element SSS 1.0 216b, ..., and to storage element M.O 216m
  • virtual erase block 2 may be mapped to erase block 2 of storage element SSS 0.1 218a, to erase block 2 of storage element SSS 1.1 218b, ..., and to storage element M.I 218m, etc.
  • the remapping module could change the logical-to- physical mapping for the logical address that pointed to erase block 1 of virtual erase block 1. If a spare erase block (call it erase block 221) of storage element SSS 0.0 216a is available and currently not mapped, the remapping module could change the mapping of virtual erase block 1 to point to erase block 221 of storage element SSS 0.0 216a, while continuing to point to erase block 1 of storage element SSS 1.0 216b, erase block 1 of storage element SSS 2.0 (not shown) ..., and to storage element M.O 216m.
  • the mapping module 424 or remapping module 430 could map erase blocks in a prescribed order (virtual erase block 1 to erase block 1 of the storage elements, virtual erase block 2 to erase block 2 of the storage elements, etc.) or may map erase blocks of the storage elements 216, 218, 220 in another order based on some other criteria.
  • the erase blocks could be grouped by access time. Grouping by access time, meaning time to execute a command, such as programming (writing) data into pages of specific erase blocks, can level command completion so that a command executed across the erase blocks of a virtual erase block is not limited by the slowest erase block.
  • the erase blocks may be grouped by wear level, health, etc. One of skill in the art will recognize other factors to consider when mapping or remapping erase blocks.
  • the storage bus controller 348 includes a status capture module 426 that receives status messages from the solid-state storage 110 and sends the status messages to the status MUX 422.
  • the storage bus controller 348 when the solid-state storage 110 is flash memory, the storage bus controller 348 includes a NAND bus controller 428.
  • the NAND bus controller 428 directs commands from the read and write data pipelines 106, 108 to the correct location in the solid-state storage 110, coordinates timing of command execution based on characteristics of the flash memory, etc. If the solid-state storage 110 is another solid-state storage type, the NAND bus controller 428 would be replaced by a bus controller specific to the storage type.
  • FLOW CHARTS FLOW CHARTS
  • Figure 5A is a schematic flow chart diagram illustrating one embodiment of a method 500 for managing data in a solid-state storage device 102 using a data pipeline in accordance with the present invention.
  • the method 500 begins 502 and the input buffer 306 receives 504 one or more data segments to be written to the solid-state storage 110.
  • the one or more data segments typically include at least a portion of an object but may be an entire object.
  • the packetizer 302 may create one or more object specific packets in conjunction with an object.
  • the packetizer 302 adds a header to each packet which typically includes the length of the packet and a sequence number for the packet within the object.
  • the packetizer 302 receives 504 the one or more data or metadata segments that were stored in the input buffer 306 and packetizes 506 the one or more data or metadata segments by creating one or more packets sized for the solid-state storage 110 where each packet includes one header and data from the one or more segments.
  • a first packet includes an object identifier that identifies the object for which the packet was created.
  • a second packet may include a header with information used by the solid-state storage device 102 to associate the second packet to the object identified in the first packet and offset information locating the second packet within the object, and data.
  • the solid- state storage device controller 202 manages the bank 214 and physical area to which the packets are streamed.
  • the ECC generator 304 receives a packet from the packetizer 302 and generates 508 ECC for the data packets.
  • An ECC block may comprise one or more packets.
  • a packet may comprise one or more ECC blocks.
  • a packet may start and end anywhere within an ECC block.
  • a packet may start anywhere in a first ECC block and end anywhere in a subsequent ECC block.
  • the write synchronization buffer 308 buffers 510 the packets as distributed within the corresponding ECC blocks prior to writing ECC blocks to the solid-state storage 1 10 and then the solid-state storage controller 104 writes 512 the data at an appropriate time considering clock domain differences, and the method 500 ends 514.
  • the write synch buffer 308 is located at the boundary between a local clock domain and a solid-state storage 110 clock domain. Note that the method 500 describes receiving one or more data segments and writing one or more data packets for convenience, but typically a stream of data segments is received and a group. Typically a number of ECC blocks comprising a complete virtual page of solid-state storage 110 are written to the solid-state storage 110.
  • the packetizer 302 receives data segments of one size and generates packets of another size. This necessarily requires data or metadata segments or parts of data or metadata segments to be combined to form data packets to capture all of the data of the segments into packets.
  • FIG. 5B is a schematic flow chart diagram illustrating one embodiment of a method for in-server SAN in accordance with the present invention.
  • the method 500 begins 552 and the storage communication module 162 facilitates 554 communication between a first storage controller 152a and at least one device external to the first server 1 12a.
  • the communication between the first storage controller 152a and the external device is independent from the first server 112a.
  • the first storage controller 112a is within the first server 112a and the first storage controller 152a controls at least one storage device 154a.
  • the first server 112a includes a network interface 156a collocated with the first server 112a and the first storage controller 152a.
  • the in-server SAN module 164 services 556 a storage request and the method 501 ends 558.
  • the in-server SAN module services 556 the storage request using a network protocol and/or a bus protocol.
  • the in-server SAN module 164 services 556 the storage request independent from the first server 112a and the service request is received from a client 1 14, 114a.
  • Figure 6 is a schematic flow chart diagram illustrating another embodiment of a method
  • the method 600 begins 602 and the input buffer 306 receives 604 one or more data or metadata segments to be written to the solid-state storage 110.
  • the packetizer 302 adds a header to each packet which typically includes the length of the packet within the object.
  • the packetizer 302 receives 604 the one or more segments that were stored in the input buffer 306 and packetizes 606 the one or more segments by creating one or more packets sized for the solid-state storage 110 where each packet includes a header and data from the one or more segments.
  • the ECC generator 304 receives a packet from the packetizer 302 and generates 608 one or more ECC blocks for the packets.
  • the write synchronization buffer 308 buffers 610 the packets as distributed within the corresponding ECC blocks prior to writing ECC blocks to the solid-state storage 110 and then the solid-state storage controller 104 writes 612 the data at an appropriate time considering clock domain differences.
  • ECC blocks comprising one or more data packets are read into the read synchronization buffer 328 and buffered 614.
  • the ECC blocks of the packet are received over the storage I/O bus 210. Since the storage I/O bus 210 is bi-directional, when data is read, write operations, command operations, etc. are halted.
  • the ECC correction module 322 receives the ECC blocks of the requested packets held in the read synchronization buffer 328 and corrects 616 errors within each ECC block as necessary. If the ECC correction module 322 determines that one or more errors exist in an ECC block and the errors are correctable using the ECC syndrom, the ECC correction module 322 corrects 616 the error in the ECC block. If the ECC correction module 322 determines that a detected error is not correctable using the ECC, the ECC correction module 322 sends an interrupt. The depacketizer 324 receives 618 the requested packet after the ECC correction module
  • the alignment module 326 receives packets after depacketizing, removes unwanted data, and re-formats 620 the data packets as data or metadata segments of an object in a form compatible with the device requesting the segment or object.
  • the output buffer 330 receives requested packets after depacketizing and buffers 622 the packets prior to transmission to the requesting device, and the method 600 ends 624.
  • FIG. 7 is a schematic flow chart diagram illustrating an embodiment of a method 700 for managing data in a solid-state storage device 102 using a bank interleave in accordance with the present invention.
  • the method 600 begins 602 and the bank interleave controller 344 directs 604 one or more commands to two or more queues 410, 412, 414, 416.
  • the agents 402, 404, 406, 408 direct 604 the commands to the queues 410, 412, 414, 416 by command type.
  • Each set of queues 410, 412, 414, 416 includes a queue for each command type.
  • the bank interleave controller 344 coordinates 606 among the banks 214 execution of the commands stored in the queues 410, 412, 414, 416 so that a command of a first type executes on one bank 214a while a command of a second type executes on a second bank 214b, and the method 600 ends 608.
  • FIG. 8 is a schematic block diagram illustrating one embodiment of an apparatus 800 for garbage collection in a solid-state storage device 102 in accordance with the present invention.
  • the apparatus 800 includes a sequential storage module 802, a storage division selection module 804, a data recovery module 806, and a storage division recovery module 808, which are described below.
  • the apparatus 800 includes a garbage marking module 810 and an erase module 812.
  • the apparatus 800 includes a sequential storage module 802 that sequentially writes data packets in a page within a storage division. The packets are sequentially stored whether they are new packets or modified packets. Modified packets are in this embodiment are typically not written back to a location where they were previously stored.
  • the sequential storage module 802 writes a packet to a first location in a page of a storage division, then to the next location in the page, and to the next, and the next, until the page is filled. The sequential storage module 802 then starts to fill the next page in the storage division. This continues until the storage division is filled.
  • the sequential storage module 802 starts writing packets to storage write buffers in the storage elements (e.g. SSS 0.0 to SSS M.O 216) of a bank (bank-0 214a).
  • the solid-state storage controller 104 causes the data in the storage write buffers to be programmed into designated pages within the storage elements 216 of the bank 214a.
  • another bank e.g. bank-1 214b
  • the sequential storage module 802 starts writing packets to storage write buffers of the storage elements 218 of the bank 214b while the first bank-0 is programming the designated pages.
  • the storage division includes a portion of a solid-state storage 110 in a solid-state storage device 102.
  • the storage division is an erase block.
  • an erase operation on an erase block writes ones to every bit in the erase block by charging each cell. This is a lengthy process compared to a program operation which starts with a location being all ones, and as data is written, some bits are changed to zero by discharging the cells written with a zero.
  • the solid-state storage 110 is not flash memory or has flash memory where an erase cycle takes a similar amount of time as other operations, such as a read or a program, the storage division may not be required to be erased.
  • a storage division is equivalent in area to an erase block but may or may not be erased.
  • an erase block may refer to a particular area of a designated size within a storage element (e.g. SSS 0.0 216a) and typically includes a certain quantity of pages.
  • a storage element e.g. SSS 0.0 216a
  • an erase block may include one erase block or a group of erase blocks with one erase block in each of a row of storage elements (e.g.
  • SSS 0.0 to SSS M.O 216a-n which may also be referred to herein as a virtual erase block.
  • the erase blocks may be referred to herein as a logical erase block (“LEB").
  • the packets are sequentially stored by order of processing.
  • the sequential storage module 802 stores packets in the order that they come out of the write data pipeline 106. This order may be a result of data segments arriving from a requesting device 155 mixed with packets of valid data that arebeing read from another storage division as valid data is being recovered from a storage division during a recovery operation as explained below. Re-routing recovered, valid data packets to the write data pipeline 106 may include the garbage collector bypass 316 as described above in relation to the solid-state storage controller 104 of Figure 3.
  • the apparatus 800 includes a storage division selection module 804 that selects a storage division for recovery. Selecting a storage division for recovery may be to reuse the storage division by the sequential storage module 802 for writing data, thus adding the recovered storage division to the storage pool, or to recover valid data from the storage division after determining that the storage division is failing, unreliable, should be refreshed, or other reason to take the storage division temporarily or permanently out of the storage pool.
  • the storage division selection module 804 selects a storage division for recovery by identifying a storage division or erase block with a high amount of invalid data.
  • the storage division selection module 804 selects a storage division for recovery by identifying a storage division or erase block with a low amount of wear.
  • identifying a storage division or erase block with a low amount of wear may include identifying a storage division with a low amount of invalid data, a low number of erase cycles, low bit error rate, or low program count (low number of times a page of data in a buffer is written to a page in the storage division; program count may be measured from when the device was manufactured, from when the storage division was last erased, from other arbitrary events, and from combinations of these).
  • the storage division selection module 804 may also use any combination of the above or other parameters to determine a storage division with a low amount of wear. Selecting a storage division for recovery by determining a storage division with a low amount of wear may be desirable to find storage divisions that are under used, may be recovered for wear leveling, etc.
  • the storage division selection module 804 selects a storage division for recovery by identifying a storage division or erase block with a high amount of wear. For example, identifying a storage division or erase block with a high amount of wear may include identifying a storage division with a high number of erase cycles, high bit error rate, a storage division with a non-recoverable ECC block, or high program count.
  • the storage division selection module 804 may also use any combination of the above or other parameters to determine a storage division with a high amount of wear. Selecting a storage division for recovery by determining a storage division with a high amount of wear may be desirable to find storage divisions that are over used, may be recovered by refreshing the storage division using an erase cycle, etc. or to retire the storage division from service as being unusable.
  • the apparatus 800 includes a data recovery module 806 that reads valid data packets from the storage division selected for recovery, queues the valid data packets with other data packets to be written sequentially by the sequential storage module 802, and updates an index with a new physical address of the valid data written by the sequential storage module 802.
  • the index is the object index mapping data object identifiers of objects to physical addresses of where packets derived from the data object are stored in the solid-state storage 110.
  • the apparatus 800 includes a storage division recovery module 808 that prepares the storage division for use or reuse and marks the storage division as available to the sequential storage module 802 for sequentially writing data packets after the data recovery module 806 has completed copying valid data from the storage division, .
  • the apparatus 800 includes a storage division recovery module 808 that marks the storage division selected for recovery as unavailable for storing data. Typically this is due to the storage division selection module 804 identifying a storage division or erase block with a high amount of wear such that the storage division or erase block is not in condition to be used for reliable data storage.
  • the apparatus 800 is in a solid-state storage device controller 202 of a solid-state storage device 102. In another embodiment, the apparatus 800 controls a solid-state storage device controller 202. In another embodiment, a portion of the apparatus 800 is in a solid-state storage device controller 202. In another embodiment, the object index updated by the data recovery module 806 is also located in the solid-state storage device controller 202
  • the storage division is an erase block and the apparatus 800 includes an erase module 810 that erases an erase block selected for recovery after the data recovery module 806 has copied valid data packets from the selected erase block and before the storage division recovery module 808 marks the erase block as available.
  • the erase module 810 may be executed on one bank while other banks are executing reads, writes, or other operations.
  • the apparatus 800 includes a garbage marking module 812 that identifies a data packet in a storage division as invalid in response to an operation indicating that the data packet is no longer valid. For example, if a data packet is deleted, the garbage marking module 812 may identify the data packet as invalid. A read-modify-write operation is another way for a data packet to be identified as invalid. In one embodiment, the garbage marking module 812 may identify the data packet as invalid by updating an index. In another embodiment, the garbage marking module 812 may identify the data packet as invalid by storing another data packet that indicates that the invalid data packet has been deleted. This is advantageous because storing, in the solid-state storage 110, information that the data packet has been deleted allows the object index reconstruction module 262 or similar module to reconstruct the object index with an entry indicating that the invalid data packet has been deleted.
  • the apparatus 800 may be utilized to fill the remainder of a virtual page of data following a flush command in order to improve overall performance, where the flush command halts data flowing into the write pipeline 106 until the write pipeline 106 empties and all packets have been permanently written into non- volatile solid-state storage 110.
  • This has the benefit of reducing the amount of garbage collection required, the amount of time used to erase storage divisions, and the amount of time required to program virtual pages.
  • a flush command may be received when only one small packet is prepared for writing into the virtual page of the solid-state storage 100.
  • FIG. 9 is a schematic flow chart diagram illustrating an embodiment of a method 900 for storage recovery in accordance with the present invention.
  • the method 900 begins 902 and the sequential storage module 802 sequentially writes 904 data packets in a storage division.
  • the storage division is a portion of a solid-state storage 110 in a solid-state storage device 102.
  • a storage division is an erase block.
  • the data packets are derived from an object and the data packets are sequentially stored by order of processing.
  • the storage division selection module 804 selects 906 a storage division for recovery and the data recovery module 806 reads 908 valid data packets from the storage division selected for recovery.
  • valid data packets are data packets that have not been marked for erasure or deletion or some other invalid data marking and are considered valid or "good" data.
  • the data recovery module 806 queues 910 the valid data packets with other data packets scheduled to be written sequentially by the sequential storage module 802.
  • the data recovery module 806 updates 912 an index with a new physical address of the valid data written by the sequential storage module 802.
  • the index includes a mapping of physical addresses of data packets to object identifiers.
  • the data packets are those stored in stored in the solid-state storage 110 and the object identifiers correspond to the data packets.
  • the storage division recovery module 808 marks 914 the storage division selected for recovery as available to the sequential storage module 802 for sequentially writing data packets and the method 900 ends 916.
  • an erase command deletes a directory entry in the file system while leaving the data in place in the storage device containing the data.
  • a data storage device is not involved in this type of erase operation.
  • Another method of erasing data is to write zeros, ones, or some other null data character to the data storage device to actually replace the erased file.
  • this is inefficient because valuable bandwidth is used while transmitting the data is being overwritten.
  • space in the storage device is taken up by the data used to overwrite invalid data.
  • Some storage devices are not random access storage devices so updating previously stored data does not overwrite existing data. Attempting to overwrite data with a string of ones or a string of zeros on such a device takes up valuable space without fulfilling the desired intent of overwriting the existing data.
  • a client 114 typically does not have an ability to overwrite data to erase it.
  • the received data When receiving a string of repeated characters or character strings, the received data is highly compressible, but typically compression is done by a file system prior to transmission to a storage device. A typical storage device cannot distinguish between compressed data and uncompressed data.
  • the storage device may also receive a command to read the erased file so the storage device may transmit a stream of zeros, ones, or a null character to the requesting device. Again, bandwidth is required to transmit data representing the erased file. From the foregoing discussion, it should be apparent that a need exists for an apparatus, system, and method for a storage device to receive a directive that data is to be erased so that the storage device can store a data segment token that represents an empty data segment or data with repeated characters or character strings. The apparatus, system, and method may also erase the existing data so that the resulting used storage space comprises the small data segment token. An apparatus, system, and method are presented that overcome some or all of the shortcomings of the prior art.
  • FIG. 10 is a schematic block diagram illustrating one embodiment of a system 1000 with an apparatus for generating a token directive in accordance with the present invention.
  • the apparatus includes a token directive generation module 1002, a token directive transmission module 1004, a read receiver module 1006, a read request transmission module 1008, a read token directive receiver module 1010, a requesting client response module 1012, and data segment regeneration module 1014, which are described below.
  • the apparatus is in a server 1 12 connected to a storage device 150 with a storage controller 152 and a data storage device 154, which are substantially similar to those described above.
  • the apparatus includes a token directive generation module 1002 that generates a storage request with a token directive.
  • the token directive includes a request to store a data segment token on the storage device 150.
  • the token directive is intended to be substituted for a series of repeated, identical characters or a series of repeated, identical character strings that would be sent to the storage device 150 and stored as a data segment if the data segment token was not sent in its place.
  • the series of repeated, identical characters indicate that the data segment is empty.
  • the series of repeated, identical characters may be zeros or ones and a data segment filled with zeros or ones may be interpreted as empty.
  • the token directive includes at least a data segment identifier and a data segment length.
  • the data segment identifier is typically an object DD, file name, or other identifier known to a file system, application, server 112, etc. seeking to store the repeated, identical characters or character string on the storage device.
  • the data segment length is typically the storage space required by the series of repeated, identical characters or character strings.
  • the data segment token and the token directive typically do not include data of the data segment, such as the series of repeated, identical characters.
  • the token directive may, however, include other pertinent information for forming the data segment token, such as at least one instance of the repeated, identical character or character string.
  • the token directive may also include metadata, such as a data segment location, an address from a file system, location on a data storage device corresponding to the data segment, etc.
  • the directive, generation module 1002 generates a data segment token along with the token directive.
  • the token directive generation module 1002 generates both a token directive and a secure erase command in response to a request to overwrite existing data on the storage device 150.
  • the existing data includes data identified on the storage device with the same data segment identifier as the data segment identifier in the token directive.
  • a request to overwrite data is sent where it is not sufficient to merely mark data as invalid or garbage, delete a pointer to the data, or other typical delete operation, but where the data is required to be overwritten in such a way that that the data is not recoverable.
  • the request to overwrite the data may be required where data is considered sensitive information and must be destroyed for security reasons.
  • the secure erase command directs the storage device 150 to overwrite existing data so that the existing data is non-recoverable.
  • the storage device 150 then creates the data segment token as well as overwrites, recovers, erases, etc. the existing data.
  • the existing data is non-recoverable and the data segment token is stored on the storage device 150, which typically takes much less storage space than the existing data.
  • the apparatus includes an erase confirmation module 1016 that receives a confirmation that the existing data on the storage device has been overwritten with characters so that the existing data is non-recoverable.
  • the confirmation may be forwarded to a requesting device or client 114 and may be used to verify that the existing data has been put in a condition where it is non-recoverable.
  • the secure erase command may direct the storage device 150 to overwrite the existing data with a specific character or character string or the execute command may be executed multiple times.
  • One of skill in the art will recognize other ways to configure one or more secure erase commands to ensure the existing data is non-recoverable.
  • Data may be encrypted and then stored on a storage device' 150 where encryption is accomplished using an encryption key received by the storage device 150 in conjunction with storing the data.
  • the token directive generation module 1002 generates an encryption erase command along with generating a token directive in response to receiving a request to overwrite the existing data.
  • the encryption erase command erases the encryption key used to store the existing data so that the encryption key is non-recoverable.
  • erasing the encryption key includes erasing the encryption key from the requesting device. In another embodiment, erasing the encryption key includes erasing the encryption key from a server, key vault, or other location where the encryption key is stored. Erasing the encryption key may include replacing the encryption key with other data or with a series of characters so that the encryption key cannot be recovered in any way. Erasing the encryption key typically makes the existing data on the storage device 150 non-recoverable where an encryption routine was used to encrypt the existing data that is robust enough to thwart attempts to decrypt the existing data.
  • the request to overwrite the existing data could be a secure erase directive where the data is overwritten for security reasons, a request to overwrite data to erase the data, a request that seeks to replace the existing data with the repeated, identical characters or character strings, or the like.
  • a secure erase directive causes devices to both securely erase the encryption key and securely erase the existing data.
  • erasure of the encryption key may allow secure erasure of the data on the storage device to be postponed until a garbage collection process erases the data as part of a storage space recovery process.
  • One of skill in the art will recognize other ways to erase an encryption key and other ways to receive a request to overwrite existing data.
  • a token directive includes the data segment token and the token directive transmission module 1004 transmits the data segment token with the token directive.
  • a token directive does not include the data segment token and includes a command for the storage device 150 to generate the data segment token.
  • the token directive transmission module 1004 transmits the token directive with the command to generate a data segment token, but does not transmit a data segment token.
  • the apparatus includes a token directive transmission module 1004 that transmits the token directive to the storage device 150.
  • the token directive transmission module 1004 transmits the token directive as part of a storage request.
  • the storage request may be in the form of an object request, a data request, or other form known to those of skill in the art.
  • the token directive transmission module 1004 transmits the secure erase directive to the storage device 150.
  • the token directive generation module 1002 generates an erase encryption key command
  • the erase encryption key command is transmitted, where necessary, to another device to execute the command.
  • the token directive transmission module 1004 transmits a token directive without a data segment token.
  • the token directive includes instructions and information for the storage device 150 to create a data segment token.
  • the token directive transmission module 1004 transmits a token directive that includes a data segment token.
  • the storage device 150 is capable of recognizing that the data segment token received with the token directive represents a data segment and takes appropriate action to store the data segment token such that the data segment token represents the data segment rather than merely storing the data segment token as ordinary data.
  • the apparatus in a particular embodiment, includes a read receiver module 1006 that receives a storage request to read the data segment from the storage device 150 and a read request transmission module 1008 that transmits the storage request to the storage device 150.
  • the storage request is received from a requesting client 114, such as an external client 114, a client 114 internal to the server 112, such as an application or file server running on the server 112, etc.
  • a requesting client 114 such as an external client 114, a client 114 internal to the server 112, such as an application or file server running on the server 112, etc.
  • One of skill in the art will recognize other devices and software functioning as a requesting client 114 from which the read receiver module 1006 can receive a storage request.
  • the storage request includes a request to read the data segment corresponding to the data segment token requested to be stored in the token directive transmitted to the storage device 150 by the token directive transmission module 1004.
  • the requesting client 114 in one embodiment, is unaware that the data segment has been stored in the form of a data segment token. In another embodiment, the requesting device is aware that the data segment has been stored as a data segment token but is unaware of the information stored in the data segment token.
  • the apparatus in the particular embodiment, also includes a read token directive receiver module 1010 that receives a message corresponding to the requested data segment token from the storage device, where the message includes at least the data segment identifier and the data segment length. The message typically does not include data of the data segment.
  • the message may also include other information stored in the data segment token, such as a data segment location or the repeated, identical character or character string.
  • the apparatus includes a requesting client response module 1012 that transmits a response to the requesting client 1 13 formulated from the message received from the storage device 150.
  • read token directive receiver module 1010 also receives in the message a confirmation that existing data has been overwritten with characters such that the existing data is non-recoverable, where the existing data has been previously stored on the storage device and referenced with the same data segment identifier from the data segment token received in the message.
  • the confirmation may also be received from the storage device 150 independently from any storage request to read the data segment.
  • the apparatus includes a data segment regeneration module 1014 that reconstitutes data of the data segment using information contained in the message.
  • the response sent to the requesting client includes the reconstituted data segment.
  • the response sent to the requesting client includes information contained in the message received from the storage device 150.
  • the requesting client 114 may then reconstitute the data segment or use the information in some other way.
  • the message includes the data segment token.
  • the data segment token may be used by the data segment regeneration module 1014 to reconstitute the data segment before forwarding to the requesting client 114 or the requesting client response module 1012 may simply forward the data segment token.
  • the storage request with the token directive also includes a request to reserve storage space on the storage device 150, where the requested reserved storage space is an amount of storage space that is about the same to the data segment length. In another embodiment, the request to reserve storage space is for an amount of storage space different than the data segment length.
  • the solid-state storage device 102 may be connected to a hard drive or other long-term, inexpensive storage while the solid-state storage 110 is configured as cache for the long-term storage.
  • the request to reserve storage may cause the solid-state storage device 102 to flush a portion of the cache to the long-term storage in preparation for writing data to the solid-state storage device 102.
  • One of skill in the art will recognize other situations were a request to reserve storage space is desired.
  • an apparatus may be provided with a read receiver module 1006, a read request transmission module 1008, a read token directive receiver module 1010, and a requesting client response module 1012, which are substantially similar to those described above.
  • the modules 1006-1012 may be independent from an apparatus including a token generation module 1002 or a token directive transmission module 1004.
  • the apparatus includes a data segment regeneration module 1014, which is substantially similar to the data segment regeneration module 1014 described above.
  • Figure 11 is a schematic flow chart diagram illustrating an embodiment of a method 1100 for generating and transmitting a token directive in accordance with the present invention.
  • the method 1100 begins 1102 and the token directive generation module 1002 generates 1104 a storage request with a token directive, where the token directive includes a request to store a data segment token on the storage device 150.
  • the token directive transmission module 1004 transmits 1106 the token directive to the storage device 150 and the method 1100 ends 1108.
  • the storage request includes a token directive to store the data segment token where the storage request is essentially free from data of the data segment.
  • storage request includes data from the data segment.
  • a software application creates a storage request using the token directive so as to avoid the creation of the data segment.
  • a software application requests the creation of the token directive.
  • Figure 12 is a schematic flow chart diagram illustrating an embodiment of a method 1200 for reading a data segment token in accordance with the present invention.
  • the method 1200 begins 1202 and the read receiver module 1006 receives 1204 a storage request to read a data segment from a storage device 150 from a requesting client 114.
  • the read request transmission module 1008 transmits 1206 the storage request to the storage device 150.
  • the read token directive receiver module 1008 receives 1208 a message corresponding to the requested data segment token from the storage device 150, where the message includes at least the data segment identifier and the data segment length. The message is substantially free from data of the data segment.
  • the requesting client response module 1012 transmits 1210 a response to the requesting client formulated from the message received from the storage device 150 and the method 1200 ends 1212.
  • FIG. 13 is a schematic block diagram illustrating one embodiment of a system 1300 with an apparatus for managing a data segment token in accordance with the present invention.
  • the system 1300 includes an apparatus with a write request receiver module 1302 and a data segment token storage module 1304, and in various embodiments a token directive generation module 1306, a read request receiver module 1308, a read data segment token module 1310, a read request response module 1312 with a transmit data segment token module 1314 and a transmit data segment module 1316, a reconstitute data segment module 1318, a secure erase module 1320 with an erase confirmation module 1322, and a storage space reservation module 1324, which are described below.
  • the system 1300 includes a storage device 150 with a storage controller 152 and a data storage device 154, which are substantially similar to those described above.
  • the system 1300 includes a requesting device 1326, which is described below, in communication with the storage device 150.
  • the modules 1302-1324 are included in the storage device 150 or storage controller 152. In another embodiment, at least a portion of one or more of the modules 1302-1324 is located outside the storage device 150. In a further embodiment, the requesting device 1326 includes a portion of the modules 1302-1324 in the form of drivers, software, or other function of one or more of the modules 1302-1324. For example, a token generation module 1306 and a reconstitute data segment module 1318 are shown in the requesting device 1326. One of skill in the art will recognize other ways to distribute and implement the functionality of the modules 1302-1324.
  • the apparatus includes a write request receiver module 1302 that receives a storage request from the requesting device 1326, where the storage request includes a request to store a data segment in the storage device 150.
  • the data segment includes a series of repeated, identical characters or character strings. Typically, the series of repeated, identical characters signify that the data segment is empty. This is especially true when the series of repeated, identical characters are ones or zeros.
  • the apparatus includes a data segment token storage module 1304 that stores a data segment token in the storage device 150.
  • the data segment token includes at least a data segment identifier and a data segment length. The data segment token is substantially free of the actual data from the data segment.
  • the data segment token may be stored in many forms.
  • the index may be an object index as described above in relation to the apparatus 200 depicted in Figure 2.
  • the index may also be file system index, a block storage index, or other index known to those of skill in the art.
  • the data segment token includes or is in the form of metadata stored on the storage device 150.
  • the data segment token is stored as metadata on the storage device and includes an entry in an index.
  • One of skill in the art will recognize other ways to storage a data segment token.
  • the storage request includes a token directive to store the data segment token where the storage request is essentially free from data of the data segment.
  • the token directive may include the data segment token or a command to generate a data segment token. Where the token directive does not include the data segment token, the data segment token storage module 1304 generates the data segment token from information in the token directive. If the token directive includes the data segment token, the data segment token storage module 1304 recognizes the data segment token as a data structure representing the data segment identified by the data segment identifier in the token directive and stores the data segment token appropriately.
  • the data segment token storage module 1304 recognizes a data segment token
  • the data segment token is differentiated in some way from other data stored on the storage device 150.
  • a requesting device 1326 may merely compress data and send a compressed object, file, or data segment so that the storage device 150 does not distinguish the compressed data segment from other data received by way of other storage requests.
  • the data segment token storage module 1304 may store the data segment token in such a way that when read, it may appear as a data segment rather than the data segment token.
  • the data segment token storage module 1304 may store a data segment token after recognizing that a received data segment token is a data segment token rather than a data segment.
  • storage request includes data from the data segment.
  • the apparatus includes a token generation module 1306 that generates a data segment token from the data segment, where the data segment token is created in response to the storage request to store the data segment.
  • the token generation module 1306 resides in the requesting device 1326, possibly in the form of a driver.
  • the apparatus includes a secure erase module 1320 that overwrites existing data with characters such that the existing data is non-recoverable, where the existing data includes data of a data segment previously stored on the storage device identified with the same data segment identifier as the data segment identified in the storage request.
  • a data segment token is stored with the data segment identifier and data segment length and existing data identified by the same data segment identifier stored in the data segment token is erased by overwriting the existing data.
  • the existing characters are overwritten by zeros, ones, or some other character string so that the existing data is destroyed and is non-recoverable.
  • the secure erase module also includes an erase confirmation module 1322 that transmits a message indicating that the existing data has been overwritten. Typically the message is sent to the requesting device 1326.
  • the erase confirmation message is transmitted after the secure erase module 1320 has overwritten the existing data. The message may be transmitted in the same transaction as the storage request or in a different transaction.
  • the secure erase module 1320 overwrites the existing data during a storage space recovery operation.
  • the storage space recovery operation may be related to the garbage collection describe in relation to the apparatus 800 depicted in Figure 8.
  • a storage space recovery operation involving a request to overwrite the existing data would typically be expedited so that the storage location where the existing data is stored is necessarily recovered prior to any confirmation message is sent by the erase confirmation module 1322.
  • the existing data is marked or otherwise identified to indicate that a secure erase has been requested. The confirmation message would typically not be sent until the existing data marked for erasure has been overwritten and made non-recoverable.
  • the secure erase module 1320 merely marks the existing data as invalid for later storage space recovery.
  • the secure erase updates an index to indicate that the existing data is invalid and prevents access to this data until the data is overwritten during later storage space recovery.
  • the secure erase module 1320 overwrites the existing data each time a data segment token is stored.
  • the storage request specifically includes a request to overwrite the existing data and the secure erase module 1320 overwrites the existing data in response to the request to overwrite the existing data.
  • the secure erase module 1320 stores metadata information regarding confirmation that the existing data has been erased so that subsequent reads can indicate the erasure.
  • the existing data is deleted.
  • deleting the data includes deleting an index entry, address, etc.
  • the when a data segment token is stored, the corresponding existing data is marked as invalid or otherwise ready for storage recovery. The data may be later recovered in a storage recovery operation, garbage collection operation, etc.
  • the apparatus includes a read request receiver module 1308 that receives a storage request to read the data segment, a read data segment token module 1310 that reads the data segment token corresponding to the data segment requested by the storage request, and a read request response module 1312 that transmits a response to the requesting device 1326.
  • the response is generated using the data segment token corresponding to the requested data segment.
  • the storage request to read the data segment in one embodiment, is associated with the storage request and serves to confirm that the storage request has been successful. In another embodiment, the request to read the data segment is independent from the storage request and may be initiated by the requesting device 1326 that made the storage request or another separate requesting device 1326.
  • the read request response module 1312 includes a transmit data segment token module 1314 that transmits in the response a message to the requesting device 1326.
  • the message includes at least the data segment identifier and the data segment length, but may also include a data segment location, at least one instance of the repeated, identical character or character string, or other pertinent information.
  • the message does not include the actual data of the data segment, other than what is included in the data segment token.
  • the apparatus includes a reconstitute data segment module 1318 that reconstitutes data of the data segment using the data segment token.
  • the read request response module 1312 also includes a transmit data segment module 1316 that transmits the reconstituted requested data segment to the requesting device 1326.
  • the reconstitute data segment module 1318 resides at the requesting device 1326, possibly as in the form of a driver, and the transmit data segment token module 1314 transmits the message with the data segment token information to the requesting device 1326.
  • the reconstitute data segment module 1318 at the requesting device 1326 reconstitutes the requested data segment from the message.
  • the system 1300 includes a separate apparatus that includes a read request receiver module 1308, a read data segment token module 1310, a read request response module 1312, which are substantially similar to those described above.
  • the apparatus may be independent from the apparatus including the write request receiver module 1302 and the data segment token storage module 1304.
  • the read request response module 1312 includes a transmit data segment token module 1314 and/or a transmit data segment module 1316, and the apparatus may include a reconstitute data segment module 1318, where the modules 1314, 1316, 1318 are substantially similar to those described above.
  • Figure 14 is a schematic flow chart diagram illustrating an embodiment of a method 1400 for storing a data segment token in accordance with the present invention.
  • the method 1400 begins 1402 and the write request receiver module 1302 receives 1404 a storage request from the requesting device 1326, where the storage request includes a request to store a data segment in the storage device 150.
  • the data segment includes a series of repeated, identical characters or character strings.
  • the a data segment token storage module 1304 stores 1406 a data segment token in the storage device 150 and the method 1400 ends 1408.
  • the data segment token includes at least a data segment identifier and a data segment length and the data segment token does not include data from the data segment for the most part.
  • Figure 15 is a schematic flow chart diagram illustrating an embodiment of a method 1500 for reading a data segment token in accordance with the present invention.
  • the method 1500 begins 1502 and the read request receiver module 1308 receives 1504 a storage request to read a data segment from the storage device 150.
  • the data segment is represented on the storage device by a data segment token and the data segment includes a series of repeated, identical characters or character strings.
  • the data segment token includes at least a data segment identifier and a data segment length and the data segment token does not include data from the data segment.
  • the a read data segment token module 1310 reads 1506 the data segment token corresponding to the data segment requested in the storage request, the read request response module 1312 transmits 1508 a response to the requesting device 150 and the method 1500 ends 1510. The response is generated using the data segment token corresponds to the requested data segment.
  • a redundant array of independent drives can be structured in many ways to achieve various goals.
  • a drive is a mass storage device for data.
  • a drive, or storage device may be a solid-state storage 110, a hard disk drive (“HDD”), a tape drive, an optical drive, or any other mass storage device known to those of skill in the art.
  • a drive comprises a portion of a mass storage device accessed as a virtual volume.
  • a drive includes two or more data storage devices accessible together as a virtual volume and configured in a storage area network (“SAN”), as a RAID, as just a- bunch of disks/drives (“JBOD”), etc.
  • SAN storage area network
  • JBOD just a- bunch of disks/drives
  • a drive is accessed as a single unit or virtual volume through a storage controller 152.
  • the storage controller 152 comprises a solid-state storage controller 104.
  • a drive and a storage device 150 are used interchangeably.
  • the various RAID configurations are called RAID levels.
  • One basic RAID configuration is RAID level 0 which creates a mirror copy of a storage device 150.
  • RAID 0 An advantage of RAID 0 is that a complete copy of data on one or more storage devices 150 is also available on a mirror copy of the one or more storage devices 150 so that reading the data on the primary drives or mirrored drives is relatively fast. RAID 0 also provides a backup copy of data in case of a failure in the primary storage devices 150. A disadvantage of RAID 0 is that writes are relatively slow because written data must be written twice.
  • RAID level 1 Another traditional RAID configuration is RAID level 1.
  • data written to the RAID is divided into N data segments corresponding to N storage devices 150 in a set of storage devices 150.
  • the N data segments form a "stripe.”
  • performance is enhanced because the storage devices 150 can work in parallel to store the N data segments faster than a single storage device 150 can save data comprising the N data segments.
  • Reading data is relatively slow, however, because is data may be spread over multiple storage devices 150 and access time of multiple storage devices 150 is typically slower than reading data from one storage device 150 containing all of the desired data.
  • RAID 1 provides no failure protection.
  • RAID level 5 which includes striping of N data segments across N storage devices 150 and storing a parity data segment on an N+l storage device 150.
  • RAID 5 offers failure tolerance because the RAID can tolerate a single failure of a storage device 150. For example, if a storage device 150 fails, missing a data segment of a stripe can be created using the other available data segments and the parity data segment calculated specifically for the stripe.
  • RAID 5 also typically uses less storage space than RAID 0 because each storage device 150 of the RAIDed set of storage devices 150 is not required to store a complete copy of the data, but only a data segment of a stripe or a parity data segment.
  • RAID 5 like RAID 1 , is relatively fast for writing data, but is relatively slow for reading data. Writing data for a typical traditional RAID 5 is slower than for RAID 1 , however, because a parity data segment must be calculated for each stripe from the N data segments of the stripe.
  • RAID level 6 Another popular RAID configuration is RAID level 6 which includes dual distributed parity.
  • two storage devices 150 are assigned as parity-mirror devices (e.g. 1602a, 1602b). Each parity data segment for a stripe is calculated separately so that losing any two storage devices 150 in the storage device set is recoverable using the remaining, available data segments and/or parity data segments.
  • RAID 6 has similar performance advantages and disadvantages as RAID 5.
  • Nested RAID may also be used to increase fault tolerance where high reliability is required. For example, two storage device sets, each configured as RAID 5, may be mirrored in a RAID 0 configuration. The resulting configuration may be called RAID 50. If RAID 6 is used for each mirrored set, the configuration may be called RAID 60. Nested RAID configurations typically have similar performance issues as the underlying RAID groups.
  • FIG 10 is a schematic block diagram illustrating one embodiment of a system 1600 for progressive RAID in accordance with the present inventions.
  • the system 1600 includes N storage devices 150 and M parity-mirror storage devices 1602 accessible through a computer network 116 by one or more clients 114.
  • the N storage devices 150 and parity-mirror storage devices 1602 may be located in one or more servers 112.
  • the storage devices 150, servers 112, computer network 116, and clients 114 are substantially similar to those described above.
  • the parity-mirror devices 1602 are typically similar or identical to the N storage devices 150 and are typically designated as a parity-mirror storage device 1602 for a stripe.
  • the N storage devices 150 and M parity-mirror storage devices 1602 are included in or accessible through one server 112 and may be networked together using a system bus, SAN, or other computer network 116. In another embodiment, the N storage devices 150 and M parity-mirror storage devices 1602 are located in or accessible through multiple servers 112a-n+m. For example, the storage devices 150 and parity-mirror storage devices 1602 may be part of an in-server SAN as described above in relation to the system 103 of Figure 1C and the method 105 of Figure 5B.
  • a parity-mirror storage device 1602 stores all parity data segments of the stripes stored in the progressive RAID.
  • a storage device 150 of the storage device set 1604 assigned to the progressive RAID is assigned to be a parity- mirror storage device 1602 for a particular stripe and the assignment is rotated so that the parity data segments are rotated, for each stripe, among the N+M storage devices 150.
  • This embodiment offers a performance advantage over assigning a single storage device 150 to be a parity-mirror storage device 1602 for each stripe. By rotating the parity-mirror storage device 1602, the overhead associated with calculating and storing parity data segments can be distributed.
  • the storage devices 150 are solid-state storage devices 102, each with associated solid-state storage 110 and a solid-state storage controller 104.
  • each storage device 150 includes a solid-state storage controller 104 and associated solid-state storage 110 acts as cache for other less expensive, lower performance storage, such as tape storage or hard disk drives.
  • one or more of the servers 112 include one or more clients 114 that send storage requests to the progressive RAID.
  • One of skill in the art will recognize other system configurations with N storage devices 150 and one or more parity-mirror storage devices 1602 that may be configured for progressive RAID.
  • FIG. 17 is a schematic block diagram illustrating one embodiment of an apparatus 1700 for progressive RAID in accordance with the present invention.
  • the apparatus 1700 includes, in various embodiments, a storage request receiver module 1702, a striping module 1704, a parity- mirror module 1706, and a parity progression module 1708, a parity alteration module 1710, a mirrored set module 1712, an update module 1714, a mirror restoration module 1716 with a direct client response module 1718, a pre-consolidation module 1720, a post-consolidation module 1722, a data rebuild module 1724, and a parity rebuild module 1726, which are described below.
  • the modules 1702-1726 are depicted in a server 112, but some or all of the functions of the modules 1702-1726 may also be distributed in multiple servers 112, storage controllers 152, storage devices 150, clients 114, etc.
  • the apparatus 1700 includes a storage request receiver module 1702 that receives a request to store data, where the data is data of a file or of an object.
  • the storage request is an object request.
  • the storage request is a block storage request.
  • the storage request in one embodiment, does not include data, but includes commands that can be used by the storage devices 150 and parity-mirror storage devices 1602 to DMA or RDMA data from a client 114 or other source.
  • the storage request includes data to be stored as a result of the storage request.
  • the storage request includes one command capable of having the data stored in the storage device set 1604.
  • the storage request includes multiple commands.
  • One of skill in the art will recognize other storage requests to store data appropriate for progressive RAID.
  • the data is stored in a location accessible to the apparatus 1700.
  • the data is available in a random access memory ("RAM"), such as a RAM used by the client 114 or server.
  • RAM random access memory
  • the data is stored in a hard disk drive, tape storage, or other mass storage device.
  • the data is configured as an object or as a file.
  • the data is configured as a data block which is part of an object or a file.
  • the apparatus 1700 includes a striping module 1704 that calculates a stripe pattern for the data.
  • the stripe pattern includes one or more stripes, where each stripe includes a set of N data segments.
  • the number of data segments in a stripe depends on how many storage devices 150 are assigned to the RAID group. For example, if RAID 5 is used, one storage device 150 is assigned as a parity-mirror storage device 1602a to store parity data for a particular stripe. If four other storage devices 150a, 150b, 150c, 150d are assigned to the RAID group, a stripe will have four data segments in addition to the parity data segment.
  • the striping module 1704 writes N data segments to N of a stripe to N storage devices 150a-n so that each of the N data segments is written to a separate storage device 150a, 150b, ... 150n within a set 1604 of storage devices 150 assigned to the stripe.
  • One of skill in the art will appreciate various combinations of storage devices 150 that may be assigned to a RAID group for a particular RAID level and how to create a striping pattern and divide data into N data segments per stripe.
  • the apparatus 1700 includes a parity-mirror module 1706 that writes a set of N data segments of the stripe to one or more parity-mirror storage devices 1602 within the storage device set 1604, where the parity-mirror storage devices 1602 are in addition to the N storage devices 150.
  • the N data segments are then available for future calculation of a parity data segment.
  • the parity-mirror module 1706 copies the set of N data segments to the parity-mirror storage devices 1602, which typically requires less time than storing the N data segments. Once the N data segments are stored on the parity-mirror storage device 1602, the N data segments are available to be read or used to restore data if one of the N storage devices 150 becomes unavailable.
  • Reading data also has the advantages of a RAID 0 configuration because all of the N data segments are available together from one storage device (e.g. 1602a).
  • the parity-mirror module 1706 copies the N data segments to each parity-mirror storage device 1602a, 1602b.
  • the apparatus 1700 includes a parity progression module 1708 that calculates one or more parity data segments for the stripe in response to a storage consolidation operation.
  • the one or more parity data segments calculated from the N data segments are stored on the parity- mirror storage devices 1602.
  • the parity progression module 1708 stores a parity data segment on each of the one or more parity-mirror storage devices 1602.
  • the storage consolidation operation is conducted to recover at least storage space or data or both on at least one of the one or more parity-mirror storage devices 1602.
  • a storage consolidation operation may be a data garbage collection on a solid-state storage device 102 as described above in relation to the apparatus 800 and method 900 of Figures 8 and 9.
  • the storage consolidation operation may also include a defragmentation operation for a hard disk drive, or other similar operation that consolidates data to increase storage space.
  • the storage consolidation operation as used herein, may also include an operation to recover data, for example, if a storage device 150 is unavailable, to recover from an error, or other reason for reading data from the parity-mirror storage device 1602.
  • the parity generation module 1708 simply calculates the parity data segment when the parity-mirror storage device 1602 is less busy.
  • the N data segments on the parity-mirror storage device 1602 are available for reading the data segments, recovering data, rebuilding data on a storage device 150 until more storage space is needed on the parity-mirror storage device 1602 or other reason for a storage consolidation operation.
  • the parity progression module 1708 may then run as a background operation, autonomously from the storage request receiver module 1702, the striping module 1704, or the parity-mirror module 1706.
  • One of skill in the art will easily recognize other reasons to delay calculation of a parity data segment as part of a progressive RAID operation.
  • the apparatus 1700 includes a parity alternation module 1710 that alternates, for each stripe, which of the storage devices 150 within the storage device set 1604 are assigned to be the one or more parity-mirror storage devices 1602 for the stripe. As discussed above in relation to the system 1600 of Figure 10, by rotating which storage device 150 is used for the parity-mirror storage device for a stripe, the work calculation of the various parity data segments is spread among the storage devices 150 of a storage device set 1604.
  • the storage device set 1604 is a first storage device set and the apparatus 1700 includes a mirrored set module 1712 that creates one or more storage device sets in addition to the first storage set 1604 so that each of the one or more additional storage device sets include at least an associated striping module 1704 that writes the N data segments to N storage devices 150 of each of the one or more additional storage sets.
  • each of the one or more additional storage device sets includes an associated a parity-mirror module 1706 for storing a set of the N data segments and a parity progression module 1708 for calculating one or more parity data segments.
  • the mirrored set module 1712 creates one or more mirrored storage device sets
  • the RAID may be a nested RAID such as RAID 50.
  • the RAID level may be progressed from a RAID 10 where data is striped and mirrored, to a RAID 50 or RAID 60, where a parity data segment is calculated and stored for each storage device set 1604.
  • the apparatus 1700 includes and update module 1714.
  • the update module 1714 is typically used where the N data segments on a parity-mirror storage device 1602 have not been progressed to a parity data segment.
  • the update module 1714 receives an updated data segment, where the updated data segment corresponds to an existing data segment of the N data segments stored on the N storage devices 150.
  • the update module 1714 copies the updated data segment to the storage device 150 of the stripe where the existing data segment is stored and to the one or more parity-mirror storage devices 1602 of the stripe.
  • the update module 1714 replaces the existing data segment stored on the storage device 150 of the N storage devices 150a-n with the updated data segment and replaces the corresponding existing data segment stored on the one or more parity-mirror storage devices 1602 with the updated data segment.
  • replacing a data segment includes writing the data segment to a storage device 150 and then marking a corresponding data segment as invalid for subsequent garbage collection.
  • An example of this embodiment is described for solid-state storage 110 and the garbage collection apparatus described above in relation to Figures 8 and 9.
  • replacing a data segment includes overwriting an existing data segment with an updated data segment.
  • the set of storage devices 1604 is a first storage device set and the apparatus 1700 includes a mirror restoration module 1716 that recovers a data segment stored on a storage device 150 of the first storage set 1604 where the storage device 150 of the first storage set 1604 is unavailable.
  • the data segment is recovered from a mirror storage device containing a copy of the data segment.
  • the mirror storage device includes one of a set of one or more storage devices 150 that stores a copy of the N data segments.
  • the mirror restoration module 1716 recovers the data segment in response to a read request from a client 114 to read the data segment.
  • the mirror restoration module 1716 also includes a direct client response module 1718 that sends the requested data segment to the client 114 from the mirror storage device. In this embodiment, the requested data segment is copied to the client 114 so that the client 114 does not have to wait until the data segment is recovered before transmitting the data segment on to the client 114.
  • the apparatus 1700 includes a pre-consolidation restoration module 1720 that recovers a data segment stored on a storage device 150 of the storage set 1604 in response to a request to read the data segment.
  • the storage device 150 is unavailable and the data segment is recovered from the a parity-mirror storage device 1602 prior to the parity progression module 1708 generating the one or more parity data segments on the one or more parity-mirror storage devices 1602.
  • the apparatus 1700 includes a post-consolidation restoration module 1724 that recovers a data segment stored on a storage device 150 of the storage set.
  • the storage device 150 is unavailable and the data segment is recovered using one or more parity data segments stored on one or more of the parity-mirror storage devices 150 after the parity progression module 1708 generates the one or more parity data segments.
  • the post-consolidation restoration module 1724 uses a parity data segment and available data segments on the available N storage devices 150 to recreate the missing data segment.
  • the apparatus 1700 includes a data rebuild module 1724 that stores a recovered data segment on a replacement storage device in a rebuild operation, where the recovered data segment matches an unavailable data segment stored on an unavailable storage device 150.
  • the unavailable storage device 150 is one of the N storage devices 150 of the storage device set 1602.
  • the rebuild operation occurs after a failure of the storage device 150 that stores the unavailable data segment.
  • the rebuild operation is to restore data segments onto the replacement storage device to match data segments stored previously on the unavailable storage device 150.
  • the data segment may be recovered for the rebuild operation from several sources.
  • the data segment may be recovered from a parity-mirror storage device 1602 prior to progression if the matching data segment resides on the parity-mirror storage device 1602.
  • the data segment may be recovered from a mirror storage device containing a copy of the unavailable data segment.
  • the data segment is recovered from the mirror storage device if the recovered data segment does not reside on the one or more parity-mirror storage devices 1602, but may be recovered from the mirror storage device even if the matching data segment is available on the mirror storage device.
  • a regenerated data segment is regenerated from one or more parity data segments and available data segments of the N data segments if the recovered data segment does not reside on a parity-mirror storage device 1604 or the mirror storage device.
  • the missing data segment is regenerated only if it does not exist on another storage device 150 in some form.
  • the apparatus 1700 includes a parity rebuild module 1726 that rebuilds a recovered parity data segment on a replacement storage device in a parity rebuild operation where the recovered parity data segment matches an unavailable parity data segment stored on an unavailable parity-mirror storage device.
  • the unavailable parity-mirror storage device is one of the one or more parity-mirror storage devices 1602.
  • the parity rebuild operation restores parity data segments onto the replacement storage device to match parity data segments stored previously on the unavailable parity-mirror storage device.
  • data used for the rebuild may be from various sources.
  • the recovered parity data segment is recovered using a parity data segment stored on a parity-mirror storage device 1602 in a second set of storage devices 150 storing a mirror copy of the stripe. Where a mirror copy is available, using the mirrored parity data segment is desirable because the recovered parity data segment does not have to be recalculated.
  • the recovered parity data segment is regenerated from the N data segments stored on one of the N storage devices 150 if the N data segments are available on the N storage devices. Typically, the N data segments would be available on the N storage devices 150 where a single failure occurs on the parity-mirror storage device 1602 being rebuilt.
  • the recovered parity data segment is regenerated from one or more storage devices 150 of the second set of storage devices 150 storing copies of the N data segments if one or more of the N data segments are unavailable from the N storage devices 150 of the first storage device set 1604 and a matching parity data segment is not available on the second set of storage devices 150.
  • the recovered parity data segment is regenerated from the available data segments and non-matching parity data segments regardless of their location within the one or more sets of storage devices 150. Where the parity-mirror storage device is alternated among the storage devices 150 of the storage device set 1604, typically the data rebuild module 1724 and the parity rebuild module 1726 act in conjunction to rebuild data segments and parity data segments on a rebuilt storage device 150.
  • the data rebuild module 1724 and the parity rebuild module 1726 can rebuild two storage devices after a failure of two storage devices 150, 1602 of the storage device set 1604.
  • a parity-mirror storage device 1602 is not progressed to create a parity-mirror data segment
  • recovery of a data segment or a storage device 150 is quicker than if the parity-mirror storage device 1602 is progressed and the parity data segment for a stripe has been calculated and stored and the N data segments on the parity-mirror storage device 1602 used to calculate the parity data segment have been deleted.
  • FIG 18 is a schematic block diagram illustrating one embodiment of an apparatus 1800 for updating a data segment using progressive RAED in accordance with the present invention.
  • the apparatus 1800 pertains to a RAID group where one or more of the parity-mirror storage devices 1602 have been progressed and include a parity daa segment and not the N data segments used to create the parity data segment.
  • the apparatus 1800 includes an update receiver module 1802, an update copy module 1804, a parity update module 1806, which are described below.
  • the modules 1802-1806 of the apparatus 1800 are depicted in a server 112, but may be in a storage device 150, a client 114, or any combination of devices, or may be distributed among several devices.
  • a stripe, data segments, storage devices 150, a storage device set 1604, parity data segments, and the one or more parity-mirror storage device 1602 are substantially similar to a stripe as describe above in relation to the apparatus 1700 of Figure 17.
  • the apparatus 1800 includes an update receiver module 1802 that receives an updated data segment where the updated data segment corresponds to an existing data segment of an existing stripe.
  • the update receiver module 1802 may also receive multiple updates and may handle the updates together or separately.
  • the apparatus 1800 includes an update copy module 1804 that copies the updated data segment to the storage device 150 where the corresponding existing data segment is stored and to the one or more parity-mirror storage devices 1602 corresponding to the existing stripe.
  • the update copy module 1804 copies the updated data segment to either the parity-mirror storage device 1602 or to the storage device 150 storing the existing data segment and then verifies that a copy of the updated data segment is forwarded to the other device 1602, 150.
  • the apparatus 1800 includes a parity update module 1806 that calculates one or more updated parity data segments for the one or more parity-mirror storage devices of the existing stripe in response to a storage consolidation operation.
  • the storage consolidation operation is similar to the storage consolidation operation described above in relation to the apparatus 1700 in Figure 17.
  • the storage consolidation operation is conducted to recover at least storage space and/or data on one or more parity-mirror storage devices 1602 with the one or more updated parity data segments. By waiting to update the one or more parity data segments, the " update can be postponed until it is more convenient or until necessary to consolidate storage space.
  • the updated parity data segment is calculated from the existing parity data segment, the updated data segment, and the existing data segment.
  • the existing data segment is maintained in place prior to reading the existing data segment for generation of the updated parity data segment.
  • the existing data segment is copied to the data-mirror storage • device 1602 when the storage device 150 of the N storage devices 150a-n where the existing data segment is stored receives a copy of the updated data segment. The existing data segment is then stored until the storage consolidation operation.
  • the existing data segment is copied to the data-mirror storage device 1602 in response to a storage consolidation operation on the storage device 150 of the N storage devices 150a-n where the existing data segment is stored if the storage consolidation operation occurs before the storage consolidation operation that triggers calculation of the updated parity data segment.
  • the latter embodiment is advantageous because the existing data segment is not copied until required by a storage consolidation operation on either the storage device 150 where the existing data segment is stored or on the parity-mirror storage device 1602.
  • the updated parity data segment is calculated from the existing parity data segment, the updated data segment, and a delta data segment, where the delta data segment is generated as a difference between the updated data segment and the existing data segment.
  • generating a delta data segment is a partial solution or intermediate step in updating the parity data segment.
  • Generating a delta data segment is advantageous because it may be highly compressible and may be compressed before transmission.
  • the delta data segment is stored on the storage device storing the existing data segment prior to reading the delta data segment for generation of the updated parity data segment.
  • the delta data segment is copied to the data-mirror storage device 1602 when the storage device 150 where the existing data segment is stored receives a copy of the updated data segment.
  • the delta data segment is copied to the data-mirror storage device 1602 in response to a storage consolidation operation on the storage device 150 where the existing data segment is stored.
  • the latter embodiment is advantageous because the delta data file is not moved until the earlier of a storage consolidation operation on the storage device 150 storing the existing data segment or another storage consolidation operation triggering calculation of the updated parity data segment.
  • all of a portion of the actions of the modules 1802, 1804, 1806, namely receiving an updated data segment, copying the updated data segment, and calculating the updated parity data segment, occurs on a storage device 150 of the storage device set 1604, a client 114, or a third-party RAID management device.
  • the storage consolidation operation is conducted autonomously from the operations of the update receiver module 1802 and the update copy module 1804.
  • FIG 19 is a schematic flow chart diagram illustrating an embodiment of a method 1900 for managing data using progressive RAIDing in accordance with the present invention.
  • the method 1900 begins 1902 and the storage request receiver module 1702 receives 1904 a request to store data, where the data is data of a file or of an object.
  • the striping module 1704 calculates a stripe pattern for the data and writes 1906 the N data segments to N storage devices 150.
  • the stripe pattern includes one or more stripes.
  • Each stripe includes a set of N data segments where each of the N data segments is written to a separate storage device 150 within a set of storage devices 1604 assigned to the stripe.
  • the parity-mirror module 1706 writes 1908 a set of N data segments of the stripe to one or more parity-mirror storage devices 1602 within the set of storage devices 1604.
  • the one or more parity-mirror storage devices are in addition to the N storage devices 150a-n.
  • the parity generation module 1708 determines 1910 if there is a pending storage consolidation operation. If the parity generation module 1708 determines 1910 that there is no pending storage consolidation operation, the method 1900 returns and again determines 1910 if there is a pending storage consolidation operation. In other embodiments, the storage request receiver module 1702, the striping module 1704, and the parity-mirror module 1706, continue to receive storage requests, calculate striping patterns, and storing data segments.
  • the parity generation module 1708 determines 1910 that there is no pending storage consolidation operation, the parity generation module 1708 calculates 1914 a parity data segment for the stripe.
  • the parity data segment is calculated from the N data segments stored on a parity-mirror storage device 1602.
  • the parity generation module 1708 stores 1912 the parity data segment on the parity-mirror storage devicel602 and the method 1900 ends 1916.
  • the storage consolidation operation is conducted autonomously from receiving 1904 a request to store N data segments, writing 1906 the N data segments to the N storage devices, or writing 1908 the N data segments to one or more parity-mirror storage devices.
  • the storage consolidation operation is conducted to recover at least storage space or data on the parity-mirror storage device 1602.
  • Figure 20 is a schematic flow chart diagram illustrating an embodiment of a method 2000 for updating a data segment using progressive RAIDing in accordance with the present invention.
  • the method 2000 begins 2002 and the update receiver module 1802 receives 2004 an updated data segment where the updated data segment corresponds to an existing data segment of an existing stripe.
  • the update copy module 1804 copies 2006 the updated data segment to the storage device 150 where the corresponding existing data segment is stored and to the one or more parity-mirror storage devices 1602 corresponding to the existing stripe.
  • the parity update module 1806 determines 2008 if a storage consolidation operation is pending. If the parity update module 1806 determines 2008 that there is no pending storage consolidation operation, the parity update module 1806 waits for a storage consolidation operation. In one embodiment, the method 2000 returns and receives 2004 other updated data segments and copies 2006 the updated data segments. If the parity update module 1806 determines 2008 that there is no pending storage consolidation operation, the parity update module 1806 calculates 2010 one or more updated parity data segments for the one or more parity-mirror storage devices of the existing stripe and the method 2000 ends 2012. FRONT-END DISTRIBUTED RAID
  • RAID controller that functions to receive data, calculate striping patterns for the data, divide the data into data segments, calculate a parity stripe, store the data on storage devices, update the data segments, etc. While some RAID controllers allow some functions to be distributed, the storage devices managed by the RAID controller do not communicate with clients 114 directly for storing data striped in a RAID. Instead storage requests and data for RAIDing pass through the storage controller.
  • Requiring the RAID controller to touch all of the data to be stored in a RAID is inefficient because it creates a dataflow bottleneck. This is especially true during a read-modify- write process where bandwidth and performance of all of the drives in the RAID group is consumed while only a subset is actually updated.
  • the a region of the storage device designated for data managed by the RAID controller is typically dedicated to the RAID group and cannot be accessed independently. Access to a storage device 150 by a client must typically be accomplished by partitioning the storage device 150. Where partitioning is used, partitions accessible for general storage are not used for RAID and partitions allocated to the RAID group are not accessible for general data storage. Schemes that oversubscribe partitions in order to globally optimize utilization are complex and more difficult to manage.
  • storage space allocated for one RAID group cannot be accessed by more than one RAID controller unless one is designated as master and other RAID controllers act as slaves unless the master RAID controller is inactive, non-functional, etc.
  • Typical RAID controllers also generate parity data segments outside of the storage devices 150 of the RAID group. This can be inefficient because parity data segments are typically generated and then are sent to a storage device 150 for storage, which requires computing capacity of the RAID controller. Tracking parity data segment location and updates must also be done at the RAID controller instead of autonomously at a storage device 150.
  • RAID controllers are typically cross connected to the drives and to each other, and/or mirrored as complete sets, making data availability expensive and difficult to manage, and dramatically reducing the reliability of the storage subsystem.
  • a RAID group can be created for one data segment, object, or file and managed within one group of storage devices by one RAID controller while a second RAID group may be created for another data segment, object, or file that encompasses some of the same storage devices of the first RAID group.
  • the RAID control functions may be distributed among clients 114, a third-party RAID management device, or among storage devices 150.
  • the front-end distributed RAID system, apparatus, and method may also send commands to storage devices 150 of a RAID group and may allow the storage devices 150 to directly access and copy data through direct memory access (“DMA”), or remote DMA (“RDMA").
  • DMA direct memory access
  • RDMA remote DMA
  • Figure 10 is a schematic block diagram illustrating one embodiment of a system 1600 that may be accessed for a front-end distributed RAID in accordance with the present inventions.
  • the storage device set 1604 forms a RAID group and includes storage devices 150 that are autonomous and are capable of independently receiving and servicing storage requests from a client 114 over a network 116 or one or more redundant networks 116.
  • the storage devices 150 within the storage device set 1604 one or more are designated as parity-mirror storage devices 1602 for a stripe.
  • the one or more parity- mirror storage devices 1602 function substantially similar to the other storage devices 150.
  • the parity-mirror storage devices 1602 In typical configurations where the designated parity-mirror storage devices 1602 alternate among the storage devices 150 of the storage device set 1604, the parity-mirror storage devices 1602 have essentially the same characteristics as the other storage devices 150 because they must also operate as non-parity-mirror storage devices. The similar characteristics are with respect to operation within a RAID group and autonomous operation for independent client 114 communication as described above. In various embodiments, the storage devices 150 of the storage device set 1604 may differ in other aspects not related to functioning within the described RAID environment. -
  • the storage devices 150 of the storage device set 1604 may be stand alone, grouped within one or more servers 112, may each reside in a server 112, may be accessed through one or more servers 112, etc.
  • One or more clients 114 may reside in servers 112 that include one or more storage devices 150, may reside in separate servers 112, may reside in computers, workstations, laptops, etc. -that access the storage devices 150 through one or more computer networks 116, or the like.
  • the network 116 includes a system bus and one or more of the storage devices 150, 1602 of the storage device set 1604 communicate using the system bus.
  • the system bus may be a PCI-e bus, a Serial Advanced Technology Attachment ("serial ATA") bus, parallel ATA, or the like.
  • the system bus is an external bus such as small computer system interface (“SCSI”), FireWire, Fiber Channel, USB, PCIe-AS, Infiniband, or the like.
  • SCSI small computer system interface
  • FireWire FireWire
  • Fiber Channel Universal Serial Bus
  • USB Peripheral Component Interconnect Express
  • PCIe-AS Peripheral Component Interconnect Express
  • Infiniband or the like.
  • FIG 11 is a schematic block diagram illustrating one embodiment of an apparatus 2100 for front-end distributed RAID in accordance with the present invention.
  • the apparatus 2100 includes a storage request receiver module 2102, a striping association module 2104, a parity-mirror association module 2106, a storage request transmitter module 2108, a front-end parity generation module 2110, a parity alternation module 2112, a data segment recovery module 2114, a data rebuild module 2116, a parity rebuild module 2118, and a peer-to-peer communication module 2120, which are described below.
  • the apparatus 2100 may be included in a storage device 150 such as a solid-state storage device 102, a storage device controller 152 such as a solid-state storage controller 104, a server 112, a third-party RAID management device, etc. or may be distributed among more than one component.
  • a storage device 150 such as a solid-state storage device 102
  • a storage device controller 152 such as a solid-state storage controller 104
  • server 112 a third-party RAID management device, etc. or may be distributed among more than one component.
  • the apparatus 2100 includes a storage request receiver module 2102 that receives a storage request to store data in a storage device set 1604.
  • the data may be a portion of a file or an object or may be an entire file or object.
  • a file may include a block of arbitrary information, or resource for storing information, which is available to a computer program.
  • a file may include any data structure accessed by a processor.
  • a file may include a database, a string of text, computer code, etc.
  • An object is typically a data structure for object-oriented programming and may include a structure with or without data. In one embodiment, an object is a subset of a file. In another embodiment, an object is independent of a file. In any case, an object and a file are defined herein to include the entire set of data, data structures, computer code, and other information that may be stored on a storage device.
  • the storage device set 1604 includes autonomous storage devices 150 forming a RAID group that independently receive storage requests from a client 114 over one or more networks 116.
  • One or more of the autonomous storage devices 150 within the storage device set 1604 are designated as parity-mirror storage devices 1602 for a stripe.
  • Other storage requests from another client 114 may be stored on a second storage device set where the second storage device set may include one or more of the same storage devices 150 (and parity-mirror storage devices 1602) as the first storage device set 1604.
  • the storage devices 150 common to both storage device sets 1604 may have overlapping assigned storage space within the common storage devices 150.
  • the apparatus 2100 includes a striping association module 2104 that calculates a stripe pattern for the data.
  • the stripe pattern includes one or more stripes.
  • Each stripe includes of a set of N data segments.
  • the N data segments of a stripe may also include one or more empty data segments.
  • the striping association module 2104 associates each of the N data segments with one of N storage devices 150a-n in the storage device set 1604 assigned to the stripe.
  • the striping association module 2104 associates a data segment with a storage device 150 with a storage request to be sent the storage device 150 that directs the storage device 150 to get data corresponding to the data segment from the client -114 sending the storage request.
  • the storage request is substantially free of data of the data segments.
  • Substantially free of data means that the storage request generally does not include the data that is the subject of the storage request but may include characters, character strings, etc. that may be part of the data.
  • the storage request may include an indication that the data includes a series of zeros without including all of the zeros contained in the data.
  • the storage request includes commands that allow the N storage devices 150a-n to retrieve the data using a DMA or RDMA operation or the like.
  • the striping association module 2104 associates a data segment with a storage device 150 by identifying in a storage request to be sent to the storage device 150 the data of the data segment. Identifying the data of the data segment may include a data segment identifier, a data segment location or address, a data segment length, or other information that will allow the storage device 150 to recognize which data comprises the data segment.
  • the striping association module 2104 associates a data segment with a storage device 150 in a storage request so that a client 114 can send data comprising the data segments in a broadcast so that each storage device 150 is able to store associated data segments and discard data corresponding to data segments not assigned to the storage device 150.
  • the striping association module 2104 associates a data segment with a storage device 150 in a storage request, possibly by addressing each data segment, so that a client 1 14 can send data comprising the data segments in a multicast so that each storage device 150 is able to store associated data segments and discard data corresponding to data segments not assigned to the storage device 150.
  • One of skill in the art will recognize other ways for the striping module 2104 to associate a data segment with a storage device 150 to broadcast, multicast, unicast, anycast, etc. one or more data segments to the one or more storage devices.
  • the striping association module 2104 associates a data segment with a storage device 150 in a storage request so that a client 114 can broadcast, multicast, unicast, etc. the storage request and each storage device 150 is able to receive a portion of the storage request from the client 1 14 pertaining to the data segment associated with the storage device 150 and can discard portions the storage request that do not pertain to the one or more data segments not associated with the storage device 150.
  • the storage request received by the storage request receiver module 2102 includes the data that is the subject of the storage request and the striping association module 2104 associates a data segment with a storage device 150 by preparing a storage request for the storage device 150 that includes data segment.
  • the striping association module 2104 may operate within a client 114, a third-party RAID management device, a storage device 150, 1602, etc.
  • the apparatus 2100 includes a parity-mirror association module 2106 that associates a set of the N data segments with one or more parity-mirror storage devices 1602 in the storage device set 1604.
  • the one or more parity-mirror storage devices 1602 are in addition to the N storage devices 150a-n.
  • the parity-mirror association module 2106 associates a set of N data segments to each parity-mirror storage device 1602 so each parity-mirror storage device 1602 can receive and store the N data segments of a stripe for generating a parity data segment.
  • the parity-mirror association module 2106 associates a data segment of the stripe with each parity-mirror storage device 1602 so that the parity-mirror storage devices 1602a-m act as a mirror to the N data segments stored on the N storage devices 150a-n.
  • the parity-mirror association module 2106 associates the set of N data segments with the one or more parity-mirror storage devices 1602 using a single storage request, multiple storage requests, or other association technique described above in relation to the striping association module 2104, such as storage requests setting the parity-mirror storage device 1602 up for DMA, RDMA, broadcasts, multicasts, or including the N data segments in the storage requests.
  • the parity-mirror association module 2106 may operate within a client 114, a third-party RAID management device, a storage device 150, 1602, etc.
  • the apparatus 2100 includes a storage request transmitter module 2108 that transmits one or more storage requests to each storage device 150, 1602 in the storage device set 1604, each storage request sufficient to store onto the storage device 150, 1602 the one or more data segments associated with the storage device 150, 1602 receiving the storage request.
  • each storage request does not include data that is the subject of the storage request.
  • each storage request enables the N storage devices 150 and parity- mirror storage devices 1602 of the storage device set 1604 to download data of an associated data segment using DMA or RDMA.
  • a storage request contains sufficient information to pick out relevant storage requests or relevant data for the associated data segments from a broadcast from the client 114.
  • a storage request includes the data of an associated data segment.
  • each storage request identifies the storage devices 150, 1602 that are part of the storage device set 1604 of a stripe.
  • an identification of the storage devices 150, 1604 of the storage device set 1604 in the event of a failure of a storage device 150 acting as master, another storage device 150 may take over as master for managing the RAIDed data.
  • the identification of the storage device set 1604 enables the autonomous storage devices 150, 1602 to recover data when a storage device is off-line, and rebuild data when a replacement storage device is added within the storage device set 1604 independent of the client.
  • the identification of the storage devices 150, 1602 of the storage device set 1604 represents a multi-cast group for transmission of data segments or storage requests. The identification may be stored along with metadata for the object or file stored on the storage devices 150, 1602 within the storage device set 1604.
  • the apparatus 2100 when the parity-mirror association module 2106 associates a set of N data segments with each of the one or more parity-mirror storage devices 1602, the apparatus 2100 includes a front-end parity generation module 2110 that calculates, independent of a client 114, a parity data segment for the stripe and stores the parity data segment on the parity-mirror storage device 1602. The parity data segment is calculated from the set of N data segments provided to the parity-mirror storage device 1602.
  • the front-end parity generation module 2110 typically generates the various parity data segments so that two or more storage devices 150, 1602 in the storage device set 1604 may fail and the parity data segment information allows for recovery of unavailable data segments or parity data segments.
  • the front-end parity generation module 2110 calculates the parity data segment when operating within a storage device 150 of the storage device set 1604 and/or a third party RAID management device.
  • a server 112 separate from the client 114 transmitting the storage request may calculate the parity data segment.
  • the front-end parity generation module 2110 operates within a parity-mirror storage device to calculate the parity data segment.
  • a storage controller 152 in the parity-mirror storage device 1602 may act as a master storage controller for the RAID group formed by the storage device set 1604.
  • the front-end parity generation module 2110 calculates the parity data segment and then transmits the calculated parity data segment to one or more additional parity-mirror storage devices 1604 in a second set of storage devices forming a mirror.
  • This embodiment is advantageous because overhead associated with calculating a parity data segment is expended once rather than for each storage device set 1604 with the additional benefit of reducing the data traffic on the network 116.
  • the apparatus 2100 may also include, in one embodiment, a data segment recovery module 2112 that recovers a data segment stored on a storage device 150 of the storage device set 1604 if the storage device 150 is unavailable and a request is received to read either the unavailable data segment or data that includes the unavailable data segment.
  • the data segment is recovered using the data segments on available storage devices 150 of the storage device set 1604, a combination of the parity data segments and the data segments on available storage devices 150, 1602 of the storage device set 1604, or from a mirror storage device containing a copy of the data segment.
  • the mirror storage device is one storage device 150 of a mirror storage device set that stores a copy of the N data segments.
  • the data segment recovery module 2112 may operate and recover the unavailable data segment from a storage device 150, a parity-mirror storage device 1602, a third-party RAID management device, a mirror storage device, etc.
  • the apparatus 2100 includes a data rebuild module 2114 that stores a recovered data segment on a replacement storage device 150 in a rebuild operation. For example, if a storage device 150 becomes unavailable due to failure, loss of synchronization, etc. the data rebuild module 2114 may rebuild a storage device 150 to replace the unavailable storage device 150.
  • the rebuilt storage device 150 is the original storage device 150 that has been made available.
  • the recovered data segment matches an unavailable data segment stored on the unavailable storage device 150 of the storage device set 1604.
  • the rebuild operation typically restores one or more of data segments and parity data segments onto the replacement storage device 150 to match data segments and parity data segments stored previously on the unavailable storage device 150.
  • the recovered data segment is recovered for the rebuild operation using the available data segments on available storage devices 150 of the storage device set 1602. In another embodiment, the recovered data segment is recovered for the rebuild operation using a combination of a parity data segment from one or more of the parity-mirror storage devices 1602 and the available data segments on available storage devices 150 of the storage device set 1604. In another embodiment, the recovered data segment is recovered for the rebuild operation using a matching data segment read from a parity-mirror storage device 1602. In yet another embodiment, the recovered data segment is recovered for the rebuild operation using a matching data segment from a mirror storage device.
  • the data rebuild module 21 14 could operate and store a received data segment from a client 114, a third party RAID management device, a storage device 150, 1602, a mirror storage device, etc.
  • the apparatus 2100 includes, in another embodiment, a parity rebuild module 2116 that rebuilds the recovered parity data segment on a replacement storage device 1602 in a rebuild operation.
  • a rebuild operation is substantially similar to the rebuild operation described in relation to the data rebuild module 2114.
  • the parity rebuild module 2116 operates similar to the data rebuild module 21 14 except the parity rebuild module 2116 rebuilds a recovered parity data segment.
  • the recovered parity data segment matches an unavailable parity data segment stored on an unavailable parity-mirror storage device 1602 assigned to the stripe.
  • the parity data segment is recovered, in various embodiments, by copying the parity data segment stored on a parity-mirror storage device 1602 in a mirrored storage device set, copying the parity data segment from a parity-mirror storage device 1602 in the storage device set 1604 (if identical to the unavailable parity data segment), generating the parity data segment using one or more of the N data segments and parity data segments stored on the available storage devices 150, 1602 of the storage device set 1604 and a mirror storage device containing a copy of a data segment, etc.
  • the data rebuild module 2116 may operates and stores a recovered data segment while residing on a client 1 14, a third party RAID management device, a storage device 150, a mirror storage device, etc.
  • the apparatus 2100 is not limited to storing data in the storage devices 150, 1602 to partitions dedicated to the front-end, distributed RATD operation described herein.
  • an autonomous storage device e.g. 150a
  • one or more storage requests received by the storage request receiver module 2102 or transmitted by the storage request transmitter module 2108 identify the storage devices 150 that comprise the storage device set 1604 of the stripe.
  • identifying the storage device 150 of the storage device set 1604 in the storage requests facilitates a backup RAID controller to operate if a master controller is non-functional. For example, if the storage devices 150 of the storage device set 1604 are identified in storage requests and the master controller is in a parity-mirror storage device 1602 and is unavailable, another parity-mirror storage device 1602 or another of the N storage devices 150a-n may become the master controller.
  • the apparatus 2100 includes a parity alternation module 2118 that alternates, for each stripe, which storage devices 150 in the storage device set 1604 are designated as the parity-mirror storage devices 1602 for the stripe.
  • the benefits of the parity alternation module 2118 are described above.
  • the storage devices 150 of the storage device set 1604 form a group of peers and the apparatus 2100 includes a peer-to-peer communication module 2120 that transmits and receives storage requests within the storage devices 150, 1602 of the storage device set 1604.
  • the peer-to-peer communication module 2120 may also transmit and receive storage requests with peer devices outside the storage device set 1604.
  • the storage request is an object request to store an object by striping data of the object across the storage devices 150, 1602 of the storage device set 1604 using the modules 2102-2120 of the apparatus 2100.
  • one or more of the autonomous storage devices 150, 1602 of the storage device set 1604 are allocated within a first RAID group for at least a portion of a first object or file and allocated within a second RAID group for at least a portion of a second object or file.
  • one storage device 150a may be a master RAID controller for the storage device set 1604 for one or more stripes and a second storage device 150b may be a master RAID controller for a RAID group that includes some or all of the storage devices 150 of the storage device set.
  • FIG. 12 is a schematic flow chart diagram illustrating an embodiment of a method 2200 for front-end distributed RAID in accordance with the present invention.
  • the method 2200 begins 2202 and the storage request receiver module 2102 receives 2204 a storage request to store data in N storage devices 150a-n of the storage device set 1604.
  • the striping association module 2104 calculates 2206 a stripe pattern for the data and associates 2208 the N data segments each with one of the N storage devices 150a-n.
  • the parity-mirror association module 2106 associates 2210 a set of N data segments with one or more parity-mirror storage devices 1602.
  • the storage request transmitter module 2108 transmits 2212 one or more storage requests to each storage device 150, 1602 in the storage device set 1604. Each storage request is sufficient to store onto the storage device 150 the one or more data segments associated with the storage device 150 receiving the storage request.
  • the data segments of the data are then transferred to the storage devices 150, 1602 of the storage device set 1604 using DMA, RDMA, broadcast, multicast, etc. as directed by the storage requests.
  • the front-end parity generation module 2110 calculates 2214 a parity data segment for the stripe and the method 2200 ends 2216. SHARED, FRONT-END, DISTRIBUTED RAID
  • RAID utilizes an array of disks or other storage devices with at least a portion of each device dedicated to the RAID and forming a RAID group.
  • a RAID controller manages storage requests to the RAID group. For redundant systems, the RAID controller has a backup RAID controller ready to take over if the master RAID controller fails or is unavailable. Storage requests from multiple clients that seek to access the same data stored in the RAID are typically sequentially executed in order of arrival.
  • a front-end, distributed RAID system as described above in relation to the system 1600, apparatus 2100, and method 2200 depicted in Figures 10, 11, and 12 respectively, includes autonomous storage devices 150 that may each include a storage controller 152 that can function as a distributed RAID controller and the storage devices 150 can each be configured in multiple, overlapping RAID groups serving multiple clients 114. Occasionally, two clients 114 may seek to access the same data. If one storage request arrives first and executes, then typically there is no inconsistency of the data. If, on the other hand, two or more storage requests for the same data arrive at the same time or nearly the same time, the data may be corrupted.
  • the first storage device 150a may commence execution of the storage request on the first storage device 150a then the other storage devices 150b-n of the RAID group.
  • the second RAID controller on the second storage device 150b may commence execution of the second storage request on another storage device (e.g. 150b) and then on the remaining storage devices 150a,c-n of the RAID group. This mismatch in execution may be caused by physical distance between the storage devices 150, execution time discrepancies, etc. The result may be corrupted data.
  • Figure 10 is a schematic block diagram illustrating one embodiment that serves as a system 1600 for shared, front-end distributed RAID in accordance with the present inventions, in addition to progressive RAID and front-end distributed RAID.
  • the storage device set 1604 forms a RAID group and includes storage devices 150 that are autonomous and are capable of independently receiving and servicing storage requests from a client 114 over a network 116.
  • the system 1600 includes two or more clients 114 such that the two or more clients 114 each send a storage request relating to the same data.
  • the storage requests are concurrent in that the storage requests arrive such that one storage request is not completed prior to arrival of another of another storage request.
  • one or more are designated as parity- mirror storage devices 1602 for a stripe.
  • the one or more parity-mirror storage devices 1602 function substantially similar to the other storage devices 150.
  • the parity-mirror storage devices 1602 In typical configurations where the designated parity-mirror storage devices 1602 alternate among the storage devices 150 of the storage device set 1604, the parity-mirror storage devices 1602 have essentially the same characteristics as the other storage devices 150 because they must also operate as non-parity-mirror storage devices. The similar characteristics are with respect to operation within a RAID group and autonomous operation for independent client 114 communication as described above. In various embodiments, the storage devices 150 of the storage device set 1604 may differ in other aspects not related to functioning within the described RAID environment.
  • the storage devices 150 of the storage device set 1604 may be stand alone, grouped within one or more servers 112, may each reside in a server 112, may be accessed through one or more servers 112, etc.
  • One or more clients 114 may reside in servers 112 that include one or more storage devices 150, may reside in separate servers 112, may reside in computers, workstations, laptops, etc. that access the storage devices 150 through a computer network 116, or the like.
  • the network 116 includes a system bus and one or more of the storage devices 150, 1602 of the storage device set 1604 communicate using the system bus.
  • the system bus may be a PCI-e bus, a Serial Advanced Technology Attachment ("serial ATA") bus, parallel ATA, or the like.
  • the system bus is an external bus such as small computer system interface (“SCSI”), FireWire, Fiber Channel, USB, PCIe-AS, Infiniband, or the like.
  • SCSI small computer system interface
  • FireWire FireWire
  • Fiber Channel Universal Serial Bus
  • USB PCIe-AS
  • Infiniband or the like.
  • FIG. 13 is a schematic block diagram illustrating one embodiment of an apparatus 2300 for shared, front-end distributed RAID in accordance with the present invention.
  • the apparatus 2300 includes, in various embodiments, a multiple storage request receiver module 2302, a striping module 2304, a parity-mirror module 2306, a sequencer module 2308, a master validation module 2310, master determination module 2312, a master error module 2314, parity generation module 2316, and a parity alternation module 2318, which are described below.
  • the apparatus 2300 includes a multiple storage request receiver module 2302 that receives at least two storage requests from at least two clients 114 to store data in the storage devices 150 of the storage device set 1602.
  • the data includes data of a file or of an object.
  • the storage requests of concern to the apparatus each have at least a portion of the data in common and, in addition, are concurrent storage requests by arriving such that one storage request is not completed before to arrival of the storage requests. These concurrent storage requests run the risk of corrupting the common data in a front-end distributed RAID system 1600.
  • the concurrent storage requests may be from one client 114.
  • the concurrent storage requests are from two or more clients 114.
  • the multiple storage requests may update one or more data segments stored on the storage devices 150 of the storage device set 1602 where the previously stored data is striped by the striping module 2304 into data segments stored on the storage devices 150 of the storage device set 1604.
  • a storage request writes the data for the first time to the RAID group. In this case, the data typically would have existed elsewhere and accessed by one or more clients 114 and then one storage request copies the data to the RAID group while another storage request concurrently accesses the data.
  • the multiple storage requests may comprise one request to update one or more data segments stored on the storage devices 150 of the storage device set 1602 and one or more read requests targeting at least a portion of the data in common. If the update request is not complete, then the read requests response from the storage devices 150 of the storage device set 1602 may be comprised of a combination of pre-existing and updated data that corrupts the data.
  • the apparatus 2300 includes a striping module 2304 that calculates, for each of the concurrent storage requests, a stripe pattern for the data and writes N data segments of a stripe to N storage devices 150a-n within the storage device set 1604.
  • the stripe pattern includes one or more stripes and each stripe includes a set of N data segments. Each of the N data segments is written to a separate storage device 150 within the storage device set 1604 and assigned to the stripe.
  • the apparatus 2300 includes a parity-mirror module 2306 that writes, for each of the concurrent storage requests, a set of N data segments of the stripe to the storage devices 150 within the storage device set 1604 designated as parity-mirror storage devices 1602.
  • the parity- mirror storage devices 1602 are in addition to the N storage devices 150a-n.
  • the striping module 2304 is also used to calculate the identity of one or more storage devices 150a-n from which to read one or more data segments that are part of a file or object.
  • the apparatus 2300 includes a sequencer module 2308 that ensures completion of a first storage request from a first client 114 before executing a second storage request from a second client 114 where the at least two concurrent storage requests include the first and second storage requests.
  • the sequencer module 2308 ensures completion of the first storage request before executing two or more other concurrent storage requests.
  • the sequencer module 2308 facilitates an orderly execution of concurrent storage requests to prevent corruption of data.
  • the sequencer module 2308 coordinates execution of the concurrent storage requests by using a master controller that all storage requests must access for the data, by using a locking system, a two-phase commit, or other means known to those in the art. Some of the methods used by the sequencer module 2308 are discussed below.
  • the sequencer module 2308 ensures completion of the first storage request prior to execution of concurrent storage requests by receiving an acknowledgement from each of the storage devices 150 of the storage device set 1602 that received a storage request in conjunction with the first storage request prior to execution of the second storage request. Typically, an acknowledgment acknowledges completion of a storage request. In one embodiment, each of the storage devices 150 affected by the storage request is written to and an acknowledgement received from each of the storage devices 150 prior to the sequencer module 2308 commencing execution of a second storage request.
  • Completion of a storage request may include completion of a portion of a first storage request directed to a single storage device (e.g. 150a) before execution of a portion of a pending second storage request on the same storage device 150a.
  • the sequencer module 2308 may independently verify completion of the portions of the storage request on the storage devices 150. In this embodiment, writing data segments related to a first storage request need not be held up until all data segments of the first storage request are completed.
  • the sequencer module 2308 may coordinate the various executions taking place on the storage devices 150 of the storage device set 1604 to ensure that the data is not corrupted.
  • the acknowledgment of completion of a storage request is received after the striping module 2304 and the parity-mirror module 2306 each write the data segments related to the storage request to the storage devices 150 of the storage device set 1604.
  • the acknowledgment of completion of a storage request is received after the striping module 2304 and the parity-mirror module 2306 each write the data segments related to the storage request to the storage devices 150 of the storage device set 1604 and each of the storage devices 150, 1602 confirms that the data segments have been written.
  • the sequencer module 2308 selects a first storage request for execution by selecting a storage request from among the concurrent requests that arrived first.
  • the sequencer module 2308 selects a first storage request for execution by selecting a storage request with an earliest timestamp. In another embodiment, the sequencer module 2308 selects a first storage request for execution by selecting a storage request using some selection criteria. For example, the sequencer module 2308 may select a storage request that is marked in some way by a requesting client 114 as high priority, may select a storage request from a favored client 114, etc. One of skill in the art will recognize other ways that the sequencer module 2308 may select a first storage request using some selection criteria.
  • the storage request receiver module 2302, the striping module 2304, the parity-mirror module 2306, and the sequencer module 2308 are part of a master controller (not shown) that controls and services the concurrent storage requests. All or part of the master controller may reside and operate in a client 114, a third-party RAID management device, a storage device 150 of the storage device set 1604, or a storage controller 152 in a storage device 150.
  • the sequencer module 2302 may be aware of storage requests directed to the data and may then recognize concurrent storage requests and may then sequence the concurrent storage requests in a manner that the data stored in the storage devices 150 of the storage device set is not corrupted.
  • a master controller that controls servicing of a storage request directed at the data.
  • the master controller is part of a group of two or more master controllers able to service the concurrent storage requests from one or more clients 114 where the storage requests are directed at the data stored on the storage devices 150 of the storage device set 1604.
  • a master controller may service storage requests for a first client 114 and a second master controller may services storage requests for a second client 114.
  • the first and second clients 114 may both have access to data stored on the storage devices 150 of the storage device set 1604, thus enabling concurrent storage requests.
  • One master controller may be part of one storage device 150a while the other master controller may be part of a second storage device 150b.
  • the first master controller may be part of a first storage device set 1604a and the second master controller may be part of a mirrored storage device set 1604b.
  • the apparatus 2300 may include a master validation module 2310 that confirms that a master controller servicing a received storage request is controlling execution of the storage request ahead of execution of one or more concurrent storage requests prior to execution of the received storage request.
  • the concurrent storage requests are received by other master controllers and the service request has at least a portion of the data in common with the concurrent storage requests received by the other master controllers.
  • a master controller may receive a storage request and the master validation module 2310 may then poll the other master controllers before execution of the storage request to verify that the master controller is still the master controller for the data of the storage request. Part of the validation may include verification that the master controllers can communicate with each other so that a designated master controller is verified prior to execution of the storage request. This may be useful in situations were one front-end RAID controller is designated as master and another is backup.
  • a master controller may receive a storage request to read a data segment from a file or object and the master validation module 2310 may then poll the other master controllers to verify that no updates are in progress for the file or object.
  • a master controller may use the master validation module to acquire control of the data for the storage request.
  • One way to verify that a master controller is still master for execution of a storage request is to use a three-way polling scheme where two devices/controllers must be available to vote that a controller is master for a storage request to proceed.
  • the scheme uses a device (not shown) that is a third-party to the controllers vying to be master and maintains a record of which controller is assigned to be master.
  • This master verification device may be another controller, may be a client 114 on a server, etc. and is able to communicate with controllers in the group that may act as master controller.
  • a portion of the master validation module 2310 may then reside on the master verification device with a portion of the master validation module 2310 residing in each controller.
  • the system 1600 includes a first front-end distributed RAID controller ("first controller”), a second front-end distributed RAID controller (“second controller”), each of which may be master, and a separate master verification device.
  • the first and second controllers and master verification device are all in communication with each other.
  • the master verification module 2310 may designate the first controller as master controller and the second controller as backup for data stored on the storage devices 150 of the storage device set 1604 and the master verification module 2310 may store this master information on the controllers and master verification device. As long as communication is maintained between the first controller, the second controller, and the master verification device, the master verification module 2310 can confirm that the first controller is master.
  • the master validation module 2310 can verify through communication between the master verification device and the first, master controller that the first controller is still master, and since both the first controller and the master verification device confirm that the first controller is indeed master controller, the master validation module 2310 may allow the storage request to proceed. Storage requests received by the second backup controller would not proceed because, through the master verification module 2310, the second controller recognizes it is not the master.
  • the master validation module 2310 can recognize that both the second controller and the master verification module cannot communicate with the first controller and the master verification module 2310 can designate the second, backup controller to be master and the storage request can proceed. The change in master designation may then be recorded on the second controller.
  • any storage requests for the data received by the first controller will not be executed. If communication is restored, the first controller will still not execute storage requests because both the second controller and the master verification device recognize the second controller as the master. Of course this master designation may be reset.
  • One of skill in the art will recognize a variety of static and dynamic means for assigning and reassigning the master designation to one of the master controllers.
  • the portion of the master verification module 2310 operating on the first and second controllers can verify that the first controller is master and the storage request can proceed. If the second controller receives a storage request, the portion of the master verification module 2310 operating on the first and second controllers can verify that the first controller is master and the storage request will not proceed. In other embodiments, more than two controllers are part of a polling scheme. One of skill in the art will recognize other ways that the master verification module 2310 can verify that a controller is master prior to execution of a storage request.
  • the apparatus 2300 includes a master determination module 2312.
  • the master determination module 2312 Prior to sending a storage request, the master determination module 2312 sends a master determination request to the group of master controllers. The group of master controllers then identifies which controller is designated as master for a storage request and sends back a response identifying the master controller to the master determination module 2312.
  • the master determination module 2312 receives the identification of the master controller for the storage request and directs the requesting device to send the storage request to the designated master controller.
  • the master determination module 2312 resides and operates in a client 114.
  • the master determination module 2312 resides and executes in a third-party RAID management device.
  • the master determination module 2312 resides in a storage device 150.
  • the master determination module is distributed between two more storage devices 150.
  • the apparatus 2300 includes a master error module 2314 that returns an error indication.
  • the master error module 2314 returns an error indication, in one embodiment, if a multiple storage request receiver module 2302 that is controlled by a master controller receives a storage request not controlled by the master controller.
  • the master error module 2314 returns an error indication if the master determination module 2312 or the master validation module 2310 determines that the master controller is no longer the determined master at the time of the completion of execution of the storage request. This embodiment typically occurs when a master controller begins executing a storage request and loses communication with other master controllers of the group, or, in a polling scheme, loses communication with the other master controllers and the master verification device.
  • the master error module 2312 returns an error indication if a multiple storage request receiver module 2302 controlled by a master controller receives a storage request that is not controlled by the master controller.
  • the master controller controls storage requests to one or more secondary master controllers.
  • the secondary master controllers each control storage requests for data stored on the storage devices 150, 1602 of the storage device set 1604.
  • the master controller that controls secondary master controller is also a secondary master controller for storage requests directed to data stored on the storage devices 150, 1602, of the storage device set 1604.
  • the master controller controls storage requests to one or more secondary master controllers and each secondary master controller controls storage requests for data stored on storage devices 150 of a storage device set unique to the secondary master controller.
  • the apparatus 2300 is flexible so that any of the master controllers can be. master to other controllers that act as secondary master controllers. Some secondary master controllers can share a storage device set 1604 and others can controls a different storage device set.
  • the master controller can be a parity-mirror storage device 1602 or one of the N storage devices 150a-n.
  • a secondary master controller can become a master controller when the master controller is off line or unable to determine that it is the designated master.
  • the apparatus 2300 includes a parity generation module 2316 that calculates a parity data segment for the stripe and stores the parity data segment on a parity- mirror storage device 1602.
  • the parity stripe is calculated from the set of N data segments on the parity-mirror storage device 1602. This embodiment is typical of RAID 5, RAID 6, or some other RAID levels, but is typically not included for RAID 0, RAID 1, RAID 10, etc.
  • the apparatus 2300 includes a parity alternation module
  • the parity alternation module 2318 may be used in conjunction with the striping module 2304 to calculate the identity of one or more storage devices 150a-n from which to read, write, or update one or more data segments that are part of a file or object.
  • the functions of the various modules 2302-2318 may reside together in a single master controller or may be distributed among one or more clients 114, third-party RAID management devices, and one or more storage devices 150, 1602.
  • One of skill in the art will recognize various embodiments where the functions described herein are distributed.
  • FIG 14 is a schematic flow chart diagram illustrating an embodiment of a method 2400 for shared, front-end distributed RAID in accordance with the present invention.
  • the method 2400 begins 2402 and the multiple storage request receiver module 2302 receives 2404 at least two storage requests from at least two clients 114 to read or store data in one or more storage devices 150 of a storage device set 1604.
  • the data is from a file or of an object and the storage requests each have at least a portion of the data in common and are concurrent by arriving such that one storage request is not completed prior to arrival of another of the at least two storage requests.
  • the striping module 2304 calculates 2406 a stripe pattern for the data, where the stripe pattern includes one or more stripes and each stripe includes a set of N data segments.
  • the striping module 2304 also reads or writes 2408 the N data segments of a stripe to N storage devices 150a-n within the storage device set 1604 where each of the N data segments is written to or read from a separate storage device 150.
  • the parity-mirror module 2306 writes 2410 a set of N data segments of the stripe to one or more parity-mirror storage devices 1602 within the storage device set 1604 where the parity-mirror storage devices 1602 are in addition to the N storage devices 150a-n.
  • the parity-mirror module2306 may also read 2410 data segments stored in the parity-mirror devices 1602 or a parity data segment.
  • the sequencer module 2308 ensures 2412 completion of a first storage request from a first client 114 prior to executing a second storage request from a second client 114 and the method 2400 ends 2416.
  • the first and second storage requests are concurrent storage requests.
  • cache is advantageous because data that is accessed often or that is loaded as part of an application or operating system may be stored in cache with subsequent access much quicker than when the data must be accessed through a high-capacity, non-volatile (“HCNV”) storage device, such as a hard disk drive (“HDD”), an optical drive, tape storage, etc.
  • HCNV non-volatile
  • HDD hard disk drive
  • CDS optical drive
  • tape storage etc.
  • Cache is typically included in a computer.
  • Some storage devices and systems include cache in HCNV storage devices.
  • Some HCNV storage devices contain non-volatile solid state cache; these provide benefit in reducing access times, but can only deliver performance consistent with the usually limited capability of the HCNV storage device interface.
  • Some non-volatile solid-state cache storage devices exist that are typically placed on a motherboard; these devices cannot be used in multi-client environments as no cache coherence is provided.
  • Some controllers of HCNV devices also include cache. Where redundant HCNV cache controllers are shared between multiple clients, sophisticated cache coherency algorithms are required to ensure that data is not corrupted.
  • caches are implemented in DRAM, making cache capacity a premium, and requiring relatively high power per performance. If power supporting the volatile cache is lost, data stored in the cache is lost. Typically, some battery backup is used to avoid data loss in case of power failure, with sufficient capability to flush the cache to non-volatile memory prior to failure of the batter backup. In addition, battery backup systems consume power, require redundancy, negatively impact reliability and consume space. Batteries must also be serviced on a regular basis and battery backup can be relatively expensive.
  • FIG. 15 is a schematic block diagram illustrating one embodiment of a system 3400 with solid-state storage 110 as cache for a high-capacity, non- volatile storage device in accordance with the present invention.
  • the system 3400 includes a solid-state storage device 102 with a storage controller 152 that includes a solid-state storage controller 104 and an HCLV controller 3402, solid-state storage 110, and a network interface 156.
  • the system 3400 includes a requesting device 155 connected to the solid-state storage device 102 through a computer network 116, and one or more HCNV storage devices 3404a-n.
  • a requesting device 155 connected to the solid-state storage device 102 through a computer network 116
  • HCNV storage devices 3404a-n One of skill in the art will recognize that the system 3400 depicted in Figure 15 is merely one embodiment and that many other configurations are possible that allow solid-state storage 110 to be cache for a storage device.
  • the system 3400 includes a solid-state storage device 102 with network interface 156 and a storage controller 152.
  • the network interface 156 is outside of the solid-state storage device 102.
  • the network interface 156 may be in a server 112 that may or may not include the solid-state storage device 102.
  • the solid-state storage device 102 includes a storage controller 152 that includes a solid-state storage controller 104 and a high-capacity, non- volatile ("HCNV") storage controller 3402.
  • the solid-state storage device 102 includes a solid-state storage controller 104 and an HCNV storage controller 3402 that are not in a storage controller 152.
  • the solid-state storage device 102 includes a solid-state storage controller 104 that includes an HCNV storage controller 3402, or vice-versa.
  • the system 3400 includes a solid-state storage device 102 with an integrated solid-state storage 110 and with external HCNV storage devices 3404a-n.
  • the storage controllers 152, 104, 3402 may be separate from the solid-state storage 110.
  • the controllers 152, 104, 3402 and solid-state storage 110 are included in an HCNV storage device 3404.
  • the HCNV storage device 3404 may also include a network interface 156.
  • the solid-state storage device 102, the solid-state storage controller 104, the solid-state storage 110, storage I/O bus 210, network interface 156, computer network 116, and requesting device 155 are substantially similar to other embodiments of the devices and bus described above.
  • the requesting device 155 is connected to the solid-state storage device 102, storage controller 152, solid-state storage controller 104, etc. through a system bus. Data transfers between the requesting device 155 and the solid-state storage 110 may occur over the system bus.
  • the HCNV storage devices 3404 are typically high-capacity storage devices that provide non- volatile storage and are typically slower for writing and reading data than solid-state storage 110.
  • the HCNV storage devices 3404 may also be cheaper per unit storage capacity than solid- state storage 110.
  • the HCNV storage devices 3404 may be hard disk drive ("HDD"), an optical drive, a tape storage, and the like. Providing solid-state storage 110 as cache for the HCNV storage devices 3404 typically increases speed of data access and storage.
  • HDD hard disk drive
  • optical drive an optical drive
  • tape storage and the like.
  • Providing solid-state storage 110 as cache for the HCNV storage devices 3404 typically increases speed of data access and storage.
  • One of skill in the art will recognize other benefits of solid-state storage 110 as cache for an HCNV storage device 3404.
  • the HCNV storage devices 3404 are connected to the storage controller 152 through a storage area network ("SAN"). In one embodiment, a separate SAN controller connects the HCNV storage devices 3404 to the storage controller 152. In another embodiment, the HCNV storage controller 3402 or the storage controller 152 acts as a SAN controller. One of skill in the art will recognize other ways that the HCNV storage devices 3404 may be connected in a SAN.
  • Figure 16 is a schematic block diagram illustrating one embodiment of an apparatus 3500 with solid-state storage as cache for a high-capacity, non-volatile storage device in accordance with the present invention.
  • the apparatus 3500 includes a cache front-end module 3502, a cache back-end module 3504, an object storage controller 3506, an HCNV module 3508, and a standard device emulation module 3510, which are described below.
  • the modules 3502-3510 of the apparatus 3500 are depicted in a storage controller 152 with a solid-state storage controller 104 and an HCNV storage controller 3402, but some or all of each module 3502-3510 may be included in the solid-state storage controller 104, the HCNV storage controller 3402, a server 112, an HCNV storage device 3404, or other location.
  • the apparatus 3500 includes a cache front-end module 3502 that manages data transfers associated with a storage request, where the data transfers are between the requesting device 155 and solid-state storage 110 functioning as cache for one or more HCNV storage devices 3404a-n.
  • the apparatus 3500 also includes a cache back-end module 3504 that manages data transfers between the solid-state storage 110 and the HCNV storage devices 3404a-n.
  • the data transfers may include data, metadata, and/or metadata indexes.
  • the solid-state storage 110 as described above, is an array of non-volatile, solid-state data storage elements 216, 218, 220, which are typically arranged in banks 214.
  • the solid-state storage 110 may be flash memory, nano random access memory (“nano RAM” or “NRAM”), magneto-resistive RAM (“MRAM”), dynamic RAM (“DRAM”), phase change RAM (“PRAM”), or the like.
  • NRAM nano random access memory
  • MRAM magneto-resistive RAM
  • DRAM dynamic RAM
  • PRAM phase change RAM
  • the cache front-end module 3502, the cache back-end module 3504, and the solid-state storage controller 104 operate autonomously from the requesting device 155.
  • the requesting device 155 may view the storage controller 152 with the solid-state storage controller 104 and HCNV storage controller 3402, along with the associated storage 110, 3404a-n. as a single storage device.
  • the requesting device 155 may view the HCNV storage devices 3404a-n and the solid-state storage 110 may be transparent.
  • the solid-state storage controller 104 includes an object storage controller module 3506 that services object requests from one or more requesting devices 155 and manages objects of the object requests within the solid-state storage 110.
  • the solid-state controller 104 along with the object storage controller module 3506, manage object requests as described above, and in particular as described in relation to the apparatus 200 depicted in Figure 2A.
  • the apparatus 3500 includes an HCNV RAID module 3508 that stores data cached in the solid-state storage 110 in two or more HCNV storage devices 3404a-n in redundant array of independent drives (“RAID") consistent with a RAID level.
  • the data appears to a requesting device 155 as a whole such that the RAIDing is hidden from the requesting device 155.
  • the cache front-end module 3502 may cache data from the requesting device 155 in the solid-state storage 110 and the cache back-end module 3504 may cooperate with the HCNV RAID module 3508 to stripe the data and store data segments and parity data segments in the HCNV storage devices 3404a-n consistent with a RAID level.
  • One of skill in the art will recognize other ways that data from a requesting device 155 may be RAIDed in the HCNV storage devices 3404a-n.
  • the solid-state storage 110 and the HCNV storage devices comprise a hybrid storage device within a hybrid storage device set that is configured as a RAID group.
  • the hybrid storage device set may be a front-end, distributed RAID storage device set 1604 and the hybrid storage device may be a storage device 150, 1602 in the storage device set as described above in relation to the system 1600, apparatus 2100, and method 2200 depicted in Figures 10, 1 1 , and 12 respectively.
  • a data segment cached in the solid-state storage 1 10 and later stored on an HCNV device 3404 is one of N data segments of a stripe or a parity data segment of the stripe.
  • the hybrid storage device receives storage requests from one or more clients 114 independent of data segments of a RAID stripe.
  • the hybrid storage device is a storage device 150, 4602 of a shared, front-end distributed RAID group 1604 that receives two or more simultaneous storage requests from two or more clients 114, as described above in relation to shared front-end RAID as described in relation to the system 1600, apparatus 2300, and method 2400 depicted in Figures 10, 13, and 14, respectively.
  • this embodiment ensures that the shared, redundant cache maintains coherence without additional, complex coherence algorithms and protocols.
  • the solid-state storage 110 and the HCNV storage devices 3404a- n comprise a hybrid storage device and the apparatus 3500 includes a standard device emulation module 3510 that provides access to the hybrid storage device by emulating a standard device attached to one or more requesting devices 155 prior to loading the requesting devices 155 with code specific to the operation of the hybrid storage device.
  • the standard device is supported by an industry standard BIOS. This bootstrap operation allows the hybrid device to be recognized and accessed by the requesting devices 155 with limited functionality until drivers specific to the solid-state storage controller 104, HCNV storage controller 3404, and possibly the other modules 3502-3510 of the apparatus 3500 can be loaded on the requesting devices 155.
  • the solid-state storage device 110 may be partitioned into two or more regions where one or more of the partitions are used as solid-state storage independent of the solid-state storage functioning as cache for the HCNV storage devices 3404. For example, some partitions of the solid-state storage 110 may be accessed by clients 114 for general data storage while one or more partitions are dedicated as cache for the HCNV storage devices 3404. In one embodiment, more than one client 114 (or requesting device 155) is able to send cache control messages to the cache front-end module 3502 and the cache back-end module 3504 to manage a state of one or more of files or objects stored within the solid-state storage device 1 10 and the one or more HCNV storage devices 3404. Beneficially, the ability for clients 114/requesting devices 155 to manage cache on a per file, per object, or per data segment basis provides a great deal of flexibility for sharing a solid-state storage device 110.
  • a cache control message may include a control message that causes the cache back-end module 3504 to pin a portion of an object or file in the solid-state storage 110.
  • Another cache control message may include a control message that causes the cache back-end module 3504 to unpin a portion of an object or file in the solid-state storage 110.
  • Another cache control message may include a control message that causes the cache back-end module 3404 to flush a portion of an object or file from the solid-state storage 110 to the one or more HCVN storage devices 3404.
  • Another cache control message may include a control message that causes the cache back-end module 3404 to preload a portion of an object or file to the solid-state storage 110 from the one or more HCVN storage devices 3404.
  • Another cache control message may include a control message that causes the cache back-end module 3504 to offload one or more portions of one or more objects or files from the solid-state storage to the HCVN storage devices 3404 in order to free up a determined amount of storage space in the solid-state storage 110.
  • a control message that causes the cache back-end module 3504 to offload one or more portions of one or more objects or files from the solid-state storage to the HCVN storage devices 3404 in order to free up a determined amount of storage space in the solid-state storage 110.
  • the cache control messages are communicated through metadata ("cache control metadata") for the object or file.
  • the cache control metadata in one embodiment, is persistent.
  • the cache control metadata is established through attributes set at a time of creation of the file or object.
  • the attributes may be inherited through relationship to a particular object class, defaults characteristic of specific file types, etc.
  • the cache control metadata is obtained from a file or object management system.
  • the system 3400 includes a volatile cache storage element.
  • the system 3400 may also include random access memory ("RAM”) of some type that is volatile.
  • the cache front-end module 3502 and the cache back-end module 3504 store some data in the volatile cache storage element and manage data stored in the solid-state storage 1 10 and volatile cache storage element and the back-end storage module 3504 also manages data transfers between the volatile cache storage element, the solid state storage, and the HCVN storage devices. For example, data that is not critical or may easily be recovered from another source may be stored in the volatile cache while other data may be stored in the solid-state storage 110 functioning as cache.
  • metadata and/or index metadata for objects and files stored in the HCVN storage devices 3404 is maintained within the solid-state storage device 110 and in the volatile cache storage element.
  • certain metadata may be stored in volatile cache storage element and may be used to rebuild an index if the data in the volatile cache storage element is lost.
  • metadata and index metadata is stored in the solid-state storage 110 where no volatile cache storage element is included.
  • FIG 17 is a schematic flow chart diagram illustrating one embodiment of a method 3600 with solid-state storage as cache for a high-capacity, non-volatile storage device in accordance with the present invention.
  • the method 3600 begins 3602 and the cache front-end module 3502 manages 3604 data transfers associated with a storage request, where the data transfers are between a requesting device 155 and solid-state storage 110 functioning as cache for one or more HCNV storage devices 3404a-n.
  • the cache back-end module 3504 manages 3606 data transfers between the solid-state storage 110 and the one or more HCNV storage devices 110 and the method 3600 ends 3608.
  • the method 3600 operates substantially similar as described above in relation to the apparatus 3500 of Figure 10.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Computer Hardware Design (AREA)
  • Software Systems (AREA)
  • Microelectronics & Electronic Packaging (AREA)
  • Quality & Reliability (AREA)
  • Mathematical Physics (AREA)
  • Power Engineering (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Security & Cryptography (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Techniques For Improving Reliability Of Storages (AREA)
  • Multi Processors (AREA)
  • Debugging And Monitoring (AREA)
  • Stored Programmes (AREA)
  • Storage Device Security (AREA)
  • Information Transfer Between Computers (AREA)
  • Bus Control (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
  • Signal Processing For Digital Recording And Reproducing (AREA)
  • Cooling Or The Like Of Electrical Apparatus (AREA)
  • Turbine Rotor Nozzle Sealing (AREA)
  • Information Transfer Systems (AREA)

Abstract

An apparatus, system, and method are disclosed for solid-state storage as cache for high-capacity, non-volatile storage. The apparatus, system, and method are provided with a plurality of modules including a cache front-end module and a cache back-end module. The cache front-end module manages data transfers associated with a storage request. The data transfers between a requesting device and solid-state storage function as cache for one or more HCNV storage devices, and the data transfers may include one or more of data, metadata, and metadata indexes. The solid-state storage may include an array of non-volatile, solid-state data storage elements. The cache back-end module manages data transfers between the solid-state storage and the one or more HCNV storage devices.

Description

APPARATUS, SYSTEM, AND METHOD FOR SOLID-STATE STORAGE AS CACHE FOR HIGH-CAPACΓΓY, NON- VOLATILE STORAGE
BACKGROUND OF THE INVENTION CROSS-REFERENCES TO RELATED APPLICATIONS This application claims priority to U.S. Provisional Patent Application Number
60/873,111 entitled "Elemental Blade System" and filed on December 6, 2006 for David Flynn, et al., and U.S. Provisional Patent Application Number 60/974,470 entitled "Apparatus, System, and Method for Object-Oriented Solid-State Storage" and filed on September 22, 2007 for David Flynn, et al., which are incorporated herein by reference. BACKGROUND OF THE INVENTION
FIELD OF THE INVENTION
This invention relates to managing data and more particularly relates to using solid-state storage as cache for high-capacity, non-volatile storage devices. DESCRIPTION OF THE RELATED ART In general, cache is advantageous because data that is accessed often or that is loaded as part of an application or operating system may be stored in cache with subsequent access much quicker than when the data must be accessed through a high-capacity, non-volatile ("HCNV") storage device, such as a hard disk drive ("HDD"), an optical drive, tape storage, etc. Cache is typically included in a computer. SUMMARY OF THE INVENTION
Some storage devices and systems include cache in HCNV storage devices. Some HCNV storage devices contain non-volatile solid state cache; these provide benefit in reducing access times, but can only deliver performance consistent with the usually limited capability of the HCNV storage device interface. Some non-volatile solid-state cache storage devices exist that are typically placed on a motherboard; these devices cannot be used in multi-client environments as no cache coherence is provided. Some controllers of HCNV devices also include cache. Where redundant HCNV cache controllers are shared between multiple clients, sophisticated cache coherency algorithms are required to ensure that data is not corrupted.
Typically, caches are implemented in DRAM, making cache capacity a premium, and requiring relatively high power per performance. If power supporting the volatile cache is lost, data stored in the cache is lost. Typically, some battery backup is used to avoid data loss in case of power failure, with sufficient capability to flush the cache to non-volatile memory prior to failure of the batter backup. In addition, battery backup systems consume power, require redundancy, negatively impact reliability and consume space. Batteries must also be serviced on a regular basis and battery backup can be relatively expensive.
From the foregoing discussion, it should be apparent that a need exists for an apparatus, system, and method that manage data using solid-state storage as cache. Beneficially, such an apparatus, system, and method would provide a non-volatile cache that consumes little power, provides significantly larger capacity and does not require a battery backup to maintain data stored in the cache.
The present invention has been developed in response to the present state of the art, and in particular, in response to the problems and needs in the art that have not yet been fully solved by currently available systems for managing data storage. Accordingly, the present invention has been developed to provide an apparatus, system, and method for managing the storage of data on one or more high capacity, non-volatile ("HCNV") storage devices that overcome many or all of the above-discussed shortcomings in the art.
The apparatus is provided, in one embodiment, with a plurality of modules including a cache front-end module and a cache back-end module. The cache front-end module manages data transfers associated with a storage request. The data transfers are between a requesting device and solid-state storage function as cache for one or more HCNV storage devices, and the data transfers may include one or more of data, metadata, and metadata indexes. The solid-state storage may include an array of non-volatile, solid-state data storage elements. The cache back- end module manages data transfers between the solid-state storage and the one or more HCNV storage devices.
In one embodiment of the apparatus, the cache front-end module and the cache back-end module are co-located with a solid-state storage controller that manages the solid-state storage. In a further embodiment, the cache front-end module, the cache back-end module, and the solid- state storage controller may operate autonomously from the requesting device.
In one embodiment, the apparatus includes an HCNV RAID module that stores data cached in the solid-state storage in two or more HCNV storage devices in redundant array of independent drives ("RAID") consistent with a RAID level. The data may appear to a requesting device as a whole. In another embodiment, the solid-state storage and the one or more HCNV storage devices may include a hybrid storage device within a hybrid storage device set that is configured as a RAID group. A data segment cached in the solid-state storage and later stored on an HCNV device may include one of N data segments of a stripe or a parity data segment of the stripe. The hybrid storage device typically receives storage requests from one or more clients independent of data segments of a RAID stripe. In a further embodiment, the hybrid storage device may be a storage device of a shared, front-end distributed RAID group that receives two or more simultaneous storage requests from two or more clients.
In an additional embodiment of the apparatus, the HCNV storage device may be a hard disk drive ("HDD"), an optical drive, or a tape storage. In another embodiment, the solid-state storage and the one or more HCNV storage devices may be a hybrid storage device. In one embodiment, the apparatus may also include a standard device emulation module that provides access to the hybrid storage device by emulating a standard device attached to one or more requesting devices prior to loading the one or more requesting devices with code specific to the operation of the hybrid storage device. The standard device typically may be supported by an industry standard BIOS.
In another embodiment, the solid-state storage device may be partitioned into two or more regions, wherein one or more partitions may be used as solid-state storage independent of the solid-state storage functioning as cache for the HCNV storage devices. In yet another embodiment, one or more clients send cache control messages to the cache front-end module and the cache back-end module to manage a state of one or more of files or objects stored within the solid-state storage device and the one or more HCNV storage devices.
In one embodiment of the apparatus, the cache control messages may include one or more control messages. Various embodiments of the control messages may include a control message that causes the cache back-end module to pin a portion of an object or file in the solid- state storage or a control message that causes the cache back-end module to unpin a portion of an object or file in the solid-state storage. Other embodiments of the control messages may include a control message that causes the cache back-end module to flush a portion of an object or file from the solid-state storage to the one or more HCVN storage devices or a control message causes the cache back-end module to preload a portion of an object or file to the solid-state storage from the one or more HCVN storage devices. Yet another embodiment of a control message may be a control message that causes the cache back-end module to offload one or more portions of one or more objects or files from the solid-state storage to the one or more HCVN storage devices in order to free up a determined amount of storage space in the solid-state storage. In one embodiment, the cache control messages are communicated through metadata ("cache control metadata") for the object or file. In a further embodiment, the cache control metadata may be persistent. In another embodiment, the cache control metadata may be established through attributes set at a time of creation of the file or object. In yet another embodiment, the cache control metadata may be obtained from a file or object management system. In one embodiment of the apparatus, the apparatus may include a volatile cache storage element wherein the cache front-end module and the cache back-end module store data in the volatile cache storage element and manage data stored in the solid-state storage and volatile cache storage element. The back-end storage module may further manage data transfers between the volatile cache storage element, the solid state storage, and the HCVN storage devices. In a further embodiment, metadata and/or index metadata for objects and files stored in the HCVN storage devices may be maintained within the solid-state storage device and the volatile cache storage element.
In an additional embodiment of the apparatus, metadata and/or index metadata for objects and files stored in the HCVN storage devices may be maintained within the solid-state storage device. In another embodiment, the solid-state storage and the one or more HCNV storage devices may include a storage device such that the HCNV storage devices are hidden from view of a client connected to the storage device.
A system of the present invention is also presented. The system substantially includes the modules and embodiments described above with regard to the apparatus. In one embodiment, the system includes a solid-state storage that includes an array of non-volatile, solid-state data storage elements. The system also includes one or more HCNV storage devices and a storage controller. The storage controller, in one embodiment, may include a solid-state storage controller and an HCNV storage device controller. The storage controller may also include a cache front-end module and a cache back-end module. The cache front-end module manages data transfers associated with a storage request. The data transfers are typically between a requesting device and the solid-state storage functioning as cache for the one or more HCNV storage devices. The data transfers may include one or more of data, metadata, and metadata indexes. The cache back-end module manages data transfers between the solid-state storage and the one or more HCNV storage devices.
In one embodiment, the system includes a network interface connected to the storage controller, wherein the network interface facilitates data transfers between the requesting device and the solid-state storage controller through a computer network. In another embodiment, the system includes a server that includes the solid-state storage, the one or more HCNV storage devices, and the storage controller. In yet another embodiment, the one or more HCNV storage devices are connected to the storage controller through a storage area network ("SAN").
A method of the present invention is also presented for sharing a device between multiple hosts. The method in the disclosed embodiments substantially includes the steps necessary to carry out the functions presented above with respect to the operation of the described apparatus and system. In one embodiment, the method includes managing data transfers associated with a storage request, wherein the data transfers are between a requesting device and solid-state storage functioning as cache for one or more HCNV storage devices. The data transfers may include one or more of data, metadata, and metadata indexes. The solid-state storage may include an array of non-volatile, solid-state data storage elements. The method may also include managing data transfers between the solid-state storage and the one or more HCNV storage devices.
Reference throughout this specification to features, advantages, or similar language does not imply that all of the features and advantages that may be realized with the present invention should be or are in any single embodiment of the invention. Rather, language referring to the features and advantages is understood to mean that a specific feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the present invention. Thus, discussion of the features and advantages, and similar language, throughout this specification may, but do not necessarily, refer to the same embodiment. Furthermore, the described features, advantages, and characteristics of the invention may be combined in any suitable manner in one or more embodiments. One skilled in the relevant art will recognize that the invention may be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of the invention.
These features and advantages of the present invention will become more fully apparent from the following description and appended claims, or may be learned by the practice of the invention as set forth hereinafter.
BRIEF DESCRIPTION OF THE DRAWINGS In order that the advantages of the invention will be readily understood, a more particular description of the invention briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only typical embodiments of the invention and are not therefore to be considered to be limiting of its scope, the invention will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:
Figure IA is a schematic block diagram illustrating one embodiment of a system for data management in a solid-state storage device in accordance with the present invention;
Figure IB is a schematic block diagram illustrating one embodiment of a system for object management in a storage device in accordance with the present invention; Figure 1C is a schematic block diagram illustrating one embodiment of a system for an in-server storage area network in accordance with the present invention;
Figure 2A is a schematic block diagram illustrating one embodiment of an apparatus for object management in a storage device in accordance with the present invention; Figure 2B is a schematic block diagram illustrating one embodiment of a solid-state storage device controller in a solid-state storage device in accordance with the present invention;
Figure 3 is a schematic block diagram illustrating one embodiment of a solid-state storage controller with a write data pipeline and a read data pipeline in a solid-state storage device in accordance with the present invention; Figure 4A is a schematic block diagram illustrating one embodiment of a bank interleave controller in the solid-state storage controller in accordance with the present invention;
Figure 4B is a schematic block diagram illustrating an alternate embodiment of a bank interleave controller in the solid-state storage controller in accordance with the present invention;
Figure 5A is a schematic flow chart diagram illustrating one embodiment of a method for managing data in a solid-state storage device using a data pipeline in accordance with the present invention;
Figure 5B is a schematic flow chart diagram illustrating one embodiment of a method for in-server SAN in accordance with the present invention;
Figure 6 is a schematic flow chart diagram illustrating another embodiment of a method for managing data in a solid-state storage device using a data pipeline in accordance with the present invention;
Figure 7 is a schematic flow chart diagram illustrating an embodiment of a method for managing data in a solid-state storage device using a bank interleave in accordance with the present invention; Figure 8 is a schematic block diagram illustrating one embodiment of an apparatus for garbage collection in a solid-state storage device in accordance with the present invention;
Figure 9 is a schematic flow chart diagram illustrating one embodiment of a method for garbage collection in a solid state storage device in accordance with the present invention;
Figure 10 is a schematic block diagram illustrating one embodiment of a system for progressive RAID, front-end distributed RAID, and shared, front-end distributed RAID in accordance with the present inventions;
Figure 11 is a schematic block diagram illustrating one embodiment of an apparatus for front-end distributed RAID in accordance with the present invention; Figure 12 is a schematic flow chart diagram illustrating an embodiment of a method for front-end distributed RAID in accordance with the present invention;
Figure 13 is a schematic block diagram illustrating one embodiment of an apparatus for shared, front-end distributed RAID in accordance with the present invention; Figure 14 is a schematic flow chart diagram illustrating an embodiment of a method for shared, front-end distributed RAID in accordance with the present invention;
Figure 15 is a schematic block diagram illustrating one embodiment of a system with solid-state storage as cache for a high-capacity, non-volatile storage device in accordance with the present invention; Figure 16 is a schematic block diagram illustrating one embodiment of an apparatus with solid-state storage as cache for a high-capacity, non-volatile storage device in accordance with the present invention; and
Figure 17 is a schematic flow chart diagram illustrating one embodiment of a method with solid-state storage as cache for a high-capacity, non-volatile storage device in accordance with the present invention.
DETAILED DESCRIPTION OF THE INVENTION
Many of the functional units described in this specification have been labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom VLSI circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.
Modules may also be implemented in software for execution by various types of processors. An identified module of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.
Indeed, a module of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network. Where a module or portions of a module are implemented in software, the software portions are stored on one or more computer readable media.
Reference throughout this specification to "one embodiment," "an embodiment," or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrases "in one embodiment," "in an embodiment," and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment.
Reference to a signal bearing medium may take any form capable of generating a signal, causing a signal to be generated, or causing execution of a program of machine-readable instructions on a digital processing apparatus. A signal bearing medium may be embodied by a transmission line, a compact disk, digital-video disk, a magnetic tape, a Bernoulli drive, a magnetic disk, a punch card, flash memory, integrated circuits, or other digital processing apparatus memory device.
Furthermore, the described features, structures, or characteristics of the invention may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments of the invention. One skilled in the relevant art will recognize, however, that the invention may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the invention.
The schematic flow chart diagrams included herein are generally set forth as logical flow chart diagrams. As such, the depicted order and labeled steps are indicative of one embodiment of the presented method. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more steps, or portions thereof, of the illustrated method. Additionally, the format and symbols employed are provided to explain the logical steps of the method and are understood not to limit the scope of the method. Although various arrow types and line types may be employed in the flow chart diagrams, they are understood not to limit the scope of the corresponding method. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the method. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted method. Additionally, the order in which a particular method occurs may or may not strictly adhere to the order of the corresponding steps shown. SOLID-STATE STORAGE SYSTEM
Figure IA is a schematic block diagram illustrating one embodiment of a system 100 for data management in a solid-state storage device in accordance with the present invention. The system 100 includes a solid-state storage device 102, a solid-state storage controller 104, a write data pipeline 106, a read data pipeline 108, a solid-state storage 110, a computer 112, a client 114, and a computer network 116, which are described below.
The system 100 includes at least one solid-state storage device 102. In another embodiment, the system 100 includes two or more solid-state storage devices 102. Each solid- state storage device 102 may include non- volatile, solid-state storage 110, such as flash memory, nano random access memory ("nano RAM or NRAM"), magneto-resistive RAM ("MRAM"), dynamic RAM ("DRAM"), phase change RAM ("PRAM"), etc. The solid-state storage device 102 is described in more detail with respect to Figures 2 and 3. The solid-state storage device 102 is depicted in a computer 112 connected to a client 114 through a computer network 116. In one embodiment, the solid-state storage device 102 is internal to the computer 112 and is connected using a system bus, such as a peripheral component interconnect express ("PCI-e") bus, a Serial Advanced Technology Attachment ("serial ATA") bus, or the like. In another embodiment, the solid-state storage device 102 is external to the computer 112 and is connected, a universal serial bus ("USB") connection, an Institute of Electrical and Electronics Engineers ("IEEE") 1394 bus ("FireWire"), or the like. In other embodiments, the solid-state storage device 102 is connected to the computer 112 using a peripheral component interconnect ("PCI") express bus using external electrical or optical bus extension or bus networking solution such as Infiniband or PCI Express Advanced Switching ("PCIe-AS"), or the like.
In various embodiments, the solid-state storage device 102 may be in the form of a dual- inline memory module ("DEvIM"), a daughter card, or a micro-module. In another embodiment, the solid-state storage device 102 is an element within a rack-mounted blade. In another embodiment, the solid state storage device 102 is contained within a package that is integrated directly onto a higher level assembly (e.g. mother board, lap top, graphics processor). In another embodiment, individual components comprising the solid-state storage device 102 are integrated directly onto a higher level assembly without intermediate packaging. The solid-state storage device 102 includes one or more solid-state storage controllers 104, each may include a write data pipeline 106 and a read data pipeline 108 and each includes a solid-state storage 110, which are described in more detail below with respect to Figures 2 and 3. The system 100 includes one or more computers 112 connected to the solid-state storage device 102. A computer 112 may be a host, a server, a storage controller of a storage area network ("SAN"), a workstation, a personal computer, a laptop computer, a handheld computer, a supercomputer, a computer cluster, a network switch, router, or appliance, a database or storage appliance, a data acquisition or data capture system, a diagnostic system, a test system, a robot, a portable electronic device, a wireless device, or the like. In another embodiment, a computer 112 may be a client and the solid-state storage device 102 operates autonomously to service data requests sent from the computer 112. In this embodiment, the computer 112 and solid-state storage device 102 may be connected using a computer network, system bus, or other communication means suitable for connection between a computer 112 and an autonomous solid-state storage device 102. In one embodiment, the system 100 includes one or more clients 114 connected to one or more computer 112 through one or more computer networks 116. A client 114 may be a host, a server, a storage controller of a SAN, a workstation, a personal computer, a laptop computer, a handheld computer, a supercomputer, a computer cluster, a network switch, router, or appliance, a database or storage appliance, a data acquisition or data capture system, a diagnostic system, a test system, a robot, a portable electronic device, a wireless device, or the like. The computer network 116 may include the Internet, a wide area network ("WAN"), a metropolitan area network ("MAN"), a local area network ("LAN"), a token ring, a wireless network, a fiber channel network, a SAN, network attached storage ("NAS"), ESCON, or the like, or any combination of networks. The computer network 116 may also include a network from the IEEE 802 family of network technologies, such Ethernet, token ring, WiFi, WiMax, and the like.
The computer network 116 may include servers, switches, routers, cabling, radios, and other equipment used to facilitate networking computers 112 and clients 114. In one embodiment, the system 100 includes multiple computers 112 that communicate as peers over a computer network 116. In another embodiment, the system 100 includes multiple solid-state storage devices 102 that communicate as peers over a computer network 116. One of skill in the art will recognize other computer networks 116 comprising one or more computer networks 116 and related equipment with single or redundant connection between one or more clients 114 or other computer with one or more solid-state storage devices 102 or one or more solid-state storage devices 102 connected to one or more computers 112. In one embodiment, the system 100 includes two or more solid-state storage devices 102 connected through the computer network 118 to a client 116 without a computer 1 12.
STORAGE CONTROLLER-MANAGED OBJECTS
Figure IB is a schematic block diagram illustrating one embodiment of a system 101 for object management in a storage device in accordance with the present invention. The system
101 includes one or more storage device 150, each with a storage controller 152 and one or more data storage devices 154, and one or more requesting devices 155. The storage devices 152 are networked together and coupled to one or more requesting devices 155. The requesting device 155 sends object requests to a storage device 150a. An object request may be a request to create an object, a request to write data to an object, a request to read data from an object, a request to delete an object, a request to checkpoint an object, a request to copy an object, and the like. One of skill in the art will recognize other object requests.
In one embodiment, the storage controller 152 and data storage device 154 are separate devices. In another embodiment, the storage controller 152 and data storage device 154 are integrated into one storage device 150. In another embodiment, a data storage device 154 is a solid-state storage 110 and the storage controller is a solid-state storage device controller 202. In other embodiments, a data storage device 154 may be a hard disk drive, an optical drive, tape storage, or the like. In another embodiment, a storage device 150 may include two or more data storage devices 154 of different types. In one embodiment, the data storage device 154 is a solid-state storage 1 10 and is arranged as an array of solid-state storage elements 216, 218, 220. In another embodiment, the solid-state storage 110 is arranged in two or more banks 214a-n. Solid-state storage 110 is described in more detail below with respect to Figure 2B.
The storage devices 150a-n may be networked together and act as a distributed storage device. The storage device 150a coupled to the requesting device 155 controls object requests to the distributed storage device. In one embodiment, the storage devices 150 and associated storage controllers 152 manage objects and appear to the requesting device(s) 155 as a distributed object file system. In this context, a parallel object file system is an example of a type of distributed object file system. In another embodiment, the storage devices 150 and associated storage controllers 152 manage objects and appear to the requesting device(s) 155 as distributed object file servers. In this context, a parallel object file server is an example of a type of distributed object file server. In these and other embodiments the requesting device 155 may exclusively manage objects or participate in managing objects in conjunction with storage devices 150; this typically does not limit the ability of storage devices 150 to fully manage objects for other clients 114. In the degenerate case, each distributed storage device, distributed object file system and distributed object file server can operate independently as a single device. The networked storage devices 150a-n may operate as distributed storage devices, distributed object file systems, distributed object file servers, and any combination thereof having images of one or more of these capabilities configured for one or more requesting devices 155. Fore example, the storage devices 150 may be configured to operate as distributed storage devices for a first requesting device 155a, while operating as distributed storage devices and distributed object file systems for requesting devices 155b. Where the system 101 includes one storage device 150a, the storage controller 152a of the storage device 150a manages objects may appear to the requesting device(s) 155 as an object file system or an object file server.
In one embodiment where the storage devices 150 are networked together as a distributed storage device, the storage devices 150 serve as a redundant array of independent drives ("RAID") managed by one or more distributed storage controllers 152. For example, a request to write a data segment of an object results in the data segment being stripped across the data storage devices 154a-n with a parity stripe, depending upon the RAID level. One benefit of such an arrangement is that such an object management system may continue to be available when a single storage. device 150 has a failure, whether of the storage controller 152, the data storage device 154, or other components of storage device 150.
When redundant networks are used to interconnect the storage devices 150 and requesting devices 155, the object management system may continue to be available in the presence of network failures as long as one of the networks remains operational. A system 101 with a single storage device 150a may also include multiple data storage devices 154a and the storage controller 152a of the storage device 150a may act as a RAID controller and stripe the data segment across the data storage devices 154a of the storage device 150a and may include a parity stripe, depending upon the RAID level.
In one embodiment, where the one or more storage devices 150a-n are solid-state storage devices 102 with a solid-state storage device controller 202 and solid-state storage 110, the solid- state storage device(s) 102 may be configured in a DIMM configuration, daughter card, micromodule, etc. and reside in a computer 112. The computer 112 may be a server or similar device with the solid-state storage devices 102 networked together and acting as distributed RAID controllers. Beneficially, the storage devices 102 may be connected using PCI-e, PCIe-AS, Infiniband or other high-performance bus, switched bus, networked bus, or network and may provide a very compact, high performance RAID storage system with single or distributed solid- state storage controllers 202 autonomously striping a data segment across solid-state storage 110a-n.
In one embodiment, the same network used by the requesting device 155 to communicate with storage devices 150 may be used by the peer storage device 150a to communicate with peer storage devices 150b-n to accomplish RAID functionality. In another embodiment, a separate network may be used between the storage devices 150 for the purpose of RAIDing. In another embodiment, the requesting devices 155 may participate in the RAIDing process by sending redundant requests to the storage devices 150. For example, requesting device 155 may send a first object write request to a first storage device 150a and a second object write request with the same data segment to a second storage device 150b to achieve simple mirroring.
With the ability for object handling within the storage device(s) 102, the storage controller(s) 152 uniquely have the ability to store one data segment or object using one RAID level while another data segment or object is stored using a different RAID level or without RAID striping. These multiple RAID groupings may be associated with multiple partitions within the storage devices 150. RAID 0, RAID 1, RAID5, RAID6 and composite RAID types 10, 50, 60, can be supported simultaneously across a variety of RAID groups comprising data storage devices 154a-n. One skilled in the art will recognize other RAID types and configurations that may also be simultaneously supported.
Also, because the storage controller(s) 152 operate autonomously as" RAID controllers, the RAID controllers can perform progressive RAIDing and can transform objects or portions of objects striped across data storage devices 154 with one RAID level to another RAID level without the requesting device 155 being affected, participating or even detecting the change in RAID levels. In the preferred embodiment, progressing the RAID configuration from one level to another level may be accomplished autonomously on an object or even a packet bases and is initiated by a distributed RAID control module operating in one of the storage devices 150 or the storage controllers 152. Typically, RAID progression will be from a higher performance and lower efficiency storage configuration such as RAIDl to a lower performance and higher storage efficiency configuration such as RAID5 where the transformation is dynamically initiated based on the frequency of access. But, one can see that progressing the configuration from RAID5 to RAIDl is also possible. Other processes for initiating RAID progression may be configured or requested from clients or external agents such a storage system management server request. One of skill in the art will recognize other features and benefits of a storage device 102 with a storage controller 152 that autonomously manages objects.
SOLID-STATE STORAGE DEVICE WITH IN-SERVER SAN Figure 1C is a schematic block diagram illustrating one embodiment of a system 103 for an in-server storage area network ("SAN") in accordance with the present invention. The system 103 includes a computer 112 typically configured as a server ("server 112"). Each server 112 includes one or more storage devices 150 where the server 112 and storage devices 150 are each connected to a shared network interface 156. Each storage device 150 includes a storage controller 152 and corresponding data storage device 154. The system 103 includes clients 114, 114a, 114b that are either internal or external to the servers 112. The clients 114, 114a, 114b may communicate with each server 112 and each storage device 150 through over one or more computer networks 116, which are substantially similar to those described above. The storage device 150 includes a DAS module 158, a NAS module 160, a storage communication module 162, an in-server SAN module 164, a common interface module 166, a proxy module 170, a virtual bus module 172, a front-end RAID module 174, and back-end RAID module 176, which are described below. While the modules 158-176 are shown in a storage device 150, all or a portion of each module 158-176 may be in the storage device 150, server 112, storage controller 152, or other location.
A server 112, as used in conjunction with in-server SAN, is a computer functioning as a server. The server 112 includes at least one server function, such as a file server function, but may also include other server functions as well. The servers 112 may be part of a server farm and may service other clients 114. In other embodiments, the server 112 may also be a personal computer, a workstation, or other computer that houses storage devices 150. A server 112 may access one or more storage devices 150 in the server 112 as direct attached storage ("DAS"), SAN attached storage or network attached storage ("NAS"). Storage controllers 150 participating in an in-server SAN or NAS may be internal or external to the server 112.
In one embodiment, the in-server SAN apparatus includes a DAS module 158 that configures at least a portion of the at least one data storage device 154 controlled by a storage controller 152 in a server 112 as a DAS device attached to the server 112 for servicing storage requests from at least one client 114 to the server 112. In one embodiment, a first data storage device 154a is configured as a DAS to the first server 112a while also being configured as an in- server SAN storage device to the first server 112a. In another embodiment, the first data storage device 154a is partitioned so one partition is a DAS and the other is an in-server SAN. In another embodiment, at least a portion of storage space within the first data storage device 154a is configured as a DAS to the first server 112a and the same portion of storage space on the first data storage device 154a is configured as an in-server SAN to the first server 112a. In another embodiment, the in-server SAN apparatus includes a NAS module 160 that configures a storage controller 152 as a NAS device for at least one client 114 and services file requests from the client 114. The storage controller 152 may be also configured as an in-server SAN device for the first server 112a. The storage devices 150 may directly connect to the computer network 116 through the shared network interface 156 independent from the server 112 in which the storage device 150 resides.
In one elemental form, an apparatus for in-server SAN includes a first storage controller 152a within a first server 112a where the first storage controller 152a controls at least one storage device 154a. The first server 112a includes a network interface 156 shared by the first server 112a and the first storage controller 152a. The in-server SAN apparatus includes a storage communication module 162 that facilitates communication between the first storage controller 152a and at least one device external to the first server 112asuch that the communication between the first storage controller 152a and the external device is independent from the first server 112a. The storage communication module 162 may allow the first storage controller 152a to independently access the network interface 156a for external communication. In one embodiment, the storage communication module 162 accesses a switch in the network interface 156a to direct network traffic between the first storage controller 152a and external devices.
The in-server SAN apparatus also includes an in-server SAN module 164 that services a storage request using one or both of a network protocol and a bus protocol. The in-server SAN module 164 services the storage request independent from the first server 112a and the service request is received from an internal or external client 114, 114a.
In one embodiment, the device external to the first server 112a is a second storage controller 152b. The second storage controller 152b controls at least one data storage device 154b. The in-server SAN module 164 services the storage request using communication through the network interface 156a and between the first and second storage controllers 152a, 152b independent of the first server 112a. The second storage controller 152b may be within a second server 112b or within some other device.
In another embodiment, the device external to the first server 112a is a client 114 and the storage request originates with the external client 114 where the first storage controller is configured as at least part of a SAN and the in-server SAN module 164 services the storage request through the network interface 156a independent of the first server 112a. The external client 114 may be in the second server 112b or may be external to the second server 112b. In one embodiment, the in-server SAN module 164 can service storage requests from the external client 114 even when the first server 112a is unavailable. In another embodiment, the client 114a originating the storage request is internal to the first server 112a where the first storage controller 152a is configured as at least part of a SAN and the in-server SAN module 164 services the storage request through one or more of the network interface 156a and system bus. Traditional SAN configurations allow a storage device remote from a server 1 12 to be accessed as if the storage device resides within the server 112 as direct attached storage ("DAS") so that the storage device appears as a block storage device. Typically, a storage device connected as a SAN requires a SAN protocol, such as fiber channel, Internet small computer system interface ("iSCSI"), HyperSCSI, Fiber Connectivity ("FICON"), Advanced Technology Attachment ("ATA") over Ethernet, etc. In-server SAN includes a storage controller 152 inside a server 112 while still allowing network connection between the storage controller 152a and a remote storage controller 152b or an external client 114 using a network protocol and/or a bus protocol.
Typically, SAN protocols are a form of network protocol and more network protocols are emerging, such as Infiniband that would allow a storage controller 150a, and associated data storage devices 154a, to be configured as a SAN and communicate with an external client 114 or second storage controller 152b. In another example, a first storage controller 152a may communicate with an external client 114 or second storage controller 152b using Ethernet.
A storage controller 152 may communicate over a bus with internal storage controllers 152 or clients 114a. For example, a storage controller 152 may communicate over a bus using PCI-e that may support PCI Express Input/Output Virtualization ("PCIe-IOV"). Other emerging bus protocols allow a system bus to extend outside a computer or server 112 and would allow a storage controller 152a to be configured as a SAN. One such bus protocol is PCIe-AS. The present invention is not limited to simply SAN protocols, but may also take advantage of the emerging network and bus protocols to service storage requests. An external device, either in the form of a client 114 or external storage controller 152b, may communicate over an extended system bus or a computer network 1 16. A storage request, as used herein, includes requests to write data, read data, erase data, query data, etc. and may include object data, metadata, and management requests as well as block data requests. A traditional server 1 12 typically has a root complex that controls access to devices within the server 1 12. Typically, this root complex of the server 112 owns the network interface 156 such so any communication through the network interface 156 is controlled by the server 112. However, in the preferred embodiment of the in-server SAN apparatus, the storage controller 152 is able to access the network interface 156 independently so that clients 114 may communicate directly with one or more of the storage controllers 152a in the first server 112a forming a SAN or so that one or more first storage controllers 152a may be networked together with a second storage controller 152b or other remote storage controllers 152 to form a SAN. In the preferred embodiment, devices remote from the first server 112a may access the first server 112a or the first storage controller 152a through a single, shared network address. In one embodiment, the in-server SAN apparatus includes a common interface module 166 that configures the network interface 156, the storage controller 152, and the server 112 such that the server 112 and the storage controller 152 are accessible using a shared network address.
In other embodiments, the server 1 12 includes two or more network interfaces 156. For example, the server 112 may communicate over one network interface 156 while the storage device 150 may communicate over another interface. In another example, the server 112 includes multiple storage devices 150, each with a network interface 156. One of skill in the art will recognize other configurations of a server 1 12 with one or more storage devices 150 and one or more network interfaces 156 where one or more of the storage devices 150 access a network interface 156 independent of the server 112. One of skill in the art will also recognize how these various configurations may be extended to support network redundancy and improve availability.
Advantageously, the in-server SAN apparatus eliminates much of the complexity and expense of a traditional SAN. For example, a typical SAN requires servers 112 with external storage controllers 152 and associated data storage devices 154. This takes up additional space in a rack and requires cabling, switches, etc. The cabling, switching, another other overhead required to configure a traditional SAN take space, degrade bandwidth, and are expensive. The in-server SAN apparatus allows the storage controllers 152 and associated storage 154 to fit in a server 112 form factor, thus reducing required space and costing less. In-server SAN also allows connection using relatively fast communication over internal and external high-speed data buses. In one embodiment, the storage device 150 is a solid-state storage device 102, the storage controller 152 is a solid-state storage controller 104, and the data storage device 154 is a solid- state storage 110. This embodiment is advantageous because of the speed of solid-state storage device 102 as described herein. In addition, the solid-state storage device 102 may be configured in a DIMM which may conveniently fit in a server 112 and require a small amount of space. The one or more internal clients 114a in the server 112 may also connect to the computer network 116 through the server's network interface 156 and the client's connection is typically controlled by the server 1 12. This has several advantages. Clients 114a may locally and remotely access the storage devices 150 directly and may initiate a local or remote direct memory access ("DMA," "RDMA") data transfer between the memory of a client 114a and a storage device 150.
In another embodiment, clients 114, 114a within or external to a server 112 may act as file servers to clients 114 through one or more networks 1 16 while utilizing locally attached storage devices 150 as DAS devices, network attached storage devices 150, network attached solid-state storages 102 devices participating as part of in-server SANs, external SANs, and hybrid SANs. A storage device 150 may participate in a DAS, in-server-SAN, SAN, NAS, etc, simultaneously and in any combination. Additionally, each storage device 150 may be partitioned in such a way that a first partition makes the storage device 150 available as a DAS, a second partition makes the storage device 150 available as an element in an in-server-SAN, a third partition makes the storage device 150 available as a NAS, a fourth partition makes the storage device 150 available as an element in a SAN, etc. Similarly, the storage device 150 may be partitioned consistent with security and access control requirements. One of skill in the art will recognize that any number of combinations and permutations of storage devices, virtual storage devices, storage networks, virtual storage networks, private storage, shared storage, parallel file systems, parallel object file systems, block storage devices, object storage devices, storage appliances, network appliances, and the like may be constructed and supported.
In addition, by directly connecting to the computer network 116, the storage devices 150 can communicate with each other and can act as an in-server SAN. Clients 114a in the servers 112 and clients 114 connected through the computer network 116 may access the storage devices 150 as a SAN. By moving the storage devices 150 into the servers 112 and having the ability to configure the storage devices 150 as a SAN, the server 112/storage device 150 combination eliminates the need in conventional SANs for dedicated storage controllers, fiber channel networks, and other equipment. The in-server SAN system 103 has the advantage of enabling the storage device 150 to share common resources such as power, cooling, management, and physical space with the client 114 and computer 112. For example, storage devices 150 may fill empty slots of servers 1 12 and provide all the performance capabilities, reliability and availability of a SAN or NAS. One of skill in the art will recognize other features and benefits of an in-server SAN system 103. In another configuration, multiple in-server-SAN storage devices 150a are collocated within a single server 112a infrastructure. In one embodiment, the server 112a is comprised of one or more internal bladed server clients 114a interconnected using PCI-express IO V without an external network interface 156, external client 114, 114b or external storages device 150b. In addition, in-server SAN storage device 150 may communicate through one or more computer networks 116 with peer storage devices 150 that are located in a computer 1 12 (per Figure IA), or are connected directly to the computer network 116 without a computer 112 to form a hybrid SAN which has all the capabilities of both SAN and in-server SAN. This flexibility has the benefit of simplifying extensibility and migration between a variety of possible solid-state storage network implementations. One skilled in the art will recognize other combinations, configurations, implementations, and architectures for locating and interconnecting solid-state controllers 104.
Where the network interface 156a can be controlled by only one agent operating within the server 112a, a link setup module 168 operating within that agent can set up communication paths between internal clients 114a and storage devices 150a/first storage controllers 152a through network interface 156a to external storage devices 150b and clients 114, 114b. In a preferred embodiment, once the communication path is established, the individual internal storage devices 150a and internal clients 114a are able to establish and manage their own command queues and transfer both commands and data through network interface 156a to external storage devices 150b and clients 114, 114b in either direction, directly and through RDMA independent of the proxy or agent controlling the network interface 156a. In one embodiment, the link setup module 168 establishes the communication links during an initialization process, such as a startup or initialization of hardware. In another embodiment, a proxy module 170 directs at least a portion of commands used in servicing a storage request through the first server 112a while at least data, and possibly other commands, associated with the storage request are communicated between the first storage controller and the external storage device independent of the first server. In another embodiment, the proxy module 170 forwards commands or data in behalf of the internal storage devices 150a and clients 114a.
In one embodiment, the first server 112a includes one or more servers within the first server 112a and includes a virtual bus module 172 that allows the one or more servers in the first server 112a to independently access one or more storage controllers 152a through separate virtual buses. The virtual buses may be established using an advanced bus protocol such as PCIe-IOV. Network interfaces 156a supporting IOV may allow the one or more servers and the one or more storage controllers to independently control the one or more network interfaces 156a.
In various embodiments, the in-server SAN apparatus allows two or more storage devices 150 to be configured in a RAID. In one embodiment, the in-server SAN apparatus includes a front-end RAID module 174 that configures two or more storage controllers 152 as a RAID. Where a storage request from a client 114, 114a includes a request to store data, the front-end RAID module 174 services the storage request by writing the data to the RAID consistent with the particular implemented RAID level. A second storage controller 152 may be located either in the first server 112a or external to the first server 112a. The front-end RAID module 174 allows RAIDing of storage controllers 152 such that the storage controllers 152 are visible to the client 114, 114a sending the storage request. This allows striping and parity information to be managed by a storage controller 152 designated as master or by the client 114, 114a.
In another embodiment, the in-server SAN apparatus includes a back-end RAID module 176 that configures two or more data storage devices 154 controlled by a storage controller as a RAID. Where the storage request from the client comprises a request to store data, the back-end RAID module 176 services the storage request by writing the data to the RAID consistent with an implemented RAID level such that the storage devices 154 configured as a RAID are accessed by the client 114, 114a as a single data storage device 154 controlled by the first storage controller 152. This RAID implementation allows RAIDing of the data storage devices 154 controlled by a storage controller 152 in a way that the RAIDing is transparent to any client 114, 114a accessing the data storage devices 154. In another embodiment, both front-end RAID and back-end RAID are implemented to have multi-level RAID. One of skill in the art will recognize other ways to RAID the storage devices 152 consistent with the solid-state storage controller 104 and associated solid-state storage 110 described herein.
APPARATUS FOR STORAGE CONTROLLER-MANAGED OBJECTS Figure 2A is a schematic block diagram illustrating one embodiment of an apparatus 200 for object management in a storage device in accordance with the present invention. The apparatus 200 includes a storage controller 152 with an object request receiver module 260, a parsing module 262, a command execution module 264, an object index module 266, an object request queuing module 268, a packetizer 302 with a messages module 270, and an object index reconstruction module 272, which are described below.
The storage controller 152 is substantially similar to the storage controller 152 described in relation to the system 102 of Figure IB and may be a solid-state storage device controller 202 described in relation to Figure 2. The apparatus 200 includes an object request receiver module 260 that receives an object request from one or more requesting devices 155. For example, for a store object data request, the storage controller 152 stores the data segment as a data packet in a data storage device 154 coupled to the storage controller 152. The object request is typically directed at a data segment stored or to be stored in one or more object data packets for an object managed by the storage controller. The object request may request that the storage controller 152 create an object to be later filled with data through later object request which may utilize a local or remote direct memory access ("DMA," "RDMA") transfer.
In one embodiment, the object request is a write request to write all or part of an object to a previously created object. In one example, the write request is for a data segment of an object. The other data segments of the object may be written to the storage device 150 or to other storage devices 152. In another example, the write request is for an entire object. In another example, the object request is to read data from a data segment managed by the storage controller 152. In yet another embodiment, the object request is a delete request to delete a data segment or object.
Advantageously, the storage controller 152 can accept write requests that do more than write a new object or append data to an existing object. For example, a write request received by the object request receiver module 260 may include a request to add data ahead of data stored by the storage controller 152, to insert data into the stored data, or to replace a segment of data. The object index maintained by the storage controller 152 provides the flexibility required for these complex write operations that is not available in other storage controllers, but is currently available only outside of storage controllers in file systems of servers and other computers.
The apparatus 200 includes a parsing module 262 that parses the object request into one or more commands. Typically, the parsing module 262 parses the object request into one or more buffers. For example, one or more commands in the object request may be parsed into a command buffer. Typically the parsing module 262 prepares an object request so that the information in the object request can be understood and executed by the storage controller 152. One of skill in the art will recognize other functions of a parsing module 262 that parses an object request into one or more commands. The apparatus 200 includes a command execution module 264 that executes the command(s) parsed from the object request. In one embodiment, the command execution module 264 executes one command. In another embodiment, the command execution module 264 executes multiple commands. Typically, the command execution module 264 interprets a command parsed from the object request, such as a write command, and then creates, queues, and executes subcommands. For example, a write command parsed from an object request may direct the storage controller 152 to store multiple data segments. The object request may also include required attributes such as encryption, compression, etc. The command execution module 264 may direct the storage controller 152 to compress the data segments, encrypt the data segments, create one or more data packets and associated headers for each data packet, encrypt the data packets with a media encryption key, add error correcting code, and store the data packets a specific location. Storing the data packets at a specific location and other subcommands may also be broken down into other lower level subcommands. One of skill in the art will recognize other ways that the command execution module 264 can execute one or more commands parsed from an object request.
The apparatus 200 includes an object index module 266 that creates an object entry in an object index in response to the storage controller 152 creating an object or storing the data segment of the object. Typically, the storage controller 152 creates a data packet from the data segment and the location of where the data packet is stored is assigned at the time the data segment is stored. Object metadata received with a data segment or as part of an object request may be stored in a similar way.
The object index module 266 creates an object entry into an object index at the time the data packet is stored and the physical address of the data packet is assigned. The object entry includes a mapping between a logical identifier of the object and one or more physical addresses corresponding to where the storage controller 152 stored one or more data packets and any object metadata packets. In another embodiment, the entry in the object index is created before the data packets of the object are stored. For example, if the storage controller 152 determines a physical address of where the data packets are to be stored earlier, the object index module 266 may create the entry in the object index earlier. Typically, when an object request or group of object requests results in an object or data segment being modified, possibly during a read-modify-write operation, the object index module 266 updates an entry in the object index corresponding the modified object. In one embodiment, the object index creates a new object and a new entry in the object index for the modified object. Typically, where only a portion of an object is modified, the object includes modified data packets and some data packets that remain unchanged. In this case, the new entry includes a mapping to the unchanged data packets as where they were originally written and to the modified objects written to a new location.
In another embodiment, where the object request receiver module 260 receives an object request that includes a command that erases a data block or other object elements, the storage controller 152 may store at least one packet such as an erase packet that includes information including a reference to the object, relationship to the object, and the size of the data block erased. Additionally, it may further indicate that the erased object elements are filled with zeros. Thus, the erase object request can be used to emulate actual memory or storage that is erased and actually has a portion of the appropriate memory/storage actually stored with zeros in the cells of the memory/storage.
Beneficially, creating an object index with entries indicating mapping between data segments and metadata of an object allows the storage controller 152 to autonomously handle and manage objects. This capability allows a great amount of flexibility for storing data in the storage device 150. Once the index entry for the object is created, subsequent object requests regarding the object can be serviced efficiently by the storage controller 152.
In one embodiment, the storage controller 152 includes an object request queuing module that queues one or more object requests received by the object request receiver module 260 prior to parsing by the parsing module 262. The object request queuing module 268 allows flexibility between when an object request is received and when it is executed.
In another embodiment, the storage controller 152 includes a packetizer 302 that creates one or more data packets from the one or more data segments where the data packets are sized for storage in the data storage device 154. The packetizer 302 is described below in more detail with respect to Figure 3. The packetizer 302 includes, in one embodiment, a messages module 270 that creates a header for each packet. The header includes a packet identifier and a packet length. The packet identifier relates the packet to the object for which the packet was formed.
In one embodiment, each packet includes a packet identifier that is self-contained in that the packet identifier contains adequate information to identify the object and relationship within the object of the object elements contained within the packet. However, a more efficient preferred embodiment is to store packets in containers.
A container is a data construct that facilitates more efficient storage of packets and helps establish relationships between an object and data packets, metadata packets, and other packets related to the object that are stored within the container. Note that the storage controller 152 typically treats object metadata received as part of an object and data segments in a similar manner. Typically "packet" may refer to a data packet comprising data, a metadata packet comprising metadata, or another packet of another packet type. An object may be stored in one or more containers and a container typically includes packets for no more than one unique object.
An object may be distributed between multiple containers. Typically a container is stored within a single logical erase block (storage division) and is typically never split between logical erase blocks.
A container, in one example, may be split between two or more logical/virtual pages. A container is identified by a container label that associates that container with an object. A container may contain zero to many packets and the packets within a container are typically from one object. A packet may be of many object element types, including object attribute elements, object data elements, object index elements, and the like. Hybrid packets may be created that include more than one object element type. Each packet may contain zero to many elements of the same element type. Each packet within a container typically contains a unique identifier that identifies the relationship to the object.
Each packet is associated with one container. In a preferred embodiment, containers are limited to an erase block so that at or near the beginning of each erase block a container packet can be found. This helps limit data loss to an erase block with a corrupted packet header. In this embodiment, if the object index is unavailable and a packet header within the erase block is corrupted, the contents from the corrupted packet header to the end of the erase block may be lost because there is possibly no reliable mechanism to determine the location of subsequent packets. In another embodiment, a more reliable approach is to have a container limited to a page boundary. This embodiment requires more header overhead. In another embodiment, containers can flow across page and erase block boundaries. This requires less header overhead but a larger portion of data may be lost if a packet header is corrupted. For these several embodiments it is expected that some type of RAID is used to further ensure data integrity.
In one embodiment, the apparatus 200 includes an object index reconstruction module 272 that that reconstructs the entries in the object index using information from packet headers stored in the data storage device 154. In one embodiment, the object index reconstruction module 272 reconstructs the entries of the object index by reading headers to determine the object to which each packet belongs and sequence information to determine where in the object the data or metadata belongs. The object index reconstruction module 272 uses physical address information for each packet and timestamp or sequence information to create a mapping between the physical locations of the packets and the object identifier and data segment sequence. Timestamp or sequence information is used by the object index reconstruction module 272 to replay the sequence of changes made to the index and thereby typically reestablish the most recent state.
In another embodiment, the object index reconstruction module 272 locates packets using packet header information along with container packet information to identify physical locations of the packets, object identifier, and sequence number of each packet to reconstruct entries in the object index. In one embodiment, erase blocks are time stamped or given a sequence number as packets are written and the timestamp or sequence information of an erase block is used along with information gathered from container headers and packet headers to reconstruct the object index. In another embodiment, timestamp or sequence information is written to an erase block when the erase block is recovered.
Where the object index is stored in volatile memory, an error, loss of power, or other problem causing the storage controller 152 to shut down without saving the object index could be a problem if the object index cannot be reconstructed. The object index reconstruction module 272 allows the object index to be stored in volatile memory allowing the advantages of volatile memory, such as fast access. The object index reconstruction module 272 allows quick reconstruction of the object index autonomously without dependence on a device external to the storage device 150. In one embodiment, the object index in volatile memory is stored periodically in a data storage device 154. In a particular example, the object index, or "index metadata," is stored periodically in a solid-state storage 110. In another embodiment, the index metadata is stored in a solid-state storage HOn separate from solid-state storage l lOa-i lOn-1 storing packets. The index metadata is managed independently from data and object metadata transmitted from a requesting device 155 and managed by the storage controller 152/solid-state storage device controller 202. Managing and storing index metadata separate from other data and metadata from an object allows efficient data flow without the storage controller 152/solid-state storage device controller 202 unnecessarily processing object metadata.
In one embodiment, where an object request received by the object request receiver module 260 includes a write request, the storage controller 152 receives one or more data segments of an object from memory of a requesting device 155 as a local or remote direct memory access ("DMA," "RDMA") operation. In a preferred example, the storage controller 152 pulls data from the memory of the requesting device 155 in one or more DMA or RDMA operations. In another example, the requesting device 155 pushes the data segment(s) to the storage controller 152 in one or more DMA or RDMA operations. In another embodiment, where the object request includes a read request, the storage controller 152 transmits one or more data segments of an object to the memory of the requesting device 155 in one or more DMA or RDMA operations. In a preferred example, the storage controller 152 pushes data to the memory of the requesting device 155 in one or more DMA or RDMA operations. In another example, the requesting device 155 pulls data from the storage controller 152 in one or more DMA or RDMA operations. In another example, the storage controller 152 pulls object command request sets from the memory of the requesting device 155 in one or more DMA or RDMA operations. In another example, the requesting device 155 pushes object command request sets to the storage controller 152 in one or more DMA or RDMA operations. In one embodiment, the storage controller 152 emulates block storage and an object communicated between the requesting device 155 and the storage controller 152 comprises one or more data blocks. In one embodiment, the requesting device 155 includes a driver so that the storage device 150 appears as a block storage device. For example, the requesting device 152 may send a block of data of a certain size along with a physical address of where the requesting device 155 wants the data block stored. The storage controller 152 receives the data block and uses the physical block address transmitted with the data block or a transformation of the physical block address as an object identifier. The storage controller 156 then stores the data block as an object or data segment of an object by packetizing the data block and storing the data block at will. The object index module 266 then creates an entry in the object index using the physical block-based object identifier and the actual physical location where the storage controller 152 stored the data packets comprising the data from the data block.
In another embodiment, the storage controller 152 emulates block storage by accepting block objects. A block object may include one or more data blocks in a block structure. In one embodiment, the storage controller 152 treats the block object as any other object. In another embodiment, an object may represent an entire block device, partition of a block device, or some other logical or physical sub-element of a block device including a track, sector, channel, and the like. Of particular note is the ability to remap a block device RAID group to an object supporting a different RAID construction such as progressive RAID. One skilled in the art will recognize other mappings of traditional or future block devices to objects. SOLID-STATE STORAGE DEVICE
Figure 2B is a schematic block diagram illustrating one embodiment 201 of a solid-state storage device controller 202 that includes a write data pipeline 106 and a read data pipeline 108 in a solid-state storage device 102 in accordance with the present invention. The solid-state storage device controller 202 may include a number of solid-state storage controllers 0-N 104a-n, each controlling solid-state storage 110. In the depicted embodiment, two solid-state controllers are shown: solid-state controller 0 104a and solid-state storage controller N 104n, and each controls solid-state storage 110a-n. In the depicted embodiment, solid-state storage controller 0 104a controls a data channel so that the attached solid-state storage 110a stores data. Solid-state storage controller N 104n controls an index metadata channel associated with the stored data and the associated solid-state storage 11On stores index metadata. In an alternate embodiment, the solid-state storage device controller 202 includes a single solid-state controller 104a with a single solid-state storage 110a. In another embodiment, there are a plurality of solid-state storage controllers 104a-n and associated solid-state storage 110a-n. In one embodiment, one or more solid state controllers 104a-104n-l, coupled to their associated solid-state storage 11 Oa- 11 On-I, control data while at least one solid-state storage controller 104n, coupled to its associated solid- state storage 11On, controls index metadata.
In one embodiment, at least one solid-state controller 104 is field-programmable gate array ("FPGA") and controller functions are programmed into the FPGA. In a particular embodiment, the FPGA is a Xilinx® FPGA. In another embodiment, the solid-state storage controller 104 comprises components specifically designed as a solid-state storage controller 104, such as an application-specific integrated circuit ("ASIC") or custom logic solution. Each solid-state storage controller 104 typically includes a write data pipeline 106 and a read data pipeline 108, which are describe further in relation to Figure 3. In another embodiment, at least one solid-state storage controller 104 is made up of a combination FPGA, ASIC, and custom logic components.
Solid-State Storage
The solid state storage 110 is an array of non- volatile solid-state storage elements 216, 218, 220, arranged in banks 214, and accessed in parallel through a bi-directional storage input/output ("I/O") bus 210. The storage I/O bus 210, in one embodiment, is capable of unidirectional communication at any one time. For example, when data is being written to the solid-state storage 110, data cannot be read from the solid-state storage 110. In another embodiment, data can flow both directions simultaneously. However bi-directional, as used herein with respect to a data bus, refers to a data pathway that can have data flowing in only one direction at a time, but when data flowing one direction on the bi-directional data bus is stopped, data can flow in the opposite direction on the bi-directional data bus.
A solid-state storage element (e.g. SSS 0.0 216a) is typically configured as a chip (a package of one or more dies) or a die on a circuit board. As depicted, a solid-state storage element (e.g. 216a) operates independently or semi-independently of other solid-state storage elements (e.g. 218a) even if these several elements are packaged together in a chip package, a stack of chip packages, or some other package element. As depicted, a column of solid-state storage elements 216, 218, 220 is designated as a bank 214. As depicted, there may be "n" banks 214a-n and "m" solid-state storage elements 216a-m, 218a-m, 220a-m per bank in an array of n x m solid-state storage elements 216, 218, 220 in a solid-state storage 110. In one embodiment, a solid-state storage HOa includes twenty solid-state storage elements 216, 218, 220 per bank 214 with eight banks 214 and a solid-state storage 11On includes 2 solid-state storage elements 216, 218 per bank 214 with one bank 214. In one embodiment, each solid-state storage element 216, 218, 220 is comprised of a single-level cell ("SIX:") devices. In another embodiment, each solid-state storage element 216, 218, 220 is comprised of multi-level cell ("MLC") devices.
In one embodiment, solid-state storage elements for multiple banks that share a common storage I/O bus 210a row (e.g. 216b, 218b, 220b) are packaged together. In one embodiment, a solid-state storage element 216, 218, 220 may have one or more dies per chip with one or more chips stacked vertically and each die may be accessed independently. In another embodiment, a solid-state storage element (e.g. SSS 0.0216a) may have one or more virtual dies per die and one or more dies per chip and one or more chips stacked vertically and each virtual die may be accessed independently. In another embodiment, a solid-state storage element SSS 0.0 216a may have one or more virtual dies per die and one or more dies per chip with some or all of the one or more dies stacked vertically and each virtual die may be accessed independently.
In one embodiment, two dies are stacked vertically with four stacks per group to form eight storage elements (e.g. SSS O.O-SSS 0.8) 216a-220a, each in a separate bank 214a-n. In another embodiment, 20 storage elements (e.g. SSS O.O-SSS 20.0) 216 form a virtual bank 214a so that each of the eight virtual banks has 20 storage elements (e.g. SSSO.O-SSS 20.8) 216, 218, 220. Data is sent to the solid-state storage 110 over the storage I/O bus 210 to all storage elements of a particular group of storage elements (SSS O.O-SSS 0.8) 216a, 218a, 220a. The storage control bus 212a is used to select a particular bank (e.g. Bank-0 214a) so that the data received over the storage I/O bus 210 connected to all banks 214 is written just to the selected bank 214a.
In a preferred embodiment, the storage I/O bus 210 is comprised of one or more independent I/O buses ("ϋOBa-m" comprising 210a.a-m, 210n.a-m) wherein the solid-state storage elements within each row share one of the independent I/O buses accesses each solid- state storage element 216, 218, 220 in parallel so that all banks 214 are accessed simultaneously. For example, one channel of the storage I/O bus 210 may access a first solid-state storage element 216a, 218a, 220a of each bank 214a-n simultaneously. A second channel of the storage I/O bus 210 may access a second solid-state storage element 216b, 218b, 220b of each bank 214a-n simultaneously. Each row of solid-state storage element 216, 218, 220 is accessed simultaneously. In one embodiment, where solid-state storage elements 216, 218, 220 are multi- level (physically stacked), all physical levels of the solid-state storage elements 216, 218, 220 are accessed simultaneously. As used herein, "simultaneously" also includes near simultaneous access where devices are accessed at slightly different intervals to avoid switching noise. Simultaneously is used in this context to be distinguished from a sequential or serial access wherein commands and/or data are sent individually one after the other. Typically, banks 214a-n are independently selected using the storage control bus 212. In one embodiment, a bank 214 is selected using a chip enable or chip select. Where both chip select and chip enable are available, the storage control bus 212 may select one level of a multilevel solid-state storage element 216, 218, 220. In other embodiments, other commands are used 5 by the storage control bus 212 to individually select one level of a multi-level solid-state storage element 216, 218, 220. Solid-state storage elements 216, 218, 220 may also be selected through a combination of control and of address information transmitted on storage I/O bus 210 and the storage control bus 212.
In one embodiment, each solid-state storage element 216, 218, 220 is partitioned into0 erase blocks and each erase block is partitioned into pages. A typical page is 2000 bytes
("2kB"). In one example, a solid-state storage element (e.g. SSSO.O) includes two registers and can program two pages so that a two-register solid-state storage element 216, 218, 220 has a capacity of 4kB. A bank 214 of 20 solid-state storage elements 216, 218, 220 would then have an 8OkB capacity of pages accessed with the same address going out the channels of the storage5 I/O bus 210.
This group of pages in a bank 214 of solid-state storage elements 216, 218, 220 of 8OkB may be called a virtual page. Similarly, an erase block of each storage element 216a-m of a bank 214a may be grouped to form a virtual erase block. In a preferred embodiment, an erase block of ' pages within a solid-state storage element 216, 218, 220 is erased when an erase command is < 0 received within a solid-state storage element 216, 218, 220. Whereas the size and number of erase blocks, pages, planes, or other logical and physical divisions within a solid-state storage element 216, 218, 220 are expected to change over time with advancements in technology, it is to be expected that many embodiments consistent with new configurations are possible and are consistent with the general description herein. 5 Typically, when a packet is written to a particular location within a solid-state storage element 216, 218, 220, wherein the packet is intended to be written to a location within a particular page which is specific to a of a particular erase block of a particular element of a particular bank, a physical address is sent on the storage I/O bus 210 and followed by the packet. The physical address contains enough information for the solid-state storage element 216, 218,0 220 to direct the packet to the designated location within the page. Since all storage elements in a row of storage elements (e.g. SSS 0.0-SSS 0.N 216a, 218a, 220a) are accessed simultaneously by the appropriate bus within the storage I/O bus 210a.a, to reach the proper page and to avoid writing the data packet to similarly addressed pages in the row of storage elements (SSS 0.0-SSS 0.N 216a, 218a, 220a), the bank 214a that includes the solid-state storage element SSS 0.0 216a with the correct page where the data packet is to be written is simultaneously selected by the storage control bus 212.
Similarly, a read command traveling on the storage I/O bus 212 requires a simultaneous command on the storage control bus 212 to select a single bank 214a and the appropriate page within that bank 214a. In a preferred embodiment, a read command reads an entire page, and because there are multiple solid-state storage elements 216, 218, 220 in parallel in a bank 214, an entire virtual page is read with a read command. However, the read command may be broken into subcommands, as will be explained below with respect to bank interleave. A virtual page may also be accessed in a write operation. An erase block erase command may be sent out to erase an erase block over the storage
I/O bus 210 with a particular erase block address to erase a particular erase block. Typically, an erase block erase command may be sent over the parallel paths of the storage I/O bus 210 to erase a virtual erase block, each with a particular erase block address to erase a particular erase block. Simultaneously a particular bank (e.g. bank-0 214a) is selected over the storage control bus 212 to prevent erasure of similarly addressed erase blocks in all of the banks (banks 1-N 214b-n). Other commands may also be sent to a particular location using a combination of the storage I/O bus 210 and the storage control bus 212. One of skill in the art will recognize other ways to select a particular storage location using the bi-directional storage I/O bus 210 and the storage control bus 212. In one embodiment, packets are written sequentially to the solid-state storage 110. For example, packets are streamed to the storage write buffers of a bank 214a of storage elements 216 and when the buffers are full, the packets are programmed to a designated virtual page. Packets then refill the storage write buffers and, when full, the packets are written to the next virtual page. The next virtual page may be in the same bank 214a or another bank (e.g. 214b). This process continues, virtual page after virtual page, typically until a virtual erase block is filled. In another embodiment, the streaming may continue across virtual erase block boundaries with the process continuing, virtual erase block after virtual erase block.
In a read, modify, write operation, data packets associated with the object are located and read in a read operation. Data segments of the modified object that have been modified are not written to the location from which they are read. Instead, the modified data segments are again converted to data packets and then written to the next available location in the virtual page currently being written. The object index entries for the respective data packets are modified to point to the packets that contain the modified data segments. The entry or entries in the object index for data packets associated with the same object that have not been modified will include pointers to original location of the unmodified data packets. Thus, if the original object is maintained, for example to maintain a previous version of the object, the original object will have pointers in the object index to all data packets as originally written. The new object will have pointers in the object index to some of the original data packets and pointers to the modified data packets in the virtual page that is currently being written.
In a copy operation, the object index includes an entry for the original object mapped to a number of packets stored in the solid-state storage 110. When a copy is made, a new object is created and a new entry is created in the object index mapping the new object to the original packets. The new object is also written to the solid-state storage 110 with its location mapped to the new entry. in the object index. The new object packets may be used to identify the packets within the original object that are referenced in case changes have been made in the original object that have not been propagated to the copy and the object index is lost or corrupted.
Beneficially, sequentially writing packets facilitates a more even use of the solid-state storage 110 and allows the solid-storage device controller 202 to monitor storage hot spots and level usage of the various virtual pages in the solid-state storage 110. Sequentially writing packets also facilitates a powerful, efficient garbage collection system, which is described in detail below. One of skill in the art will recognize other benefits of sequential storage of data packets.
Solid-State Storage Device Controller In various embodiments, the solid-state storage device controller 202 also includes a data bus 204, a local bus 206, a buffer controller 208, buffers 0-N 222a-n, a master controller 224, a direct memory access ("DMA") controller 226, a memory controller 228, a dynamic memory array 230, a static random memory array 232, a management controller 234, a management bus 236, a bridge 238 to a system bus 240, and miscellaneous logic 242, which are described below. In other embodiments, the system bus 240 is coupled to one or more network interface cards ("NICs") 244, some of which may include remote DMA ("RDMA") controllers 246, one or more central processing unit ("CPU") 248, one or more external memory controllers 250 and associated external memory arrays 252, one or more storage controllers 254, peer controllers 256, and application specific processors 258, which are described below. The components 244- 258 connected to the system bus 240 may be located in the computer 112 or may be other devices.
Typically the solid-state storage controller(s) 104 communicate data to the solid-state storage 1 10 over a storage I/O bus 210. In a typical embodiment where the solid-state storage is arranged in banks 214 and each bank 214 includes multiple storage elements 216, 218, 220 accessed in parallel, the storage I/O bus 210 is an array of busses, one for each row of storage elements 216, 218, 220 spanning the banks 214. As used herein, the term "storage I/O bus" may refer to one storage I/O bus 210 or an array of data independent busses 204. In a preferred embodiment, each storage I/O bus 210 accessing a row of storage elements (e.g. 216a, 218a, 220a) may include a logical-to-physical mapping for storage divisions (e.g. erase blocks) accessed in a row of storage elements 216a, 218a, 220a. This mapping allows a logical address mapped to a physical address of a storage division to be remapped to a different storage division if the first storage division fails, partially fails, is inaccessible, or has some other problem. Remapping is explained further in relation to the remapping module 314 of Figure 3. Data may also be communicated to the solid-state storage controller(s) 104 from a requesting device 155 through the system bus 240, bridge 238, local bus 206, buffer(s) 22, and finally over a data bus 204. The data bus 204 typically is connected to one or more buffers 222a- n controlled with a buffer controller 208. The buffer controller 208 typically controls transfer of data from the local bus 206 to the buffers 222 and through the data bus 204 to the pipeline input buffer 306 and output buffer 330 . The buffer controller 222 typically controls how data arriving from a requesting device can be temporarily stored in a buffer 222 and then transferred onto a data bus 204, or vice versa, to account for different clock domains, to prevent data collisions, etc. The buffer controller 208 typically works in conjunction with the master controller 224 to coordinate data flow. As data arrives, the data will arrive on the system bus 240, be transferred to the local bus 206 through a bridge 238.
Typically the data is transferred from the local bus 206 to one or more data buffers 222 as directed by the master controller 224 and the buffer controller 208. The data then flows out of the buffer(s) 222 to the data bus 204, through a solid-state controller 104, and on to the solid- state storage 110 such as NAND flash or other storage media. In a preferred embodiment, data and associated out-of-band metadata ("object metadata") arriving with the data is communicated using one or more data channels comprising one or more solid-state storage controllers 104a- 104n-l and associated solid-state storage 11 Oa- 11 On-I while at least one channel (solid-state storage controller 104n, solid-state storage 11 On) is dedicated to in-band metadata, such as index information and other metadata generated internally to the solid-state storage device 102. The local bus 206 is typically a bidirectional bus or set of busses that allows for communication of data and commands between devices internal to the solid-state storage device controller 202 and between devices internal to the solid-state storage device 102 and devices 244-258 connected to the system bus 240. The bridge 238 facilitates communication between the local bus 206 and system bus 240. One of skill in the art will recognize other embodiments such as ring structures or switched star configurations and functions of buses 240, 206, 204, 210 and bridges 238.
The system bus 240 is typically a bus of a computer 112 or other device in which the solid-state storage device 102 is installed or connected. In one embodiment, the system bus 240 may be a PCI-e bus, a Serial Advanced Technology Attachment ("serial ATA") bus, parallel ATA, or the like. In another embodiment, the system bus 240 is an external bus such as small computer system interface ("SCSI"), FireWire, Fiber Channel, USB, PCIe-AS, or the like. The solid-state storage device 102 may be packaged to fit internally to a device or as an externally connected device. The solid-state storage device controller 202 includes a master controller 224 that controls higher-level functions within the solid-state storage device 102. The master controller 224, in various embodiments, controls data flow by interpreting object requests and other requests, directs creation of indexes to map object identifiers associated with data to physical locations of associated data, coordinating DMA requests, etc. Many of the functions described herein are controlled wholly or in part by the master controller 224.
In one embodiment, the master controller 224 uses embedded controller(s). In another embodiment, the master controller 224 uses local memory such as a dynamic memory array 230 (dynamic random access memory "DRAM"), a static memory array 323 (static random access memory "SRAM"), etc. In one embodiment, the local memory is controlled using the master controller 224. In another embodiment, the master controller accesses the local memory via a memory controller 228. In another embodiment, the master controller runs a Linux server and may support various common server interfaces, such as the World Wide Web, hyper-text markup language ("HTML"), etc. In another embodiment, the master controller 224 uses a nano- processor. The master controller 224 may be constructed using programmable or standard logic, or any combination of controller types listed above. One skilled in the art will recognize many embodiments for the master controller.
In one embodiment, where the storage device 152/solid-state storage device controller 202 manages multiple data storage devices/solid-state storage HOa-n, the master controller 224 divides the work load among internal controllers, such as the solid-state storage controllers 104a- n. For example, the master controller 224 may divide an object to be written to the data storage devices (e.g. solid-state storage 110a-n) so that a portion of the object is stored on each of the attached data storage devices. This feature is a performance enhancement allowing quicker storage and access to an object. In one embodiment, the master controller 224 is implemented using an FPGA. In another embodiment, the firmware within the master controller 224 may be updated through the management bus 236, the system bus 240 over a network connected to a NIC 244 or other device connected to the system bus 240.
In one embodiment, the master controller 224, which manages objects, emulates block storage such that a computer 102 or other device connected to the storage device 152/solid-state storage device 102 views the storage device 152/solid-state storage device 102 as a block storage device and sends data to specific physical addresses in the storage device 152/solid-state storage device 102. The master controller 224 then divides up the blocks and stores the data blocks as it would objects. The master controller 224 then maps the blocks and physical address sent with the block to the actual locations determined by the master controller 224. The mapping is stored in the object index. Typically, for block emulation, a block device application program interface ("API") is provided in a driver in the computer 112, client 114, or other device wishing to use the storage device 152/solid-state storage device 102 as a block storage device.
In another embodiment, the master controller 224 coordinates with NIC controllers 244 and embedded RDMA controllers 246 to deliver just-in-time RDMA transfers of data and command sets. NIC controller 244 may be hidden behind a non-transparent port to enable the use of custom drivers. Also, a driver on a client 114 may have access to the computer network 118 through an I/O memory driver using a standard stack API and operating in conjunction with NICs 244.
In one embodiment, the master controller 224 is also a redundant array of independent drive ("RAID") controller. Where the data storage device/solid-state storage device 102 is networked with one or more other data storage devices/solid-state storage devices 102, the master controller 224 may be a RAID controller for single tier RAID, multi-tier RAID, progressive RAID, etc. The master controller 224 also allows some objects to be stored in a RAID array and other objects to be stored without RAID. In another embodiment, the master controller 224 may be a distributed RAID controller element. In another embodiment, the master controller 224 may comprise many RAID, distributed RAID, and other functions as described elsewhere.
In one embodiment, the master controller 224 coordinates with single or redundant network managers (e.g. switches) to establish routing, to balance bandwidth utilization, failover, etc. In another embodiment, the master controller 224 coordinates with integrated application specific logic (via local bus 206) and associated driver software. In another embodiment, the master controller 224 coordinates with attached application specific processors 258 or logic (via the external system bus 240) and associated driver software. In another embodiment, the master controller 224 coordinates with remote application specific logic (via the computer network 118) and associated driver software. In another embodiment, the master controller 224 coordinates with the local bus 206 or external bus attached hard disk drive ("HDD") storage controller.
In one embodiment, the master controller 224 communicates with one or more storage controllers 254 where the storage device/solid-state storage device 102 may appear as a storage device connected through a SCSI bus, Internet SCSI ("iSCSI"), fiber channel, etc. Meanwhile the storage device/solid-state storage device 102 may autonomously manage objects and may appear as an object file system or distributed object file system. The master controller 224 may also be accessed by peer controllers 256 and/or application specific processors 258.
In another embodiment, the master controller 224 coordinates with an autonomous integrated management controller to periodically validate FPGA code and/or controller software, validate FPGA code while running (reset) and/or validate controller software during power on (reset), support external reset requests, support reset requests due to watchdog timeouts, and support voltage, current, power, temperature, and other environmental measurements and setting of threshold interrupts. In another embodiment, the master controller 224 manages garbage collection to free erase blocks for reuse. In another embodiment, the master controller 224 manages wear leveling. In another embodiment, the master controller 224 allows the data storage device/solid-state storage device 102 to be partitioned into multiple virtual devices and allows partition-based media encryption. In yet another embodiment, the master controller 224 supports a solid-state storage controller 104 with advanced, multi-bit ECC correction. One of skill in the art will recognize other features and functions of a master controller 224 in a storage controller 152, or more specifically in a solid-state storage device 102. '
In one embodiment, the solid-state storage device controller 202 includes a memory controller 228 which controls a dynamic random memory array 230 and/or a static random memory array 232. As stated above, the memory controller 228 may be independent or integrated with the master controller 224. The memory controller 228 typically controls volatile memory of some type, such as DRAM (dynamic random memory array 230) and SRAM (static random memory array 232). In other examples, the memory controller 228 also controls other memory types such as electrically erasable programmable read only memory ("EEPROM"), etc. In other embodiments, the memory controller 228 controls two or more memory types and the memory controller 228 may include more than one controller. Typically, the memory controller 228 controls as much SRAM 232 as is feasible and by DRAM 230 to supplement the SRAM 232.
In one embodiment, the object index is stored in memory 230, 232 and then periodically off-loaded to a channel of the solid-state storage 11On or other non- volatile memory. One of skill in the art will recognize other uses and configurations of the memory controller 228, dynamic memory array 230, and static memory array 232.
In one embodiment, the solid-state storage device controller 202 includes a DMA controller 226 that controls DMA operations between the storage device/solid-state storage device 102 and one or more external memory controllers 250 and associated external memory arrays 252 and CPUs 248. Note that the external memory controllers 250 and external memory arrays 252 are called external because they are external to the storage device/solid-state storage device 102. In addition the DMA controller 226 may also control RDMA operations with requesting devices through a NIC 244 and associated RDMA controller 246. DMA and RDMA are explained in more detail below.
In one embodiment, the solid-state storage device controller 202 includes a management controller 234 connected to a management bus 236. Typically the management controller 234 manages environmental metrics and status of the storage device/solid-state storage device 102. The management controller 234 may monitor device temperature, fan speed, power supply settings, etc. over the management bus 236. The management controller may support the reading and programming of erasable programmable read only memory ("EEPROM") for storage of FPGA code and controller software. Typically the management bus 236 is connected to the various components within the storage device/solid-state storage device 102. The management controller 234 may communicate alerts, interrupts, etc. over the local bus 206 or may include a separate connection to a system bus 240 or other bus. In one embodiment the management bus 236 is an Inter-Integrated Circuit ("I2C") bus. One of skill in the art will recognize other related functions and uses of a management controller 234 connected to components of the storage device/solid-state storage device 102 by a management bus 236.
In one embodiment, the solid-state storage device controller 202 includes miscellaneous logic 242 that may be customized for a specific application. Typically where the solid-state device controller 202 or master controller 224 is/are configured using a FPGA or other configurable controller, custom logic may be included based on a particular application, customer requirement, storage requirement, etc. DATA PIPELINE Figure 3 is a schematic block diagram illustrating one embodiment 300 of a solid-state storage controller 104 with a write data pipeline 106 and a read data pipeline 108 in a solid-state storage device 102 in accordance with the present invention. The embodiment 300 includes a data bus 204, a local bus 206, and buffer control 208, which are substantially similar to those described in relation to the solid-state storage device controller 202 of Figure 2. The write data pipeline includes a packetizer 302 and an error-correcting code ("ECC") generator 304. In other embodiments, the write data pipeline includes an input buffer 306, a write synchronization buffer
" 308, a write program module 310, a compression module 312, an encryption module 314, a garbage collector bypass 316 (with a portion within the read data pipeline), a media encryption module 318, and a write buffer 320. The read data pipeline 108 includes a read synchronization buffer 328, an ECC correction module 322, a depacketizer 324, an alignment module 326, and an output buffer 330. In other embodiments, the read data pipeline 108 may include a media decryption module 332, a portion of the garbage collector bypass 316, a decryption module 334, a decompression module 336, and a read program module 338. The solid-state storage controller 104 may also include control and status registers 340 and control queues 342, a bank interleave controller 344, a synchronization buffer 346, a storage bus controller 348, and a multiplexer ("MUX") 350. The components of the solid-state controller 104 and associated write data pipeline 106 and read data pipeline 108 are described below. In other embodiments, synchronous solid-state storage 110 may be used and synchronization buffers 308 328 may be eliminated.
Write Data Pipeline
The write data pipeline 106 includes a packetizer 302 that receives a data or metadata segment to be written to the solid-state storage, either directly or indirectly through another write data pipeline 106 stage, and creates one or more packets sized for the solid-state storage 110. The data or metadata segment is typically part of an object, but may also include an entire object. In another embodiment, the data segment is part of a block of data, but may also include an entire block of data. Typically, an object is received from a computer 112, client 114, or other computer or device and is transmitted to the solid-state storage device 102 in data segments streamed to the solid-state storage device 102 or computer 112. A data segment may also be known by another name, such as data parcel, but as referenced herein includes all or a portion of an object or data block.
Each object is stored as one or more packets. Each object may have one or more container packets. Each packet contains a header. The header may include a header type field. Type fields may include data, object attribute, metadata, data segment delimiters (multi-packet), object structures, object linkages, and the like. The header may also include information regarding the size of the packet, such as the number of bytes of data included in the packet. The length of the packet may be established by the packet type. The header may include information that establishes the relationship of the packet to the object. An example might be the use of an offset in a data packet header to identify the location of the data segment within the object. One of skill in the art will recognize other information that may be included in a header added to data by a packetizer 302 and other information that may be added to a data packet.
Each packet includes a header and possibly data from the data or metadata segment. The header of each packet includes pertinent information to relate the packet to the object to which the packet belongs. For example, the header may include an object identifier and offset that indicates the data segment, object, or data block from which the data packet was formed. The header may also include a logical address used by the storage bus controller 348 to store the packet. The header may also include information regarding the size of the packet, such as the number of bytes included in the packet. The header may also include a sequence number that identifies where the data segment belongs with respect to other packets within the object when reconstructing the data segment or object. The header may include a header type field. Type fields may include data, object attributes, metadata, data segment delimiters (multi-packet), object structures, object linkages, and the like. One of skill in the art will recognize other information that may be included in a header added to data or metadata by a packetizer 302 and other information that may be added to a packet.
The write data pipeline 106 includes an ECC generator 304 that generates one or more error-correcting codes ("ECC") for the one or more packets received from the packetizer 302. The ECC generator 304 typically uses an error correcting algorithm to generate ECC which is stored with the packet. The ECC stored with the packet is typically used to detect and correct errors introduced into the data through transmission and storage. In one embodiment, packets are streamed into the ECC generator 304 as un-encoded blocks of length N. A syndrome of length S is calculated, appended and output as an encoded block of length N+S. The value of N and S are dependent upon the characteristics of the algorithm which is selected to achieve specific performance, efficiency, and robustness metrics. In the preferred embodiment, there is no fixed relationship between the ECC blocks and the packets; the packet may comprise more than one ECC block; the ECC block may comprise more than one packet; and a first packet may end anywhere within the ECC block and a second packet may begin after the end of the first packet within the same ECC block. In the preferred embodiment, ECC algorithms are not dynamically modified. In a preferred embodiment, the ECC stored with the data packets is robust enough to correct errors in more than two bits.
Beneficially, using a robust ECC algorithm allowing more than single bit correction or even double bit correction allows the life of the solid-state storage 110 to be extended. For example, if flash memory is used as the storage medium in the solid-state storage 110, the flash memory may be written approximately 100,000 times without error per erase cycle. This usage limit may be extended using a robust ECC algorithm. Having the ECC generator 304 and corresponding ECC correction module 322 onboard the solid-state storage device 102, the solid- state storage device 102 can internally correct errors and has a longer useful life than if a less robust ECC algorithm is used, such as single bit correction. However, in other embodiments the ECC generator 304 may use a less robust algorithm and may correct single-bit or double-bit errors. In another embodiment, the solid-state storage device 110 may comprise less reliable storage such as multi-level cell ("MLC") flash in order to increase capacity, which storage may not be sufficiently reliable without more robust ECC algorithms.
In one embodiment, the write pipeline 106 includes an input buffer 306 that receives a data segment to be written to the solid-state storage 110 and stores the incoming data segments until the next stage of the write data pipeline 106, such as the packetizer 302 (or other stage for a more complex write data pipeline 106) is ready to process the next data segment. The input buffer 306 typically allows for discrepancies between the rate data segments are received and processed by the write data pipeline 106 using an appropriately sized data buffer. The input buffer 306 also allows the data bus 204 to transfer data to the write data pipeline 106 at rates greater than can be sustained by the write data pipeline 106 in order to improve efficiency of operation of the data bus 204. Typically when the write data pipeline 106 does not include an input buffer 306, a buffering function is performed elsewhere, such as in the solid-state storage device 102 but outside the write data pipeline 106, in the computer 112, such as within a network interface card ("NIC"), or at another device, for example when using remote direct memory access ("RDMA").
In another embodiment, the write data pipeline 106 also includes a write synchronization buffer 308 that buffers packets received from the ECC generator 304 prior to writing the packets to the solid-state storage 110. The write synch buffer 308 is located at a boundary between a local clock domain and a solid-state storage clock domain and provides buffering to account for the clock domain differences. In other embodiments, synchronous solid-state storage 110 may be used and synchronization buffers 308 328 may be eliminated.
In one embodiment, the write data pipeline 106 also includes a media encryption module 318 that receives the one or more packets from the packetizer 302, either directly or indirectly, and encrypts the one or more packets using an encryption key unique to the solid-state storage device 102 prior to sending the packets to the ECC generator 304. Typically, the entire packet is encrypted, including the headers. In another embodiment, headers are not encrypted. In this document, encryption key is understood to mean a secret encryption key that is managed externally from an embodiment that integrates the solid-state storage 110 and where the embodiment requires encryption protection. The media encryption module 318 and corresponding media decryption. module 332 provide a level of security for data stored in the solid-state storage 110. For example, where data is encrypted with the media encryption module 318, if the solid-state storage 110 is connected to a different solid-state storag'e controller 104, solid-state storage device 102, or computer 112, the contents of the solid-state storage 110 typically could not be read without use of the same encryption key used during the write of the data to the solid-state storage 110 without significant effort.
In a typical embodiment, the solid-state storage device 102 does not store the encryption key in non-volatile storage and allows no external access to the encryption key. The encryption key is provided to the solid-state storage controller 104 during initialization. The solid-sate storage device 102 may use and store a non-secret cryptographic nonce that is used in conjunction with an encryption key. A different nonce may be stored with every packet. Data segments may be split between multiple packets with unique nonces for the purpose of improving protection by the encryption algorithm. The encryption key may be received from a client 114, a computer 112, key manager, or other device that manages the encryption key to be used by the solid-state storage controller 104. In another embodiment, the solid-state storage 110 may have two or more partitions and the solid-state storage controller 104 behaves as though it were two or more solid-state storage controllers 104, each operating on a single partition within the solid-state storage 110. In this embodiment, a unique media encryption key may be used with each partition.
In another embodiment, the write data pipeline 106 also includes an encryption module 314 that encrypts a data or metadata segment received from the input buffer 306, either directly or indirectly, prior sending the data segment to the packetizer 302, the data segment encrypted using an encryption key received in conjunction with the data segment. The encryption module 314 differs from the media encryption module 318 in that the encryption keys used by the encryption module 318 to encrypt data may not be common to all data stored within the solid- state storage device 102 but may vary on an object basis and received in conjunction with receiving data segments as described below. For example, an encryption key for a data segment to be encrypted by the encryption module 318 may be received with the data segment or may be received as part of a command to write an object to which the data segment belongs. The solid- sate storage device 102 may use and store a non-secret cryptographic nonce in each object packet that is used in conjunction with the encryption key. A different nonce may be stored with every packet. Data segments may be split between multiple packets with unique nonces for the purpose of improving protection by the encryption algorithm. In one embodiment, the nonce used by the media encryption module 318 is the same as that used by the encryption module 314.
The encryption key may be received from a client 114, a computer 112, key manager, or other device that holds the encryption key to be used to encrypt the data segment. In one embodiment, encryption keys are transferred to the solid-state storage controller 104 from one of a solid-state storage device 102, computer 1 12, client 114, or other external agent which has the ability to execute industry standard methods to securely transfer and protect private and public keys.
In one embodiment, the encryption module 318 encrypts a first packet with a first encryption key received in conjunction with the packet and encrypts a second packet with a second encryption key received in conjunction with the second packet. In another embodiment, the encryption module 318 encrypts a first packet with a first encryption key received in conjunction with the packet and passes a second data packet on to the next stage without encryption. Beneficially, the encryption module 318 included in the write data pipeline 106 of the solid-state storage device 102 allows object-by-object or segment-by-segment data encryption without a single file system or other external system to keep track of the different encryption keys used to store corresponding objects or data segments. Each requesting device 155 or related key manager independently manages encryption keys used to encrypt only the objects or data segments sent by the requesting device 155. In another embodiment, the write data pipeline 106 includes a compression module 312 that compresses the data for metadata segment prior to sending the data segment to the packetizer 302. The compression module 312 typically compresses a data or metadata segment using a compression routine known to those of skill in the art to reduce the storage size of the segment. For example, if a data segment includes a string of 512 zeros, the compression module 312 may replace the 512 zeros with code or token indicating the 512 zeros where the code is much more compact than the space taken by the 512 zeros.
In one embodiment, the compression module 312 compresses a first segment with a first compression routine and passes along a second segment without compression. In another embodiment, the compression module 312 compresses a first segment with a first compression routine and compresses the second segment with a second compression routine. Having this flexibility within the solid-state storage device 102 is beneficial so that clients 114 or other devices writing data to the solid-state storage device 102 may each specify a compression routine or so that one can specify a compression routine while another specifies no compression. Selection of compression routines may also be selected according to default settings on a per object type or object class basis. For example, a first object of a specific object may be able to override default compression routine settings and a second object of the same object class and object type may use the default compression routine and a third object of the same object class and object type may use no compression. In one embodiment, the write data pipeline 106 includes a garbage collector bypass 316 that receives data segments from the read data pipeline 108 as part of a data bypass in a garbage collection system. A garbage collection system typically marks packets that are no longer valid, typically because the packet is marked for deletion or has been modified and the modified data is stored in a different location. At some point, the garbage collection system determines that a particular section of storage may be recovered. This determination may be due to a lack of available storage capacity, the percentage of data marked as invalid reaching a threshold, a consolidation of valid data, an error detection rate for that section of storage reaching a threshold, or improving performance based on data distribution, etc. Numerous factors may be considered by a garbage collection algorithm to determine when a section of storage is to be recovered.
Once a section of storage has been marked for recovery, valid packets in the section typically must be relocated. The garbage collector bypass 316 allows packets to be read into the read data pipeline 108 and then transferred directly to the write data pipeline 106 without being routed out of the solid-state storage controller 104. In a preferred embodiment, the garbage collector bypass 316 is part of an autonomous garbage collector system that operates within the solid-state storage device 102. This allows the solid-state storage device 102 to manage data so that data is systematically spread throughout the solid-state storage 110 to improve performance, data reliability and to avoid overuse and underuse of any one location or area of the solid-state storage 110 and to lengthen the useful life of the solid-state storage 110. The garbage collector bypass 316 coordinates insertion of segments into the write data pipeline 106 with other segments being written by clients 116 or other devices. In the depicted embodiment, the garbage collector bypass 316 is before the packetizer 302 in the write data pipeline 106 and after the depacketizer 324 in the read data pipeline 108, but may also be located elsewhere in the read and write data pipelines 106, 108. The garbage collector bypass 316 may be used during a flush of the write pipeline 106 to fill the remainder of the virtual page in order to improve the efficiency of storage within the Solid-State Storage 110 and thereby reduce the frequency of garbage collection.
In one embodiment, the write data pipeline 106 includes a write buffer 320 that buffers data for efficient write operations. Typically, the write buffer 320 includes enough capacity for packets to fill at least one virtual page in the solid-state storage 110. This allows a write operation to send an entire page of data to the solid-state storage 110 without interruption. By sizing the write buffer 320 of the write data pipeline 106 and buffers within the read data pipeline 108 to be the same capacity or larger than a storage write buffer within the solid-state storage 110, writing and reading data is more efficient since a single write command may be crafted to send a full virtual page of data to the solid-state storage 110 instead of multiple commands.
While the write buffer 320 is being filled, the solid-state storage 110 may be used for other read operations. This is advantageous because other solid-state devices with a smaller write buffer or no write buffer may tie up the solid-state storage when data is written to a storage write buffer and data flowing into the storage write buffer stalls. Read operations will be blocked until the entire storage write buffer is filled and programmed. Another approach for systems without a write buffer or a small write buffer is to flush the storage write buffer that is not full in order to enable reads. Again this is inefficient because multiple write/program cycles are required to fill a page.
For depicted embodiment with a write buffer 320 sized larger than a virtual page, a single write command, which includes numerous subcommands, can then be followed by a single program command to transfer the page of data from the storage write buffer in each solid-state storage element 216, 218, 220 to the designated page within each solid-state storage element 216, 218, 220. This technique has the benefits of eliminating partial page programming, which is known to reduce data reliability and durability and freeing up the destination bank for reads and other commands while the buffer fills.
In one embodiment, the write buffer 320 is a ping-pong buffer where one side of the buffer is filled and then designated for transfer at an appropriate time while the other side of the ping-pong buffer is being filled. In another embodiment, the write buffer 320 includes a first-in first-out ("FIFO") register with a capacity of more than a virtual page of data segments. One of skill in the art will recognize other write buffer 320 configurations that allow a virtual page of data to be stored prior to writing the data to the solid-state storage 110.
In another embodiment, the write buffer 320 is sized smaller than a virtual page so that less than a page of information could be written to a storage write buffer in the solid-state storage 110. In the embodiment, to prevent a stall in the write data pipeline 106 from holding up read operations, data is queued using the garbage collection system that needs to be moved from one location to another as part of the garbage collection process. In case of a data stall in the write data pipeline 106, the data can be fed through the garbage collector bypass 316 to the write buffer 320 and then on to the storage write buffer in the solid-state storage 110 to fill the pages of a virtual page prior to programming the data. In this way a data stall in the write data pipeline 106 would not stall reading from the solid-state storage device 106.
In another embodiment, the write data pipeline 106 includes a write program module 310 with one or more user-definable functions within the write data pipeline 106. The write program module 310 allows a user to customize the write data pipeline 106. A user may customize the write data pipeline 106 based on a particular data requirement or application. Where the solid- state storage controller 104 is an FPGA, the user may program the write data pipeline 106 with custom commands and functions relatively easily. A user may also use the write program module 310 to include custom functions with an ASIC, however, customizing an ASIC may be more difficult than with an FPGA. The write program module 310 may include buffers and bypass mechanisms to allow a first data segment to execute in the write program module 310 while a second data segment may continue through the write data pipeline 106. In another embodiment, the write program module 310 may include a processor core that can be programmed through software.
Note that the write program module 310 is shown between the input buffer 306 and the compression module 312, however, the write program module 310 could be anywhere in the write data pipeline 106 and may be distributed among the various stages 302-320. In addition, there may be multiple write program modules 310 distributed among the various states 302-320 that are programmed and operate independently. In addition, the order of the .stages 302-320 may be altered. One of skill in the art will recognize workable alterations to the order of the stages 302-320 based on particular user requirements. Read Data Pipeline The read data pipeline 108 includes an ECC correction module 322 that determines if a data error exists in ECC blocks a requested packet received from the solid-state storage 110 by using ECC stored with each ECC block of the requested packet. The ECC correction module 322 then corrects any errors in the requested packet if any error exists and the errors are correctable using the ECC. For example, if the ECC can detect an error in six bits but can only correct three bit errors, the ECC correction module 322 corrects ECC blocks of the requested packet with up to three bits in error. The ECC correction module 322 corrects the bits in error by changing the bits in error to the correct one or zero state so that the requested data packet is identical to when it was written to the solid-state storage 110 and the ECC was generated for the packet. If the ECC correction module 322 determines that the requested packets contains more bits in error than the ECC can correct, the ECC correction module 322 cannot correct the errors in the corrupted ECC blocks of the requested packet and sends an interrupt. In one embodiment, the ECC correction module 322 sends an interrupt with a message indicating that the requested packet is in error. The message may include information that the ECC correction module 322 cannot correct the errors or the inability of the ECC correction module 322 to correct the errors may be implied. In another embodiment, the ECC correction module 322 sends the corrupted ECC blocks of the requested packet with the interrupt and/or the message.
In the preferred embodiment, a corrupted ECC block or portion of a corrupted ECC block of the requested packet that cannot be corrected by the ECC correction module 322 is read by the master controller 224, corrected, and returned to the ECC correction module 322 for further processing by the read data pipeline 108. In one embodiment, a corrupted ECC block or portion of a corrupted ECC block of the requested packet is sent to the device requesting the data. The requesting device 155 may correct the ECC block or replace the data using another copy, such as a backup or mirror copy, and then may use the replacement data of the requested data packet or return it to the read data pipeline 108. The requesting device 155 may use header information in the requested packet in error to identify data required to replace the corrupted requested packet or to replace the object to which the packet belongs. In another preferred embodiment, the solid- state storage controller 104 stores data using some type of RAID and is able to recover the corrupted data. In another embodiment, the ECC correction module 322 sends and interrupt and/or message and the receiving device fails the read operation associated with the requested data packet. One of skill in the art will recognize other options and actions to be taken as a result of the ECC correction module 322 determining that one or more ECC blocks of the requested packet are corrupted and that the ECC correction module 322 cannot correct the errors. The read data pipeline 108 includes a depacketizer 324 that receives ECC blocks of the requested packet from the ECC correction module 322, directly or indirectly, and checks and removes one or more packet headers. The depacketizer 324 may validate the packet headers by checking packet identifiers, data length, data location, etc. within the headers. In one embodiment, the header includes a hash code that can be used to validate that the packet delivered to the read data pipeline 108 is the requested packet. The depacketizer 324 also removes the headers from the requested packet added by the packetizer 302. The depacketizer 324 may directed to not operate on certain packets but pass these forward without modification. An example might be a container label that is requested during the course of a rebuild process where the header information is required by the object index reconstruction module 272. Further examples include the transfer of packets of various types destined for use within the solid-state storage device 102. In another embodiment, the depacketizer 324 operation may be packet type dependent.
The read data pipeline 108 includes an alignment module 326 that receives data from the depacketizer 324 and removes unwanted data. In one embodiment, a read command sent to the solid-state storage 110 retrieves a packet of data. A device requesting the data may not require all data within the retrieved packet and the alignment module 326 removes the unwanted data. If all data within a retrieved page is requested data, the alignment module 326 does not remove any data. The alignment module 326 re-formats the data as data segments of an object in a form compatible with a device requesting the data segment prior to forwarding the data segment to the next stage. Typically, as data is processed by the read data pipeline 108, the size of data segments or packets changes at various stages. The alignment module 326 uses received data to format the data into data segments suitable to be sent to the requesting device 155 and joined to form a response. For example, data from a portion of a first data packet may be combined with data from a portion of a second data packet. If a data segment is larger than a data requested by the requesting device, the alignment module 326 may discard the unwanted data.
In one embodiment, the read data pipeline 108 includes a read synchronization buffer 328 that buffers one or more requested packets read from the solid-state storage 110 prior to processing by the read data pipeline 108. The read synchronization buffer 328 is at the boundary between the solid-state storage clock domain and the local bus clock domain and provides buffering to account for the clock domain differences.
In another embodiment, the read data pipeline 108 includes an output buffer 330 that receives requested packets from the alignment module 326 and stores the packets prior to transmission to the requesting device. The output buffer 330 accounts for differences between when data segments are received from stages of the read data pipeline 108 and when the data segments are transmitted to other parts of the solid-state storage controller 104 or to the requesting device. The output buffer 330 also allows the data bus 204 to receive data from the read data pipeline 108 at rates greater than can be sustained by the read data pipeline 108 in order to improve efficiency of operation of the data bus 204.
In one embodiment, the read data pipeline 108 includes a media decryption module 332 that receives one or more encrypted requested packets from the ECC correction module 322 and decrypts the one or more requested packets using the encryption key unique to the solid-state storage device 102 prior to sending the one or more requested packets to the depacketizer 324. Typically the encryption key used to decrypt data by the media decryption module 332 is identical to the encryption key used by the media encryption module 318. In another embodiment, the solid-state storage 110 may have two or more partitions and the solid-state storage controller 104 behaves as though it were two or more solid-state storage controllers 104 each operating on a single partition within the solid-state storage 110. In this embodiment, a unique media encryption key may be used with each partition.
In another embodiment, the read data pipeline 108 includes a decryption module 334 that decrypts a data segment formatted by the depacketizer 324 prior to sending the data segment to the output buffer 330. The data segment decrypted using an encryption key received in conjunction with the read request that initiates retrieval of the requested packet received by the read synchronization buffer 328. The decryption module 334 may decrypt a first packet with an encryption key received in conjunction with the read request for the first packet and then may decrypt a second packet with a different encryption key or may pass the second packet on to the next stage of the read data pipeline 108 without decryption. Typically, the decryption module 334 uses a different encryption key to decrypt a data segment than the media decryption module 332 uses to decrypt requested packets. When the packet was stored with a non-secret cryptographic nonce, the nonce is used in conjunction with an encryption key to decrypt the data packet. The encryption key may be received from a client 114, a computer 112, key manager, or other device that manages the encryption key to be used by the solid-state storage controller 104. In another embodiment, the read data pipeline 108 includes a decompression module 336 that decompresses a data segment formatted by the depacketizer 324. In the preferred embodiment, the decompression module 336 uses compression information stored in one or both of the packet header and the container label to select a complementary routine to that used to compress the data by the compression module 312. In another embodiment, the decompression routine used by the decompression module 336 is dictated by the device requesting the data segment being decompressed. In another embodiment, the decompression module 336 selects a decompression routine according to default settings on a per object type or object class basis. A first packet of a first object may be able to override a default decompression routine and a second packet of a second object of the same object class and object type may use the default decompression routine and a third packet of a third object of the same object class and object type may use no decompression.
In another embodiment, the read data pipeline 108 includes a read program module 338 that includes one or more user-definable functions within the read data pipeline 108. The read program module 338 has similar characteristics to the write program module 310 and allows a user to provide custom functions to the read data pipeline 108. The read program module 338 may be located as shown in Figure 3, may be located in another position within the read data pipeline 108, or may include multiple parts in multiple locations within the read data pipeline 108. Additionally, there may be multiple read program modules 338 within multiple locations within the read data pipeline 108 that operate independently. One of skill in the art will recognize other forms of a read program module 338 within a read data pipeline 108. As with the write data pipeline 106, the stages of the read data pipeline 108 may be rearranged and one of skill in the art will recognize other orders of stages within the read data pipeline 108.
The solid-state storage controller 104 includes control and status registers 340 and corresponding control queues 342. The control and status registers 340 and control queues 342 facilitate control and sequencing commands and subcommands associated with data processed in the write and read data pipelines 106, 108. For example, a data segment in the packetizer 302 may have one or more corresponding control commands or instructions in a control queue 342 associated with the ECC generator. As the data segment is packetized, some of the instructions or commands may be executed within the packetizer 302. Other commands or instructions may be passed to the next control queue 342 through the control and status registers 340 as the newly formed data packet created from the data segment is passed to the next stage.
Commands or instructions may be simultaneously loaded into the control queues 342 for a packet being forwarded to the write data pipeline 106 with each pipeline stage pulling the appropriate command or instruction as the respective packet is executed by that stage. Similarly, commands or instructions may be simultaneously loaded into the control queues 342 for a packet being requested from the read data pipeline 108 with each pipeline stage pulling the appropriate command or instruction as the respective packet is executed by that stage. One of skill in the art will recognize other features and functions of control and status registers 340 and control queues 342.
The solid-state storage controller 104 and or solid-state storage device 102 may also include a bank interleave controller 344, a synchronization buffer 346, a storage bus controller 348, and a multiplexer ("MUX") 350, which are described in relation to Figures 4A and 4B. BANK INTERLEAVE Figure 4A is a schematic block diagram illustrating one embodiment 400 of a bank interleave controller 344 in the solid-state storage controller 104 in accordance with the present invention. The bank interleave controller 344 is connected to the control and status registers 340 and to the storage I/O bus 210 and storage control bus 212 through the MUX 350, storage bus controller 348, and synchronous buffer 346, which are described below. The bank interleave controller includes a read agent 402, a write agent 404, an erase agent 406, a management agent 408, read queues 410a-n, write queues 412a-n, erase queues 414a-n, and management queues 416a-n for the banks 214 in the solid-state storage 110, bank controllers 418a-n, a bus arbiter 420, and a status MUX 422, which are described below. The storage bus controller 348 includes a mapping module 424 with a remapping module 430, a status capture module 426, and a NAND bus controller 428, which are described below.
The bank interleave controller 344 directs one or more commands to two or more queues in the bank interleave controller 344 and coordinates among the banks 214 of the solid-state storage 110 execution of the commands stored in the queues, such that a command of a first type executes on one bank 214a while a command of a second type executes on a second bank 214b. The one or more commands are separated by command type into the queues. Each bank 214 of the solid-state storage 110 has a corresponding set of queues within the bank interleave controller 344 and each set of queues includes a queue for each command type.
The bank interleave controller 344 coordinates among the banks 214 of the solid-state storage 110 execution of the commands stored in the queues. For example, a command of a first type executes on one bank 214a while a command of a second type executes on a second bank 214b. Typically the command types and queue types include read and write commands and queues 410, 412, but may also include other commands and queues that are storage media specific. For example, in the embodiment depicted in Figure 4 A, erase and management queues 414, 416 are included and would be appropriate for flash memory, NRAM, MRAM, DRAM, PRAM, etc.
For other types of solid-state storage 110, other types of commands and corresponding queues may be included without straying from the scope of the invention. The flexible nature of an FPGA solid-state storage controller 104 allows flexibility in storage media. If flash memory were changed to another solid-state storage type, the bank interleave controller 344, storage bus controller 348, and MUX 350 could be altered to accommodate the media type without significantly affecting the data pipelines 106, 108 and other solid-state storage controller 104 functions.
In the embodiment depicted in Figure 4A, the bank interleave controller 344 includes, for each bank 214, a read queue 410 for reading data from the solid-state storage 110, a write queue 412 for write commands to the solid-state storage 110, an erase queue 414 for erasing an erase block in the solid-state storage, an a management queue 416 for management commands. The bank interleave controller 344 also includes corresponding read, write, erase, and management agents 402, 404, 406, 408. In another embodiment, the control and status registers 340 and control queues 342 or similar components queue commands for data sent to the banks 214 of the solid-state storage 110 without a bank interleave controller 344.
The agents 402, 404, 406, 408, in one embodiment, direct commands of the appropriate type destined for a particular bank 214a to the correct queue for the bank 214a. For example, the read agent 402 may receive a read command for bank-1 214b and directs the read command to the bank-1 read queue 410b. The write agent 404 may receive a write command to write data to a location in bank-0 214a of the solid-state storage 110 and will then send the write command to the bank-0 write queue 412a. Similarly, the erase agent 406 may receive an erase command to erase an erase block in bank-1 214b and will then pass the erase command to the bank-1 erase queue 414b. The management agent 408 typically receives management commands, status requests, and the like, such as a reset command or a request to read a configuration register of a bank 214, such as bank-0 214a. The management agent 408 sends the management command to the bank-0 management queue 416a.
The agents 402, 404, 406, 408 typically also monitor status of the queues 410, 412, 414, 416 and send status, interrupt, or other messages when the queues 410, 412, 414, 416 are full, nearly full, non-functional, etc. In one embodiment, the agents 402, 404, 406, 408 receive commands and generate corresponding sub-commands. In one embodiment, the agents 402, 404, 406, 408 receive commands through the control & status registers 340 and generate corresponding sub-commands which are forwarded to the queues 410, 412, 414, 416. One of skill in the art will recognize other functions of the agents 402, 404, 406, 408.
The queues 410, 412, 414, 416 typically receive commands and store the commands until required to be sent to the solid-state storage banks 214. In a typical embodiment, the queues 410, 412, 414, 416 are first-in, first-out ("FIFO") registers or a similar component that operates as a FIFO. In another embodiment, the queues 410, 412, 414, 416 store commands in an order that matches data, order of importance, or other criteria.
The bank controllers 418 typically receive commands from the queues 410, 412, 414, 416 and generate appropriate subcommands. For example, the bank-0 write queue 412a may receive a command to write a page of data packets to bank-0 214a. The bank-0 controller 418a may receive the write command at an appropriate time and may generate one or more write subcommands for each data packet stored in the write buffer 320 to be written to the page in bank-0 214a. For example, bank-0 controller 418a may generate commands to validate the status of bank 0 214a and the solid-state storage array 216, select the appropriate location for writing one or more data packets, clear the input buffers within the solid-state storage memory array 216, transfer the one or more data packets to the input buffers, program the input buffers into the selected location, verify that the data was correctly programmed, and if program failures occur do one or more of interrupting the master controller, retrying the write to the same physical location, and retrying the write to a different physical location. Additionally, in conjunction with example write command, the storage bus controller 348 will cause the one or more commands to multiplied to each of the each of the storage I/O buses 210a-n with the logical address of the command mapped to a first physical addresses for storage I/O bus 210a, and mapped to a second physical address for storage I/O bus 210b, and so forth as further described below.
Typically, bus arbiter 420 selects from among the bank controllers 418 and pulls subcommands from output queues within the bank controllers 418 and forwards these to the Storage Bus Controller 348 in a sequence that optimizes the performance of the banks 214. In another embodiment, the bus arbiter 420 may respond to a high level interrupt and modify the normal selection criteria. In another embodiment, the master controller 224 can control the bus arbiter 420 through the control and status registers 340. One of skill in the art will recognize other means by which the bus arbiter 420 may control and interleave the sequence of commands from the bank controllers 418 to the solid-state storage 110.
The bus arbiter 420 typically coordinates selection of appropriate commands, and corresponding data when required for the command type, from the bank controllers 418 and sends the commands and data to the storage bus controller 348. The bus arbiter 420 typically also sends commands to the storage control bus 212 to select the appropriate bank 214. For the case of flash memory or other solid-state storage 110 with an asynchronous, bi-directional serial storage I/O bus 210, only one command (control information) or set of data can be transmitted at a time. For example, when write commands or data are being transmitted to the solid-state storage 110 on the storage I/O bus 210, read commands, data being read, erase commands, management commands, or other status commands cannot be transmitted on the storage I/O bus 210. For example, when data is being read from the storage I/O bus 210, data cannot be written to the solid-state storage 110.
For example, during a write operation on bank-0 the bus arbiter 420 selects the bank-0 controller 418a which may have a write command or a series of write sub-commands on the top of its queue which cause the storage bus controller 348 to execute the following sequence. The bus arbiter.420 forwards the write command to the storage bus controller 348, which sets up a write command by selecting bank-0 214a through the storage control bus 212, sending a command to clear the input buffers of the solid-state storage elements 110 associated with the bank-0 214a, and sending a command to validate the status of the solid-state storage elements 216, 218, 220 associated with the bank-0 214a. The storage bus controller 348 then transmits a write subcommand on the storage I/O bus 210, which contains the physical addresses including the address of the logical erase block for each individual physical erase solid-stage storage element 216a-m as mapped from the logical erase block address. The storage bus controller 348 then muxes the write buffer 320 through the write sync buffer 308 to the storage I/O bus 210 through the MUX 350 and streams write data to the appropriate page. When the page is full, then storage bus controller 348 causes the solid-state storage elements 216a-m associated with the bank-0 214a to program the input buffer to the memory cells within the solid-state storage elements 216a-m. Finally, the storage bus controller 348 validates the status to ensure that page was correctly programmed. A read operation is similar to the write example above. During a read operation, typically the bus arbiter 420, or other component of the bank interleave controller 344, receives data and corresponding status information and sends the data to the read data pipeline 108 while sending the status information on to the control and status registers 340. Typically, a read data command forwarded from bus arbiter 420 to the storage bus controller 348 will cause the MUX 350 to gate the read data on storage I/O bus 210 to the read data pipeline 108 and send status information to the appropriate control and status registers 340 through the status MUX 422.
The bus arbiter 420 coordinates the various command types and data access modes so that only an appropriate command type or corresponding data is on the bus at any given time. If the bus arbiter 420 has selected a write command, and write subcommands and corresponding data are being written to the solid-state storage 110, the bus arbiter 420 will not allow other command types on the storage I/O bus 210. Beneficially, the bus arbiter 420 uses timing information, such as predicted command execution times, along with status information received concerning bank 214 status to coordinate execution of the various commands on the bus with the goal of minimizing or eliminating idle time of the busses. The master controller 224 through the bus arbiter 420 typically uses expected completion times of the commands stored in the queues 410, 412, 414, 416, along with status information, so that when the subcommands associated with a command are executing on one bank 214a, other subcommands of other commands are executing on other banks 214b-n. When one command is fully executed on a bank 214a, the bus arbiter 420 directs another command to the bank 214a. The bus arbiter 420 may also coordinate commands stored in the queues 410, 412, 414, 416 with other commands that are not stored in the queues 410, 412, 414, 416.
For example, an erase command may be sent out to erase a group of erase blocks within the solid-state storage 1 10. An erase command may take 10 to 1000 times more time to execute than a write or a read command or 10 to 100 times more time to execute than a program command. For N banks 214, the bank interleave controller 344 may split the erase command into N commands, each to erase a virtual erase block of a bank 214a. While bank-0 214a is executing an erase command, the bus arbiter 420 may select other commands for execution on the other banks 214b-n. The bus arbiter 420 may also work with other components, such as the storage bus controller 348, the master controller 224, etc., to coordinate command execution among the buses. Coordinating execution of commands using the bus arbiter 420, bank controllers 418, queues 410, 412, 414, 416, and agents 402, 404, 406, 408 of the bank interleave controller 344 can dramatically increase performance over other solid-state storage systems without a bank interleave function. In one embodiment, the solid-state controller 104 includes one bank interleave controller
344 that serves all of the storage elements 216, 218, 220 of the solid-state storage 110. In another embodiment, the solid-state controller 104 includes a bank interleave controller 344 for each row of storage elements 216a-m, 218a-m, 220a-m. For example, one bank interleave controller 344 serves one row of storage elements SSS 0.0-SSS 0.N 216a, 218a, 220a, a second bank interleave controller 344 serves a second row of storage elements SSS 1.0-SSS l.N 216b, 218b, 220b, etc.
Figure 4B is a schematic block diagram illustrating an alternate embodiment 401 of a bank interleave controller in the solid-state storage controller in accordance with the present invention. The components 210, 212, 340, 346, 348, 350, 402-430 depicted in the embodiment shown in Figure 4B are substantially similar to the bank interleave apparatus 400 described in relation to Figure 4 A except that each bank 214 includes a single queue 432a-n and the read commands, write commands, erase commands, management commands, etc. for a bank (e.g. Bank-0 214a) are directed to a single queue 432a for the bank 214a. The queues 432, in one embodiment, are FIFO. In another embodiment, the queues 432 can have commands pulled from the queues 432 in an order other than the order they were stored. In another alternate embodiment (not shown), the read agent 402, write agent 404, erase agent 406, and management agent 408 may be combined into a single agent assigning commands to the appropriate queues 432a-n.
In another alternate embodiment (not shown), commands are stored in a single queue where the commands may be pulled from the queue in an order other than how they are stored so that the bank interleave controller 344 can execute a command on one bank 214a while other commands are executing on the remaining banks 214b-n. One of skill in the art will easily recognize other queue configurations and types to enable execution of a command on one bank 214a while other commands are executing on other banks 214b-n. STORAGE-SPECIFIC COMPONENTS
The solid-state storage controller 104 includes a synchronization buffer 346 that buffers commands and status messages sent and received from the solid-state storage 110. The synchronization buffer 346 is located at the boundary between the solid-state storage clock domain and the local bus clock domain and provides buffering to account for the clock domain differences. The synchronization buffer 346, write synchronization buffer 308, and read synchronization buffer 328 may be independent or may act together to buffer data, commands, status messages, etc. In the preferred embodiment, the synchronization buffer 346 is located where there are the fewest number of signals crossing the clock domains. One skilled in the art will recognize that synchronization between clock domains may be arbitrarily moved to other locations within the solid-state storage device 102 in order to optimize some aspect of design implementation.
. The solid-state storage controller 104 includes a storage bus controller 348 that interprets and translates commands for data sent to and read from the solid-state storage 110 and status messages received from the solid-state storage 110 based on the type of solid-state storage 110. For example, the storage bus controller 348 may have different timing requirements for different types of storage, storage with different performance characteristics, storage from different manufacturers, etc. The storage bus controller 348 also sends control commands to the storage control bus 212. In the preferred embodiment, the solid-state storage controller 104 includes a MUX 350 that comprises an array of multiplexers 350a-n where each multiplexer is dedicated to a row in the solid-state storage array 110. For example, multiplexer 350a is associated with solid-state storage elements 216a, 218a, 220a. MUX 350 routes the data from the write data pipeline 106 and commands from the storage bus controller 348 to the solid-state storage 110 via the storage I/O bus 210 and routes data and status messages from the solid-state storage 110 via the storage I/O bus 210 to the read data pipeline 106 and the control and status registers 340 through the storage bus controller 348, synchronization buffer 346, and bank interleave controller 344.
In the preferred embodiment, the solid-state storage controller 104 includes a MUX 350 for each row of solid-state storage elements (e.g. SSS 0.1 216a, SSS 0.2 218a, SSS 0.N 220a). A MUX 350 combines data from the write data pipeline 106 and commands sent to the solid-state storage 1 10 via the storage I/O bus 210 and separates data to be processed by the read data pipeline 108 from commands. Packets stored in the write buffer 320 are directed on busses out of the write buffer 320 through a write synchronization buffer 308 for each row of solid-state storage elements (SSS x.O to SSS x.N 216, 218, 220) to the MUX 350 for each row of solid-state storage elements (SSS x.O to SSS x.N 216, 218, 220). The commands and read data are received by the MUXes 350 from the storage I/O bus 210. The MUXes 350 also direct status messages to the storage bus controller 348.
The storage bus controller 348 includes a mapping module 424. The mapping module 424 maps a logical address of an erase block to one or more physical addresses of an erase block. For example, a solid-state storage 110 with an array of twenty storage elements (e.g. SSS 0.0 to SSS M.O 216) per block 214a may have a logical address for a particular erase block mapped to twenty physical addresses of the erase block, one physical address per storage element. Because the storage elements are accessed in parallel, erase blocks at the same position in each storage element in a row of storage elements 216a, 218a, 220a will share a physical address. To select one erase block (e.g. in storage element SSS 0.0 216a) instead of all erase blocks in the row (e.g. in storage elements SSS 0.0, 0.1, ... 0.N 216a, 218a, 220a), one bank (in this case bank-0 214a) is selected.
This logical-to-physical mapping for erase blocks is beneficial because if one erase block becomes damaged or inaccessible, the mapping can be changed to map to another erase block. This mitigates the loss of losing an entire virtual erase block when one element's erase block is faulty. The remapping module 430 changes a mapping of a logical address of an erase block to one or more physical addresses of a virtual erase block (spread over the array of storage elements). For example, virtual erase block 1 may be mapped to erase block 1 of storage element SSS 0.0 216a, to erase block 1 of storage element SSS 1.0 216b, ..., and to storage element M.O 216m, virtual erase block 2 may be mapped to erase block 2 of storage element SSS 0.1 218a, to erase block 2 of storage element SSS 1.1 218b, ..., and to storage element M.I 218m, etc.
If erase block 1 of a storage element SSSO.O 216a is damaged, experiencing errors due to wear, etc., or cannot be used for some reason, the remapping module could change the logical-to- physical mapping for the logical address that pointed to erase block 1 of virtual erase block 1. If a spare erase block (call it erase block 221) of storage element SSS 0.0 216a is available and currently not mapped, the remapping module could change the mapping of virtual erase block 1 to point to erase block 221 of storage element SSS 0.0 216a, while continuing to point to erase block 1 of storage element SSS 1.0 216b, erase block 1 of storage element SSS 2.0 (not shown) ..., and to storage element M.O 216m. The mapping module 424 or remapping module 430 could map erase blocks in a prescribed order (virtual erase block 1 to erase block 1 of the storage elements, virtual erase block 2 to erase block 2 of the storage elements, etc.) or may map erase blocks of the storage elements 216, 218, 220 in another order based on some other criteria. In one embodiment, the erase blocks could be grouped by access time. Grouping by access time, meaning time to execute a command, such as programming (writing) data into pages of specific erase blocks, can level command completion so that a command executed across the erase blocks of a virtual erase block is not limited by the slowest erase block. In other embodiments, the erase blocks may be grouped by wear level, health, etc. One of skill in the art will recognize other factors to consider when mapping or remapping erase blocks.
In one embodiment, the storage bus controller 348 includes a status capture module 426 that receives status messages from the solid-state storage 110 and sends the status messages to the status MUX 422. In another embodiment, when the solid-state storage 110 is flash memory, the storage bus controller 348 includes a NAND bus controller 428. The NAND bus controller 428 directs commands from the read and write data pipelines 106, 108 to the correct location in the solid-state storage 110, coordinates timing of command execution based on characteristics of the flash memory, etc. If the solid-state storage 110 is another solid-state storage type, the NAND bus controller 428 would be replaced by a bus controller specific to the storage type. One of skill in the art will recognize other functions of a NAND bus controller 428. FLOW CHARTS
Figure 5A is a schematic flow chart diagram illustrating one embodiment of a method 500 for managing data in a solid-state storage device 102 using a data pipeline in accordance with the present invention. The method 500 begins 502 and the input buffer 306 receives 504 one or more data segments to be written to the solid-state storage 110. The one or more data segments typically include at least a portion of an object but may be an entire object. The packetizer 302 may create one or more object specific packets in conjunction with an object. The packetizer 302 adds a header to each packet which typically includes the length of the packet and a sequence number for the packet within the object. The packetizer 302 receives 504 the one or more data or metadata segments that were stored in the input buffer 306 and packetizes 506 the one or more data or metadata segments by creating one or more packets sized for the solid-state storage 110 where each packet includes one header and data from the one or more segments.
Typically, a first packet includes an object identifier that identifies the object for which the packet was created. A second packet may include a header with information used by the solid-state storage device 102 to associate the second packet to the object identified in the first packet and offset information locating the second packet within the object, and data. The solid- state storage device controller 202 manages the bank 214 and physical area to which the packets are streamed. The ECC generator 304 receives a packet from the packetizer 302 and generates 508 ECC for the data packets. Typically, there is no fixed relationship between packets and ECC blocks. An ECC block may comprise one or more packets. A packet may comprise one or more ECC blocks. A packet may start and end anywhere within an ECC block. A packet may start anywhere in a first ECC block and end anywhere in a subsequent ECC block.
The write synchronization buffer 308 buffers 510 the packets as distributed within the corresponding ECC blocks prior to writing ECC blocks to the solid-state storage 1 10 and then the solid-state storage controller 104 writes 512 the data at an appropriate time considering clock domain differences, and the method 500 ends 514. The write synch buffer 308 is located at the boundary between a local clock domain and a solid-state storage 110 clock domain. Note that the method 500 describes receiving one or more data segments and writing one or more data packets for convenience, but typically a stream of data segments is received and a group. Typically a number of ECC blocks comprising a complete virtual page of solid-state storage 110 are written to the solid-state storage 110. Typically the packetizer 302 receives data segments of one size and generates packets of another size. This necessarily requires data or metadata segments or parts of data or metadata segments to be combined to form data packets to capture all of the data of the segments into packets.
Figure 5B is a schematic flow chart diagram illustrating one embodiment of a method for in-server SAN in accordance with the present invention. The method 500 begins 552 and the storage communication module 162 facilitates 554 communication between a first storage controller 152a and at least one device external to the first server 1 12a. The communication between the first storage controller 152a and the external device is independent from the first server 112a. The first storage controller 112a is within the first server 112a and the first storage controller 152a controls at least one storage device 154a. The first server 112a includes a network interface 156a collocated with the first server 112a and the first storage controller 152a. The in-server SAN module 164 services 556 a storage request and the method 501 ends 558. The in-server SAN module services 556 the storage request using a network protocol and/or a bus protocol. The in-server SAN module 164 services 556 the storage request independent from the first server 112a and the service request is received from a client 1 14, 114a. Figure 6 is a schematic flow chart diagram illustrating another embodiment of a method
600 for managing data in a solid-state storage device 102 using a data pipeline in accordance with the present invention. The method 600 begins 602 and the input buffer 306 receives 604 one or more data or metadata segments to be written to the solid-state storage 110. The packetizer 302 adds a header to each packet which typically includes the length of the packet within the object. The packetizer 302 receives 604 the one or more segments that were stored in the input buffer 306 and packetizes 606 the one or more segments by creating one or more packets sized for the solid-state storage 110 where each packet includes a header and data from the one or more segments. The ECC generator 304 receives a packet from the packetizer 302 and generates 608 one or more ECC blocks for the packets. The write synchronization buffer 308 buffers 610 the packets as distributed within the corresponding ECC blocks prior to writing ECC blocks to the solid-state storage 110 and then the solid-state storage controller 104 writes 612 the data at an appropriate time considering clock domain differences. When data is requested from the solid- state storage 110, ECC blocks comprising one or more data packets are read into the read synchronization buffer 328 and buffered 614. The ECC blocks of the packet are received over the storage I/O bus 210. Since the storage I/O bus 210 is bi-directional, when data is read, write operations, command operations, etc. are halted.
The ECC correction module 322 receives the ECC blocks of the requested packets held in the read synchronization buffer 328 and corrects 616 errors within each ECC block as necessary. If the ECC correction module 322 determines that one or more errors exist in an ECC block and the errors are correctable using the ECC syndrom, the ECC correction module 322 corrects 616 the error in the ECC block. If the ECC correction module 322 determines that a detected error is not correctable using the ECC, the ECC correction module 322 sends an interrupt. The depacketizer 324 receives 618 the requested packet after the ECC correction module
322 corrects any errors and depacketizes 618 the packets by checking and removing the packet header of each packet. The alignment module 326 receives packets after depacketizing, removes unwanted data, and re-formats 620 the data packets as data or metadata segments of an object in a form compatible with the device requesting the segment or object. The output buffer 330 receives requested packets after depacketizing and buffers 622 the packets prior to transmission to the requesting device, and the method 600 ends 624.
Figure 7 is a schematic flow chart diagram illustrating an embodiment of a method 700 for managing data in a solid-state storage device 102 using a bank interleave in accordance with the present invention. The method 600 begins 602 and the bank interleave controller 344 directs 604 one or more commands to two or more queues 410, 412, 414, 416. Typically the agents 402, 404, 406, 408 direct 604 the commands to the queues 410, 412, 414, 416 by command type. Each set of queues 410, 412, 414, 416 includes a queue for each command type. The bank interleave controller 344 coordinates 606 among the banks 214 execution of the commands stored in the queues 410, 412, 414, 416 so that a command of a first type executes on one bank 214a while a command of a second type executes on a second bank 214b, and the method 600 ends 608.
STORAGE SPACE RECOVERY
Figure 8 is a schematic block diagram illustrating one embodiment of an apparatus 800 for garbage collection in a solid-state storage device 102 in accordance with the present invention. The apparatus 800 includes a sequential storage module 802, a storage division selection module 804, a data recovery module 806, and a storage division recovery module 808, which are described below. In other embodiments, the apparatus 800 includes a garbage marking module 810 and an erase module 812. The apparatus 800 includes a sequential storage module 802 that sequentially writes data packets in a page within a storage division. The packets are sequentially stored whether they are new packets or modified packets. Modified packets are in this embodiment are typically not written back to a location where they were previously stored. In one embodiment, the sequential storage module 802 writes a packet to a first location in a page of a storage division, then to the next location in the page, and to the next, and the next, until the page is filled. The sequential storage module 802 then starts to fill the next page in the storage division. This continues until the storage division is filled.
In a preferred embodiment, the sequential storage module 802 starts writing packets to storage write buffers in the storage elements (e.g. SSS 0.0 to SSS M.O 216) of a bank (bank-0 214a). When the storage write buffers are full, the solid-state storage controller 104 causes the data in the storage write buffers to be programmed into designated pages within the storage elements 216 of the bank 214a. Then another bank (e.g. bank-1 214b) is selected and the sequential storage module 802 starts writing packets to storage write buffers of the storage elements 218 of the bank 214b while the first bank-0 is programming the designated pages. When the storage write buffers of this bank 214b are full, the contents of the storage write buffers are programmed into another designated page in each storage element 218. This process is efficient because while one bank 214a is programming a page, storage write buffers of another bank 214b can be filling.
The storage division includes a portion of a solid-state storage 110 in a solid-state storage device 102. Typically the storage division is an erase block. For flash memory, an erase operation on an erase block writes ones to every bit in the erase block by charging each cell. This is a lengthy process compared to a program operation which starts with a location being all ones, and as data is written, some bits are changed to zero by discharging the cells written with a zero. However, where the solid-state storage 110 is not flash memory or has flash memory where an erase cycle takes a similar amount of time as other operations, such as a read or a program, the storage division may not be required to be erased.
As used herein, a storage division is equivalent in area to an erase block but may or may not be erased. Where erase block is used herein, an erase block may refer to a particular area of a designated size within a storage element (e.g. SSS 0.0 216a) and typically includes a certain quantity of pages. Where "erase block" is used in conjunction with flash memory, it is typically a storage division that is erased prior to being written. Where "erase block" is used with "solid- state storage," it may or may not be erased. As used herein, an erase block may include one erase block or a group of erase blocks with one erase block in each of a row of storage elements (e.g. SSS 0.0 to SSS M.O 216a-n), which may also be referred to herein as a virtual erase block. When referring to the logical construct associated with the virtual erase block, the erase blocks may be referred to herein as a logical erase block ("LEB").
Typically, the packets are sequentially stored by order of processing. In one embodiment, where a write data pipeline 106 is used, the sequential storage module 802 stores packets in the order that they come out of the write data pipeline 106. This order may be a result of data segments arriving from a requesting device 155 mixed with packets of valid data that arebeing read from another storage division as valid data is being recovered from a storage division during a recovery operation as explained below. Re-routing recovered, valid data packets to the write data pipeline 106 may include the garbage collector bypass 316 as described above in relation to the solid-state storage controller 104 of Figure 3.
The apparatus 800 includes a storage division selection module 804 that selects a storage division for recovery. Selecting a storage division for recovery may be to reuse the storage division by the sequential storage module 802 for writing data, thus adding the recovered storage division to the storage pool, or to recover valid data from the storage division after determining that the storage division is failing, unreliable, should be refreshed, or other reason to take the storage division temporarily or permanently out of the storage pool. In another embodiment, the storage division selection module 804 selects a storage division for recovery by identifying a storage division or erase block with a high amount of invalid data.
In another embodiment, the storage division selection module 804 selects a storage division for recovery by identifying a storage division or erase block with a low amount of wear. For example, identifying a storage division or erase block with a low amount of wear may include identifying a storage division with a low amount of invalid data, a low number of erase cycles, low bit error rate, or low program count (low number of times a page of data in a buffer is written to a page in the storage division; program count may be measured from when the device was manufactured, from when the storage division was last erased, from other arbitrary events, and from combinations of these). The storage division selection module 804 may also use any combination of the above or other parameters to determine a storage division with a low amount of wear. Selecting a storage division for recovery by determining a storage division with a low amount of wear may be desirable to find storage divisions that are under used, may be recovered for wear leveling, etc.
In another embodiment, the storage division selection module 804 selects a storage division for recovery by identifying a storage division or erase block with a high amount of wear. For example, identifying a storage division or erase block with a high amount of wear may include identifying a storage division with a high number of erase cycles, high bit error rate, a storage division with a non-recoverable ECC block, or high program count. The storage division selection module 804 may also use any combination of the above or other parameters to determine a storage division with a high amount of wear. Selecting a storage division for recovery by determining a storage division with a high amount of wear may be desirable to find storage divisions that are over used, may be recovered by refreshing the storage division using an erase cycle, etc. or to retire the storage division from service as being unusable.
The apparatus 800 includes a data recovery module 806 that reads valid data packets from the storage division selected for recovery, queues the valid data packets with other data packets to be written sequentially by the sequential storage module 802, and updates an index with a new physical address of the valid data written by the sequential storage module 802.
Typically, the index is the object index mapping data object identifiers of objects to physical addresses of where packets derived from the data object are stored in the solid-state storage 110.
In one embodiment the apparatus 800 includes a storage division recovery module 808 that prepares the storage division for use or reuse and marks the storage division as available to the sequential storage module 802 for sequentially writing data packets after the data recovery module 806 has completed copying valid data from the storage division, . In another embodiment, the apparatus 800 includes a storage division recovery module 808 that marks the storage division selected for recovery as unavailable for storing data. Typically this is due to the storage division selection module 804 identifying a storage division or erase block with a high amount of wear such that the storage division or erase block is not in condition to be used for reliable data storage.
In one embodiment, the apparatus 800 is in a solid-state storage device controller 202 of a solid-state storage device 102. In another embodiment, the apparatus 800 controls a solid-state storage device controller 202. In another embodiment, a portion of the apparatus 800 is in a solid-state storage device controller 202. In another embodiment, the object index updated by the data recovery module 806 is also located in the solid-state storage device controller 202
In one embodiment, the storage division is an erase block and the apparatus 800 includes an erase module 810 that erases an erase block selected for recovery after the data recovery module 806 has copied valid data packets from the selected erase block and before the storage division recovery module 808 marks the erase block as available. For flash memory and other solid-state storage with an erase operation taking much longer than read or write operations, erasing a data block prior to making it available for writing new data is desirable for efficient operation. Where the solid-state storage 110 is arranged in banks 214, the erase operation by the erase module 810 may be executed on one bank while other banks are executing reads, writes, or other operations.
In one embodiment, the apparatus 800 includes a garbage marking module 812 that identifies a data packet in a storage division as invalid in response to an operation indicating that the data packet is no longer valid. For example, if a data packet is deleted, the garbage marking module 812 may identify the data packet as invalid. A read-modify-write operation is another way for a data packet to be identified as invalid. In one embodiment, the garbage marking module 812 may identify the data packet as invalid by updating an index. In another embodiment, the garbage marking module 812 may identify the data packet as invalid by storing another data packet that indicates that the invalid data packet has been deleted. This is advantageous because storing, in the solid-state storage 110, information that the data packet has been deleted allows the object index reconstruction module 262 or similar module to reconstruct the object index with an entry indicating that the invalid data packet has been deleted.
In one embodiment, the apparatus 800 may be utilized to fill the remainder of a virtual page of data following a flush command in order to improve overall performance, where the flush command halts data flowing into the write pipeline 106 until the write pipeline 106 empties and all packets have been permanently written into non- volatile solid-state storage 110. This has the benefit of reducing the amount of garbage collection required, the amount of time used to erase storage divisions, and the amount of time required to program virtual pages. For example, a flush command may be received when only one small packet is prepared for writing into the virtual page of the solid-state storage 100. Programming this nearly empty virtual page might result in a need to immediately recover the wasted space, causing the valid data within the storage division to be unnecessarily garbage collected and the storage division erased, recovered and returned to the pool of available space for writing by the sequential storage module 802. Marking the data packet as invalid rather than actually erasing an invalid data packet is efficient because, as mentioned above, for flash memory and other similar storage an erase operation takes a significant amount of time. Allowing a garbage collection system, as described in the apparatus 800, to operate autonomously within the solid-state storage 110 provides a way to separate erase operations from reads, writes, and other faster operations so that the solid-state storage device 102 can operate much faster than many other solid-state storage systems or data storage devices.
Figure 9 is a schematic flow chart diagram illustrating an embodiment of a method 900 for storage recovery in accordance with the present invention. The method 900 begins 902 and the sequential storage module 802 sequentially writes 904 data packets in a storage division. The storage division is a portion of a solid-state storage 110 in a solid-state storage device 102. Typically a storage division is an erase block. The data packets are derived from an object and the data packets are sequentially stored by order of processing.
The storage division selection module 804 selects 906 a storage division for recovery and the data recovery module 806 reads 908 valid data packets from the storage division selected for recovery. Typically valid data packets are data packets that have not been marked for erasure or deletion or some other invalid data marking and are considered valid or "good" data. The data recovery module 806 queues 910 the valid data packets with other data packets scheduled to be written sequentially by the sequential storage module 802. The data recovery module 806 updates 912 an index with a new physical address of the valid data written by the sequential storage module 802. The index includes a mapping of physical addresses of data packets to object identifiers. The data packets are those stored in stored in the solid-state storage 110 and the object identifiers correspond to the data packets.
After the data recovery module 806 completes copying valid data from the storage division, the storage division recovery module 808 marks 914 the storage division selected for recovery as available to the sequential storage module 802 for sequentially writing data packets and the method 900 ends 916.
EMPTY DATA SEGMENT DIRECTIVE
Typically, when data is no longer useful it may be erased. In many file systems, an erase command deletes a directory entry in the file system while leaving the data in place in the storage device containing the data. Typically, a data storage device is not involved in this type of erase operation. Another method of erasing data is to write zeros, ones, or some other null data character to the data storage device to actually replace the erased file. However, this is inefficient because valuable bandwidth is used while transmitting the data is being overwritten. In addition, space in the storage device is taken up by the data used to overwrite invalid data.
Some storage devices, like the solid-state storage device 102 described herein, are not random access storage devices so updating previously stored data does not overwrite existing data. Attempting to overwrite data with a string of ones or a string of zeros on such a device takes up valuable space without fulfilling the desired intent of overwriting the existing data. For these non-random access devices, such as solid-state storage devices 102, a client 114 typically does not have an ability to overwrite data to erase it.
When receiving a string of repeated characters or character strings, the received data is highly compressible, but typically compression is done by a file system prior to transmission to a storage device. A typical storage device cannot distinguish between compressed data and uncompressed data. The storage device may also receive a command to read the erased file so the storage device may transmit a stream of zeros, ones, or a null character to the requesting device. Again, bandwidth is required to transmit data representing the erased file. From the foregoing discussion, it should be apparent that a need exists for an apparatus, system, and method for a storage device to receive a directive that data is to be erased so that the storage device can store a data segment token that represents an empty data segment or data with repeated characters or character strings. The apparatus, system, and method may also erase the existing data so that the resulting used storage space comprises the small data segment token. An apparatus, system, and method are presented that overcome some or all of the shortcomings of the prior art.
Figure 10 is a schematic block diagram illustrating one embodiment of a system 1000 with an apparatus for generating a token directive in accordance with the present invention. The apparatus includes a token directive generation module 1002, a token directive transmission module 1004, a read receiver module 1006, a read request transmission module 1008, a read token directive receiver module 1010, a requesting client response module 1012, and data segment regeneration module 1014, which are described below. In one embodiment, the apparatus is in a server 1 12 connected to a storage device 150 with a storage controller 152 and a data storage device 154, which are substantially similar to those described above. In one embodiment, the apparatus includes a token directive generation module 1002 that generates a storage request with a token directive. The token directive includes a request to store a data segment token on the storage device 150. The token directive is intended to be substituted for a series of repeated, identical characters or a series of repeated, identical character strings that would be sent to the storage device 150 and stored as a data segment if the data segment token was not sent in its place. In one embodiment, the series of repeated, identical characters indicate that the data segment is empty. For example, the series of repeated, identical characters may be zeros or ones and a data segment filled with zeros or ones may be interpreted as empty.
The token directive includes at least a data segment identifier and a data segment length. The data segment identifier is typically an object DD, file name, or other identifier known to a file system, application, server 112, etc. seeking to store the repeated, identical characters or character string on the storage device. The data segment length is typically the storage space required by the series of repeated, identical characters or character strings. The data segment token and the token directive typically do not include data of the data segment, such as the series of repeated, identical characters.
The token directive may, however, include other pertinent information for forming the data segment token, such as at least one instance of the repeated, identical character or character string. The token directive may also include metadata, such as a data segment location, an address from a file system, location on a data storage device corresponding to the data segment, etc. One of skill in the art will recognize other information that may be included with a token directive. In one embodiment, the directive, generation module 1002 generates a data segment token along with the token directive.
In one embodiment, the token directive generation module 1002 generates both a token directive and a secure erase command in response to a request to overwrite existing data on the storage device 150. The existing data includes data identified on the storage device with the same data segment identifier as the data segment identifier in the token directive. Typically, a request to overwrite data is sent where it is not sufficient to merely mark data as invalid or garbage, delete a pointer to the data, or other typical delete operation, but where the data is required to be overwritten in such a way that that the data is not recoverable. For example, the request to overwrite the data may be required where data is considered sensitive information and must be destroyed for security reasons.
The secure erase command directs the storage device 150 to overwrite existing data so that the existing data is non-recoverable. The storage device 150 then creates the data segment token as well as overwrites, recovers, erases, etc. the existing data. As a result, the existing data is non-recoverable and the data segment token is stored on the storage device 150, which typically takes much less storage space than the existing data.
In a further embodiment, the apparatus includes an erase confirmation module 1016 that receives a confirmation that the existing data on the storage device has been overwritten with characters so that the existing data is non-recoverable. The confirmation may be forwarded to a requesting device or client 114 and may be used to verify that the existing data has been put in a condition where it is non-recoverable. In other embodiments, the secure erase command may direct the storage device 150 to overwrite the existing data with a specific character or character string or the execute command may be executed multiple times. One of skill in the art will recognize other ways to configure one or more secure erase commands to ensure the existing data is non-recoverable.
Data may be encrypted and then stored on a storage device' 150 where encryption is accomplished using an encryption key received by the storage device 150 in conjunction with storing the data. Where the existing data is encrypted with this received encryption key before being stored, in another embodiment the token directive generation module 1002 generates an encryption erase command along with generating a token directive in response to receiving a request to overwrite the existing data. The encryption erase command erases the encryption key used to store the existing data so that the encryption key is non-recoverable.
In one embodiment, erasing the encryption key includes erasing the encryption key from the requesting device. In another embodiment, erasing the encryption key includes erasing the encryption key from a server, key vault, or other location where the encryption key is stored. Erasing the encryption key may include replacing the encryption key with other data or with a series of characters so that the encryption key cannot be recovered in any way. Erasing the encryption key typically makes the existing data on the storage device 150 non-recoverable where an encryption routine was used to encrypt the existing data that is robust enough to thwart attempts to decrypt the existing data. The request to overwrite the existing data could be a secure erase directive where the data is overwritten for security reasons, a request to overwrite data to erase the data, a request that seeks to replace the existing data with the repeated, identical characters or character strings, or the like. In one embodiment, a secure erase directive causes devices to both securely erase the encryption key and securely erase the existing data. In one embodiment, erasure of the encryption key may allow secure erasure of the data on the storage device to be postponed until a garbage collection process erases the data as part of a storage space recovery process. One of skill in the art will recognize other ways to erase an encryption key and other ways to receive a request to overwrite existing data. In one embodiment, a token directive includes the data segment token and the token directive transmission module 1004 transmits the data segment token with the token directive. In another embodiment, a token directive does not include the data segment token and includes a command for the storage device 150 to generate the data segment token. In this embodiment, the token directive transmission module 1004 transmits the token directive with the command to generate a data segment token, but does not transmit a data segment token.
The apparatus includes a token directive transmission module 1004 that transmits the token directive to the storage device 150. Typically, the token directive transmission module 1004 transmits the token directive as part of a storage request. The storage request may be in the form of an object request, a data request, or other form known to those of skill in the art. Where the token directive generation module 1002 generates a secure erase directive, the token directive transmission module 1004 transmits the secure erase directive to the storage device 150. Where the token directive generation module 1002 generates an erase encryption key command, the erase encryption key command is transmitted, where necessary, to another device to execute the command.
In one embodiment, the token directive transmission module 1004 transmits a token directive without a data segment token. In this embodiment, the token directive includes instructions and information for the storage device 150 to create a data segment token. In another embodiment, the token directive transmission module 1004 transmits a token directive that includes a data segment token. In this embodiment, the storage device 150 is capable of recognizing that the data segment token received with the token directive represents a data segment and takes appropriate action to store the data segment token such that the data segment token represents the data segment rather than merely storing the data segment token as ordinary data.
The apparatus, in a particular embodiment, includes a read receiver module 1006 that receives a storage request to read the data segment from the storage device 150 and a read request transmission module 1008 that transmits the storage request to the storage device 150. Typically, the storage request is received from a requesting client 114, such as an external client 114, a client 114 internal to the server 112, such as an application or file server running on the server 112, etc. One of skill in the art will recognize other devices and software functioning as a requesting client 114 from which the read receiver module 1006 can receive a storage request.
The storage request includes a request to read the data segment corresponding to the data segment token requested to be stored in the token directive transmitted to the storage device 150 by the token directive transmission module 1004. The requesting client 114, in one embodiment, is unaware that the data segment has been stored in the form of a data segment token. In another embodiment, the requesting device is aware that the data segment has been stored as a data segment token but is unaware of the information stored in the data segment token. The apparatus, in the particular embodiment, also includes a read token directive receiver module 1010 that receives a message corresponding to the requested data segment token from the storage device, where the message includes at least the data segment identifier and the data segment length. The message typically does not include data of the data segment. The message may also include other information stored in the data segment token, such as a data segment location or the repeated, identical character or character string. In the particular embodiment, the apparatus includes a requesting client response module 1012 that transmits a response to the requesting client 1 13 formulated from the message received from the storage device 150.
In one embodiment, read token directive receiver module 1010 also receives in the message a confirmation that existing data has been overwritten with characters such that the existing data is non-recoverable, where the existing data has been previously stored on the storage device and referenced with the same data segment identifier from the data segment token received in the message. The confirmation may also be received from the storage device 150 independently from any storage request to read the data segment. In another embodiment, where the requesting client 114 requires the data segment, the apparatus includes a data segment regeneration module 1014 that reconstitutes data of the data segment using information contained in the message. In this case, the response sent to the requesting client includes the reconstituted data segment. In another embodiment, the response sent to the requesting client includes information contained in the message received from the storage device 150. The requesting client 114 may then reconstitute the data segment or use the information in some other way. In another embodiment, the message includes the data segment token. The data segment token may be used by the data segment regeneration module 1014 to reconstitute the data segment before forwarding to the requesting client 114 or the requesting client response module 1012 may simply forward the data segment token. In one embodiment, the storage request with the token directive also includes a request to reserve storage space on the storage device 150, where the requested reserved storage space is an amount of storage space that is about the same to the data segment length. In another embodiment, the request to reserve storage space is for an amount of storage space different than the data segment length. For example, if the storage device 150 is a solid-state storage device 102, the solid-state storage device 102 may be connected to a hard drive or other long-term, inexpensive storage while the solid-state storage 110 is configured as cache for the long-term storage. The request to reserve storage may cause the solid-state storage device 102 to flush a portion of the cache to the long-term storage in preparation for writing data to the solid-state storage device 102. One of skill in the art will recognize other situations were a request to reserve storage space is desired.
In one embodiment, an apparatus may be provided with a read receiver module 1006, a read request transmission module 1008, a read token directive receiver module 1010, and a requesting client response module 1012, which are substantially similar to those described above. In the embodiment, the modules 1006-1012 may be independent from an apparatus including a token generation module 1002 or a token directive transmission module 1004. In one embodiment, the apparatus includes a data segment regeneration module 1014, which is substantially similar to the data segment regeneration module 1014 described above. Figure 11 is a schematic flow chart diagram illustrating an embodiment of a method 1100 for generating and transmitting a token directive in accordance with the present invention. The method 1100 begins 1102 and the token directive generation module 1002 generates 1104 a storage request with a token directive, where the token directive includes a request to store a data segment token on the storage device 150. The token directive transmission module 1004 transmits 1106 the token directive to the storage device 150 and the method 1100 ends 1108. In one embodiment, the storage request includes a token directive to store the data segment token where the storage request is essentially free from data of the data segment. In another embodiment, storage request includes data from the data segment. In a preferred embodiment, a software application creates a storage request using the token directive so as to avoid the creation of the data segment. In another embodiment, a software application requests the creation of the token directive.
Figure 12 is a schematic flow chart diagram illustrating an embodiment of a method 1200 for reading a data segment token in accordance with the present invention. The method 1200 begins 1202 and the read receiver module 1006 receives 1204 a storage request to read a data segment from a storage device 150 from a requesting client 114. The read request transmission module 1008 transmits 1206 the storage request to the storage device 150.
The read token directive receiver module 1008 receives 1208 a message corresponding to the requested data segment token from the storage device 150, where the message includes at least the data segment identifier and the data segment length. The message is substantially free from data of the data segment. The requesting client response module 1012 transmits 1210 a response to the requesting client formulated from the message received from the storage device 150 and the method 1200 ends 1212.
Figure 13 is a schematic block diagram illustrating one embodiment of a system 1300 with an apparatus for managing a data segment token in accordance with the present invention. The system 1300 includes an apparatus with a write request receiver module 1302 and a data segment token storage module 1304, and in various embodiments a token directive generation module 1306, a read request receiver module 1308, a read data segment token module 1310, a read request response module 1312 with a transmit data segment token module 1314 and a transmit data segment module 1316, a reconstitute data segment module 1318, a secure erase module 1320 with an erase confirmation module 1322, and a storage space reservation module 1324, which are described below. The system 1300 includes a storage device 150 with a storage controller 152 and a data storage device 154, which are substantially similar to those described above. The system 1300 includes a requesting device 1326, which is described below, in communication with the storage device 150.
In the depicted embodiment, the modules 1302-1324 are included in the storage device 150 or storage controller 152. In another embodiment, at least a portion of one or more of the modules 1302-1324 is located outside the storage device 150. In a further embodiment, the requesting device 1326 includes a portion of the modules 1302-1324 in the form of drivers, software, or other function of one or more of the modules 1302-1324. For example, a token generation module 1306 and a reconstitute data segment module 1318 are shown in the requesting device 1326. One of skill in the art will recognize other ways to distribute and implement the functionality of the modules 1302-1324.
The apparatus includes a write request receiver module 1302 that receives a storage request from the requesting device 1326, where the storage request includes a request to store a data segment in the storage device 150. The data segment includes a series of repeated, identical characters or character strings. Typically, the series of repeated, identical characters signify that the data segment is empty. This is especially true when the series of repeated, identical characters are ones or zeros. The apparatus includes a data segment token storage module 1304 that stores a data segment token in the storage device 150. The data segment token includes at least a data segment identifier and a data segment length. The data segment token is substantially free of the actual data from the data segment.
The data segment token may be stored in many forms. In one embodiment, includes an entry in an index, where the index corresponds to information and data stored on the storage device 150. For example, the index may be an object index as described above in relation to the apparatus 200 depicted in Figure 2. The index may also be file system index, a block storage index, or other index known to those of skill in the art. In another embodiment, the data segment token includes or is in the form of metadata stored on the storage device 150. In another embodiment, the data segment token is stored as metadata on the storage device and includes an entry in an index. One of skill in the art will recognize other ways to storage a data segment token.
In one embodiment, the storage request includes a token directive to store the data segment token where the storage request is essentially free from data of the data segment. The token directive may include the data segment token or a command to generate a data segment token. Where the token directive does not include the data segment token, the data segment token storage module 1304 generates the data segment token from information in the token directive. If the token directive includes the data segment token, the data segment token storage module 1304 recognizes the data segment token as a data structure representing the data segment identified by the data segment identifier in the token directive and stores the data segment token appropriately.
Typically, where the data segment token storage module 1304 recognizes a data segment token, the data segment token is differentiated in some way from other data stored on the storage device 150. For example, a requesting device 1326 may merely compress data and send a compressed object, file, or data segment so that the storage device 150 does not distinguish the compressed data segment from other data received by way of other storage requests.
Where the data segment token storage module 1304 recognizes that a received data segment token is a data segment token, the data segment token storage module 1304 may store the data segment token in such a way that when read, it may appear as a data segment rather than the data segment token. One of skill in the art will recognize other ways that the data segment token storage module 1304 may store a data segment token after recognizing that a received data segment token is a data segment token rather than a data segment.
In another embodiment, storage request includes data from the data segment. In this embodiment, the apparatus includes a token generation module 1306 that generates a data segment token from the data segment, where the data segment token is created in response to the storage request to store the data segment. In a further embodiment, the token generation module 1306 resides in the requesting device 1326, possibly in the form of a driver.
In one embodiment, the apparatus includes a secure erase module 1320 that overwrites existing data with characters such that the existing data is non-recoverable, where the existing data includes data of a data segment previously stored on the storage device identified with the same data segment identifier as the data segment identified in the storage request. In this embodiment, a data segment token is stored with the data segment identifier and data segment length and existing data identified by the same data segment identifier stored in the data segment token is erased by overwriting the existing data. Typically the existing characters are overwritten by zeros, ones, or some other character string so that the existing data is destroyed and is non-recoverable.
In a further embodiment, the secure erase module also includes an erase confirmation module 1322 that transmits a message indicating that the existing data has been overwritten. Typically the message is sent to the requesting device 1326. The erase confirmation message is transmitted after the secure erase module 1320 has overwritten the existing data. The message may be transmitted in the same transaction as the storage request or in a different transaction.
In another embodiment, the secure erase module 1320 overwrites the existing data during a storage space recovery operation. For example, if the storage device 150 is a solid-state storage device 102, as described above, the storage space recovery operation may be related to the garbage collection describe in relation to the apparatus 800 depicted in Figure 8. However, a storage space recovery operation involving a request to overwrite the existing data would typically be expedited so that the storage location where the existing data is stored is necessarily recovered prior to any confirmation message is sent by the erase confirmation module 1322. In one embodiment, the existing data is marked or otherwise identified to indicate that a secure erase has been requested. The confirmation message would typically not be sent until the existing data marked for erasure has been overwritten and made non-recoverable. In another embodiment, the secure erase module 1320 merely marks the existing data as invalid for later storage space recovery. In another embodiment, the secure erase updates an index to indicate that the existing data is invalid and prevents access to this data until the data is overwritten during later storage space recovery.
In one embodiment, the secure erase module 1320 overwrites the existing data each time a data segment token is stored. In another embodiment, the storage request specifically includes a request to overwrite the existing data and the secure erase module 1320 overwrites the existing data in response to the request to overwrite the existing data. In another embodiment, the secure erase module 1320 stores metadata information regarding confirmation that the existing data has been erased so that subsequent reads can indicate the erasure.
In other embodiments where a secure erase is not received, the existing data is deleted. In one embodiment, deleting the data includes deleting an index entry, address, etc. In a preferred embodiment, the when a data segment token is stored, the corresponding existing data is marked as invalid or otherwise ready for storage recovery. The data may be later recovered in a storage recovery operation, garbage collection operation, etc.
In a particular embodiment, the apparatus includes a read request receiver module 1308 that receives a storage request to read the data segment, a read data segment token module 1310 that reads the data segment token corresponding to the data segment requested by the storage request, and a read request response module 1312 that transmits a response to the requesting device 1326. The response is generated using the data segment token corresponding to the requested data segment. The storage request to read the data segment, in one embodiment, is associated with the storage request and serves to confirm that the storage request has been successful. In another embodiment, the request to read the data segment is independent from the storage request and may be initiated by the requesting device 1326 that made the storage request or another separate requesting device 1326. In one embodiment, where the requesting device is capable of receiving information from the data segment token in place of actual data, the read request response module 1312 includes a transmit data segment token module 1314 that transmits in the response a message to the requesting device 1326. The message includes at least the data segment identifier and the data segment length, but may also include a data segment location, at least one instance of the repeated, identical character or character string, or other pertinent information. Typically, the message does not include the actual data of the data segment, other than what is included in the data segment token.
In another embodiment, where the requesting device 1326 is expecting to receive a data segment, the apparatus includes a reconstitute data segment module 1318 that reconstitutes data of the data segment using the data segment token. The read request response module 1312 also includes a transmit data segment module 1316 that transmits the reconstituted requested data segment to the requesting device 1326. In another embodiment, the reconstitute data segment module 1318 resides at the requesting device 1326, possibly as in the form of a driver, and the transmit data segment token module 1314 transmits the message with the data segment token information to the requesting device 1326. The reconstitute data segment module 1318 at the requesting device 1326 reconstitutes the requested data segment from the message.
In one embodiment, the system 1300 includes a separate apparatus that includes a read request receiver module 1308, a read data segment token module 1310, a read request response module 1312, which are substantially similar to those described above. The apparatus may be independent from the apparatus including the write request receiver module 1302 and the data segment token storage module 1304. In one embodiment, the read request response module 1312 includes a transmit data segment token module 1314 and/or a transmit data segment module 1316, and the apparatus may include a reconstitute data segment module 1318, where the modules 1314, 1316, 1318 are substantially similar to those described above. Figure 14 is a schematic flow chart diagram illustrating an embodiment of a method 1400 for storing a data segment token in accordance with the present invention. The method 1400 begins 1402 and the write request receiver module 1302 receives 1404 a storage request from the requesting device 1326, where the storage request includes a request to store a data segment in the storage device 150. The data segment includes a series of repeated, identical characters or character strings. The a data segment token storage module 1304 stores 1406 a data segment token in the storage device 150 and the method 1400 ends 1408. The data segment token includes at least a data segment identifier and a data segment length and the data segment token does not include data from the data segment for the most part. Figure 15 is a schematic flow chart diagram illustrating an embodiment of a method 1500 for reading a data segment token in accordance with the present invention. The method 1500 begins 1502 and the read request receiver module 1308 receives 1504 a storage request to read a data segment from the storage device 150. The data segment is represented on the storage device by a data segment token and the data segment includes a series of repeated, identical characters or character strings. The data segment token includes at least a data segment identifier and a data segment length and the data segment token does not include data from the data segment. The a read data segment token module 1310 reads 1506 the data segment token corresponding to the data segment requested in the storage request, the read request response module 1312 transmits 1508 a response to the requesting device 150 and the method 1500 ends 1510. The response is generated using the data segment token corresponds to the requested data segment. PROGRESSIVE RAID
A redundant array of independent drives ("RAID") can be structured in many ways to achieve various goals. As described herein, a drive is a mass storage device for data. A drive, or storage device, may be a solid-state storage 110, a hard disk drive ("HDD"), a tape drive, an optical drive, or any other mass storage device known to those of skill in the art. In one embodiment, a drive comprises a portion of a mass storage device accessed as a virtual volume. In another embodiment, a drive includes two or more data storage devices accessible together as a virtual volume and configured in a storage area network ("SAN"), as a RAID, as just a- bunch of disks/drives ("JBOD"), etc. Typically, a drive is accessed as a single unit or virtual volume through a storage controller 152. In a preferred embodiment, the storage controller 152 comprises a solid-state storage controller 104. One of skill in the art will recognize other forms of a drive in the form of a mass storage device that may be configured in a RAID. In the embodiments described herein, a drive and a storage device 150 are used interchangeably. Traditionally, the various RAID configurations are called RAID levels. One basic RAID configuration is RAID level 0 which creates a mirror copy of a storage device 150. An advantage of RAID 0 is that a complete copy of data on one or more storage devices 150 is also available on a mirror copy of the one or more storage devices 150 so that reading the data on the primary drives or mirrored drives is relatively fast. RAID 0 also provides a backup copy of data in case of a failure in the primary storage devices 150. A disadvantage of RAID 0 is that writes are relatively slow because written data must be written twice.
Another traditional RAID configuration is RAID level 1. In RAID 1, data written to the RAID is divided into N data segments corresponding to N storage devices 150 in a set of storage devices 150. The N data segments form a "stripe." By striping data across multiple storage devices 150, performance is enhanced because the storage devices 150 can work in parallel to store the N data segments faster than a single storage device 150 can save data comprising the N data segments. Reading data is relatively slow, however, because is data may be spread over multiple storage devices 150 and access time of multiple storage devices 150 is typically slower than reading data from one storage device 150 containing all of the desired data. In addition, RAID 1 provides no failure protection.
A popular RAID configuration is RAID level 5 which includes striping of N data segments across N storage devices 150 and storing a parity data segment on an N+l storage device 150. RAID 5 offers failure tolerance because the RAID can tolerate a single failure of a storage device 150. For example, if a storage device 150 fails, missing a data segment of a stripe can be created using the other available data segments and the parity data segment calculated specifically for the stripe. RAID 5 also typically uses less storage space than RAID 0 because each storage device 150 of the RAIDed set of storage devices 150 is not required to store a complete copy of the data, but only a data segment of a stripe or a parity data segment. RAID 5, like RAID 1 , is relatively fast for writing data, but is relatively slow for reading data. Writing data for a typical traditional RAID 5 is slower than for RAID 1 , however, because a parity data segment must be calculated for each stripe from the N data segments of the stripe.
Another popular RAID configuration is RAID level 6 which includes dual distributed parity. In RAID 6, two storage devices 150 are assigned as parity-mirror devices (e.g. 1602a, 1602b). Each parity data segment for a stripe is calculated separately so that losing any two storage devices 150 in the storage device set is recoverable using the remaining, available data segments and/or parity data segments. RAID 6 has similar performance advantages and disadvantages as RAID 5. Nested RAID may also be used to increase fault tolerance where high reliability is required. For example, two storage device sets, each configured as RAID 5, may be mirrored in a RAID 0 configuration. The resulting configuration may be called RAID 50. If RAID 6 is used for each mirrored set, the configuration may be called RAID 60. Nested RAID configurations typically have similar performance issues as the underlying RAID groups.
From the foregoing discussion, it should be apparent that a need exists for an apparatus, system, and method for progressive RAID that offers the benefits of fault tolerance, faster data writing than traditional fault-tolerant RAID levels, such as RAID 0, RAID 5, RAID 6, etc. while also offering faster data reading than traditional striped RAID levels, such as RAID 1, RAID 5, RAID 6, etc.. Beneficially, such an apparatus, system, and method would write N data segments to a parity-mirror storage device 1602, offering the advantage of a RAID 0 system, until the parity data segment is required to be calculated, such as before or part of a storage consolidation operation.
Figure 10 is a schematic block diagram illustrating one embodiment of a system 1600 for progressive RAID in accordance with the present inventions. The system 1600 includes N storage devices 150 and M parity-mirror storage devices 1602 accessible through a computer network 116 by one or more clients 114. The N storage devices 150 and parity-mirror storage devices 1602 may be located in one or more servers 112. The storage devices 150, servers 112, computer network 116, and clients 114 are substantially similar to those described above. The parity-mirror devices 1602 are typically similar or identical to the N storage devices 150 and are typically designated as a parity-mirror storage device 1602 for a stripe.
In one embodiment, the N storage devices 150 and M parity-mirror storage devices 1602 are included in or accessible through one server 112 and may be networked together using a system bus, SAN, or other computer network 116. In another embodiment, the N storage devices 150 and M parity-mirror storage devices 1602 are located in or accessible through multiple servers 112a-n+m. For example, the storage devices 150 and parity-mirror storage devices 1602 may be part of an in-server SAN as described above in relation to the system 103 of Figure 1C and the method 105 of Figure 5B.
In one embodiment, a parity-mirror storage device 1602 stores all parity data segments of the stripes stored in the progressive RAID. In another preferred embodiment, a storage device 150 of the storage device set 1604 assigned to the progressive RAID is assigned to be a parity- mirror storage device 1602 for a particular stripe and the assignment is rotated so that the parity data segments are rotated, for each stripe, among the N+M storage devices 150. This embodiment, offers a performance advantage over assigning a single storage device 150 to be a parity-mirror storage device 1602 for each stripe. By rotating the parity-mirror storage device 1602, the overhead associated with calculating and storing parity data segments can be distributed.
In one embodiment, the storage devices 150 are solid-state storage devices 102, each with associated solid-state storage 110 and a solid-state storage controller 104. In another embodiment, each storage device 150 includes a solid-state storage controller 104 and associated solid-state storage 110 acts as cache for other less expensive, lower performance storage, such as tape storage or hard disk drives. In another embodiment, one or more of the servers 112 include one or more clients 114 that send storage requests to the progressive RAID. One of skill in the art will recognize other system configurations with N storage devices 150 and one or more parity-mirror storage devices 1602 that may be configured for progressive RAID.
Figure 17 is a schematic block diagram illustrating one embodiment of an apparatus 1700 for progressive RAID in accordance with the present invention. The apparatus 1700 includes, in various embodiments, a storage request receiver module 1702, a striping module 1704, a parity- mirror module 1706, and a parity progression module 1708, a parity alteration module 1710, a mirrored set module 1712, an update module 1714, a mirror restoration module 1716 with a direct client response module 1718, a pre-consolidation module 1720, a post-consolidation module 1722, a data rebuild module 1724, and a parity rebuild module 1726, which are described below. The modules 1702-1726 are depicted in a server 112, but some or all of the functions of the modules 1702-1726 may also be distributed in multiple servers 112, storage controllers 152, storage devices 150, clients 114, etc.
The apparatus 1700 includes a storage request receiver module 1702 that receives a request to store data, where the data is data of a file or of an object. In one embodiment, the storage request is an object request. In another embodiment, the storage request is a block storage request. The storage request in one embodiment, does not include data, but includes commands that can be used by the storage devices 150 and parity-mirror storage devices 1602 to DMA or RDMA data from a client 114 or other source. In another embodiment, the storage request includes data to be stored as a result of the storage request. In another embodiment, the storage request includes one command capable of having the data stored in the storage device set 1604. In another embodiment, the storage request includes multiple commands. One of skill in the art will recognize other storage requests to store data appropriate for progressive RAID.
The data is stored in a location accessible to the apparatus 1700. In one embodiment, the data is available in a random access memory ("RAM"), such as a RAM used by the client 114 or server. In another embodiment, the data is stored in a hard disk drive, tape storage, or other mass storage device. In one embodiment, the data is configured as an object or as a file. In another embodiment, the data is configured as a data block which is part of an object or a file. One of skill in the art will recognize other forms and locations for the data that is the subject of the storage request. The apparatus 1700 includes a striping module 1704 that calculates a stripe pattern for the data. The stripe pattern includes one or more stripes, where each stripe includes a set of N data segments. Typically the number of data segments in a stripe depends on how many storage devices 150 are assigned to the RAID group. For example, if RAID 5 is used, one storage device 150 is assigned as a parity-mirror storage device 1602a to store parity data for a particular stripe. If four other storage devices 150a, 150b, 150c, 150d are assigned to the RAID group, a stripe will have four data segments in addition to the parity data segment. The striping module 1704 writes N data segments to N of a stripe to N storage devices 150a-n so that each of the N data segments is written to a separate storage device 150a, 150b, ... 150n within a set 1604 of storage devices 150 assigned to the stripe. One of skill in the art will appreciate various combinations of storage devices 150 that may be assigned to a RAID group for a particular RAID level and how to create a striping pattern and divide data into N data segments per stripe.
The apparatus 1700 includes a parity-mirror module 1706 that writes a set of N data segments of the stripe to one or more parity-mirror storage devices 1602 within the storage device set 1604, where the parity-mirror storage devices 1602 are in addition to the N storage devices 150. The N data segments are then available for future calculation of a parity data segment. Rather than immediately calculating the parity data segment, the parity-mirror module 1706 copies the set of N data segments to the parity-mirror storage devices 1602, which typically requires less time than storing the N data segments. Once the N data segments are stored on the parity-mirror storage device 1602, the N data segments are available to be read or used to restore data if one of the N storage devices 150 becomes unavailable. Reading data also has the advantages of a RAID 0 configuration because all of the N data segments are available together from one storage device (e.g. 1602a). For more than one parity-mirror storage device (e.g. 1602a, 1602b), the parity-mirror module 1706 copies the N data segments to each parity-mirror storage device 1602a, 1602b. The apparatus 1700 includes a parity progression module 1708 that calculates one or more parity data segments for the stripe in response to a storage consolidation operation. The one or more parity data segments calculated from the N data segments are stored on the parity- mirror storage devices 1602. The parity progression module 1708 stores a parity data segment on each of the one or more parity-mirror storage devices 1602. The storage consolidation operation is conducted to recover at least storage space or data or both on at least one of the one or more parity-mirror storage devices 1602. For example, a storage consolidation operation may be a data garbage collection on a solid-state storage device 102 as described above in relation to the apparatus 800 and method 900 of Figures 8 and 9. The storage consolidation operation may also include a defragmentation operation for a hard disk drive, or other similar operation that consolidates data to increase storage space. The storage consolidation operation, as used herein, may also include an operation to recover data, for example, if a storage device 150 is unavailable, to recover from an error, or other reason for reading data from the parity-mirror storage device 1602. In another embodiment, the parity generation module 1708 simply calculates the parity data segment when the parity-mirror storage device 1602 is less busy.
Advantageously, by delaying calculation and storage of the parity data segment of a stripe, the N data segments on the parity-mirror storage device 1602 are available for reading the data segments, recovering data, rebuilding data on a storage device 150 until more storage space is needed on the parity-mirror storage device 1602 or other reason for a storage consolidation operation. The parity progression module 1708 may then run as a background operation, autonomously from the storage request receiver module 1702, the striping module 1704, or the parity-mirror module 1706. One of skill in the art will easily recognize other reasons to delay calculation of a parity data segment as part of a progressive RAID operation.
In one embodiment, some or all of the functions of the modules 1702-1708, receiving an request to store data, calculating a stripe pattern and writing N data segments to the N storage devices, writing a set of N data segments to a parity-mirror storage device, and calculating the parity data segment, occur on a storage device 150 of the storage device set 1604, a client 114, and a third-party RAID management device. The third-party RAID management device may be a server 114 or other computer. In one embodiment, the apparatus 1700 includes a parity alternation module 1710 that alternates, for each stripe, which of the storage devices 150 within the storage device set 1604 are assigned to be the one or more parity-mirror storage devices 1602 for the stripe. As discussed above in relation to the system 1600 of Figure 10, by rotating which storage device 150 is used for the parity-mirror storage device for a stripe, the work calculation of the various parity data segments is spread among the storage devices 150 of a storage device set 1604.
In another embodiment, the storage device set 1604 is a first storage device set and the apparatus 1700 includes a mirrored set module 1712 that creates one or more storage device sets in addition to the first storage set 1604 so that each of the one or more additional storage device sets include at least an associated striping module 1704 that writes the N data segments to N storage devices 150 of each of the one or more additional storage sets. In a related embodiment, each of the one or more additional storage device sets includes an associated a parity-mirror module 1706 for storing a set of the N data segments and a parity progression module 1708 for calculating one or more parity data segments. Where the mirrored set module 1712 creates one or more mirrored storage device sets, the RAID may be a nested RAID such as RAID 50. In this embodiment, the RAID level may be progressed from a RAID 10 where data is striped and mirrored, to a RAID 50 or RAID 60, where a parity data segment is calculated and stored for each storage device set 1604.
In one embodiment, the apparatus 1700 includes and update module 1714. The update module 1714 is typically used where the N data segments on a parity-mirror storage device 1602 have not been progressed to a parity data segment. The update module 1714 receives an updated data segment, where the updated data segment corresponds to an existing data segment of the N data segments stored on the N storage devices 150. The update module 1714 copies the updated data segment to the storage device 150 of the stripe where the existing data segment is stored and to the one or more parity-mirror storage devices 1602 of the stripe. The update module 1714 replaces the existing data segment stored on the storage device 150 of the N storage devices 150a-n with the updated data segment and replaces the corresponding existing data segment stored on the one or more parity-mirror storage devices 1602 with the updated data segment.
In one embodiment replacing a data segment includes writing the data segment to a storage device 150 and then marking a corresponding data segment as invalid for subsequent garbage collection. An example of this embodiment is described for solid-state storage 110 and the garbage collection apparatus described above in relation to Figures 8 and 9. In another embodiment, replacing a data segment includes overwriting an existing data segment with an updated data segment. In one embodiment, the set of storage devices 1604 is a first storage device set and the apparatus 1700 includes a mirror restoration module 1716 that recovers a data segment stored on a storage device 150 of the first storage set 1604 where the storage device 150 of the first storage set 1604 is unavailable. The data segment is recovered from a mirror storage device containing a copy of the data segment. The mirror storage device includes one of a set of one or more storage devices 150 that stores a copy of the N data segments.
In a further embodiment, the mirror restoration module 1716 recovers the data segment in response to a read request from a client 114 to read the data segment. In another related embodiment, the mirror restoration module 1716 also includes a direct client response module 1718 that sends the requested data segment to the client 114 from the mirror storage device. In this embodiment, the requested data segment is copied to the client 114 so that the client 114 does not have to wait until the data segment is recovered before transmitting the data segment on to the client 114.
In one embodiment, the apparatus 1700 includes a pre-consolidation restoration module 1720 that recovers a data segment stored on a storage device 150 of the storage set 1604 in response to a request to read the data segment. In the embodiment the storage device 150 is unavailable and the data segment is recovered from the a parity-mirror storage device 1602 prior to the parity progression module 1708 generating the one or more parity data segments on the one or more parity-mirror storage devices 1602. In another embodiment, the apparatus 1700 includes a post-consolidation restoration module 1724 that recovers a data segment stored on a storage device 150 of the storage set. In the embodiment, the storage device 150is unavailable and the data segment is recovered using one or more parity data segments stored on one or more of the parity-mirror storage devices 150 after the parity progression module 1708 generates the one or more parity data segments. For example, the post-consolidation restoration module 1724 uses a parity data segment and available data segments on the available N storage devices 150 to recreate the missing data segment.
In one embodiment, the apparatus 1700 includes a data rebuild module 1724 that stores a recovered data segment on a replacement storage device in a rebuild operation, where the recovered data segment matches an unavailable data segment stored on an unavailable storage device 150. The unavailable storage device 150 is one of the N storage devices 150 of the storage device set 1602. Typically, the rebuild operation occurs after a failure of the storage device 150 that stores the unavailable data segment. The rebuild operation is to restore data segments onto the replacement storage device to match data segments stored previously on the unavailable storage device 150.
The data segment may be recovered for the rebuild operation from several sources. For example, the data segment may be recovered from a parity-mirror storage device 1602 prior to progression if the matching data segment resides on the parity-mirror storage device 1602. In another example, the data segment may be recovered from a mirror storage device containing a copy of the unavailable data segment. Typically the data segment is recovered from the mirror storage device if the recovered data segment does not reside on the one or more parity-mirror storage devices 1602, but may be recovered from the mirror storage device even if the matching data segment is available on the mirror storage device. In another example, a regenerated data segment is regenerated from one or more parity data segments and available data segments of the N data segments if the recovered data segment does not reside on a parity-mirror storage device 1604 or the mirror storage device. Typically the missing data segment is regenerated only if it does not exist on another storage device 150 in some form.
In another embodiment, the apparatus 1700 includes a parity rebuild module 1726 that rebuilds a recovered parity data segment on a replacement storage device in a parity rebuild operation where the recovered parity data segment matches an unavailable parity data segment stored on an unavailable parity-mirror storage device. The unavailable parity-mirror storage device is one of the one or more parity-mirror storage devices 1602. The parity rebuild operation restores parity data segments onto the replacement storage device to match parity data segments stored previously on the unavailable parity-mirror storage device.
To regenerate the recovered parity data segment in the rebuild operation, data used for the rebuild may be from various sources. In one example, the recovered parity data segment is recovered using a parity data segment stored on a parity-mirror storage device 1602 in a second set of storage devices 150 storing a mirror copy of the stripe. Where a mirror copy is available, using the mirrored parity data segment is desirable because the recovered parity data segment does not have to be recalculated. In another example, the recovered parity data segment is regenerated from the N data segments stored on one of the N storage devices 150 if the N data segments are available on the N storage devices. Typically, the N data segments would be available on the N storage devices 150 where a single failure occurs on the parity-mirror storage device 1602 being rebuilt.
In another example, the recovered parity data segment is regenerated from one or more storage devices 150 of the second set of storage devices 150 storing copies of the N data segments if one or more of the N data segments are unavailable from the N storage devices 150 of the first storage device set 1604 and a matching parity data segment is not available on the second set of storage devices 150. In yet another example, the recovered parity data segment is regenerated from the available data segments and non-matching parity data segments regardless of their location within the one or more sets of storage devices 150. Where the parity-mirror storage device is alternated among the storage devices 150 of the storage device set 1604, typically the data rebuild module 1724 and the parity rebuild module 1726 act in conjunction to rebuild data segments and parity data segments on a rebuilt storage device 150. Where a second parity-mirror storage device 1602b is available, the data rebuild module 1724 and the parity rebuild module 1726 can rebuild two storage devices after a failure of two storage devices 150, 1602 of the storage device set 1604. Where a parity-mirror storage device 1602 is not progressed to create a parity-mirror data segment, recovery of a data segment or a storage device 150 is quicker than if the parity-mirror storage device 1602 is progressed and the parity data segment for a stripe has been calculated and stored and the N data segments on the parity-mirror storage device 1602 used to calculate the parity data segment have been deleted.
Figure 18 is a schematic block diagram illustrating one embodiment of an apparatus 1800 for updating a data segment using progressive RAED in accordance with the present invention. Typically, the apparatus 1800 pertains to a RAID group where one or more of the parity-mirror storage devices 1602 have been progressed and include a parity daa segment and not the N data segments used to create the parity data segment. The apparatus 1800 includes an update receiver module 1802, an update copy module 1804, a parity update module 1806, which are described below. The modules 1802-1806 of the apparatus 1800 are depicted in a server 112, but may be in a storage device 150, a client 114, or any combination of devices, or may be distributed among several devices.
A stripe, data segments, storage devices 150, a storage device set 1604, parity data segments, and the one or more parity-mirror storage device 1602 are substantially similar to a stripe as describe above in relation to the apparatus 1700 of Figure 17. The apparatus 1800 includes an update receiver module 1802 that receives an updated data segment where the updated data segment corresponds to an existing data segment of an existing stripe. In another embodiment, the update receiver module 1802 may also receive multiple updates and may handle the updates together or separately.
The apparatus 1800 includes an update copy module 1804 that copies the updated data segment to the storage device 150 where the corresponding existing data segment is stored and to the one or more parity-mirror storage devices 1602 corresponding to the existing stripe. In another embodiment, the update copy module 1804 copies the updated data segment to either the parity-mirror storage device 1602 or to the storage device 150 storing the existing data segment and then verifies that a copy of the updated data segment is forwarded to the other device 1602, 150. The apparatus 1800 includes a parity update module 1806 that calculates one or more updated parity data segments for the one or more parity-mirror storage devices of the existing stripe in response to a storage consolidation operation. The storage consolidation operation is similar to the storage consolidation operation described above in relation to the apparatus 1700 in Figure 17. The storage consolidation operation is conducted to recover at least storage space and/or data on one or more parity-mirror storage devices 1602 with the one or more updated parity data segments. By waiting to update the one or more parity data segments, the" update can be postponed until it is more convenient or until necessary to consolidate storage space.
In one embodiment, the updated parity data segment is calculated from the existing parity data segment, the updated data segment, and the existing data segment. In one embodiment, the existing data segment is maintained in place prior to reading the existing data segment for generation of the updated parity data segment. An advantage to this embodiment, is the overhead associated from copying the existing data segment to the parity-mirror storage device 1602 or other location where the updated parity data segment is generated can be postponed until necessary. A disadvantage of this embodiment is that if the storage device 150 that maintains the existing data segment fails, the existing data segment must be recovered before the updated parity data segment can be generated.
In another embodiment, the existing data segment is copied to the data-mirror storage •device 1602 when the storage device 150 of the N storage devices 150a-n where the existing data segment is stored receives a copy of the updated data segment. The existing data segment is then stored until the storage consolidation operation. In another embodiment, the existing data segment is copied to the data-mirror storage device 1602 in response to a storage consolidation operation on the storage device 150 of the N storage devices 150a-n where the existing data segment is stored if the storage consolidation operation occurs before the storage consolidation operation that triggers calculation of the updated parity data segment. The latter embodiment is advantageous because the existing data segment is not copied until required by a storage consolidation operation on either the storage device 150 where the existing data segment is stored or on the parity-mirror storage device 1602.
In one embodiment, the updated parity data segment is calculated from the existing parity data segment, the updated data segment, and a delta data segment, where the delta data segment is generated as a difference between the updated data segment and the existing data segment. Typically, generating a delta data segment is a partial solution or intermediate step in updating the parity data segment. Generating a delta data segment is advantageous because it may be highly compressible and may be compressed before transmission. In one embodiment, the delta data segment is stored on the storage device storing the existing data segment prior to reading the delta data segment for generation of the updated parity data segment. In another embodiment, the delta data segment is copied to the data-mirror storage device 1602 when the storage device 150 where the existing data segment is stored receives a copy of the updated data segment. In another embodiment, the delta data segment is copied to the data-mirror storage device 1602 in response to a storage consolidation operation on the storage device 150 where the existing data segment is stored. As with copying the existing data segment, the latter embodiment is advantageous because the delta data file is not moved until the earlier of a storage consolidation operation on the storage device 150 storing the existing data segment or another storage consolidation operation triggering calculation of the updated parity data segment.
In various embodiments, all of a portion of the actions of the modules 1802, 1804, 1806, namely receiving an updated data segment, copying the updated data segment, and calculating the updated parity data segment, occurs on a storage device 150 of the storage device set 1604, a client 114, or a third-party RAID management device. In another embodiment, the storage consolidation operation is conducted autonomously from the operations of the update receiver module 1802 and the update copy module 1804.
Figure 19 is a schematic flow chart diagram illustrating an embodiment of a method 1900 for managing data using progressive RAIDing in accordance with the present invention. The method 1900 begins 1902 and the storage request receiver module 1702 receives 1904 a request to store data, where the data is data of a file or of an object. The striping module 1704 calculates a stripe pattern for the data and writes 1906 the N data segments to N storage devices 150. The stripe pattern includes one or more stripes. Each stripe includes a set of N data segments where each of the N data segments is written to a separate storage device 150 within a set of storage devices 1604 assigned to the stripe.
The parity-mirror module 1706 writes 1908 a set of N data segments of the stripe to one or more parity-mirror storage devices 1602 within the set of storage devices 1604. The one or more parity-mirror storage devices are in addition to the N storage devices 150a-n. The parity generation module 1708 determines 1910 if there is a pending storage consolidation operation. If the parity generation module 1708 determines 1910 that there is no pending storage consolidation operation, the method 1900 returns and again determines 1910 if there is a pending storage consolidation operation. In other embodiments, the storage request receiver module 1702, the striping module 1704, and the parity-mirror module 1706, continue to receive storage requests, calculate striping patterns, and storing data segments. If the parity generation module 1708 determines 1910 that there is no pending storage consolidation operation, the parity generation module 1708 calculates 1914 a parity data segment for the stripe. The parity data segment is calculated from the N data segments stored on a parity-mirror storage device 1602. The parity generation module 1708 stores 1912 the parity data segment on the parity-mirror storage devicel602 and the method 1900 ends 1916. The storage consolidation operation is conducted autonomously from receiving 1904 a request to store N data segments, writing 1906 the N data segments to the N storage devices, or writing 1908 the N data segments to one or more parity-mirror storage devices. The storage consolidation operation is conducted to recover at least storage space or data on the parity-mirror storage device 1602.
Figure 20 is a schematic flow chart diagram illustrating an embodiment of a method 2000 for updating a data segment using progressive RAIDing in accordance with the present invention. The method 2000 begins 2002 and the update receiver module 1802 receives 2004 an updated data segment where the updated data segment corresponds to an existing data segment of an existing stripe. The update copy module 1804 copies 2006 the updated data segment to the storage device 150 where the corresponding existing data segment is stored and to the one or more parity-mirror storage devices 1602 corresponding to the existing stripe.
The parity update module 1806 determines 2008 if a storage consolidation operation is pending. If the parity update module 1806 determines 2008 that there is no pending storage consolidation operation, the parity update module 1806 waits for a storage consolidation operation. In one embodiment, the method 2000 returns and receives 2004 other updated data segments and copies 2006 the updated data segments. If the parity update module 1806 determines 2008 that there is no pending storage consolidation operation, the parity update module 1806 calculates 2010 one or more updated parity data segments for the one or more parity-mirror storage devices of the existing stripe and the method 2000 ends 2012. FRONT-END DISTRIBUTED RAID
Traditional RAID systems are configured with a RAID controller that functions to receive data, calculate striping patterns for the data, divide the data into data segments, calculate a parity stripe, store the data on storage devices, update the data segments, etc. While some RAID controllers allow some functions to be distributed, the storage devices managed by the RAID controller do not communicate with clients 114 directly for storing data striped in a RAID. Instead storage requests and data for RAIDing pass through the storage controller.
Requiring the RAID controller to touch all of the data to be stored in a RAID is inefficient because it creates a dataflow bottleneck. This is especially true during a read-modify- write process where bandwidth and performance of all of the drives in the RAID group is consumed while only a subset is actually updated. In addition, the a region of the storage device designated for data managed by the RAID controller is typically dedicated to the RAID group and cannot be accessed independently. Access to a storage device 150 by a client must typically be accomplished by partitioning the storage device 150. Where partitioning is used, partitions accessible for general storage are not used for RAID and partitions allocated to the RAID group are not accessible for general data storage. Schemes that oversubscribe partitions in order to globally optimize utilization are complex and more difficult to manage. In addition, storage space allocated for one RAID group cannot be accessed by more than one RAID controller unless one is designated as master and other RAID controllers act as slaves unless the master RAID controller is inactive, non-functional, etc.
Typical RAID controllers also generate parity data segments outside of the storage devices 150 of the RAID group. This can be inefficient because parity data segments are typically generated and then are sent to a storage device 150 for storage, which requires computing capacity of the RAID controller. Tracking parity data segment location and updates must also be done at the RAID controller instead of autonomously at a storage device 150.
Where it is necessary to ensure that the data remains available if the separate RAID controller is offline, RAID controllers are typically cross connected to the drives and to each other, and/or mirrored as complete sets, making data availability expensive and difficult to manage, and dramatically reducing the reliability of the storage subsystem.
What is needed is a system, apparatus, and method for front-end distributed RAID that allows RAIDing on a per data segment, per object, per file, or similar basis and that eliminates the need for RAID controllers and RAID controller couplets situated between the client and the storage devices. In such a system, apparatus, and method, a RAID group can be created for one data segment, object, or file and managed within one group of storage devices by one RAID controller while a second RAID group may be created for another data segment, object, or file that encompasses some of the same storage devices of the first RAID group. The RAID control functions may be distributed among clients 114, a third-party RAID management device, or among storage devices 150. The front-end distributed RAID system, apparatus, and method may also send commands to storage devices 150 of a RAID group and may allow the storage devices 150 to directly access and copy data through direct memory access ("DMA"), or remote DMA ("RDMA").
Figure 10 is a schematic block diagram illustrating one embodiment of a system 1600 that may be accessed for a front-end distributed RAID in accordance with the present inventions. The descriptions above for the components depicted in Figure 10 related to progressive RAID are also applicable to front-end distributed RAID. With respect to front-end distributed RAID, the storage device set 1604 forms a RAID group and includes storage devices 150 that are autonomous and are capable of independently receiving and servicing storage requests from a client 114 over a network 116 or one or more redundant networks 116. Among the storage devices 150 within the storage device set 1604, one or more are designated as parity-mirror storage devices 1602 for a stripe. Typically, the one or more parity- mirror storage devices 1602 function substantially similar to the other storage devices 150. In typical configurations where the designated parity-mirror storage devices 1602 alternate among the storage devices 150 of the storage device set 1604, the parity-mirror storage devices 1602 have essentially the same characteristics as the other storage devices 150 because they must also operate as non-parity-mirror storage devices. The similar characteristics are with respect to operation within a RAID group and autonomous operation for independent client 114 communication as described above. In various embodiments, the storage devices 150 of the storage device set 1604 may differ in other aspects not related to functioning within the described RAID environment. -
The storage devices 150 of the storage device set 1604 may be stand alone, grouped within one or more servers 112, may each reside in a server 112, may be accessed through one or more servers 112, etc. One or more clients 114 may reside in servers 112 that include one or more storage devices 150, may reside in separate servers 112, may reside in computers, workstations, laptops, etc. -that access the storage devices 150 through one or more computer networks 116, or the like.
In one embodiment, the network 116 includes a system bus and one or more of the storage devices 150, 1602 of the storage device set 1604 communicate using the system bus. For example, the system bus may be a PCI-e bus, a Serial Advanced Technology Attachment ("serial ATA") bus, parallel ATA, or the like. In another embodiment, the system bus is an external bus such as small computer system interface ("SCSI"), FireWire, Fiber Channel, USB, PCIe-AS, Infiniband, or the like. One of skill in the art will appreciate other system 1600 configurations with storage devices 150 that are autonomous and are capable of independently receiving and servicing storage requests from a client 114 over one or more networks 116.
Figure 11 is a schematic block diagram illustrating one embodiment of an apparatus 2100 for front-end distributed RAID in accordance with the present invention. The apparatus 2100, in various embodiments, includes a storage request receiver module 2102, a striping association module 2104, a parity-mirror association module 2106, a storage request transmitter module 2108, a front-end parity generation module 2110, a parity alternation module 2112, a data segment recovery module 2114, a data rebuild module 2116, a parity rebuild module 2118, and a peer-to-peer communication module 2120, which are described below. In various embodiments, the apparatus 2100 may be included in a storage device 150 such as a solid-state storage device 102, a storage device controller 152 such as a solid-state storage controller 104, a server 112, a third-party RAID management device, etc. or may be distributed among more than one component.
The apparatus 2100 includes a storage request receiver module 2102 that receives a storage request to store data in a storage device set 1604. The data may be a portion of a file or an object or may be an entire file or object. A file may include a block of arbitrary information, or resource for storing information, which is available to a computer program. A file may include any data structure accessed by a processor. A file may include a database, a string of text, computer code, etc. An object is typically a data structure for object-oriented programming and may include a structure with or without data. In one embodiment, an object is a subset of a file. In another embodiment, an object is independent of a file. In any case, an object and a file are defined herein to include the entire set of data, data structures, computer code, and other information that may be stored on a storage device.
The storage device set 1604 includes autonomous storage devices 150 forming a RAID group that independently receive storage requests from a client 114 over one or more networks 116. One or more of the autonomous storage devices 150 within the storage device set 1604 are designated as parity-mirror storage devices 1602 for a stripe. Other storage requests from another client 114 may be stored on a second storage device set where the second storage device set may include one or more of the same storage devices 150 (and parity-mirror storage devices 1602) as the first storage device set 1604. The storage devices 150 common to both storage device sets 1604 may have overlapping assigned storage space within the common storage devices 150.
The apparatus 2100 includes a striping association module 2104 that calculates a stripe pattern for the data. The stripe pattern includes one or more stripes. Each stripe includes of a set of N data segments. The N data segments of a stripe may also include one or more empty data segments. The striping association module 2104 associates each of the N data segments with one of N storage devices 150a-n in the storage device set 1604 assigned to the stripe. In one embodiment, the striping association module 2104 associates a data segment with a storage device 150 with a storage request to be sent the storage device 150 that directs the storage device 150 to get data corresponding to the data segment from the client -114 sending the storage request.
In another embodiment, the storage request is substantially free of data of the data segments. Substantially free of data means that the storage request generally does not include the data that is the subject of the storage request but may include characters, character strings, etc. that may be part of the data. For example, if the data comprises a series of repeated, identical characters, such as a series of zeros, the storage request may include an indication that the data includes a series of zeros without including all of the zeros contained in the data. One of skill in the art will recognize other ways to send a storage request without sending the bulk of the data while still allowing a small amount or single instance of certain characters or character strings in the storage request. The storage request includes commands that allow the N storage devices 150a-n to retrieve the data using a DMA or RDMA operation or the like.
In another embodiment, the striping association module 2104 associates a data segment with a storage device 150 by identifying in a storage request to be sent to the storage device 150 the data of the data segment. Identifying the data of the data segment may include a data segment identifier, a data segment location or address, a data segment length, or other information that will allow the storage device 150 to recognize which data comprises the data segment.
In one embodiment, the striping association module 2104 associates a data segment with a storage device 150 in a storage request so that a client 114 can send data comprising the data segments in a broadcast so that each storage device 150 is able to store associated data segments and discard data corresponding to data segments not assigned to the storage device 150. In another embodiment, the striping association module 2104 associates a data segment with a storage device 150 in a storage request, possibly by addressing each data segment, so that a client 1 14 can send data comprising the data segments in a multicast so that each storage device 150 is able to store associated data segments and discard data corresponding to data segments not assigned to the storage device 150. One of skill in the art will recognize other ways for the striping module 2104 to associate a data segment with a storage device 150 to broadcast, multicast, unicast, anycast, etc. one or more data segments to the one or more storage devices.
In a related embodiment, the striping association module 2104 associates a data segment with a storage device 150 in a storage request so that a client 114 can broadcast, multicast, unicast, etc. the storage request and each storage device 150 is able to receive a portion of the storage request from the client 1 14 pertaining to the data segment associated with the storage device 150 and can discard portions the storage request that do not pertain to the one or more data segments not associated with the storage device 150. In another embodiment, the storage request received by the storage request receiver module 2102 includes the data that is the subject of the storage request and the striping association module 2104 associates a data segment with a storage device 150 by preparing a storage request for the storage device 150 that includes data segment. The striping association module 2104 may operate within a client 114, a third-party RAID management device, a storage device 150, 1602, etc.
The apparatus 2100 includes a parity-mirror association module 2106 that associates a set of the N data segments with one or more parity-mirror storage devices 1602 in the storage device set 1604. The one or more parity-mirror storage devices 1602 are in addition to the N storage devices 150a-n. In one embodiment, the parity-mirror association module 2106 associates a set of N data segments to each parity-mirror storage device 1602 so each parity-mirror storage device 1602 can receive and store the N data segments of a stripe for generating a parity data segment. In another embodiment, the parity-mirror association module 2106 associates a data segment of the stripe with each parity-mirror storage device 1602 so that the parity-mirror storage devices 1602a-m act as a mirror to the N data segments stored on the N storage devices 150a-n.
In various embodiments, the parity-mirror association module 2106 associates the set of N data segments with the one or more parity-mirror storage devices 1602 using a single storage request, multiple storage requests, or other association technique described above in relation to the striping association module 2104, such as storage requests setting the parity-mirror storage device 1602 up for DMA, RDMA, broadcasts, multicasts, or including the N data segments in the storage requests. The parity-mirror association module 2106 may operate within a client 114, a third-party RAID management device, a storage device 150, 1602, etc. The apparatus 2100 includes a storage request transmitter module 2108 that transmits one or more storage requests to each storage device 150, 1602 in the storage device set 1604, each storage request sufficient to store onto the storage device 150, 1602 the one or more data segments associated with the storage device 150, 1602 receiving the storage request. In one embodiment, each storage request does not include data that is the subject of the storage request. In a further embodiment, each storage request enables the N storage devices 150 and parity- mirror storage devices 1602 of the storage device set 1604 to download data of an associated data segment using DMA or RDMA. In another embodiment, a storage request contains sufficient information to pick out relevant storage requests or relevant data for the associated data segments from a broadcast from the client 114. In another embodiment, a storage request includes the data of an associated data segment.
In one embodiment, each storage request identifies the storage devices 150, 1602 that are part of the storage device set 1604 of a stripe. By including an identification of the storage devices 150, 1604 of the storage device set 1604, in the event of a failure of a storage device 150 acting as master, another storage device 150 may take over as master for managing the RAIDed data. In another embodiment, the identification of the storage device set 1604 enables the autonomous storage devices 150, 1602 to recover data when a storage device is off-line, and rebuild data when a replacement storage device is added within the storage device set 1604 independent of the client. In another embodiment, the identification of the storage devices 150, 1602 of the storage device set 1604 represents a multi-cast group for transmission of data segments or storage requests. The identification may be stored along with metadata for the object or file stored on the storage devices 150, 1602 within the storage device set 1604.
In one embodiment, when the parity-mirror association module 2106 associates a set of N data segments with each of the one or more parity-mirror storage devices 1602, the apparatus 2100 includes a front-end parity generation module 2110 that calculates, independent of a client 114, a parity data segment for the stripe and stores the parity data segment on the parity-mirror storage device 1602. The parity data segment is calculated from the set of N data segments provided to the parity-mirror storage device 1602. Where more than one parity-mirror storage device 1602 is included in the storage device set 1604, the front-end parity generation module 2110 typically generates the various parity data segments so that two or more storage devices 150, 1602 in the storage device set 1604 may fail and the parity data segment information allows for recovery of unavailable data segments or parity data segments.
In another embodiment, the front-end parity generation module 2110 calculates the parity data segment when operating within a storage device 150 of the storage device set 1604 and/or a third party RAID management device. For example, a server 112 separate from the client 114 transmitting the storage request may calculate the parity data segment. In another embodiment, the front-end parity generation module 2110 operates within a parity-mirror storage device to calculate the parity data segment. For example, a storage controller 152 in the parity-mirror storage device 1602 may act as a master storage controller for the RAID group formed by the storage device set 1604.
In another embodiment, the front-end parity generation module 2110 calculates the parity data segment and then transmits the calculated parity data segment to one or more additional parity-mirror storage devices 1604 in a second set of storage devices forming a mirror. This embodiment is advantageous because overhead associated with calculating a parity data segment is expended once rather than for each storage device set 1604 with the additional benefit of reducing the data traffic on the network 116.
The apparatus 2100 may also include, in one embodiment, a data segment recovery module 2112 that recovers a data segment stored on a storage device 150 of the storage device set 1604 if the storage device 150 is unavailable and a request is received to read either the unavailable data segment or data that includes the unavailable data segment. The data segment is recovered using the data segments on available storage devices 150 of the storage device set 1604, a combination of the parity data segments and the data segments on available storage devices 150, 1602 of the storage device set 1604, or from a mirror storage device containing a copy of the data segment. Typically, the mirror storage device is one storage device 150 of a mirror storage device set that stores a copy of the N data segments. The data segment recovery module 2112 may operate and recover the unavailable data segment from a storage device 150, a parity-mirror storage device 1602, a third-party RAID management device, a mirror storage device, etc. In another embodiment, the apparatus 2100 includes a data rebuild module 2114 that stores a recovered data segment on a replacement storage device 150 in a rebuild operation. For example, if a storage device 150 becomes unavailable due to failure, loss of synchronization, etc. the data rebuild module 2114 may rebuild a storage device 150 to replace the unavailable storage device 150. In one embodiment, the rebuilt storage device 150 is the original storage device 150 that has been made available.
The recovered data segment matches an unavailable data segment stored on the unavailable storage device 150 of the storage device set 1604. The rebuild operation typically restores one or more of data segments and parity data segments onto the replacement storage device 150 to match data segments and parity data segments stored previously on the unavailable storage device 150.
In one embodiment, the recovered data segment is recovered for the rebuild operation using the available data segments on available storage devices 150 of the storage device set 1602. In another embodiment, the recovered data segment is recovered for the rebuild operation using a combination of a parity data segment from one or more of the parity-mirror storage devices 1602 and the available data segments on available storage devices 150 of the storage device set 1604. In another embodiment, the recovered data segment is recovered for the rebuild operation using a matching data segment read from a parity-mirror storage device 1602. In yet another embodiment, the recovered data segment is recovered for the rebuild operation using a matching data segment from a mirror storage device. The data rebuild module 21 14 could operate and store a received data segment from a client 114, a third party RAID management device, a storage device 150, 1602, a mirror storage device, etc.
The apparatus 2100 includes, in another embodiment, a parity rebuild module 2116 that rebuilds the recovered parity data segment on a replacement storage device 1602 in a rebuild operation. A rebuild operation is substantially similar to the rebuild operation described in relation to the data rebuild module 2114. The parity rebuild module 2116 operates similar to the data rebuild module 21 14 except the parity rebuild module 2116 rebuilds a recovered parity data segment. The recovered parity data segment matches an unavailable parity data segment stored on an unavailable parity-mirror storage device 1602 assigned to the stripe. The parity data segment is recovered, in various embodiments, by copying the parity data segment stored on a parity-mirror storage device 1602 in a mirrored storage device set, copying the parity data segment from a parity-mirror storage device 1602 in the storage device set 1604 (if identical to the unavailable parity data segment), generating the parity data segment using one or more of the N data segments and parity data segments stored on the available storage devices 150, 1602 of the storage device set 1604 and a mirror storage device containing a copy of a data segment, etc. The data rebuild module 2116 may operates and stores a recovered data segment while residing on a client 1 14, a third party RAID management device, a storage device 150, a mirror storage device, etc.
Advantageously, the apparatus 2100 is not limited to storing data in the storage devices 150, 1602 to partitions dedicated to the front-end, distributed RATD operation described herein. Instead, an autonomous storage device (e.g. 150a) may independently receive storage requests from a client 1 14 to store RAIDed or un-RAIDed data in one or more regions of the storage device 150a that is also available for storing data by the striping association module 2104, the parity-mirror association module 2106, and the front-end parity generation module 2110. In one embodiment, one or more storage requests received by the storage request receiver module 2102 or transmitted by the storage request transmitter module 2108, identify the storage devices 150 that comprise the storage device set 1604 of the stripe. Advantageously, identifying the storage device 150 of the storage device set 1604 in the storage requests facilitates a backup RAID controller to operate if a master controller is non-functional. For example, if the storage devices 150 of the storage device set 1604 are identified in storage requests and the master controller is in a parity-mirror storage device 1602 and is unavailable, another parity-mirror storage device 1602 or another of the N storage devices 150a-n may become the master controller.
In one embodiment, the apparatus 2100 includes a parity alternation module 2118 that alternates, for each stripe, which storage devices 150 in the storage device set 1604 are designated as the parity-mirror storage devices 1602 for the stripe. The benefits of the parity alternation module 2118 are described above. In another embodiment, the storage devices 150 of the storage device set 1604 form a group of peers and the apparatus 2100 includes a peer-to-peer communication module 2120 that transmits and receives storage requests within the storage devices 150, 1602 of the storage device set 1604. The peer-to-peer communication module 2120 may also transmit and receive storage requests with peer devices outside the storage device set 1604.
In a preferred embodiment, the storage request is an object request to store an object by striping data of the object across the storage devices 150, 1602 of the storage device set 1604 using the modules 2102-2120 of the apparatus 2100. In another embodiment, one or more of the autonomous storage devices 150, 1602 of the storage device set 1604 are allocated within a first RAID group for at least a portion of a first object or file and allocated within a second RAID group for at least a portion of a second object or file. For example, one storage device 150a may be a master RAID controller for the storage device set 1604 for one or more stripes and a second storage device 150b may be a master RAID controller for a RAID group that includes some or all of the storage devices 150 of the storage device set. Advantageously, the apparatus 2100 allows flexibility in grouping storage devices 150, 1602 to form RAID groups for various clients 114. Figure 12 is a schematic flow chart diagram illustrating an embodiment of a method 2200 for front-end distributed RAID in accordance with the present invention. The method 2200 begins 2202 and the storage request receiver module 2102 receives 2204 a storage request to store data in N storage devices 150a-n of the storage device set 1604. The striping association module 2104 calculates 2206 a stripe pattern for the data and associates 2208 the N data segments each with one of the N storage devices 150a-n.
The parity-mirror association module 2106 associates 2210 a set of N data segments with one or more parity-mirror storage devices 1602. The storage request transmitter module 2108 transmits 2212 one or more storage requests to each storage device 150, 1602 in the storage device set 1604. Each storage request is sufficient to store onto the storage device 150 the one or more data segments associated with the storage device 150 receiving the storage request. The data segments of the data are then transferred to the storage devices 150, 1602 of the storage device set 1604 using DMA, RDMA, broadcast, multicast, etc. as directed by the storage requests. Optionally, the front-end parity generation module 2110 calculates 2214 a parity data segment for the stripe and the method 2200 ends 2216. SHARED, FRONT-END, DISTRIBUTED RAID
Traditional RAID utilizes an array of disks or other storage devices with at least a portion of each device dedicated to the RAID and forming a RAID group. A RAID controller manages storage requests to the RAID group. For redundant systems, the RAID controller has a backup RAID controller ready to take over if the master RAID controller fails or is unavailable. Storage requests from multiple clients that seek to access the same data stored in the RAID are typically sequentially executed in order of arrival.
A front-end, distributed RAID system, as described above in relation to the system 1600, apparatus 2100, and method 2200 depicted in Figures 10, 11, and 12 respectively, includes autonomous storage devices 150 that may each include a storage controller 152 that can function as a distributed RAID controller and the storage devices 150 can each be configured in multiple, overlapping RAID groups serving multiple clients 114. Occasionally, two clients 114 may seek to access the same data. If one storage request arrives first and executes, then typically there is no inconsistency of the data. If, on the other hand, two or more storage requests for the same data arrive at the same time or nearly the same time, the data may be corrupted.
For example, if data is stored on four storage devices 150 in a RAID group, where one of the storage devices 150is assigned as a parity-mirror storage device 1602, and a first client 114 sends a storage request to a first storage controller 150a acting as a RAID controller and a second client 114 sends a second storage request to a second storage device 150a acting as a second RAID controller and both storage requests access the same data, the first storage device 150a may commence execution of the storage request on the first storage device 150a then the other storage devices 150b-n of the RAID group. Concurrently, the second RAID controller on the second storage device 150b may commence execution of the second storage request on another storage device (e.g. 150b) and then on the remaining storage devices 150a,c-n of the RAID group. This mismatch in execution may be caused by physical distance between the storage devices 150, execution time discrepancies, etc. The result may be corrupted data.
What is needed is a system, apparatus, and method for shared, front-end, distributed RAID that handles concurrent storage requests seeking access of the same data. Beneficially, the system, apparatus, and method would control access to the data so one storage request is executed before a second storage request is executed.
Figure 10 is a schematic block diagram illustrating one embodiment that serves as a system 1600 for shared, front-end distributed RAID in accordance with the present inventions, in addition to progressive RAID and front-end distributed RAID. The descriptions above for the components depicted in Figure 10 related to progressive RAID and front-end distributed RAID are also applicable to shared, front-end distributed RAID. As with front-end distributed RAID, the storage device set 1604 forms a RAID group and includes storage devices 150 that are autonomous and are capable of independently receiving and servicing storage requests from a client 114 over a network 116. With respect to shared, front-end distributed RAID, the system 1600 includes two or more clients 114 such that the two or more clients 114 each send a storage request relating to the same data. The storage requests are concurrent in that the storage requests arrive such that one storage request is not completed prior to arrival of another of another storage request. Among the storage devices 150 within the storage device set 1604, one or more are designated as parity- mirror storage devices 1602 for a stripe. Typically, the one or more parity-mirror storage devices 1602 function substantially similar to the other storage devices 150.
In typical configurations where the designated parity-mirror storage devices 1602 alternate among the storage devices 150 of the storage device set 1604, the parity-mirror storage devices 1602 have essentially the same characteristics as the other storage devices 150 because they must also operate as non-parity-mirror storage devices. The similar characteristics are with respect to operation within a RAID group and autonomous operation for independent client 114 communication as described above. In various embodiments, the storage devices 150 of the storage device set 1604 may differ in other aspects not related to functioning within the described RAID environment.
The storage devices 150 of the storage device set 1604 may be stand alone, grouped within one or more servers 112, may each reside in a server 112, may be accessed through one or more servers 112, etc. One or more clients 114 may reside in servers 112 that include one or more storage devices 150, may reside in separate servers 112, may reside in computers, workstations, laptops, etc. that access the storage devices 150 through a computer network 116, or the like.
In one embodiment, the network 116 includes a system bus and one or more of the storage devices 150, 1602 of the storage device set 1604 communicate using the system bus. For example, the system bus may be a PCI-e bus, a Serial Advanced Technology Attachment ("serial ATA") bus, parallel ATA, or the like. In another embodiment, the system bus is an external bus such as small computer system interface ("SCSI"), FireWire, Fiber Channel, USB, PCIe-AS, Infiniband, or the like. One of skill in the art will appreciate other system 1600 configurations with storage devices 150 are that autonomous and are capable of independently receiving and servicing storage requests from a client 114 over a network 116. Figure 13 is a schematic block diagram illustrating one embodiment of an apparatus 2300 for shared, front-end distributed RAID in accordance with the present invention. The apparatus 2300 includes, in various embodiments, a multiple storage request receiver module 2302, a striping module 2304, a parity-mirror module 2306, a sequencer module 2308, a master validation module 2310, master determination module 2312, a master error module 2314, parity generation module 2316, and a parity alternation module 2318, which are described below.
The apparatus 2300 includes a multiple storage request receiver module 2302 that receives at least two storage requests from at least two clients 114 to store data in the storage devices 150 of the storage device set 1602. The data includes data of a file or of an object. The storage requests of concern to the apparatus each have at least a portion of the data in common and, in addition, are concurrent storage requests by arriving such that one storage request is not completed before to arrival of the storage requests. These concurrent storage requests run the risk of corrupting the common data in a front-end distributed RAID system 1600. In one embodiment, the concurrent storage requests may be from one client 114. In another embodiment, the concurrent storage requests are from two or more clients 114.
The multiple storage requests may update one or more data segments stored on the storage devices 150 of the storage device set 1602 where the previously stored data is striped by the striping module 2304 into data segments stored on the storage devices 150 of the storage device set 1604. In one embodiment, a storage request writes the data for the first time to the RAID group. In this case, the data typically would have existed elsewhere and accessed by one or more clients 114 and then one storage request copies the data to the RAID group while another storage request concurrently accesses the data.
The multiple storage requests may comprise one request to update one or more data segments stored on the storage devices 150 of the storage device set 1602 and one or more read requests targeting at least a portion of the data in common. If the update request is not complete, then the read requests response from the storage devices 150 of the storage device set 1602 may be comprised of a combination of pre-existing and updated data that corrupts the data.
The apparatus 2300 includes a striping module 2304 that calculates, for each of the concurrent storage requests, a stripe pattern for the data and writes N data segments of a stripe to N storage devices 150a-n within the storage device set 1604. The stripe pattern includes one or more stripes and each stripe includes a set of N data segments. Each of the N data segments is written to a separate storage device 150 within the storage device set 1604 and assigned to the stripe. The apparatus 2300 includes a parity-mirror module 2306 that writes, for each of the concurrent storage requests, a set of N data segments of the stripe to the storage devices 150 within the storage device set 1604 designated as parity-mirror storage devices 1602. The parity- mirror storage devices 1602 are in addition to the N storage devices 150a-n.
The striping module 2304 is also used to calculate the identity of one or more storage devices 150a-n from which to read one or more data segments that are part of a file or object. The apparatus 2300 includes a sequencer module 2308 that ensures completion of a first storage request from a first client 114 before executing a second storage request from a second client 114 where the at least two concurrent storage requests include the first and second storage requests. In other embodiments, the sequencer module 2308 ensures completion of the first storage request before executing two or more other concurrent storage requests. Beneficially, the sequencer module 2308 facilitates an orderly execution of concurrent storage requests to prevent corruption of data. In one embodiment, the sequencer module 2308 coordinates execution of the concurrent storage requests by using a master controller that all storage requests must access for the data, by using a locking system, a two-phase commit, or other means known to those in the art. Some of the methods used by the sequencer module 2308 are discussed below.
In one embodiment, the sequencer module 2308 ensures completion of the first storage request prior to execution of concurrent storage requests by receiving an acknowledgement from each of the storage devices 150 of the storage device set 1602 that received a storage request in conjunction with the first storage request prior to execution of the second storage request. Typically, an acknowledgment acknowledges completion of a storage request. In one embodiment, each of the storage devices 150 affected by the storage request is written to and an acknowledgement received from each of the storage devices 150 prior to the sequencer module 2308 commencing execution of a second storage request.
Completion of a storage request, in one embodiment; may include completion of a portion of a first storage request directed to a single storage device (e.g. 150a) before execution of a portion of a pending second storage request on the same storage device 150a. The sequencer module 2308 may independently verify completion of the portions of the storage request on the storage devices 150. In this embodiment, writing data segments related to a first storage request need not be held up until all data segments of the first storage request are completed. The sequencer module 2308 may coordinate the various executions taking place on the storage devices 150 of the storage device set 1604 to ensure that the data is not corrupted.
In one embodiment, the acknowledgment of completion of a storage request is received after the striping module 2304 and the parity-mirror module 2306 each write the data segments related to the storage request to the storage devices 150 of the storage device set 1604. In another embodiment, the acknowledgment of completion of a storage request is received after the striping module 2304 and the parity-mirror module 2306 each write the data segments related to the storage request to the storage devices 150 of the storage device set 1604 and each of the storage devices 150, 1602 confirms that the data segments have been written. In one embodiment, the sequencer module 2308 selects a first storage request for execution by selecting a storage request from among the concurrent requests that arrived first. In another embodiment, the sequencer module 2308 selects a first storage request for execution by selecting a storage request with an earliest timestamp. In another embodiment, the sequencer module 2308 selects a first storage request for execution by selecting a storage request using some selection criteria. For example, the sequencer module 2308 may select a storage request that is marked in some way by a requesting client 114 as high priority, may select a storage request from a favored client 114, etc. One of skill in the art will recognize other ways that the sequencer module 2308 may select a first storage request using some selection criteria. In one embodiment, the storage request receiver module 2302, the striping module 2304, the parity-mirror module 2306, and the sequencer module 2308 are part of a master controller (not shown) that controls and services the concurrent storage requests. All or part of the master controller may reside and operate in a client 114, a third-party RAID management device, a storage device 150 of the storage device set 1604, or a storage controller 152 in a storage device 150. By using a master controller to execute service requests for the data, the sequencer module 2302 may be aware of storage requests directed to the data and may then recognize concurrent storage requests and may then sequence the concurrent storage requests in a manner that the data stored in the storage devices 150 of the storage device set is not corrupted. One of skill in the art will recognize other implementations of a master controller that controls servicing of a storage request directed at the data.
In another embodiment, the master controller is part of a group of two or more master controllers able to service the concurrent storage requests from one or more clients 114 where the storage requests are directed at the data stored on the storage devices 150 of the storage device set 1604. For example, a master controller may service storage requests for a first client 114 and a second master controller may services storage requests for a second client 114. The first and second clients 114 may both have access to data stored on the storage devices 150 of the storage device set 1604, thus enabling concurrent storage requests. One master controller may be part of one storage device 150a while the other master controller may be part of a second storage device 150b. In another embodiment, the first master controller may be part of a first storage device set 1604a and the second master controller may be part of a mirrored storage device set 1604b.
Where the master controller is part of a group of master controllers accessing the storage devices 150 of the storage device set 1604, the apparatus 2300 may include a master validation module 2310 that confirms that a master controller servicing a received storage request is controlling execution of the storage request ahead of execution of one or more concurrent storage requests prior to execution of the received storage request. In this embodiment, the concurrent storage requests are received by other master controllers and the service request has at least a portion of the data in common with the concurrent storage requests received by the other master controllers.
For example, a master controller may receive a storage request and the master validation module 2310 may then poll the other master controllers before execution of the storage request to verify that the master controller is still the master controller for the data of the storage request. Part of the validation may include verification that the master controllers can communicate with each other so that a designated master controller is verified prior to execution of the storage request. This may be useful in situations were one front-end RAID controller is designated as master and another is backup. In another example, a master controller may receive a storage request to read a data segment from a file or object and the master validation module 2310 may then poll the other master controllers to verify that no updates are in progress for the file or object. In another example, a master controller may use the master validation module to acquire control of the data for the storage request.
One way to verify that a master controller is still master for execution of a storage request is to use a three-way polling scheme where two devices/controllers must be available to vote that a controller is master for a storage request to proceed. The scheme uses a device (not shown) that is a third-party to the controllers vying to be master and maintains a record of which controller is assigned to be master. This master verification device may be another controller, may be a client 114 on a server, etc. and is able to communicate with controllers in the group that may act as master controller. A portion of the master validation module 2310 may then reside on the master verification device with a portion of the master validation module 2310 residing in each controller.
In one example, the system 1600 includes a first front-end distributed RAID controller ("first controller"), a second front-end distributed RAID controller ("second controller"), each of which may be master, and a separate master verification device. The first and second controllers and master verification device are all in communication with each other. The master verification module 2310 may designate the first controller as master controller and the second controller as backup for data stored on the storage devices 150 of the storage device set 1604 and the master verification module 2310 may store this master information on the controllers and master verification device. As long as communication is maintained between the first controller, the second controller, and the master verification device, the master verification module 2310 can confirm that the first controller is master.
If the first, master controller receives a storage request and the second, backup controller becomes unavailable or communication is lost with the first controller and master verification device, the master validation module 2310 can verify through communication between the master verification device and the first, master controller that the first controller is still master, and since both the first controller and the master verification device confirm that the first controller is indeed master controller, the master validation module 2310 may allow the storage request to proceed. Storage requests received by the second backup controller would not proceed because, through the master verification module 2310, the second controller recognizes it is not the master.
If on the other hand, the first, master controller is unavailable or cannot communicate with the second, backup controller and the master verification device and the second, backup controller receives a storage request, the master validation module 2310 can recognize that both the second controller and the master verification module cannot communicate with the first controller and the master verification module 2310 can designate the second, backup controller to be master and the storage request can proceed. The change in master designation may then be recorded on the second controller.
If the first controller is operational and has simply lost communication with the second controller and the master verification device, any storage requests for the data received by the first controller will not be executed. If communication is restored, the first controller will still not execute storage requests because both the second controller and the master verification device recognize the second controller as the master. Of course this master designation may be reset. One of skill in the art will recognize a variety of static and dynamic means for assigning and reassigning the master designation to one of the master controllers.
If the master verification device is unavailable and the first storage controller receives a storage request, the portion of the master verification module 2310 operating on the first and second controllers can verify that the first controller is master and the storage request can proceed. If the second controller receives a storage request, the portion of the master verification module 2310 operating on the first and second controllers can verify that the first controller is master and the storage request will not proceed. In other embodiments, more than two controllers are part of a polling scheme. One of skill in the art will recognize other ways that the master verification module 2310 can verify that a controller is master prior to execution of a storage request. In another embodiment, the apparatus 2300 includes a master determination module 2312. Prior to sending a storage request, the master determination module 2312 sends a master determination request to the group of master controllers. The group of master controllers then identifies which controller is designated as master for a storage request and sends back a response identifying the master controller to the master determination module 2312. The master determination module 2312 receives the identification of the master controller for the storage request and directs the requesting device to send the storage request to the designated master controller. In one embodiment, the master determination module 2312 resides and operates in a client 114. In another embodiment, the master determination module 2312 resides and executes in a third-party RAID management device. In another embodiment, the master determination module 2312 resides in a storage device 150. In another embodiment, the master determination module is distributed between two more storage devices 150.
In a further embodiment, the apparatus 2300 includes a master error module 2314 that returns an error indication. The master error module 2314 returns an error indication, in one embodiment, if a multiple storage request receiver module 2302 that is controlled by a master controller receives a storage request not controlled by the master controller.
In another embodiment, the master error module 2314 returns an error indication if the master determination module 2312 or the master validation module 2310 determines that the master controller is no longer the determined master at the time of the completion of execution of the storage request. This embodiment typically occurs when a master controller begins executing a storage request and loses communication with other master controllers of the group, or, in a polling scheme, loses communication with the other master controllers and the master verification device. In another embodiment, the master error module 2312 returns an error indication if a multiple storage request receiver module 2302 controlled by a master controller receives a storage request that is not controlled by the master controller.
In another embodiment, the master controller controls storage requests to one or more secondary master controllers. The secondary master controllers each control storage requests for data stored on the storage devices 150, 1602 of the storage device set 1604. In another embodiment, the master controller that controls secondary master controller is also a secondary master controller for storage requests directed to data stored on the storage devices 150, 1602, of the storage device set 1604.
In another embodiment, the master controller controls storage requests to one or more secondary master controllers and each secondary master controller controls storage requests for data stored on storage devices 150 of a storage device set unique to the secondary master controller. The apparatus 2300 is flexible so that any of the master controllers can be. master to other controllers that act as secondary master controllers. Some secondary master controllers can share a storage device set 1604 and others can controls a different storage device set. In other embodiments, the master controller can be a parity-mirror storage device 1602 or one of the N storage devices 150a-n.
In another embodiment, a secondary master controller can become a master controller when the master controller is off line or unable to determine that it is the designated master. One of skill in the art will recognize a variety of static and dynamic means for assigning and reassigning the master designation among one or more secondary master controllers. In a preferred embodiment, the apparatus 2300 includes a parity generation module 2316 that calculates a parity data segment for the stripe and stores the parity data segment on a parity- mirror storage device 1602. The parity stripe is calculated from the set of N data segments on the parity-mirror storage device 1602. This embodiment is typical of RAID 5, RAID 6, or some other RAID levels, but is typically not included for RAID 0, RAID 1, RAID 10, etc. In another preferred embodiment, the apparatus 2300 includes a parity alternation module
2318 that alternates, for each stripe, which of the storage devices 150 within the storage device set 1604 are assigned to be the one or more parity-mirror storage devices 1602 for the stripe. Rotating the parity data segments per stripe improves performance. The parity alternation module 2318 may be used in conjunction with the striping module 2304 to calculate the identity of one or more storage devices 150a-n from which to read, write, or update one or more data segments that are part of a file or object.
The functions of the various modules 2302-2318 may reside together in a single master controller or may be distributed among one or more clients 114, third-party RAID management devices, and one or more storage devices 150, 1602. One of skill in the art will recognize various embodiments where the functions described herein are distributed.
Figure 14 is a schematic flow chart diagram illustrating an embodiment of a method 2400 for shared, front-end distributed RAID in accordance with the present invention. The method 2400 begins 2402 and the multiple storage request receiver module 2302 receives 2404 at least two storage requests from at least two clients 114 to read or store data in one or more storage devices 150 of a storage device set 1604. The data is from a file or of an object and the storage requests each have at least a portion of the data in common and are concurrent by arriving such that one storage request is not completed prior to arrival of another of the at least two storage requests. The striping module 2304 calculates 2406 a stripe pattern for the data, where the stripe pattern includes one or more stripes and each stripe includes a set of N data segments. The striping module 2304 also reads or writes 2408 the N data segments of a stripe to N storage devices 150a-n within the storage device set 1604 where each of the N data segments is written to or read from a separate storage device 150.
Where the storage request is a write operation, the parity-mirror module 2306 writes 2410 a set of N data segments of the stripe to one or more parity-mirror storage devices 1602 within the storage device set 1604 where the parity-mirror storage devices 1602 are in addition to the N storage devices 150a-n. The parity-mirror module2306 may also read 2410 data segments stored in the parity-mirror devices 1602 or a parity data segment. The sequencer module 2308 ensures 2412 completion of a first storage request from a first client 114 prior to executing a second storage request from a second client 114 and the method 2400 ends 2416. The first and second storage requests are concurrent storage requests.
The present invention may be embodied in other specific forms without departing from its spirit or essential characteristics. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.
SOLID-STATE STORAGE AS CACHE FOR HIGH CAPACITY, NONVOLATILE STORAGE
In general, cache is advantageous because data that is accessed often or that is loaded as part of an application or operating system may be stored in cache with subsequent access much quicker than when the data must be accessed through a high-capacity, non-volatile ("HCNV") storage device, such as a hard disk drive ("HDD"), an optical drive, tape storage, etc. Cache is typically included in a computer.
Some storage devices and systems include cache in HCNV storage devices. Some HCNV storage devices contain non-volatile solid state cache; these provide benefit in reducing access times, but can only deliver performance consistent with the usually limited capability of the HCNV storage device interface. Some non-volatile solid-state cache storage devices exist that are typically placed on a motherboard; these devices cannot be used in multi-client environments as no cache coherence is provided. Some controllers of HCNV devices also include cache. Where redundant HCNV cache controllers are shared between multiple clients, sophisticated cache coherency algorithms are required to ensure that data is not corrupted.
Typically, caches are implemented in DRAM, making cache capacity a premium, and requiring relatively high power per performance. If power supporting the volatile cache is lost, data stored in the cache is lost. Typically, some battery backup is used to avoid data loss in case of power failure, with sufficient capability to flush the cache to non-volatile memory prior to failure of the batter backup. In addition, battery backup systems consume power, require redundancy, negatively impact reliability and consume space. Batteries must also be serviced on a regular basis and battery backup can be relatively expensive.
From the foregoing discussion, it should be apparent that a need exists for an apparatus, system, and method that manage data using solid-state storage as cache. Beneficially, such an apparatus, system, and method would provide a non-volatile cache that consumes little power, provides significantly larger capacity and does not require a battery backup to maintain data stored in the cache.
Figure 15 is a schematic block diagram illustrating one embodiment of a system 3400 with solid-state storage 110 as cache for a high-capacity, non- volatile storage device in accordance with the present invention. The system 3400 includes a solid-state storage device 102 with a storage controller 152 that includes a solid-state storage controller 104 and an HCLV controller 3402, solid-state storage 110, and a network interface 156. The system 3400 includes a requesting device 155 connected to the solid-state storage device 102 through a computer network 116, and one or more HCNV storage devices 3404a-n. One of skill in the art will recognize that the system 3400 depicted in Figure 15 is merely one embodiment and that many other configurations are possible that allow solid-state storage 110 to be cache for a storage device.
The system 3400 includes a solid-state storage device 102 with network interface 156 and a storage controller 152. In another embodiment, the network interface 156 is outside of the solid-state storage device 102. For example, the network interface 156 may be in a server 112 that may or may not include the solid-state storage device 102. In the depicted embodiment, the solid-state storage device 102 includes a storage controller 152 that includes a solid-state storage controller 104 and a high-capacity, non- volatile ("HCNV") storage controller 3402. In another embodiment, the solid-state storage device 102 includes a solid-state storage controller 104 and an HCNV storage controller 3402 that are not in a storage controller 152. In other embodiments, the solid-state storage device 102 includes a solid-state storage controller 104 that includes an HCNV storage controller 3402, or vice-versa.
In the depicted embodiment, the system 3400 includes a solid-state storage device 102 with an integrated solid-state storage 110 and with external HCNV storage devices 3404a-n. In another embodiment, the storage controllers 152, 104, 3402 may be separate from the solid-state storage 110. In another embodiment, the controllers 152, 104, 3402 and solid-state storage 110 are included in an HCNV storage device 3404. The HCNV storage device 3404 may also include a network interface 156. One of skill in the art will recognize that many other configurations are possible. The solid-state storage device 102, the solid-state storage controller 104, the solid-state storage 110, storage I/O bus 210, network interface 156, computer network 116, and requesting device 155 are substantially similar to other embodiments of the devices and bus described above.
In one embodiment, the requesting device 155 is connected to the solid-state storage device 102, storage controller 152, solid-state storage controller 104, etc. through a system bus. Data transfers between the requesting device 155 and the solid-state storage 110 may occur over the system bus.
The HCNV storage devices 3404 are typically high-capacity storage devices that provide non- volatile storage and are typically slower for writing and reading data than solid-state storage 110. The HCNV storage devices 3404 may also be cheaper per unit storage capacity than solid- state storage 110. The HCNV storage devices 3404 may be hard disk drive ("HDD"), an optical drive, a tape storage, and the like. Providing solid-state storage 110 as cache for the HCNV storage devices 3404 typically increases speed of data access and storage. One of skill in the art will recognize other benefits of solid-state storage 110 as cache for an HCNV storage device 3404.
In one embodiment, the HCNV storage devices 3404 are connected to the storage controller 152 through a storage area network ("SAN"). In one embodiment, a separate SAN controller connects the HCNV storage devices 3404 to the storage controller 152. In another embodiment, the HCNV storage controller 3402 or the storage controller 152 acts as a SAN controller. One of skill in the art will recognize other ways that the HCNV storage devices 3404 may be connected in a SAN. Figure 16 is a schematic block diagram illustrating one embodiment of an apparatus 3500 with solid-state storage as cache for a high-capacity, non-volatile storage device in accordance with the present invention. The apparatus 3500 includes a cache front-end module 3502, a cache back-end module 3504, an object storage controller 3506, an HCNV module 3508, and a standard device emulation module 3510, which are described below. The modules 3502-3510 of the apparatus 3500 are depicted in a storage controller 152 with a solid-state storage controller 104 and an HCNV storage controller 3402, but some or all of each module 3502-3510 may be included in the solid-state storage controller 104, the HCNV storage controller 3402, a server 112, an HCNV storage device 3404, or other location. The apparatus 3500 includes a cache front-end module 3502 that manages data transfers associated with a storage request, where the data transfers are between the requesting device 155 and solid-state storage 110 functioning as cache for one or more HCNV storage devices 3404a-n. The apparatus 3500 also includes a cache back-end module 3504 that manages data transfers between the solid-state storage 110 and the HCNV storage devices 3404a-n. The data transfers may include data, metadata, and/or metadata indexes. The solid-state storage 110, as described above, is an array of non-volatile, solid-state data storage elements 216, 218, 220, which are typically arranged in banks 214. In various embodiments, the solid-state storage 110 may be flash memory, nano random access memory ("nano RAM" or "NRAM"), magneto-resistive RAM ("MRAM"), dynamic RAM ("DRAM"), phase change RAM ("PRAM"), or the like.
Typically the cache front-end module 3502, the cache back-end module 3504, and the solid-state storage controller 104 operate autonomously from the requesting device 155. For example, the requesting device 155 may view the storage controller 152 with the solid-state storage controller 104 and HCNV storage controller 3402, along with the associated storage 110, 3404a-n. as a single storage device. In another example, the requesting device 155 may view the HCNV storage devices 3404a-n and the solid-state storage 110 may be transparent.
In one embodiment, the solid-state storage controller 104 includes an object storage controller module 3506 that services object requests from one or more requesting devices 155 and manages objects of the object requests within the solid-state storage 110. In the embodiment, the solid-state controller 104, along with the object storage controller module 3506, manage object requests as described above, and in particular as described in relation to the apparatus 200 depicted in Figure 2A.
In one embodiment, the apparatus 3500 includes an HCNV RAID module 3508 that stores data cached in the solid-state storage 110 in two or more HCNV storage devices 3404a-n in redundant array of independent drives ("RAID") consistent with a RAID level. In the embodiment, the data appears to a requesting device 155 as a whole such that the RAIDing is hidden from the requesting device 155. For example, the cache front-end module 3502 may cache data from the requesting device 155 in the solid-state storage 110 and the cache back-end module 3504 may cooperate with the HCNV RAID module 3508 to stripe the data and store data segments and parity data segments in the HCNV storage devices 3404a-n consistent with a RAID level. One of skill in the art will recognize other ways that data from a requesting device 155 may be RAIDed in the HCNV storage devices 3404a-n.
In another embodiment, the solid-state storage 110 and the HCNV storage devices comprise a hybrid storage device within a hybrid storage device set that is configured as a RAID group. For example, the hybrid storage device set may be a front-end, distributed RAID storage device set 1604 and the hybrid storage device may be a storage device 150, 1602 in the storage device set as described above in relation to the system 1600, apparatus 2100, and method 2200 depicted in Figures 10, 1 1 , and 12 respectively. In the embodiment, a data segment cached in the solid-state storage 1 10 and later stored on an HCNV device 3404 is one of N data segments of a stripe or a parity data segment of the stripe. As in front-end RAID, the hybrid storage device receives storage requests from one or more clients 114 independent of data segments of a RAID stripe.
In a further embodiment, the hybrid storage device is a storage device 150, 4602 of a shared, front-end distributed RAID group 1604 that receives two or more simultaneous storage requests from two or more clients 114, as described above in relation to shared front-end RAID as described in relation to the system 1600, apparatus 2300, and method 2400 depicted in Figures 10, 13, and 14, respectively. Benificially, this embodiment ensures that the shared, redundant cache maintains coherence without additional, complex coherence algorithms and protocols. In another embodiment, the solid-state storage 110 and the HCNV storage devices 3404a- n comprise a hybrid storage device and the apparatus 3500 includes a standard device emulation module 3510 that provides access to the hybrid storage device by emulating a standard device attached to one or more requesting devices 155 prior to loading the requesting devices 155 with code specific to the operation of the hybrid storage device. In the embodiment, the standard device is supported by an industry standard BIOS. This bootstrap operation allows the hybrid device to be recognized and accessed by the requesting devices 155 with limited functionality until drivers specific to the solid-state storage controller 104, HCNV storage controller 3404, and possibly the other modules 3502-3510 of the apparatus 3500 can be loaded on the requesting devices 155. In one embodiment, the solid-state storage device 110 may be partitioned into two or more regions where one or more of the partitions are used as solid-state storage independent of the solid-state storage functioning as cache for the HCNV storage devices 3404. For example, some partitions of the solid-state storage 110 may be accessed by clients 114 for general data storage while one or more partitions are dedicated as cache for the HCNV storage devices 3404. In one embodiment, more than one client 114 (or requesting device 155) is able to send cache control messages to the cache front-end module 3502 and the cache back-end module 3504 to manage a state of one or more of files or objects stored within the solid-state storage device 1 10 and the one or more HCNV storage devices 3404. Beneficially, the ability for clients 114/requesting devices 155 to manage cache on a per file, per object, or per data segment basis provides a great deal of flexibility for sharing a solid-state storage device 110.
Numerous cache control messages are allowable and possible. For example, a cache control message may include a control message that causes the cache back-end module 3504 to pin a portion of an object or file in the solid-state storage 110. Another cache control message may include a control message that causes the cache back-end module 3504 to unpin a portion of an object or file in the solid-state storage 110. Another cache control message may include a control message that causes the cache back-end module 3404 to flush a portion of an object or file from the solid-state storage 110 to the one or more HCVN storage devices 3404. Another cache control message may include a control message that causes the cache back-end module 3404 to preload a portion of an object or file to the solid-state storage 110 from the one or more HCVN storage devices 3404. Another cache control message may include a control message that causes the cache back-end module 3504 to offload one or more portions of one or more objects or files from the solid-state storage to the HCVN storage devices 3404 in order to free up a determined amount of storage space in the solid-state storage 110. One of skill in the art will recognize other possible cache control messages.
In one embodiment, the cache control messages are communicated through metadata ("cache control metadata") for the object or file. The cache control metadata, in one embodiment, is persistent. In another embodiment, the cache control metadata is established through attributes set at a time of creation of the file or object. In the embodiment, the attributes may be inherited through relationship to a particular object class, defaults characteristic of specific file types, etc. In another embodiment, the cache control metadata is obtained from a file or object management system. One of skill in the art will recognize other ways that cache control messages may be communicated through metadata. In one embodiment, the system 3400 includes a volatile cache storage element. For example, in addition to the solid-state storage 110, the system 3400 may also include random access memory ("RAM") of some type that is volatile. In this embodiment, the cache front-end module 3502 and the cache back-end module 3504 store some data in the volatile cache storage element and manage data stored in the solid-state storage 1 10 and volatile cache storage element and the back-end storage module 3504 also manages data transfers between the volatile cache storage element, the solid state storage, and the HCVN storage devices. For example, data that is not critical or may easily be recovered from another source may be stored in the volatile cache while other data may be stored in the solid-state storage 110 functioning as cache. In a further embodiment, metadata and/or index metadata for objects and files stored in the HCVN storage devices 3404 is maintained within the solid-state storage device 110 and in the volatile cache storage element. As described above in relation to the apparatus 200 depicted in Figure 2A, certain metadata may be stored in volatile cache storage element and may be used to rebuild an index if the data in the volatile cache storage element is lost. In one embodiment, metadata and index metadata is stored in the solid-state storage 110 where no volatile cache storage element is included. One of skill in the art will recognize other benefits and ways to use volatile cache storage elements along with solid-state storage 110 functioning as cache.
Figure 17 is a schematic flow chart diagram illustrating one embodiment of a method 3600 with solid-state storage as cache for a high-capacity, non-volatile storage device in accordance with the present invention. The method 3600 begins 3602 and the cache front-end module 3502 manages 3604 data transfers associated with a storage request, where the data transfers are between a requesting device 155 and solid-state storage 110 functioning as cache for one or more HCNV storage devices 3404a-n. The cache back-end module 3504 manages 3606 data transfers between the solid-state storage 110 and the one or more HCNV storage devices 110 and the method 3600 ends 3608. The method 3600 operates substantially similar as described above in relation to the apparatus 3500 of Figure 10.
The present invention may be embodied in other specific forms without departing from its spirit or essential characteristics. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.

Claims

1. An apparatus for managing the storage of data on one or more high capacity, non- volatile ("HCNV") storage devices, the apparatus comprising: a cache front-end module that manages data transfers associated with a storage request, the data transfers between a requesting device and solid-state storage functioning as cache for one or more HCNV storage devices, the data transfers comprising one or more of data, metadata, and metadata indexes, the solid-state storage comprising an array of non-volatile, solid-state data storage elements; and a cache back-end module that manages data transfers between the solid-state storage and the one or more HCNV storage devices.
2. The apparatus of claim 1, wherein the cache front-end module and the cache back-end module are co-located with a solid-state storage controller that manages the solid-state storage.
3. The apparatus of claim 2, wherein the cache front-end module, the cache back-end module, and the solid-state storage controller operate autonomously from the requesting device.
4. The apparatus of claim 1 , wherein the solid state controller further comprises an object storage controller module that services object requests from one or more requesting devices and manages objects of the object requests within the solid-state storage.
5. The apparatus of claim 1, further comprising an HCNV RAID module that stores data cached in the solid-state storage in two or more HCNV storage devices in redundant array of independent drives ("RAID") consistent with a RAID level, wherein the data appears to a requesting device as a whole.
6. The apparatus of claim 1 , wherein the solid-state storage and the one or more HCNV storage device comprise a hybrid storage device within a hybrid storage devices set that is configured as a RAID group, wherein a data segment cached in the solid-state storage and later stored on an HCNV device comprises one of N data segments of a stripe or a parity data segment of the stripe, wherein the hybrid storage device receives storage requests from one or more clients independent of data segments of a RAID stripe.
7. The apparatus of claim 6, wherein the hybrid storage device is a storage device of a shared, front-end distributed RAID group that receives two or more simultaneous storage requests from two or more clients.
8. The apparatus of claim 1 , wherein the HCNV storage device is one of a hard disk drive ("HDD"), an optical drive, and a tape storage.
9. The apparatus of claim 1, wherein the solid-state storage and the one or more HCNV storage devices comprise a hybrid storage device and further comprising a standard device emulation module that provides access to the hybrid storage device by emulating a standard device attached to one or more requesting devices prior to loading the one or more requesting devices with code specific to the operation of the hybrid storage device, the standard device being supported by an industry standard BIOS.
10. The apparatus of claim 1, wherein the solid-state storage device may be partitioned into two or more regions, wherein one or more partitions may be used as solid-state storage independent of the solid-state storage functioning as cache for the HCNV storage devices.
11. The apparatus of claim 1 , wherein one or more clients send cache control messages to the cache front-end module and the cache back-end module to manage a state of one or more of files or objects stored within the solid-state storage device and the one or more HCNV storage devices.
12. The apparatus of claim 11, wherein the cache control messages comprise one or more of: a control message that causes the cache back-end module to pin a portion of an object or file in the solid-state storage; a control message that causes the cache back-end module to unpin a portion of an object or file in the solid-state storage; a control message that causes the cache back-end module to flush a portion of an object or file from the solid-state storage to the one or more HCVN storage devices; a control message that causes the cache back-end module to preload a portion of an object or file to the solid-state storage from the one or more HCVN storage devices; a control message that causes the cache back-end module to offload one or more portions of one or more objects or files from the solid-state storage to the one or more HCVN storage devices in order to free up a determined amount of storage space in the solid-state storage;
13. The apparatus of claim 11 , wherein the cache control messages are communicated through metadata ("cache control metadata") for the object or file.
14. The apparatus of claim 13, wherein the cache control metadata is persistent.
15. The apparatus of claim 13, wherein the cache control metadata is established through attributes set at a time of creation of the file or object.
16. The apparatus of claim 13, wherein the cache control metadata is obtained from a file or object management system.
17. The apparatus of claim 1, further comprising a volatile cache storage element and wherein the cache front-end module and the cache back-end module further comprise storing data in the volatile cache storage element and manage data stored in the solid- state storage and volatile cache storage element and wherein the back-end storage module further manages data transfers between the volatile cache storage element, the solid state storage, and the HCVN storage devices.
18. The apparatus of claim 17, wherein one or more of metadata and index metadata for objects and files stored in the HCVN storage devices is maintained within the solid-state storage device and the volatile cache storage element.
19. The apparatus of claim 1, wherein one or more of metadata and index metadata for objects and files stored in the HCVN storage devices is maintained within the solid-state storage device.
20. The apparatus of claim 1, wherein the solid-state storage and the one or more HCNV storage devices comprise a storage device such that the HCNV storage devices are hidden from view of a client connected to the storage device.
21. A system for managing the storage of data on one or more high capacity, non- volatile
("HCNV") storage devices, the system comprising: a solid-state storage comprising an array of nbn-volatile, solid-state data storage elements; one or more HCNV storage devices; and a storage controller comprising a solid-state storage controller; an HCNV storage device controller; a cache front-end module that manages data transfers associated with a storage request, the data transfers between a requesting device and the solid-state storage functioning as cache for the one or more HCNV storage devices, the data transfers comprising one or more of data, metadata, and metadata indexes; and a cache back-end module that manages data transfers between the solid-state storage and the one or more HCNV storage devices.
22. The system of claim 21 , further comprising a network interface connected to the storage controller, the network interface facilitating data transfers between the requesting device and the solid-state storage controller through a computer network.
23. The system of claim 21, further comprising a server, wherein the server includes the solid-state storage, the one or more HCNV storage devices, and the storage controller.
24. The system of claim 21, wherein the one or more HCNV storage devices are connected to the storage controller through a storage area network ("SAN").
25. A computer program product comprising a computer readable medium having computer usable program code executable to perform operations for managing the storage of data on one or more high capacity, non-volatile ("HCNV") storage devices, the operations of the computer program product comprising: managing data transfers associated with a storage request, the data transfers between a requesting device and solid-state storage functioning as cache for one or more
HCNV storage devices, the data transfers comprising one or more of data, metadata, and metadata indexes, the solid-state storage comprising an array of non-volatile, solid-state data storage elements; and managing data transfers between the solid-state storage and the one or more HCNV storage devices.
PCT/US2007/025049 2006-12-06 2007-12-06 Apparatus, system, and method for solid-state storage as cache for high-capacity, non-volatile storage WO2008070173A1 (en)

Priority Applications (6)

Application Number Priority Date Filing Date Title
JP2009540309A JP5523835B2 (en) 2006-12-06 2007-12-06 Apparatus, system and method for solid state storage as cache for high capacity non-volatile storage
EP07867661.6A EP2109822B1 (en) 2006-12-06 2007-12-06 Apparatus, system, and method for solid-state storage as cache for high-capacity, non-volatile storage
CN200780050973.4A CN101622606B (en) 2006-12-06 2007-12-06 Apparatus, system, and method for solid-state storage as cache for high-capacity, non-volatile storage
KR1020147028326A KR101532951B1 (en) 2006-12-06 2007-12-06 Apparatus, system and method for solid-state storage as cache for high-capacity, non-volatile storage
ES07867661.6T ES2507072T3 (en) 2006-12-06 2007-12-06 Apparatus, system, and method for solid-state storage as a cache for high-capacity non-volatile storage
CA002672100A CA2672100A1 (en) 2006-12-06 2007-12-06 Apparatus, system, and method for solid-state storage as cache for high-capacity, non-volatile storage

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US87311106P 2006-12-06 2006-12-06
US60/873,111 2006-12-06
US97447007P 2007-09-22 2007-09-22
US60/974,470 2007-09-22

Publications (1)

Publication Number Publication Date
WO2008070173A1 true WO2008070173A1 (en) 2008-06-12

Family

ID=39223046

Family Applications (15)

Application Number Title Priority Date Filing Date
PCT/US2007/086683 WO2008070796A2 (en) 2006-12-06 2007-12-06 Apparatus, system, and method for managing data using a data pipeline
PCT/US2007/086705 WO2008127458A2 (en) 2006-12-06 2007-12-06 Apparatus, system, and method for a shared, front-end, distributed raid
PCT/US2007/086686 WO2008070798A1 (en) 2006-12-06 2007-12-06 Apparatus, system, and method for managing commands of solid-state storage using bank interleave
PCT/US2007/086703 WO2008070813A2 (en) 2006-12-06 2007-12-06 Apparatus, system, and method for a front-end, distributed raid
PCT/US2007/025048 WO2008070172A2 (en) 2006-12-06 2007-12-06 Apparatus, system, and method for remote direct memory access to a solid-state storage device
PCT/US2007/086687 WO2008070799A2 (en) 2006-12-06 2007-12-06 Apparatus, system, and method for servicing object requests within a storage controller
PCT/US2007/025050 WO2008070174A2 (en) 2006-12-06 2007-12-06 Apparatus, system, and method for a device shared between multiple independent hosts
PCT/US2007/025188 WO2008070191A2 (en) 2006-12-06 2007-12-06 Apparatus, system, and method for a reconfigurable baseboard management controller
PCT/US2007/086688 WO2008070800A1 (en) 2006-12-06 2007-12-06 Apparatus, system, and method for storage space recovery in solid-state storage
PCT/US2007/086691 WO2008070803A1 (en) 2006-12-06 2007-12-06 Apparatus, system, and method for managing data from a requesting device with an empty data token directive
PCT/US2007/025049 WO2008070173A1 (en) 2006-12-06 2007-12-06 Apparatus, system, and method for solid-state storage as cache for high-capacity, non-volatile storage
PCT/US2007/086702 WO2008070812A2 (en) 2006-12-06 2007-12-06 Apparatus, system, and method for data storage using progressive raid
PCT/US2007/086704 WO2008070814A2 (en) 2006-12-06 2007-12-06 Apparatus, system, and method for a scalable, composite, reconfigurable backplane
PCT/US2007/086690 WO2008070802A2 (en) 2006-12-06 2007-12-06 Apparatus, system, and method for an in-server storage area network
PCT/US2007/086701 WO2008070811A2 (en) 2006-12-06 2007-12-06 Apparatus, system, and method for managing data in a storage device with an empty data token directive

Family Applications Before (10)

Application Number Title Priority Date Filing Date
PCT/US2007/086683 WO2008070796A2 (en) 2006-12-06 2007-12-06 Apparatus, system, and method for managing data using a data pipeline
PCT/US2007/086705 WO2008127458A2 (en) 2006-12-06 2007-12-06 Apparatus, system, and method for a shared, front-end, distributed raid
PCT/US2007/086686 WO2008070798A1 (en) 2006-12-06 2007-12-06 Apparatus, system, and method for managing commands of solid-state storage using bank interleave
PCT/US2007/086703 WO2008070813A2 (en) 2006-12-06 2007-12-06 Apparatus, system, and method for a front-end, distributed raid
PCT/US2007/025048 WO2008070172A2 (en) 2006-12-06 2007-12-06 Apparatus, system, and method for remote direct memory access to a solid-state storage device
PCT/US2007/086687 WO2008070799A2 (en) 2006-12-06 2007-12-06 Apparatus, system, and method for servicing object requests within a storage controller
PCT/US2007/025050 WO2008070174A2 (en) 2006-12-06 2007-12-06 Apparatus, system, and method for a device shared between multiple independent hosts
PCT/US2007/025188 WO2008070191A2 (en) 2006-12-06 2007-12-06 Apparatus, system, and method for a reconfigurable baseboard management controller
PCT/US2007/086688 WO2008070800A1 (en) 2006-12-06 2007-12-06 Apparatus, system, and method for storage space recovery in solid-state storage
PCT/US2007/086691 WO2008070803A1 (en) 2006-12-06 2007-12-06 Apparatus, system, and method for managing data from a requesting device with an empty data token directive

Family Applications After (4)

Application Number Title Priority Date Filing Date
PCT/US2007/086702 WO2008070812A2 (en) 2006-12-06 2007-12-06 Apparatus, system, and method for data storage using progressive raid
PCT/US2007/086704 WO2008070814A2 (en) 2006-12-06 2007-12-06 Apparatus, system, and method for a scalable, composite, reconfigurable backplane
PCT/US2007/086690 WO2008070802A2 (en) 2006-12-06 2007-12-06 Apparatus, system, and method for an in-server storage area network
PCT/US2007/086701 WO2008070811A2 (en) 2006-12-06 2007-12-06 Apparatus, system, and method for managing data in a storage device with an empty data token directive

Country Status (8)

Country Link
US (39) US20080140724A1 (en)
EP (9) EP2126698A2 (en)
JP (4) JP2010512584A (en)
KR (7) KR20090087119A (en)
CN (7) CN101689131B (en)
CA (2) CA2672100A1 (en)
ES (1) ES2507072T3 (en)
WO (15) WO2008070796A2 (en)

Cited By (68)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010071655A1 (en) 2008-12-19 2010-06-24 Hewlett-Packard Development Company, L.P. Redundant data storage for uniform read latency
WO2010093108A1 (en) * 2009-02-13 2010-08-19 (주)인디링스 Storage system using a rapid storage device as a cache
WO2010116419A1 (en) * 2009-04-10 2010-10-14 Hitachi, Ltd. Storage apparatus and method for shredding storage medium
JP2010282628A (en) * 2009-06-08 2010-12-16 Lsi Corp Method and device for protecting maintainability of data cached in direct attached storage (das) system
WO2010147827A1 (en) * 2009-06-16 2010-12-23 Sandisk Corporation Multi-bank non-volatile memory system with satellite file system
WO2011028802A1 (en) * 2009-09-01 2011-03-10 Marvell World Trade Ltd. Systems and methods for compressing data in non-volatile semiconductor memory drives
WO2011005763A3 (en) * 2009-07-06 2011-04-14 Micron Technology, Inc. Data transfer management
WO2011070526A1 (en) * 2009-12-11 2011-06-16 International Business Machines Corporation Flash memory controller
CN102110481A (en) * 2009-12-24 2011-06-29 海力士半导体有限公司 Semiconductor memory system having ECC circuit and method of controlling thereof
WO2011087602A1 (en) * 2009-12-23 2011-07-21 Sandisk Corporation System and method of error correction of control data at a memory device
EP2350830A1 (en) * 2008-10-30 2011-08-03 LSI Corporation Storage controller data redistribution
CN102223510A (en) * 2011-06-03 2011-10-19 杭州华三通信技术有限公司 Method and device for scheduling cache
US8161251B2 (en) 2009-05-27 2012-04-17 Microsoft Corporation Heterogeneous storage array optimization through eviction
EP2452266A1 (en) * 2009-07-07 2012-05-16 LSI Corporation Systems and methods for tiered non-volatile storage
US8195878B2 (en) 2009-02-19 2012-06-05 Pmc-Sierra, Inc. Hard disk drive with attached solid state drive cache
US8214621B2 (en) 2009-04-29 2012-07-03 Microsoft Corporation Storage optimization across media with differing capabilities
EP2476079A2 (en) * 2009-09-09 2012-07-18 Fusion-io, Inc. Apparatus, system, and method for allocating storage
WO2012100257A2 (en) * 2011-01-21 2012-07-26 Fusion-Io, Inc. Apparatus, system, and method for destaging cached data
US8321630B1 (en) 2010-01-28 2012-11-27 Microsoft Corporation Application-transparent hybridized caching for high-performance storage
WO2012168960A1 (en) * 2011-06-07 2012-12-13 Hitachi, Ltd. Semiconductor storage apparatus and method of controlling semiconductor storage apparatus
EP2372521A3 (en) * 2010-04-02 2013-04-24 Intel Corporation Remote direct storage access
US8443134B2 (en) 2006-12-06 2013-05-14 Fusion-Io, Inc. Apparatus, system, and method for graceful cache device degradation
US8489817B2 (en) 2007-12-06 2013-07-16 Fusion-Io, Inc. Apparatus, system, and method for caching data
WO2013105960A1 (en) * 2012-01-12 2013-07-18 Fusion-Io, Inc. Systems and methods for managing cache admission
US20130232153A1 (en) * 2012-03-02 2013-09-05 Cleversafe, Inc. Modifying an index node of a hierarchical dispersed storage index
WO2013134345A1 (en) * 2012-03-07 2013-09-12 Netapp, Inc. Hybrid storage aggregate block tracking
WO2013134347A1 (en) * 2012-03-07 2013-09-12 Netapp, Inc. Deduplicating hybrid storage aggregate
WO2013142667A1 (en) * 2012-03-23 2013-09-26 DSSD, Inc. Solid state data storage system and methods therefor
US8554963B1 (en) * 2012-03-23 2013-10-08 DSSD, Inc. Storage system with multicast DMA and unified address space
US8706968B2 (en) 2007-12-06 2014-04-22 Fusion-Io, Inc. Apparatus, system, and method for redundant write caching
US8719501B2 (en) 2009-09-08 2014-05-06 Fusion-Io Apparatus, system, and method for caching data on a solid-state storage device
EP2732375A2 (en) * 2011-07-12 2014-05-21 Violin Memory Inc. Raided memory system
US8751904B2 (en) 2010-07-22 2014-06-10 Silicon Motion Inc. Controlling methods and controllers utilized in flash memory device for referring to data compression result to adjust ECC protection capability
EP2728488A3 (en) * 2009-04-08 2014-06-11 Google, Inc. Data storage device
WO2014102879A1 (en) * 2012-12-28 2014-07-03 Hitachi, Ltd. Data storage apparatus and control method thereof
US8782344B2 (en) 2012-01-12 2014-07-15 Fusion-Io, Inc. Systems and methods for managing cache admission
WO2014116875A2 (en) 2013-01-23 2014-07-31 Nexenta Systems, Inc. Scalable transport for multicast replication and scalable object storage using multicast transport
US8825937B2 (en) 2011-02-25 2014-09-02 Fusion-Io, Inc. Writing cached data forward on read
US8966191B2 (en) 2011-03-18 2015-02-24 Fusion-Io, Inc. Logical interface for contextual storage
US8966184B2 (en) 2011-01-31 2015-02-24 Intelligent Intellectual Property Holdings 2, LLC. Apparatus, system, and method for managing eviction of data
WO2015061629A1 (en) 2013-10-24 2015-04-30 Western Digital Technologies, Inc. Data storage device supporting accelerated database operations
WO2015108670A1 (en) * 2014-01-17 2015-07-23 Netapp, Inc. File system driven raid rebuild technique
US9122579B2 (en) 2010-01-06 2015-09-01 Intelligent Intellectual Property Holdings 2 Llc Apparatus, system, and method for a storage layer
US9141291B2 (en) 2013-11-26 2015-09-22 Sandisk Technologies Inc. Adaptive context disbursement for improved performance in non-volatile memory systems
US9244842B2 (en) 2009-04-08 2016-01-26 Google Inc. Data storage device with copy command
US9251052B2 (en) 2012-01-12 2016-02-02 Intelligent Intellectual Property Holdings 2 Llc Systems and methods for profiling a non-volatile cache having a logical-to-physical translation layer
US9251086B2 (en) 2012-01-24 2016-02-02 SanDisk Technologies, Inc. Apparatus, system, and method for managing a cache
US9274937B2 (en) 2011-12-22 2016-03-01 Longitude Enterprise Flash S.A.R.L. Systems, methods, and interfaces for vector input/output operations
US9417823B2 (en) 2011-07-12 2016-08-16 Violin Memory Inc. Memory system management
US9519540B2 (en) 2007-12-06 2016-12-13 Sandisk Technologies Llc Apparatus, system, and method for destaging cached data
US9563555B2 (en) 2011-03-18 2017-02-07 Sandisk Technologies Llc Systems and methods for storage allocation
US9600184B2 (en) 2007-12-06 2017-03-21 Sandisk Technologies Llc Apparatus, system, and method for coordinating storage requests in a multi-processor/multi-thread environment
US9734086B2 (en) 2006-12-06 2017-08-15 Sandisk Technologies Llc Apparatus, system, and method for a device shared between multiple independent hosts
US9767032B2 (en) 2012-01-12 2017-09-19 Sandisk Technologies Llc Systems and methods for cache endurance
US9842128B2 (en) 2013-08-01 2017-12-12 Sandisk Technologies Llc Systems and methods for atomic storage operations
US9946607B2 (en) 2015-03-04 2018-04-17 Sandisk Technologies Llc Systems and methods for storage error management
US10019320B2 (en) 2013-10-18 2018-07-10 Sandisk Technologies Llc Systems and methods for distributed atomic storage operations
US10073630B2 (en) 2013-11-08 2018-09-11 Sandisk Technologies Llc Systems and methods for log coordination
US10102144B2 (en) 2013-04-16 2018-10-16 Sandisk Technologies Llc Systems, methods and interfaces for data virtualization
US10102117B2 (en) 2012-01-12 2018-10-16 Sandisk Technologies Llc Systems and methods for cache and storage device coordination
US10318495B2 (en) 2012-09-24 2019-06-11 Sandisk Technologies Llc Snapshots for a non-volatile device
US10444998B1 (en) 2013-10-24 2019-10-15 Western Digital Technologies, Inc. Data storage device providing data maintenance services
US10509776B2 (en) 2012-09-24 2019-12-17 Sandisk Technologies Llc Time sequence data management
US10558561B2 (en) 2013-04-16 2020-02-11 Sandisk Technologies Llc Systems and methods for storage metadata management
US11347678B2 (en) 2018-08-06 2022-05-31 Oracle International Corporation One-sided reliable remote direct memory operations
US11416447B2 (en) 2017-06-08 2022-08-16 Hitachi Vantara Llc Deduplicating distributed erasure coded objects
EP4155940A1 (en) * 2021-09-27 2023-03-29 Graid Technology Inc. Direct memory access data path for raid storage
EP2842271B1 (en) * 2012-04-25 2024-04-17 Hewlett Packard Enterprise Development LP Network management

Families Citing this family (1212)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7146524B2 (en) * 2001-08-03 2006-12-05 Isilon Systems, Inc. Systems and methods for providing a distributed file system incorporating a virtual hot spare
US7685126B2 (en) 2001-08-03 2010-03-23 Isilon Systems, Inc. System and methods for providing a distributed file system utilizing metadata to track information about data stored throughout the system
WO2003094513A1 (en) * 2002-04-30 2003-11-13 General Dynamics Advanced Information Systems, Inc. Method and apparatus for in-line serial data encryption
CN1692356B (en) 2002-11-14 2014-06-04 易斯龙系统公司 Systems and methods for restriping files in a distributed file system
US8346884B2 (en) 2003-01-21 2013-01-01 Nextio Inc. Method and apparatus for a shared I/O network interface controller
WO2005089241A2 (en) 2004-03-13 2005-09-29 Cluster Resources, Inc. System and method for providing object triggers
US8782654B2 (en) 2004-03-13 2014-07-15 Adaptive Computing Enterprises, Inc. Co-allocating a reservation spanning different compute resources types
US20070266388A1 (en) 2004-06-18 2007-11-15 Cluster Resources, Inc. System and method for providing advanced reservations in a compute environment
US8176490B1 (en) 2004-08-20 2012-05-08 Adaptive Computing Enterprises, Inc. System and method of interfacing a workload manager and scheduler with an identity manager
US8055711B2 (en) 2004-10-29 2011-11-08 Emc Corporation Non-blocking commit protocol systems and methods
US8051425B2 (en) 2004-10-29 2011-11-01 Emc Corporation Distributed system with asynchronous execution systems and methods
US8238350B2 (en) 2004-10-29 2012-08-07 Emc Corporation Message batching with checkpoints systems and methods
US8271980B2 (en) 2004-11-08 2012-09-18 Adaptive Computing Enterprises, Inc. System and method of providing system jobs within a compute environment
US8863143B2 (en) 2006-03-16 2014-10-14 Adaptive Computing Enterprises, Inc. System and method for managing a hybrid compute environment
US8631130B2 (en) 2005-03-16 2014-01-14 Adaptive Computing Enterprises, Inc. Reserving resources in an on-demand compute environment from a local compute environment
US9231886B2 (en) 2005-03-16 2016-01-05 Adaptive Computing Enterprises, Inc. Simple integration of an on-demand compute environment
CA2603577A1 (en) 2005-04-07 2006-10-12 Cluster Resources, Inc. On-demand access to compute resources
US8200887B2 (en) 2007-03-29 2012-06-12 Violin Memory, Inc. Memory management system and method
US9286198B2 (en) 2005-04-21 2016-03-15 Violin Memory Method and system for storage of data in non-volatile media
US8112655B2 (en) * 2005-04-21 2012-02-07 Violin Memory, Inc. Mesosynchronous data bus apparatus and method of data transmission
US9384818B2 (en) 2005-04-21 2016-07-05 Violin Memory Memory power management
US8452929B2 (en) 2005-04-21 2013-05-28 Violin Memory Inc. Method and system for storage of data in non-volatile media
US8143653B2 (en) * 2005-08-10 2012-03-27 Samsung Electronics Co., Ltd. Variable resistance memory device and system thereof
US8325768B2 (en) 2005-08-24 2012-12-04 Intel Corporation Interleaving data packets in a packet-based communication system
JP5008845B2 (en) 2005-09-01 2012-08-22 株式会社日立製作所 Storage system, storage apparatus and control method thereof
US20080220880A1 (en) * 2005-09-07 2008-09-11 Bally Gaming, Inc. Trusted Cabinet Identification System
US7788303B2 (en) 2005-10-21 2010-08-31 Isilon Systems, Inc. Systems and methods for distributed system scanning
US7797283B2 (en) 2005-10-21 2010-09-14 Isilon Systems, Inc. Systems and methods for maintaining distributed data
US7917474B2 (en) 2005-10-21 2011-03-29 Isilon Systems, Inc. Systems and methods for accessing and updating distributed data
US7551572B2 (en) 2005-10-21 2009-06-23 Isilon Systems, Inc. Systems and methods for providing variable protection
US7848261B2 (en) 2006-02-17 2010-12-07 Isilon Systems, Inc. Systems and methods for providing a quiescing protocol
US7930439B2 (en) * 2006-03-31 2011-04-19 Panasonic Corporation Command output control apparatus
US7756898B2 (en) 2006-03-31 2010-07-13 Isilon Systems, Inc. Systems and methods for notifying listeners of events
US8046629B1 (en) 2006-07-24 2011-10-25 Marvell World Trade Ltd. File server for redundant array of independent disks (RAID) system
US7634686B2 (en) * 2006-07-24 2009-12-15 Marvell World Trade Ltd. File server for redundant array of independent disks (RAID) system
US7953704B2 (en) 2006-08-18 2011-05-31 Emc Corporation Systems and methods for a snapshot of data
US7680836B2 (en) 2006-08-18 2010-03-16 Isilon Systems, Inc. Systems and methods for a snapshot of data
US7822932B2 (en) 2006-08-18 2010-10-26 Isilon Systems, Inc. Systems and methods for providing nonlinear journaling
US7680842B2 (en) 2006-08-18 2010-03-16 Isilon Systems, Inc. Systems and methods for a snapshot of data
US7882071B2 (en) 2006-08-18 2011-02-01 Isilon Systems, Inc. Systems and methods for a snapshot of data
US7590652B2 (en) * 2006-08-18 2009-09-15 Isilon Systems, Inc. Systems and methods of reverse lookup
US7899800B2 (en) 2006-08-18 2011-03-01 Isilon Systems, Inc. Systems and methods for providing nonlinear journaling
US8028186B2 (en) 2006-10-23 2011-09-27 Violin Memory, Inc. Skew management in an interconnection system
US9116823B2 (en) 2006-12-06 2015-08-25 Intelligent Intellectual Property Holdings 2 Llc Systems and methods for adaptive error-correction coding
US9495241B2 (en) 2006-12-06 2016-11-15 Longitude Enterprise Flash S.A.R.L. Systems and methods for adaptive data storage
US8935302B2 (en) 2006-12-06 2015-01-13 Intelligent Intellectual Property Holdings 2 Llc Apparatus, system, and method for data block usage information synchronization for a non-volatile storage volume
US7836238B2 (en) * 2006-12-19 2010-11-16 International Business Machines Corporation Hot-plug/remove of a new component in a running PCIe fabric
US7860930B2 (en) * 2006-12-19 2010-12-28 International Business Machines Corporation Communication between host systems using a transaction protocol and shared memories
US7657663B2 (en) * 2006-12-19 2010-02-02 International Business Machines Corporation Migrating stateless virtual functions from one virtual plane to another
US7984454B2 (en) * 2006-12-19 2011-07-19 International Business Machines Corporation Migration of single root stateless virtual functions
US8271604B2 (en) * 2006-12-19 2012-09-18 International Business Machines Corporation Initializing shared memories for sharing endpoints across a plurality of root complexes
US7813366B2 (en) * 2006-12-19 2010-10-12 International Business Machines Corporation Migration of a virtual endpoint from one virtual plane to another
US7991839B2 (en) * 2006-12-19 2011-08-02 International Business Machines Corporation Communication between host systems using a socket connection and shared memories
US7836129B2 (en) * 2006-12-19 2010-11-16 International Business Machines Corporation Communication between host systems using a queuing system and shared memories
US8286029B2 (en) 2006-12-21 2012-10-09 Emc Corporation Systems and methods for managing unavailable storage devices
US7593938B2 (en) 2006-12-22 2009-09-22 Isilon Systems, Inc. Systems and methods of directory entry encodings
US8139432B2 (en) * 2006-12-27 2012-03-20 Samsung Electronics Co., Ltd. Variable resistance memory device and system thereof
US8239706B1 (en) * 2007-01-03 2012-08-07 Board Of Governors For Higher Education, State Of Rhode Island And Providence Plantations Data retrieval system and method that provides retrieval of data to any point in time
US7509448B2 (en) 2007-01-05 2009-03-24 Isilon Systems, Inc. Systems and methods for managing semantic locks
US9632870B2 (en) * 2007-03-29 2017-04-25 Violin Memory, Inc. Memory system with multiple striping of raid groups and method for performing the same
US11010076B2 (en) 2007-03-29 2021-05-18 Violin Systems Llc Memory system with multiple striping of raid groups and method for performing the same
US8966080B2 (en) 2007-04-13 2015-02-24 Emc Corporation Systems and methods of managing resource utilization on a threaded computer system
US7900015B2 (en) 2007-04-13 2011-03-01 Isilon Systems, Inc. Systems and methods of quota accounting
US7779048B2 (en) 2007-04-13 2010-08-17 Isilon Systems, Inc. Systems and methods of providing possible value ranges
US8332574B2 (en) * 2007-04-30 2012-12-11 Sandisk Il Ltd. Method for efficient storage of metadata in flash memory
US8309521B2 (en) * 2007-06-19 2012-11-13 Zimmer, Inc. Spacer with a coating thereon for use with an implant device
US20090028337A1 (en) * 2007-07-23 2009-01-29 Savi Technology, Inc. Method and Apparatus for Providing Security in a Radio Frequency Identification System
US7743204B2 (en) * 2007-08-01 2010-06-22 Transcend Information, Inc. Non-volatile memory device and data access circuit and data access method
KR20090014828A (en) * 2007-08-07 2009-02-11 삼성전자주식회사 Flash memory system encrypting error correction code and encryption method of flash memory system
US11237956B2 (en) * 2007-08-13 2022-02-01 Digital Kiva, Inc. Apparatus and system for object-based storage solid-state device
US7882068B2 (en) 2007-08-21 2011-02-01 Isilon Systems, Inc. Systems and methods for adaptive copy on write
US7966289B2 (en) 2007-08-21 2011-06-21 Emc Corporation Systems and methods for reading objects in a file system
US7949692B2 (en) 2007-08-21 2011-05-24 Emc Corporation Systems and methods for portals into snapshot data
WO2009095902A2 (en) 2008-01-31 2009-08-06 Densbits Technologies Ltd. Systems and methods for handling immediate data errors in flash memory
US8041773B2 (en) 2007-09-24 2011-10-18 The Research Foundation Of State University Of New York Automatic clustering for self-organizing grids
US8527991B2 (en) * 2007-09-27 2013-09-03 Proximal System Corporation Apparatus, system, and method for cross-system proxy-based task offloading
US8694715B2 (en) 2007-10-22 2014-04-08 Densbits Technologies Ltd. Methods for adaptively programming flash memory devices and flash memory systems incorporating same
US8959307B1 (en) 2007-11-16 2015-02-17 Bitmicro Networks, Inc. Reduced latency memory read transactions in storage devices
US8453022B2 (en) 2007-12-05 2013-05-28 Densbits Technologies Ltd. Apparatus and methods for generating row-specific reading thresholds in flash memory
US8316277B2 (en) 2007-12-06 2012-11-20 Fusion-Io, Inc. Apparatus, system, and method for ensuring data validity in a data storage process
TWI350454B (en) * 2007-12-10 2011-10-11 Phison Electronics Corp Anti-attacking method for private key, controller and storage device executing the same
US8359516B2 (en) 2007-12-12 2013-01-22 Densbits Technologies Ltd. Systems and methods for error correction and decoding on multi-level physical media
CA2625274C (en) 2007-12-13 2018-11-20 Kevin Gerard Boyce Method and system for protecting a computer system during boot operation
US8621138B2 (en) 2007-12-27 2013-12-31 Sandisk Enterprise Ip Llc Flash storage controller execute loop
US9112886B2 (en) * 2007-12-27 2015-08-18 Verizon Patent And Licensing Inc. Method and system for providing centralized data field encryption, and distributed storage and retrieval
US9047468B2 (en) * 2007-12-28 2015-06-02 Intel Corporation Migration of full-disk encrypted virtualized storage between blade servers
CN101217468A (en) * 2007-12-28 2008-07-09 华为技术有限公司 A routing table look-up system, tristate content addressing memory and network processor
GB2458260A (en) * 2008-02-26 2009-09-16 Advanced Risc Mach Ltd Selectively disabling error repair circuitry in an integrated circuit
KR101086855B1 (en) * 2008-03-10 2011-11-25 주식회사 팍스디스크 Solid State Storage System with High Speed and Controlling Method thereof
JP5245472B2 (en) * 2008-03-13 2013-07-24 富士通株式会社 Control method, disk array device
US8972472B2 (en) 2008-03-25 2015-03-03 Densbits Technologies Ltd. Apparatus and methods for hardware-efficient unbiased rounding
US7870345B2 (en) 2008-03-27 2011-01-11 Isilon Systems, Inc. Systems and methods for managing stalled storage devices
US7949636B2 (en) 2008-03-27 2011-05-24 Emc Corporation Systems and methods for a read only mode for a portion of a storage system
US7953709B2 (en) 2008-03-27 2011-05-31 Emc Corporation Systems and methods for a read only mode for a portion of a storage system
US7984324B2 (en) * 2008-03-27 2011-07-19 Emc Corporation Systems and methods for managing stalled storage devices
JP2009238094A (en) * 2008-03-28 2009-10-15 Hitachi Ltd Storage system and data storage method
US10248398B2 (en) * 2008-04-07 2019-04-02 Blackberry Limited Method for virtualizing software applications
US8194492B2 (en) * 2008-04-08 2012-06-05 Samsung Electronics Co., Ltd. Variable resistance memory device and system
EP2111011A1 (en) * 2008-04-16 2009-10-21 Thomson Telecom Belgium Device and method for sharing files
US7933939B2 (en) * 2008-04-16 2011-04-26 Quantum Corporation Apparatus and method for partitioning data blocks
US9395929B2 (en) * 2008-04-25 2016-07-19 Netapp, Inc. Network storage server with integrated encryption, compression and deduplication capability
US20090319772A1 (en) * 2008-04-25 2009-12-24 Netapp, Inc. In-line content based security for data at rest in a network storage system
WO2009134772A2 (en) * 2008-04-29 2009-11-05 Maxiscale, Inc Peer-to-peer redundant file server system and methods
US8117464B1 (en) 2008-04-30 2012-02-14 Netapp, Inc. Sub-volume level security for deduplicated data
US8589697B2 (en) * 2008-04-30 2013-11-19 Netapp, Inc. Discarding sensitive data from persistent point-in-time image
US8533559B2 (en) * 2008-05-12 2013-09-10 Panasonic Corporation Semiconductor recording device with error recovery
WO2009140112A1 (en) 2008-05-13 2009-11-19 Rambus Inc. Fractional program commands for memory devices
EP2297742B1 (en) 2008-05-16 2013-07-24 Fusion-io, Inc. Apparatus, system, and method for detecting and replacing failed data storage
US8775718B2 (en) * 2008-05-23 2014-07-08 Netapp, Inc. Use of RDMA to access non-volatile solid-state memory in a network storage system
US20090300282A1 (en) * 2008-05-30 2009-12-03 Promise Technology, Inc. Redundant array of independent disks write recovery system
US8090909B2 (en) * 2008-06-06 2012-01-03 Pivot3 Method and system for distributed raid implementation
US8893160B2 (en) * 2008-06-09 2014-11-18 International Business Machines Corporation Block storage interface for virtual memory
CN101609413A (en) * 2008-06-18 2009-12-23 鸿富锦精密工业（深圳）有限公司 The device and method of remotely obtaining system information
US8185505B1 (en) * 2008-06-20 2012-05-22 Emc Corporation Techniques for processing recovery points
US8843691B2 (en) * 2008-06-25 2014-09-23 Stec, Inc. Prioritized erasure of data blocks in a flash storage device
US8719485B2 (en) * 2008-06-27 2014-05-06 Marvell World Trade Ltd. Solid-state disk with wireless functionality
US8219750B2 (en) 2008-06-30 2012-07-10 Pivot3 Method and system for execution of applications in conjunction with distributed RAID
US8300825B2 (en) * 2008-06-30 2012-10-30 Intel Corporation Data encryption and/or decryption by integrated circuit
US8615678B1 (en) 2008-06-30 2013-12-24 Emc Corporation Auto-adapting multi-tier cache
US9342528B2 (en) * 2010-04-01 2016-05-17 Avere Systems, Inc. Method and apparatus for tiered storage
US8214404B2 (en) 2008-07-11 2012-07-03 Avere Systems, Inc. Media aware distributed data layout
US9323681B2 (en) 2008-09-18 2016-04-26 Avere Systems, Inc. File storage system, cache appliance, and method
US9118695B1 (en) * 2008-07-15 2015-08-25 Pc-Doctor, Inc. System and method for secure optimized cooperative distributed shared data storage with redundancy
US8819011B2 (en) * 2008-07-16 2014-08-26 Cleversafe, Inc. Command line interpreter for accessing a data object stored in a distributed storage network
US20100017650A1 (en) * 2008-07-19 2010-01-21 Nanostar Corporation, U.S.A Non-volatile memory data storage system with reliability management
US20100125695A1 (en) * 2008-11-15 2010-05-20 Nanostar Corporation Non-volatile memory storage system
US20100017556A1 (en) * 2008-07-19 2010-01-21 Nanostar Corporationm U.S.A. Non-volatile memory storage system with two-stage controller architecture
US20100030963A1 (en) * 2008-08-04 2010-02-04 Sandisk Il Ltd. Managing storage of cached content
CN101334797B (en) * 2008-08-04 2010-06-02 中兴通讯股份有限公司 Distributed file systems and its data block consistency managing method
KR101636777B1 (en) * 2008-08-08 2016-07-21 시게이트 테크놀로지 엘엘씨 Hybrid storage device and method for assigning a logical block address thereof
US8145749B2 (en) * 2008-08-11 2012-03-27 International Business Machines Corporation Data processing in a hybrid computing environment
JP2010044827A (en) 2008-08-13 2010-02-25 Toshiba Corp Nonvolatile semiconductor storage device
US8359514B2 (en) * 2008-08-15 2013-01-22 Micron Technology, Inc. Data and error correction code mixing device and method
US8078906B2 (en) * 2008-08-21 2011-12-13 Infinidat, Ltd. Grid storage system and method of operating thereof
US8443137B2 (en) * 2008-08-21 2013-05-14 Infinidat Ltd. Grid storage system and method of operating thereof
US8452922B2 (en) * 2008-08-21 2013-05-28 Infinidat Ltd. Grid storage system and method of operating thereof
US20100049919A1 (en) * 2008-08-21 2010-02-25 Xsignnet Ltd. Serial attached scsi (sas) grid storage system and method of operating thereof
US8495291B2 (en) 2008-08-21 2013-07-23 Infinidat Ltd. Grid storage system and method of operating thereof
US8307044B2 (en) * 2008-08-28 2012-11-06 Netapp, Inc. Circuits, systems, and methods to integrate storage virtualization in a storage controller
GB2463078B (en) * 2008-09-02 2013-04-17 Extas Global Ltd Distributed storage
US7984267B2 (en) * 2008-09-04 2011-07-19 International Business Machines Corporation Message passing module in hybrid computing system starting and sending operation information to service program for accelerator to execute application program
US8141102B2 (en) 2008-09-04 2012-03-20 International Business Machines Corporation Data processing in a hybrid computing environment
WO2010026648A1 (en) * 2008-09-05 2010-03-11 富士通株式会社 Mac address controlling method
US8230442B2 (en) 2008-09-05 2012-07-24 International Business Machines Corporation Executing an accelerator application program in a hybrid computing environment
US8225019B2 (en) * 2008-09-22 2012-07-17 Micron Technology, Inc. SATA mass storage device emulation on a PCIe interface
CN102165427A (en) * 2008-09-25 2011-08-24 Lsi公司 Method and/or apparatus for certifying an out of band management application in an external storage array
US20100083247A1 (en) * 2008-09-26 2010-04-01 Netapp, Inc. System And Method Of Providing Multiple Virtual Machines With Shared Access To Non-Volatile Solid-State Memory Using RDMA
CN101685381B (en) * 2008-09-26 2013-07-24 美光科技公司 Data streaming of solid-state large-capacity storage device
US8074039B2 (en) * 2008-09-29 2011-12-06 Intel Corporation Redundant array of independent disks-related operations
US9213612B2 (en) * 2008-09-29 2015-12-15 Cisco Technology, Inc. Method and system for a storage area network
JP5183403B2 (en) * 2008-09-30 2013-04-17 株式会社日立製作所 Storage system, control program, and storage system control method
TWI380642B (en) * 2008-10-01 2012-12-21 Network bridging apparatus for storage device and data stream transmitting method thereof
US7934124B2 (en) * 2008-10-10 2011-04-26 Oracle America, Inc. Self-contained densely packed solid-state storage subsystem
EP2340491B1 (en) * 2008-10-24 2019-11-27 Hewlett-Packard Development Company, L.P. Direct-attached/network-attached storage device
US7904749B2 (en) * 2008-10-24 2011-03-08 Hitachi, Ltd. Fast data recovery from HDD failure
US8176247B2 (en) * 2008-10-28 2012-05-08 Pivot3 Method and system for protecting against multiple failures in a RAID system
US9189427B2 (en) * 2008-10-29 2015-11-17 Bruce Backa System and method for policy-based data archiving triggered by user activity
TWI385672B (en) * 2008-11-05 2013-02-11 Lite On It Corp Adaptive multi-channel controller and method for storage device
EP3361371A1 (en) * 2008-11-07 2018-08-15 Dell International L.L.C. Thin import for a data storage system
US9170897B2 (en) 2012-05-29 2015-10-27 SanDisk Technologies, Inc. Apparatus, system, and method for managing solid-state storage reliability
KR20110086725A (en) * 2008-11-10 2011-07-29 퓨전-아이오, 인크. Apparatus, system, and method for predicting failures in solid-state storage
US9063874B2 (en) 2008-11-10 2015-06-23 SanDisk Technologies, Inc. Apparatus, system, and method for wear management
US8275933B2 (en) * 2008-11-10 2012-09-25 Fusion-10, Inc Apparatus, system, and method for managing physical regions in a solid-state storage device
TW201021494A (en) * 2008-11-20 2010-06-01 Inventec Corp Remote data access device and remote data access method
US8065422B2 (en) * 2008-11-26 2011-11-22 Netapp, Inc. Method and/or apparatus for certifying an in-band management application of an external storage array
US8316201B2 (en) * 2008-12-18 2012-11-20 Sandisk Il Ltd. Methods for executing a command to write data from a source location to a destination location in a memory device
US20100161932A1 (en) * 2008-12-18 2010-06-24 Ori Moshe Stern Methods for writing data from a source location to a destination location in a memory device
US8694750B2 (en) * 2008-12-19 2014-04-08 Nvidia Corporation Method and system for data structure management
US8732350B2 (en) * 2008-12-19 2014-05-20 Nvidia Corporation Method and system for improving direct memory access offload
US9208108B2 (en) * 2008-12-19 2015-12-08 Nvidia Corporation Method and system for improved flash controller commands selection
US7925925B2 (en) 2008-12-30 2011-04-12 Intel Corporation Delta checkpoints for a non-volatile memory indirection table
US8438455B2 (en) * 2008-12-31 2013-05-07 Intel Corporation Error correction in a solid state disk
US20100180182A1 (en) * 2009-01-09 2010-07-15 Seagate Technology Llc Data memory device and controller with interface error detection and handling logic
KR101627321B1 (en) * 2009-01-13 2016-06-03 삼성전자주식회사 I/O request handling method and solid state drive using this
TWI397821B (en) * 2009-01-19 2013-06-01 Phison Electronics Corp Method, system and controller thereof for transmitting data stream
US8527734B2 (en) 2009-01-23 2013-09-03 International Business Machines Corporation Administering registered virtual addresses in a hybrid computing environment including maintaining a watch list of currently registered virtual addresses by an operating system
US9286232B2 (en) * 2009-01-26 2016-03-15 International Business Machines Corporation Administering registered virtual addresses in a hybrid computing environment including maintaining a cache of ranges of currently registered virtual addresses
US8347050B2 (en) * 2009-01-27 2013-01-01 Microsoft Corporation Append-based shared persistent storage
US8843880B2 (en) * 2009-01-27 2014-09-23 International Business Machines Corporation Software development for a hybrid computing environment
US8255909B2 (en) 2009-01-28 2012-08-28 International Business Machines Corporation Synchronizing access to resources in a hybrid computing environment
US8001206B2 (en) 2009-01-29 2011-08-16 International Business Machines Corporation Broadcasting data in a hybrid computing environment
US20100191923A1 (en) * 2009-01-29 2010-07-29 International Business Machines Corporation Data Processing In A Computing Environment
US9170864B2 (en) * 2009-01-29 2015-10-27 International Business Machines Corporation Data processing in a hybrid computing environment
JP5271424B2 (en) * 2009-01-29 2013-08-21 エルエスアイ コーポレーション An allocate-on-write snapshot mechanism for providing online data placement to volumes with dynamic storage tiering
US8543756B2 (en) * 2009-02-02 2013-09-24 Marvell World Trade Ltd. Solid-state drive command grouping
US8010718B2 (en) * 2009-02-03 2011-08-30 International Business Machines Corporation Direct memory access in a hybrid computing environment
KR20100091379A (en) * 2009-02-10 2010-08-19 삼성전자주식회사 Solid state disk device and program fail processing method thereof
US9152585B2 (en) * 2009-02-12 2015-10-06 Rambus Inc. Memory interface with reduced read-write turnaround delay
US20100211546A1 (en) * 2009-02-13 2010-08-19 Lennox Manufacturing Inc. System and method to backup data about devices in a network
US8386724B2 (en) 2009-02-19 2013-02-26 Micron Technology, Inc. Methods and apparatus for designating or using data status indicators
KR101563647B1 (en) * 2009-02-24 2015-10-28 삼성전자주식회사 Memory system and data processing method thereof
CN101504670A (en) * 2009-03-04 2009-08-12 成都市华为赛门铁克科技有限公司 Data operation method, system, client terminal and data server
JP4719802B2 (en) * 2009-03-09 2011-07-06 富士通株式会社 Storage management device, storage management method and storage system
TWI406130B (en) * 2009-03-10 2013-08-21 Phison Electronics Corp Data processing system, controller, and method thereof for searching specific memory area
US20100241868A1 (en) * 2009-03-19 2010-09-23 Hani Nachef Method and apparatus for storing, managing, and securing personal information
US8725946B2 (en) * 2009-03-23 2014-05-13 Ocz Storage Solutions, Inc. Mass storage system and method of using hard disk, solid-state media, PCIe edge connector, and raid controller
US8074037B2 (en) * 2009-03-30 2011-12-06 Inventec Corporation Storage service device with dual controller and backup method thereof
US8782326B2 (en) * 2009-04-01 2014-07-15 Seiko Epson Corporation Memory device and system including a memory device electronically connectable to a host circuit
JP5663843B2 (en) * 2009-04-01 2015-02-04 セイコーエプソン株式会社 Storage device, substrate, liquid container, control method of nonvolatile data storage unit, system including host circuit and removable storage device
US8819385B2 (en) 2009-04-06 2014-08-26 Densbits Technologies Ltd. Device and method for managing a flash memory
US8458574B2 (en) 2009-04-06 2013-06-04 Densbits Technologies Ltd. Compact chien-search based decoding apparatus and method
US20100262979A1 (en) * 2009-04-08 2010-10-14 Google Inc. Circular command queues for communication between a host and a data storage device
US8806165B2 (en) 2009-04-10 2014-08-12 Kaminario Technologies Ltd. Mass-storage system utilizing auxiliary solid-state storage subsystem
US20100262755A1 (en) * 2009-04-10 2010-10-14 Honeywell International Inc. Memory systems for computing devices and systems
US8799572B2 (en) 2009-04-20 2014-08-05 Microsoft Corporation Sliding-window multi-class striping
US8560879B1 (en) * 2009-04-22 2013-10-15 Netapp Inc. Data recovery for failed memory device of memory device array
US8037217B2 (en) * 2009-04-23 2011-10-11 International Business Machines Corporation Direct memory access in a hybrid computing environment
US8165030B2 (en) * 2009-04-30 2012-04-24 Avaya Inc. System and method for monitoring a network communication at multiple network layers
US8072890B2 (en) * 2009-05-01 2011-12-06 Avaya Inc. System and method for testing a dynamic communication across a network
CN101882119B (en) * 2009-05-08 2014-05-14 上海炬力集成电路设计有限公司 NAND flash memory controller and data transmission method thereof
US8238254B2 (en) * 2009-05-14 2012-08-07 Avaya Inc. Detection and display of packet changes in a network
US8250282B2 (en) * 2009-05-14 2012-08-21 Micron Technology, Inc. PCM memories for storage bus interfaces
US8281227B2 (en) 2009-05-18 2012-10-02 Fusion-10, Inc. Apparatus, system, and method to increase data integrity in a redundant storage system
KR20100124087A (en) * 2009-05-18 2010-11-26 삼성전자주식회사 Memory controller, memory system including the same and method of operating the same
US8307258B2 (en) * 2009-05-18 2012-11-06 Fusion-10, Inc Apparatus, system, and method for reconfiguring an array to operate with less storage elements
US9377967B2 (en) 2009-05-27 2016-06-28 Dell Products L.P. Systems and methods for scalable storage management
US9123409B2 (en) * 2009-06-11 2015-09-01 Micron Technology, Inc. Memory device for a hierarchical memory architecture
WO2010144587A2 (en) 2009-06-12 2010-12-16 Violin Memory, Inc. Memory system having persistent garbage collection
US20110004742A1 (en) * 2009-07-06 2011-01-06 Eonsil, Inc. Variable-Cycle, Event-Driven Multi-Execution Flash Processor
KR101662824B1 (en) * 2009-07-08 2016-10-06 삼성전자주식회사 Solid state drive device and driving method thereof
US9218349B2 (en) 2009-07-27 2015-12-22 International Business Machines Corporation Method and system for transformation of logical data objects for storage
US8448016B2 (en) * 2009-07-31 2013-05-21 Cleversafe, Inc. Computing core application access utilizing dispersed storage
KR20110015217A (en) * 2009-08-07 2011-02-15 삼성전자주식회사 Memory system having improved signal integrity
US8180972B2 (en) 2009-08-07 2012-05-15 International Business Machines Corporation Reducing remote reads of memory in a hybrid computing environment by maintaining remote memory values locally
CN101996685B (en) * 2009-08-11 2013-12-04 中颖电子股份有限公司 Error control method of storage management data and error controller
WO2011021237A1 (en) * 2009-08-20 2011-02-24 Hitachi,Ltd. Storage subsystem and its data processing method
US9330767B1 (en) 2009-08-26 2016-05-03 Avago Technologies General Ip (Singapore) Pte. Ltd. Flash memory module and method for programming a page of flash memory cells
US8995197B1 (en) 2009-08-26 2015-03-31 Densbits Technologies Ltd. System and methods for dynamic erase and program control for flash memory device memories
US8484414B2 (en) * 2009-08-31 2013-07-09 Hitachi, Ltd. Storage system having plurality of flash packages
US8665601B1 (en) 2009-09-04 2014-03-04 Bitmicro Networks, Inc. Solid state drive with improved enclosure assembly
US8447908B2 (en) 2009-09-07 2013-05-21 Bitmicro Networks, Inc. Multilevel memory bus system for solid-state mass storage
US9223514B2 (en) 2009-09-09 2015-12-29 SanDisk Technologies, Inc. Erase suspend/resume for memory
US8429436B2 (en) 2009-09-09 2013-04-23 Fusion-Io, Inc. Apparatus, system, and method for power reduction in a storage device
FI126228B (en) * 2009-09-16 2016-08-31 Varaani Works Oy A method and a data storage server for data redundancy
US8599863B2 (en) 2009-10-30 2013-12-03 Calxeda, Inc. System and method for using a multi-protocol fabric module across a distributed server interconnect fabric
US20130107444A1 (en) 2011-10-28 2013-05-02 Calxeda, Inc. System and method for flexible storage and networking provisioning in large scalable processor installations
US9465771B2 (en) 2009-09-24 2016-10-11 Iii Holdings 2, Llc Server on a chip and node cards comprising one or more of same
US20110103391A1 (en) 2009-10-30 2011-05-05 Smooth-Stone, Inc. C/O Barry Evans System and method for high-performance, low-power data center interconnect fabric
US9077654B2 (en) 2009-10-30 2015-07-07 Iii Holdings 2, Llc System and method for data center security enhancements leveraging managed server SOCs
US9876735B2 (en) 2009-10-30 2018-01-23 Iii Holdings 2, Llc Performance and power optimized computer system architectures and methods leveraging power optimized tree fabric interconnect
US9054990B2 (en) 2009-10-30 2015-06-09 Iii Holdings 2, Llc System and method for data center security enhancements leveraging server SOCs or server fabrics
US9069929B2 (en) 2011-10-31 2015-06-30 Iii Holdings 2, Llc Arbitrating usage of serial port in node card of scalable and modular servers
US8526605B2 (en) * 2009-10-09 2013-09-03 Seagate Technology Llc Data encryption to provide data security and memory cell bit wear leveling
US8730729B2 (en) 2009-10-15 2014-05-20 Densbits Technologies Ltd. Systems and methods for averaging error rates in non-volatile devices and storage systems
JP5391993B2 (en) * 2009-10-19 2014-01-15 富士通株式会社 Disk array device
US8724387B2 (en) 2009-10-22 2014-05-13 Densbits Technologies Ltd. Method, system, and computer readable medium for reading and programming flash memory cells using multiple bias voltages
US10877695B2 (en) 2009-10-30 2020-12-29 Iii Holdings 2, Llc Memcached server functionality in a cluster of data processing nodes
US9648102B1 (en) 2012-12-27 2017-05-09 Iii Holdings 2, Llc Memcached server functionality in a cluster of data processing nodes
US11720290B2 (en) 2009-10-30 2023-08-08 Iii Holdings 2, Llc Memcached server functionality in a cluster of data processing nodes
US9680770B2 (en) * 2009-10-30 2017-06-13 Iii Holdings 2, Llc System and method for using a multi-protocol fabric module across a distributed server interconnect fabric
US9311269B2 (en) 2009-10-30 2016-04-12 Iii Holdings 2, Llc Network proxy for high-performance, low-power data center interconnect fabric
US9098376B2 (en) * 2009-10-30 2015-08-04 Cleversafe, Inc. Distributed storage network for modification of a data object
EP2323135A1 (en) * 2009-11-12 2011-05-18 SiTel Semiconductor B.V. Method and apparatus for emulating byte wise programmable functionality into sector wise erasable memory
US8352834B2 (en) * 2009-11-12 2013-01-08 Broadlogic Network Technologies Inc. High throughput interleaver / deinterleaver
US20110119462A1 (en) * 2009-11-19 2011-05-19 Ocz Technology Group, Inc. Method for restoring and maintaining solid-state drive performance
US8495471B2 (en) * 2009-11-30 2013-07-23 International Business Machines Corporation Solid-state storage system with parallel access of multiple flash/PCM devices
US8327069B2 (en) * 2009-12-08 2012-12-04 Hitachi, Ltd. Storage system and storage control apparatus provided with cache memory group including volatile memory and nonvolatile memory
US20110137861A1 (en) * 2009-12-09 2011-06-09 International Business Machines Corporation Methods for Achieving Efficient Coherent Access to Data in a Cluster of Data Processing Computing Nodes
US8375225B1 (en) * 2009-12-11 2013-02-12 Western Digital Technologies, Inc. Memory protection
US8433865B2 (en) * 2009-12-11 2013-04-30 Microsoft Corporation Consistency without ordering dependency
KR101670746B1 (en) * 2009-12-15 2016-11-09 엘지전자 주식회사 Method for allocating resouce for multicast and broadcast service data in wireless communication system and an appratus therefor
US8683293B2 (en) * 2009-12-16 2014-03-25 Nvidia Corporation Method and system for fast two bit error correction
US8250380B2 (en) * 2009-12-17 2012-08-21 Hitachi Global Storage Technologies Netherlands B.V. Implementing secure erase for solid state drives
TWI497293B (en) 2009-12-17 2015-08-21 Ibm Data management in solid state storage devices
GB2488462B (en) * 2009-12-17 2018-01-17 Ibm Data management in solid state storage systems
US9037777B2 (en) 2009-12-22 2015-05-19 Densbits Technologies Ltd. Device, system, and method for reducing program/read disturb in flash arrays
US8321501B2 (en) * 2009-12-23 2012-11-27 Intel Corporation Secure out-of-band storage control
US9369526B2 (en) * 2009-12-29 2016-06-14 International Business Machines Corporation Distributed storage time synchronization based on retrieval delay
US20110161553A1 (en) * 2009-12-30 2011-06-30 Nvidia Corporation Memory device wear-leveling techniques
US8443263B2 (en) 2009-12-30 2013-05-14 Sandisk Technologies Inc. Method and controller for performing a copy-back operation
US9594675B2 (en) * 2009-12-31 2017-03-14 Nvidia Corporation Virtualization of chip enables
US8327225B2 (en) 2010-01-04 2012-12-04 Micron Technology, Inc. Error correction in a stacked memory
US8868575B2 (en) * 2010-01-13 2014-10-21 International Business Machines Corporation Method and system for transformation of logical data objects for storage
TWI587139B (en) * 2010-01-20 2017-06-11 旺玖科技股份有限公司 Driving device and method of accessing data
US11301592B2 (en) * 2010-01-28 2022-04-12 Pure Storage, Inc. Distributed storage with data obfuscation and method for use therewith
US9417905B2 (en) * 2010-02-03 2016-08-16 International Business Machines Corporation Terminating an accelerator application program in a hybrid computing environment
US8447916B2 (en) * 2010-02-17 2013-05-21 Microsoft Corporation Interfaces that facilitate solid state storage configuration
US8843459B1 (en) * 2010-03-09 2014-09-23 Hitachi Data Systems Engineering UK Limited Multi-tiered filesystem
US8281182B2 (en) * 2010-03-12 2012-10-02 Cleversafe, Inc. Dispersed storage unit selection
US20110230711A1 (en) * 2010-03-16 2011-09-22 Kano Akihito Endoscopic Surgical Instrument
CN102208987A (en) * 2010-03-29 2011-10-05 鸿富锦精密工业（深圳）有限公司 Mainboard management controller network configuration system and method
CN102207910A (en) * 2010-03-29 2011-10-05 联想(北京)有限公司 Read-only memory, data safety protection system, data safety protection method and computer
US8578132B2 (en) * 2010-03-29 2013-11-05 International Business Machines Corporation Direct injection of data to be transferred in a hybrid computing environment
JP5447092B2 (en) * 2010-03-30 2014-03-19 富士通株式会社 Processing apparatus, data migration method, and data migration program
US8577986B2 (en) 2010-04-02 2013-11-05 Microsoft Corporation Mapping RDMA semantics to high speed storage
JP5521716B2 (en) * 2010-04-06 2014-06-18 富士通株式会社 Storage control program, storage control method, and storage control apparatus
US8745317B2 (en) 2010-04-07 2014-06-03 Densbits Technologies Ltd. System and method for storing information in a multi-level cell memory
US8407517B2 (en) 2010-04-08 2013-03-26 Hitachi, Ltd. Methods and apparatus for managing error codes for storage systems coupled with external storage systems
US8296508B1 (en) * 2010-04-27 2012-10-23 Micron Technology, Inc. Secure memory device erase
US9015443B2 (en) 2010-04-30 2015-04-21 International Business Machines Corporation Reducing remote reads of memory in a hybrid computing environment
US20110270945A1 (en) * 2010-04-30 2011-11-03 Hitachi, Ltd. Computer system and control method for the same
US9811662B2 (en) * 2010-05-03 2017-11-07 Panzura, Inc. Performing anti-virus checks for a distributed filesystem
US20110276746A1 (en) * 2010-05-05 2011-11-10 Arvind Pruthi Caching storage adapter architecture
US8634186B2 (en) * 2010-05-07 2014-01-21 Advanced Micro Devices, Inc. Non-volatile memory controller cable arrangement
CN102244591B (en) * 2010-05-10 2015-04-15 淮南东正电子科技有限公司 Client server and method for full process monitoring on function text of client server
WO2011143628A2 (en) 2010-05-13 2011-11-17 Fusion-Io, Inc. Apparatus, system, and method for conditional and atomic storage operations
US8495296B2 (en) 2010-05-18 2013-07-23 International Business Machines Corporation System and method for optimizing data remanence over hubrid disk clusters using various storage technologies
TWI469576B (en) * 2010-05-20 2015-01-11 Hon Hai Prec Ind Co Ltd Contacts client server and method for monitoring function test of the client server
JP5598089B2 (en) * 2010-05-28 2014-10-01 富士通株式会社 Program, information processing apparatus and information processing method
US20110296131A1 (en) * 2010-05-31 2011-12-01 Samsung Electronics Co., Ltd Nonvolatile memory system and the operation method thereof
JP4829365B1 (en) * 2010-05-31 2011-12-07 株式会社東芝 Data storage device and data writing method
US8904104B2 (en) * 2010-06-09 2014-12-02 Taejin Info Tech Co., Ltd. Hybrid storage system with mid-plane
US8892980B2 (en) 2010-06-15 2014-11-18 Fusion-Io, Inc. Apparatus, system, and method for providing error correction
US8719675B1 (en) * 2010-06-16 2014-05-06 Google Inc. Orthogonal coding for data storage, access, and maintenance
US8793440B2 (en) 2010-06-17 2014-07-29 Microsoft Corporation Error detection for files
CN101883181A (en) * 2010-06-18 2010-11-10 中兴通讯股份有限公司 Method and terminal for processing short message
US8522076B2 (en) * 2010-06-23 2013-08-27 International Business Machines Corporation Error detection and recovery in a shared pipeline
US8510639B2 (en) 2010-07-01 2013-08-13 Densbits Technologies Ltd. System and method for multi-dimensional encoding and decoding
KR20120002760A (en) * 2010-07-01 2012-01-09 삼성전자주식회사 Data recording method and data recoding device for improving operation reliability of nand flash memory
JP2012022422A (en) * 2010-07-13 2012-02-02 Panasonic Corp Semiconductor recording/reproducing device
US8281043B2 (en) 2010-07-14 2012-10-02 Intel Corporation Out-of-band access to storage devices through port-sharing hardware
US8782434B1 (en) 2010-07-15 2014-07-15 The Research Foundation For The State University Of New York System and method for validating program execution at run-time
US8484415B2 (en) * 2010-07-19 2013-07-09 Taejin Info Tech Co., Ltd. Hybrid storage system for a multi-level raid architecture
EP2598996B1 (en) * 2010-07-28 2019-07-10 SanDisk Technologies LLC Apparatus, system, and method for conditional and atomic storage operations
US8725934B2 (en) 2011-12-22 2014-05-13 Fusion-Io, Inc. Methods and appratuses for atomic storage operations
US8510519B2 (en) * 2010-08-02 2013-08-13 Taejin Info Tech Co., Ltd. Hybrid raid controller
US8713268B2 (en) 2010-08-05 2014-04-29 Ut-Battelle, Llc Coordinated garbage collection for raid array of solid state disks
US9146875B1 (en) * 2010-08-09 2015-09-29 Western Digital Technologies, Inc. Hybrid drive converting non-volatile semiconductor memory to read only based on life remaining
US9530436B1 (en) * 2010-08-12 2016-12-27 Western Digital Technologies, Inc. Methods and systems for providing data security in data storage devices
US8964464B2 (en) 2010-08-24 2015-02-24 Densbits Technologies Ltd. System and method for accelerated sampling
US8621271B2 (en) * 2010-08-26 2013-12-31 Cleversafe, Inc. Reprovisioning a memory device into a dispersed storage network memory
US8850114B2 (en) 2010-09-07 2014-09-30 Daniel L Rosenband Storage array controller for flash-based storage devices
US8412672B1 (en) 2010-09-08 2013-04-02 Netapp, Inc. High availability network storage system incorporating non-shared storage suitable for use with virtual storage servers
US8583867B1 (en) 2010-09-08 2013-11-12 Netapp, Inc. Non-disruptive data migration between processing systems that do not share storage
US8984216B2 (en) 2010-09-09 2015-03-17 Fusion-Io, Llc Apparatus, system, and method for managing lifetime of a storage device
US8589625B2 (en) * 2010-09-15 2013-11-19 Pure Storage, Inc. Scheduling of reconstructive I/O read operations in a storage environment
CN101957767A (en) * 2010-09-21 2011-01-26 深圳创维数字技术股份有限公司 System software updating method based on NAND flash storage device
US20120079583A1 (en) * 2010-09-23 2012-03-29 Microsoft Corporation Offload reads and writes
JP2012068936A (en) * 2010-09-24 2012-04-05 Toshiba Corp Memory system
US9251058B2 (en) * 2010-09-28 2016-02-02 SanDisk Technologies, Inc. Servicing non-block storage requests
US9244769B2 (en) 2010-09-28 2016-01-26 Pure Storage, Inc. Offset protection data in a RAID array
US8463991B2 (en) 2010-09-28 2013-06-11 Pure Storage Inc. Intra-device data protection in a raid array
US8688899B2 (en) * 2010-09-28 2014-04-01 Fusion-Io, Inc. Apparatus, system, and method for an interface between a memory controller and a non-volatile memory controller using a command protocol
US8775868B2 (en) 2010-09-28 2014-07-08 Pure Storage, Inc. Adaptive RAID for an SSD environment
US9263102B2 (en) * 2010-09-28 2016-02-16 SanDisk Technologies, Inc. Apparatus, system, and method for data transformations within a data storage device
US9229808B2 (en) 2010-10-01 2016-01-05 Pure Storage, Inc. Reconstruct reads in a raid array with dynamic geometries
US9348696B2 (en) 2010-10-01 2016-05-24 Pure Storage, Inc. Distributed multi-level protection in a raid array based storage system
US8755221B2 (en) * 2010-10-18 2014-06-17 Avalanche Technology, Inc. Emulation of static random access memory (SRAM) by magnetic random access memory (MRAM)
US8892809B2 (en) * 2010-10-25 2014-11-18 Marvell World Trade Ltd. Data compression and encoding in a memory system
US8938574B2 (en) * 2010-10-26 2015-01-20 Lsi Corporation Methods and systems using solid-state drives as storage controller cache memory
US8990494B2 (en) 2010-11-01 2015-03-24 Taejin Info Tech Co., Ltd. Home storage system and method with various controllers
US8447925B2 (en) 2010-11-01 2013-05-21 Taejin Info Tech Co., Ltd. Home storage device and software including management and monitoring modules
US9063878B2 (en) 2010-11-03 2015-06-23 Densbits Technologies Ltd. Method, system and computer readable medium for copy back
US9092149B2 (en) 2010-11-03 2015-07-28 Microsoft Technology Licensing, Llc Virtualization and offload reads and writes
US9465728B2 (en) 2010-11-03 2016-10-11 Nvidia Corporation Memory controller adaptable to multiple memory devices
CN102467440A (en) * 2010-11-09 2012-05-23 鸿富锦精密工业（深圳）有限公司 Internal memory error detection system and method
TWI474329B (en) * 2010-11-15 2015-02-21 Silicon Motion Inc Method for enhancing error correction capability, and associated memory device and controller thereof
US8601197B2 (en) * 2010-11-15 2013-12-03 Atmel Rousset S.A.S. Microcontroller including flexible connections between modules
TW201222273A (en) * 2010-11-29 2012-06-01 Inventec Corp Computer system and method for managing computer device
WO2012099937A2 (en) 2011-01-18 2012-07-26 Lsi Corporation Higher-level redundancy information computation
CN103348330B (en) * 2010-12-01 2017-05-24 希捷科技有限公司 dynamic higher-level redundancy mode management with independent silicon elements
TW201224288A (en) * 2010-12-01 2012-06-16 Hon Hai Prec Ind Co Ltd System and method for controlling a fan
US8850100B2 (en) 2010-12-07 2014-09-30 Densbits Technologies Ltd. Interleaving codeword portions between multiple planes and/or dies of a flash memory device
JP2012123499A (en) * 2010-12-07 2012-06-28 Toshiba Corp Memory system
US9021472B2 (en) * 2010-12-10 2015-04-28 Lenovo Enterprise Solutions (Singapore) Pte. Ltd. Virtualizing baseboard management controller operation
US9208071B2 (en) 2010-12-13 2015-12-08 SanDisk Technologies, Inc. Apparatus, system, and method for accessing memory
US10817421B2 (en) 2010-12-13 2020-10-27 Sandisk Technologies Llc Persistent data structures
US9047178B2 (en) 2010-12-13 2015-06-02 SanDisk Technologies, Inc. Auto-commit memory synchronization
US8527693B2 (en) 2010-12-13 2013-09-03 Fusion IO, Inc. Apparatus, system, and method for auto-commit memory
US10817502B2 (en) 2010-12-13 2020-10-27 Sandisk Technologies Llc Persistent memory management
US9218278B2 (en) 2010-12-13 2015-12-22 SanDisk Technologies, Inc. Auto-commit memory
US9280477B2 (en) * 2010-12-13 2016-03-08 Seagate Technology Llc Data storage management in a memory device
JP5296041B2 (en) * 2010-12-15 2013-09-25 株式会社東芝 Memory system and memory system control method
US8560792B2 (en) 2010-12-16 2013-10-15 International Business Machines Corporation Synchronous extent migration protocol for paired storage
US8412816B2 (en) 2010-12-17 2013-04-02 Dell Products L.P. Native bi-directional communication for hardware management
CN103354939B (en) * 2010-12-17 2016-03-16 艾沃思宾技术公司 Staggered Memory Controller and method is accessed for making DRAM and MRAM
WO2012083308A2 (en) 2010-12-17 2012-06-21 Fusion-Io, Inc. Apparatus, system, and method for persistent data management on a non-volatile storage media
US8438247B1 (en) * 2010-12-21 2013-05-07 Amazon Technologies, Inc. Techniques for capturing data sets
AU2015202148B2 (en) * 2010-12-21 2016-05-05 Amazon Technologies, Inc. Techniques for capturing data sets
US9213594B2 (en) 2011-01-19 2015-12-15 Intelligent Intellectual Property Holdings 2 Llc Apparatus, system, and method for managing out-of-service conditions
US8972650B2 (en) * 2011-01-28 2015-03-03 Apple Inc. Methods and systems for performing efficient page reads in a non-volatile memory
US20120198126A1 (en) * 2011-01-28 2012-08-02 Apple Inc. Methods and systems for performing selective block switching to perform read operations in a non-volatile memory
US8595415B2 (en) * 2011-02-02 2013-11-26 Micron Technology, Inc. At least semi-autonomous modules in a memory system and methods
US8639971B1 (en) * 2011-02-17 2014-01-28 Scale Computing Condition detection and reporting in complex systems
CN102110154B (en) * 2011-02-21 2012-12-26 中国科学院计算技术研究所 File redundancy storage method in cluster file system
KR20120096212A (en) * 2011-02-22 2012-08-30 삼성전자주식회사 Non-volatile memory device, memory controller, and methods thereof
US8705544B2 (en) * 2011-03-07 2014-04-22 Broadcom Corporation Method and apparatus for routing in a single tier switched network
US9146765B2 (en) 2011-03-11 2015-09-29 Microsoft Technology Licensing, Llc Virtual disk storage techniques
JP5581256B2 (en) * 2011-03-28 2014-08-27 株式会社東芝 Memory system, controller, and control method of memory system
US8601085B1 (en) * 2011-03-28 2013-12-03 Emc Corporation Techniques for preferred path determination
US8924500B2 (en) * 2011-03-29 2014-12-30 Amazon Technologies, Inc. Local storage linked to networked storage system
US9047955B2 (en) 2011-03-30 2015-06-02 Stec, Inc. Adjusting operating parameters for memory cells based on wordline address and cycle information
US8677031B2 (en) * 2011-03-31 2014-03-18 Intel Corporation Facilitating, at least in part, by circuitry, accessing of at least one controller command interface
US9252985B2 (en) * 2011-04-04 2016-02-02 Taejin Info Tech Co., Ltd Impedance matching between FPGA and memory modules
US8990665B1 (en) 2011-04-06 2015-03-24 Densbits Technologies Ltd. System, method and computer program product for joint search of a read threshold and soft decoding
US10838886B2 (en) * 2011-04-19 2020-11-17 Micron Technology, Inc. Channel depth adjustment in memory systems
TWI467365B (en) * 2011-04-20 2015-01-01 Taejin Infotech Co Ltd Raid controlled semiconductor storage device, method for providing the same, and pci-express type raid controlled semiconductor storage device
US8527699B2 (en) 2011-04-25 2013-09-03 Pivot3, Inc. Method and system for distributed RAID implementation
US20120278527A1 (en) * 2011-04-26 2012-11-01 Byungcheol Cho System architecture based on hybrid raid storage
US20120278550A1 (en) * 2011-04-26 2012-11-01 Byungcheol Cho System architecture based on raid controller collaboration
US9176670B2 (en) * 2011-04-26 2015-11-03 Taejin Info Tech Co., Ltd. System architecture based on asymmetric raid storage
US8862804B2 (en) 2011-04-29 2014-10-14 Western Digital Technologies, Inc. System and method for improved parity determination within a data redundancy scheme in a solid state memory
US8909888B2 (en) * 2011-04-29 2014-12-09 Seagate Technology Llc Secure erasure of data from a non-volatile memory
US8832402B2 (en) * 2011-04-29 2014-09-09 Seagate Technology Llc Self-initiated secure erasure responsive to an unauthorized power down event
US8996790B1 (en) * 2011-05-12 2015-03-31 Densbits Technologies Ltd. System and method for flash memory management
US9110785B1 (en) 2011-05-12 2015-08-18 Densbits Technologies Ltd. Ordered merge of data sectors that belong to memory space portions
US9372792B1 (en) 2011-05-12 2016-06-21 Avago Technologies General Ip (Singapore) Pte. Ltd. Advanced management of a non-volatile memory
US9195592B1 (en) 2011-05-12 2015-11-24 Densbits Technologies Ltd. Advanced management of a non-volatile memory
US9396106B2 (en) 2011-05-12 2016-07-19 Avago Technologies General Ip (Singapore) Pte. Ltd. Advanced management of a non-volatile memory
US9501392B1 (en) 2011-05-12 2016-11-22 Avago Technologies General Ip (Singapore) Pte. Ltd. Management of a non-volatile memory module
US8543758B2 (en) * 2011-05-31 2013-09-24 Micron Technology, Inc. Apparatus including memory channel control circuit and related methods for relaying commands to logical units
KR101835604B1 (en) 2011-06-03 2018-03-07 삼성전자 주식회사 Scheduler for memory
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
US9329939B2 (en) * 2011-06-08 2016-05-03 Taejin Info Tech Co., Ltd Two-way raid controller for a semiconductor storage device
US9183165B2 (en) * 2011-06-10 2015-11-10 International Business Machines Corporation Firmware management of storage class memory for connected or disconnected I/O adapters
US8819302B2 (en) 2011-06-13 2014-08-26 Lsi Corporation System to manage input/output performance and/or deadlock in network attached storage gateway connected to a storage area network environment
US20120324143A1 (en) 2011-06-15 2012-12-20 Data Design Corporation Methods and apparatus for data access by a reprogrammable circuit module
US9417894B1 (en) 2011-06-15 2016-08-16 Ryft Systems, Inc. Methods and apparatus for a tablet computer system incorporating a reprogrammable circuit module
US8924630B2 (en) * 2011-06-21 2014-12-30 Taejin Info Tech Co., Ltd. Semiconductor storage device-based high-speed cache storage system
US8819316B2 (en) * 2011-06-21 2014-08-26 Taejin Info Tech Co., Ltd. Two-way raid controller with programmable host interface for a semiconductor storage device
US8904106B2 (en) 2011-06-22 2014-12-02 International Business Machines Corporation Parallel block allocation for declustered logical disks
US10966339B1 (en) * 2011-06-28 2021-03-30 Amazon Technologies, Inc. Storage system with removable solid state storage devices mounted on carrier circuit boards
CN102855146B (en) * 2011-06-30 2016-05-11 鸿富锦精密工业（深圳）有限公司 Firmware update system and method
US9207879B2 (en) * 2011-07-06 2015-12-08 Taejin Info Tech Co., Ltd. Redundant array of independent disk (RAID) controlled semiconductor storage device (SSD)-based system having a high-speed non-volatile host interface
US8949305B1 (en) 2011-07-15 2015-02-03 Scale Computing, Inc. Distributed dynamic system configuration
US9104651B1 (en) 2011-07-15 2015-08-11 Scale Computing, Inc. Techniques for distributing tests and test suites across a network
US8874994B2 (en) 2011-07-22 2014-10-28 Sandisk Technologies Inc. Systems and methods of storing data
US8671249B2 (en) 2011-07-22 2014-03-11 Fusion-Io, Inc. Apparatus, system, and method for managing storage capacity recovery
US12099752B2 (en) 2011-07-27 2024-09-24 Pure Storage, Inc. Error prediction based on correlation using event records
US9170868B2 (en) * 2011-07-27 2015-10-27 Cleversafe, Inc. Identifying an error cause within a dispersed storage network
US10678619B2 (en) 2011-07-27 2020-06-09 Pure Storage, Inc. Unified logs and device statistics
US11016702B2 (en) 2011-07-27 2021-05-25 Pure Storage, Inc. Hierarchical event tree
US20130036263A1 (en) * 2011-08-01 2013-02-07 Shu-Min Liu Solid state storage device using volatile memory
US9063841B1 (en) * 2011-08-01 2015-06-23 Marvell Israel (M.L.S.L.) Ltd. External memory management in a network device
US8776094B2 (en) 2011-08-11 2014-07-08 Microsoft Corporation Runtime system
KR20130021633A (en) * 2011-08-23 2013-03-06 삼성전자주식회사 Method and apparatus for veiling and detecting data using error correcting code
US8931107B1 (en) 2011-08-30 2015-01-06 Amazon Technologies, Inc. Techniques for generating block level data captures
US8656251B2 (en) * 2011-09-02 2014-02-18 Apple Inc. Simultaneous data transfer and error control to reduce latency and improve throughput to a host
US8713357B1 (en) 2011-09-06 2014-04-29 Western Digital Technologies, Inc. Systems and methods for detailed error reporting in data storage systems
US8700834B2 (en) * 2011-09-06 2014-04-15 Western Digital Technologies, Inc. Systems and methods for an enhanced controller architecture in data storage systems
US9195530B1 (en) * 2011-09-06 2015-11-24 Western Digital Technologies, Inc. Systems and methods for improved data management in data storage systems
US8707104B1 (en) 2011-09-06 2014-04-22 Western Digital Technologies, Inc. Systems and methods for error injection in data storage systems
US20130067289A1 (en) * 2011-09-14 2013-03-14 Ariel Maislos Efficient non-volatile read cache for storage system
US9269063B2 (en) 2011-09-23 2016-02-23 Elwha Llc Acquiring and transmitting event related tasks and subtasks to interface devices
US20130081022A1 (en) * 2011-09-23 2013-03-28 Elwha LLC, a limited liability company of the State of Delaware Configuring interface devices with respect to tasks and subtasks
US9619357B2 (en) * 2011-09-28 2017-04-11 International Business Machines Corporation Hybrid storage devices
EP2761465B1 (en) * 2011-09-30 2022-02-09 Intel Corporation Autonomous initialization of non-volatile random access memory in a computer system
CN107608910B (en) 2011-09-30 2021-07-02 英特尔公司 Apparatus and method for implementing a multi-level memory hierarchy with different operating modes
EP2761469B1 (en) 2011-09-30 2019-11-13 Intel Corporation Non-volatile random access memory (nvram) as a replacement for traditional mass storage
CN104115136B (en) 2011-09-30 2017-12-08 英特尔公司 BIOS device, method and system are stored in nonvolatile random access memory
WO2013048493A1 (en) * 2011-09-30 2013-04-04 Intel Corporation Memory channel that supports near memory and far memory access
JP5869135B2 (en) 2011-09-30 2016-02-24 インテル コーポレイション Direct I / O access for coprocessors
US9274864B2 (en) * 2011-10-04 2016-03-01 International Business Machines Corporation Accessing large amounts of data in a dispersed storage network
US9372755B1 (en) 2011-10-05 2016-06-21 Bitmicro Networks, Inc. Adaptive power cycle sequences for data recovery
CN102447732A (en) * 2011-10-11 2012-05-09 浪潮电子信息产业股份有限公司 Method for intelligent configuration of host computer embedded environment during BMC (Baseboard Management Controller) development
US9813491B2 (en) 2011-10-20 2017-11-07 Oracle International Corporation Highly available network filer with automatic load balancing and performance adjustment
US9263106B2 (en) * 2011-10-21 2016-02-16 Nvidia Corporation Efficient command mapping scheme for short data burst length memory devices
US9047068B2 (en) * 2011-10-31 2015-06-02 Dell Products L.P. Information handling system storage device management information access
US8694855B1 (en) 2011-11-02 2014-04-08 Pmc-Sierra Us, Inc. Error correction code technique for improving read stress endurance
US9058289B2 (en) 2011-11-07 2015-06-16 Sandisk Enterprise Ip Llc Soft information generation for memory systems
US8966172B2 (en) 2011-11-15 2015-02-24 Pavilion Data Systems, Inc. Processor agnostic data storage in a PCIE based shared storage enviroment
TW201321943A (en) * 2011-11-17 2013-06-01 Hon Hai Prec Ind Co Ltd Fan control system and method
US9015411B2 (en) 2011-12-02 2015-04-21 Compellent Technologies System and method for unbalanced raid management
US20130238900A1 (en) 2011-12-12 2013-09-12 Cleversafe, Inc. Dispersed storage network secure hierarchical file directory
US8898542B2 (en) * 2011-12-12 2014-11-25 Cleversafe, Inc. Executing partial tasks in a distributed storage and task network
US10671585B2 (en) * 2012-01-31 2020-06-02 Pure Storage, Inc. Storing indexed data to a dispersed storage network
US9430286B2 (en) 2011-12-12 2016-08-30 International Business Machines Corporation Authorizing distributed task processing in a distributed storage network
US10176045B2 (en) 2011-12-12 2019-01-08 International Business Machines Corporation Internet based shared memory in a distributed computing system
US8959416B1 (en) * 2011-12-16 2015-02-17 Western Digital Technologies, Inc. Memory defect management using signature identification
US8694849B1 (en) * 2011-12-19 2014-04-08 Pmc-Sierra Us, Inc. Shuffler error correction code system and method
US8806111B2 (en) 2011-12-20 2014-08-12 Fusion-Io, Inc. Apparatus, system, and method for backing data of a non-volatile storage device using a backing store
CN103176759A (en) * 2011-12-20 2013-06-26 鸿富锦精密工业（深圳）有限公司 BIOS POST code display system and BIOS POST code display method
US10133662B2 (en) 2012-06-29 2018-11-20 Sandisk Technologies Llc Systems, methods, and interfaces for managing persistent data of atomic storage operations
WO2013098463A1 (en) * 2011-12-29 2013-07-04 Nokia Corporation Method for erasing data entity in memory module
US9189172B1 (en) 2012-01-06 2015-11-17 Seagate Technology Llc High priority read and write
KR101888074B1 (en) * 2012-01-09 2018-08-13 삼성전자주식회사 Storage device and nonvolatile memory device and operation method thererof
US9817582B2 (en) 2012-01-09 2017-11-14 Microsoft Technology Licensing, Llc Offload read and write offload provider
WO2013112634A1 (en) * 2012-01-23 2013-08-01 The Regents Of The University Of California System and method for implementing transactions using storage device support for atomic updates and flexible interface for managing data logging
US8775714B2 (en) * 2012-01-30 2014-07-08 Infineon Technologies Ag System and method for a bus interface
US9652182B2 (en) 2012-01-31 2017-05-16 Pavilion Data Systems, Inc. Shareable virtual non-volatile storage device for a server
US20130205065A1 (en) * 2012-02-02 2013-08-08 Lsi Corporation Methods and structure for an improved solid-state drive for use in caching applications
KR101445025B1 (en) 2012-02-09 2014-09-26 서울시립대학교 산학협력단 Efficient raid scheme for reliable ssd
US8947941B2 (en) 2012-02-09 2015-02-03 Densbits Technologies Ltd. State responsive operations relating to flash memory cells
WO2013119074A1 (en) * 2012-02-09 2013-08-15 Noh Sam Hyuk Efficient raid technique for reliable ssd
US8996788B2 (en) 2012-02-09 2015-03-31 Densbits Technologies Ltd. Configurable flash interface
US8949512B2 (en) * 2012-02-17 2015-02-03 Apple Inc. Trim token journaling
US9195586B2 (en) * 2012-02-23 2015-11-24 Hgst Technologies Santa Ana, Inc. Determining bias information for offsetting operating variations in memory cells based on wordline address
US10019353B2 (en) 2012-03-02 2018-07-10 Longitude Enterprise Flash S.A.R.L. Systems and methods for referencing data on a storage medium
JP5659178B2 (en) * 2012-03-16 2015-01-28 株式会社東芝 NONVOLATILE MEMORY DEVICE AND NONVOLATILE MEMORY CONTROL METHOD
US20130242425A1 (en) 2012-03-16 2013-09-19 Toshiba America Electronics Components, Inc. Write reordering in a hybrid disk drive
CN103365667B (en) * 2012-03-26 2018-01-26 联想企业方案（新加坡）有限公司 A kind of method and apparatus of the installation operation system in host computer system
US9053008B1 (en) 2012-03-26 2015-06-09 Western Digital Technologies, Inc. Systems and methods for providing inline parameter service in data storage devices
US9135192B2 (en) 2012-03-30 2015-09-15 Sandisk Technologies Inc. Memory system with command queue reordering
US9268692B1 (en) * 2012-04-05 2016-02-23 Seagate Technology Llc User selectable caching
US9542324B1 (en) * 2012-04-05 2017-01-10 Seagate Technology Llc File associated pinning
WO2013152312A1 (en) * 2012-04-06 2013-10-10 Interdigital Patent Holdings, Inc. Optimization of peer-to-peer content delivery service
KR101969883B1 (en) * 2012-04-13 2019-04-17 에스케이하이닉스 주식회사 Data storage device and operating method thereof
CN102681794B (en) * 2012-04-23 2014-12-10 浪潮(北京)电子信息产业有限公司 Method and system for realizing redundant array protection of a disk based on double controllers
CN103377161A (en) * 2012-04-24 2013-10-30 鸿富锦精密工业（深圳）有限公司 Main board and data processing method applied to same
US8996793B1 (en) 2012-04-24 2015-03-31 Densbits Technologies Ltd. System, method and computer readable medium for generating soft information
US9218462B2 (en) * 2012-04-25 2015-12-22 Hewlett Packard Enterprise Development Lp Authentication using lights-out management credentials
US8839073B2 (en) * 2012-05-04 2014-09-16 Lsi Corporation Zero-one balance management in a solid-state disk controller
US8751710B2 (en) 2012-05-08 2014-06-10 Entegra Technologies, Inc. Reconfigurable modular computing device
KR101961324B1 (en) * 2012-05-09 2019-03-22 삼성전자주식회사 Memory device and power managing method of the same
US8838937B1 (en) 2012-05-23 2014-09-16 Densbits Technologies Ltd. Methods, systems and computer readable medium for writing and reading data
US9077665B1 (en) 2012-05-24 2015-07-07 Scale Computing, Inc. Transferring virtual machines and resource localization in a distributed fault-tolerant system
CN102710763B (en) * 2012-05-29 2015-11-25 新华网股份有限公司 The method and system of a kind of distributed caching pond, burst and Failure Transfer
US9749413B2 (en) 2012-05-29 2017-08-29 Intel Corporation Peer-to-peer interrupt signaling between devices coupled via interconnects
US8879325B1 (en) 2012-05-30 2014-11-04 Densbits Technologies Ltd. System, method and computer program product for processing read threshold information and for reading a flash memory module
US8984201B2 (en) 2012-06-01 2015-03-17 International Business Machines Corporation Providing I2C bus over Ethernet
KR102133316B1 (en) * 2012-06-07 2020-07-21 바이올린 메모리 인코포레이티드 Memory system management
US9229901B1 (en) 2012-06-08 2016-01-05 Google Inc. Single-sided distributed storage system
US9172744B2 (en) * 2012-06-14 2015-10-27 Microsoft Technology Licensing, Llc Scalable storage with programmable networks
US20130339583A1 (en) * 2012-06-19 2013-12-19 Marvell World Trade Ltd. Systems and methods for transferring data out of order in next generation solid state drive controllers
US9003162B2 (en) 2012-06-20 2015-04-07 Microsoft Technology Licensing, Llc Structuring storage based on latch-free B-trees
US8924832B1 (en) * 2012-06-26 2014-12-30 Western Digital Technologies, Inc. Efficient error handling mechanisms in data storage systems
US20140006537A1 (en) * 2012-06-28 2014-01-02 Wiliam H. TSO High speed record and playback system
US9098302B2 (en) * 2012-06-28 2015-08-04 Intel Corporation System and apparatus to improve boot speed in serial peripheral interface system using a baseboard management controller
JP6039699B2 (en) * 2012-07-23 2016-12-07 株式会社日立製作所 Storage system and data management method
JP2014026388A (en) * 2012-07-25 2014-02-06 Toshiba Corp Storage device, controller, and write control method
US9712373B1 (en) * 2012-07-30 2017-07-18 Rambus Inc. System and method for memory access in server communications
US8856431B2 (en) 2012-08-02 2014-10-07 Lsi Corporation Mixed granularity higher-level redundancy for non-volatile memory
US20140052897A1 (en) * 2012-08-17 2014-02-20 Seagate Technology Llc Dynamic formation of garbage collection units in a memory
US9699263B1 (en) 2012-08-17 2017-07-04 Sandisk Technologies Llc. Automatic read and write acceleration of data accessed by virtual machines
CN103629132B (en) * 2012-08-20 2016-09-14 国网浙江桐庐县供电公司 Fan shared control system and method
US10430216B1 (en) 2012-08-23 2019-10-01 Scale Computing Inc Virtual machine automated selection
US10019287B1 (en) 2012-08-23 2018-07-10 Scale Computing Virtual machine resource display
US9921954B1 (en) 2012-08-27 2018-03-20 Avago Technologies General Ip (Singapore) Pte. Ltd. Method and system for split flash memory management between host and storage controller
US9094163B2 (en) * 2012-08-28 2015-07-28 Aoptix Technologies, Inc. Assessment and correction of transmitted data
US8676851B1 (en) 2012-08-30 2014-03-18 Google Inc. Executing transactions in distributed storage systems
US8862561B1 (en) 2012-08-30 2014-10-14 Google Inc. Detecting read/write conflicts
US9058122B1 (en) 2012-08-30 2015-06-16 Google Inc. Controlling access in a single-sided distributed storage system
US10346095B2 (en) 2012-08-31 2019-07-09 Sandisk Technologies, Llc Systems, methods, and interfaces for adaptive cache persistence
US9164702B1 (en) 2012-09-07 2015-10-20 Google Inc. Single-sided distributed cache system
US9899066B2 (en) * 2012-09-10 2018-02-20 Texas Instruments Incorporated Priority based backup in nonvolatile logic arrays
US9122873B2 (en) 2012-09-14 2015-09-01 The Research Foundation For The State University Of New York Continuous run-time validation of program execution: a practical approach
JP2014063497A (en) * 2012-09-21 2014-04-10 Plx Technology Inc Pci express switch with logical device capability
US9304828B2 (en) * 2012-09-27 2016-04-05 Hitachi, Ltd. Hierarchy memory management
TWI502600B (en) * 2012-09-28 2015-10-01 Leadconn Technology Co Ltd Device for fixing identifier of memory
US9069782B2 (en) 2012-10-01 2015-06-30 The Research Foundation For The State University Of New York System and method for security and privacy aware virtual machine checkpointing
US9652216B2 (en) * 2012-10-04 2017-05-16 Dell Products L.P. System and method for providing out-of-band software or firmware upgrades for a switching device
KR102081980B1 (en) * 2012-10-08 2020-02-27 삼성전자 주식회사 Method for performing write operation or read operation in memory system
US20140114928A1 (en) * 2012-10-22 2014-04-24 Robert Beers Coherence protocol tables
DE112013005093T5 (en) * 2012-10-22 2015-10-22 Intel Corporation Hochleistungszusammenschaltungsbitübertragungsschicht
US8972826B2 (en) 2012-10-24 2015-03-03 Western Digital Technologies, Inc. Adaptive error correction codes for data storage systems
CA2890041C (en) * 2012-11-02 2016-12-20 Vod2 Inc. Data distribution methods and systems
WO2014081414A1 (en) * 2012-11-20 2014-05-30 Empire Technology Development Llc Multi-element solid-state storage device management
US9368225B1 (en) 2012-11-21 2016-06-14 Avago Technologies General Ip (Singapore) Pte. Ltd. Determining read thresholds based upon read error direction statistics
US9098401B2 (en) 2012-11-21 2015-08-04 Apple Inc. Fast secure erasure schemes for non-volatile memory
KR101988287B1 (en) 2012-11-26 2019-06-12 삼성전자주식회사 Storage device and computing system havint its and data transfering method thereof
US9021339B2 (en) 2012-11-29 2015-04-28 Western Digital Technologies, Inc. Data reliability schemes for data storage systems
US9059736B2 (en) 2012-12-03 2015-06-16 Western Digital Technologies, Inc. Methods, solid state drive controllers and data storage devices having a runtime variable raid protection scheme
US9448883B1 (en) * 2012-12-04 2016-09-20 Cadence Design Systems, Inc. System and method for allocating data in memory array having regions of varying storage reliability
US9071585B2 (en) 2012-12-12 2015-06-30 Microsoft Technology Licensing, Llc Copy offload for disparate offload providers
EP2880520A1 (en) 2012-12-13 2015-06-10 Hitachi, Ltd. Computer realizing high-speed access and data protection of storage device, computer system, and i/o request processing method
US9251201B2 (en) 2012-12-14 2016-02-02 Microsoft Technology Licensing, Llc Compatibly extending offload token size
WO2014098839A1 (en) * 2012-12-19 2014-06-26 Hewlett-Packard Development Company Nvram path selection
US9639457B1 (en) * 2012-12-20 2017-05-02 Datadirect Networks, Inc. Data storage system and method for data migration between high-performance computing architectures and data storage devices using storage controller with distributed XOR capability
US9214963B1 (en) 2012-12-21 2015-12-15 Western Digital Technologies, Inc. Method and system for monitoring data channel to enable use of dynamically adjustable LDPC coding parameters in a data storage system
US9049265B1 (en) 2012-12-26 2015-06-02 Google Inc. Serving remote access to storage resources
US9501398B2 (en) 2012-12-26 2016-11-22 Sandisk Technologies Llc Persistent storage device with NVRAM for staging writes
US9703697B2 (en) 2012-12-27 2017-07-11 Intel Corporation Sharing serial peripheral interface flash memory in a multi-node server system on chip platform environment
US9612948B2 (en) 2012-12-27 2017-04-04 Sandisk Technologies Llc Reads and writes between a contiguous data block and noncontiguous sets of logical address blocks in a persistent storage device
US9239751B1 (en) 2012-12-27 2016-01-19 Sandisk Enterprise Ip Llc Compressing data from multiple reads for error control management in memory systems
US9848029B2 (en) 2012-12-28 2017-12-19 Opentv, Inc. Highly-scalable data transmission
US9454420B1 (en) 2012-12-31 2016-09-27 Sandisk Technologies Llc Method and system of reading threshold voltage equalization
US9069659B1 (en) 2013-01-03 2015-06-30 Densbits Technologies Ltd. Read threshold determination using reference read threshold
US8880838B2 (en) 2013-01-08 2014-11-04 Lyve Minds, Inc. Storage network data allocation
JP5985403B2 (en) * 2013-01-10 2016-09-06 株式会社東芝 Storage device
US8995302B1 (en) 2013-01-16 2015-03-31 Pmc-Sierra Us, Inc. Method and apparatus for translated routing in an interconnect switch
US9224452B2 (en) * 2013-01-17 2015-12-29 Qualcomm Incorporated Heterogeneous memory systems, and related methods and computer-readable media for supporting heterogeneous memory access requests in processor-based systems
JP2014137721A (en) * 2013-01-17 2014-07-28 Toshiba Corp Storage control device, data storage device and storage control method
US9143279B2 (en) * 2013-01-18 2015-09-22 Qualcomm Incorporated Methods and devices for facilitating data retransmissions in wireless communication systems
US9542101B2 (en) * 2013-01-22 2017-01-10 Avago Technologies General Ip (Singapore) Pte. Ltd. System and methods for performing embedded full-stripe write operations to a data volume with data elements distributed across multiple modules
US9195585B2 (en) * 2013-01-23 2015-11-24 Vmware, Inc. Techniques for allocating and surfacing host-side storage capacity to virtual machines
US11249652B1 (en) 2013-01-28 2022-02-15 Radian Memory Systems, Inc. Maintenance of nonvolatile memory on host selected namespaces by a common memory controller
US9652376B2 (en) * 2013-01-28 2017-05-16 Radian Memory Systems, Inc. Cooperative flash memory control
US9128858B1 (en) 2013-01-29 2015-09-08 Pmc-Sierra Us, Inc. Apparatus and method for adjusting a correctable raw bit error rate limit in a memory system using strong log-likelihood (LLR) values
US9092353B1 (en) 2013-01-29 2015-07-28 Pmc-Sierra Us, Inc. Apparatus and method based on LDPC codes for adjusting a correctable raw bit error rate limit in a memory system
US9256384B2 (en) 2013-02-04 2016-02-09 Avago Technologies General Ip (Singapore) Pte. Ltd. Method and system for reducing write latency in a data storage system by using a command-push model
US9930066B2 (en) 2013-02-12 2018-03-27 Nicira, Inc. Infrastructure level LAN security
US20140229695A1 (en) * 2013-02-13 2014-08-14 Dell Products L.P. Systems and methods for backup in scale-out storage clusters
US8990661B1 (en) 2013-03-05 2015-03-24 Pmc-Sierra Us, Inc. Layer specific attenuation factor LDPC decoder
US9813080B1 (en) 2013-03-05 2017-11-07 Microsemi Solutions (U.S.), Inc. Layer specific LDPC decoder
US10230396B1 (en) 2013-03-05 2019-03-12 Microsemi Solutions (Us), Inc. Method and apparatus for layer-specific LDPC decoding
US11966355B2 (en) * 2013-03-10 2024-04-23 Mellanox Technologies, Ltd. Network adapter with a common queue for both networking and data manipulation work requests
US10275375B2 (en) 2013-03-10 2019-04-30 Mellanox Technologies, Ltd. Network interface controller with compression capabilities
US9397701B1 (en) 2013-03-11 2016-07-19 Microsemi Storage Solutions (Us), Inc. System and method for lifetime specific LDPC decoding
US8935598B1 (en) 2013-03-12 2015-01-13 Pmc-Sierra Us, Inc. System and method for adaptive check node approximation in LDPC decoding
US9727453B2 (en) * 2013-03-14 2017-08-08 Sandisk Technologies Llc Multi-level table deltas
US8984376B1 (en) 2013-03-14 2015-03-17 Pmc-Sierra Us, Inc. System and method for avoiding error mechanisms in layered iterative decoding
US10817312B2 (en) * 2013-03-14 2020-10-27 Microsoft Technology Licensing, Llc Programming model for performant computing in document-oriented storage services
US9478271B2 (en) * 2013-03-14 2016-10-25 Seagate Technology Llc Nonvolatile memory data recovery after power failure
US9870830B1 (en) 2013-03-14 2018-01-16 Sandisk Technologies Llc Optimal multilevel sensing for reading data from a storage medium
US8984365B1 (en) 2013-03-14 2015-03-17 Pmc-Sierra Us, Inc. System and method for reduced memory storage in LDPC decoding
US8954657B1 (en) * 2013-09-27 2015-02-10 Avalanche Technology, Inc. Storage processor managing solid state disk array
US9448738B2 (en) * 2013-03-15 2016-09-20 Western Digital Technologies, Inc. Compression and formatting of data for data storage systems
US9858084B2 (en) 2013-03-15 2018-01-02 Bitmicro Networks, Inc. Copying of power-on reset sequencer descriptor from nonvolatile memory to random access memory
US9367246B2 (en) 2013-03-15 2016-06-14 Sandisk Technologies Inc. Performance optimization of data transfer for soft information generation
US9934045B1 (en) 2013-03-15 2018-04-03 Bitmicro Networks, Inc. Embedded system boot from a storage device
US9235467B2 (en) 2013-03-15 2016-01-12 Pmc-Sierra Us, Inc. System and method with reference voltage partitioning for low density parity check decoding
US10489318B1 (en) 2013-03-15 2019-11-26 Bitmicro Networks, Inc. Scatter-gather approach for parallel data transfer in a mass storage system
US9236886B1 (en) 2013-03-15 2016-01-12 Sandisk Enterprise Ip Llc Universal and reconfigurable QC-LDPC encoder
US9842053B2 (en) * 2013-03-15 2017-12-12 Sandisk Technologies Llc Systems and methods for persistent cache logging
US9798688B1 (en) 2013-03-15 2017-10-24 Bitmicro Networks, Inc. Bus arbitration with routing and failover mechanism
US8983967B2 (en) * 2013-03-15 2015-03-17 Datadirect Networks, Inc. Data storage system having mutable objects incorporating time
US9612900B2 (en) * 2013-03-15 2017-04-04 SEAKR Engineering, Inc. Centralized configuration control of reconfigurable computing devices
US9244763B1 (en) 2013-03-15 2016-01-26 Sandisk Enterprise Ip Llc System and method for updating a reading threshold voltage based on symbol transition information
US9454414B2 (en) 2013-03-15 2016-09-27 Microsemi Storage Solutions (Us), Inc. System and method for accumulating soft information in LDPC decoding
US9136877B1 (en) 2013-03-15 2015-09-15 Sandisk Enterprise Ip Llc Syndrome layered decoding for LDPC codes
US9450610B1 (en) 2013-03-15 2016-09-20 Microsemi Storage Solutions (Us), Inc. High quality log likelihood ratios determined using two-index look-up table
US9430386B2 (en) 2013-03-15 2016-08-30 Bitmicro Networks, Inc. Multi-leveled cache management in a hybrid storage system
US9501436B1 (en) 2013-03-15 2016-11-22 Bitmicro Networks, Inc. Multi-level message passing descriptor
US9590656B2 (en) 2013-03-15 2017-03-07 Microsemi Storage Solutions (Us), Inc. System and method for higher quality log likelihood ratios in LDPC decoding
US9092350B1 (en) 2013-03-15 2015-07-28 Sandisk Enterprise Ip Llc Detection and handling of unbalanced errors in interleaved codewords
US9335950B2 (en) * 2013-03-15 2016-05-10 Western Digital Technologies, Inc. Multiple stream compression and formatting of data for data storage systems
US9672178B1 (en) 2013-03-15 2017-06-06 Bitmicro Networks, Inc. Bit-mapped DMA transfer with dependency table configured to monitor status so that a processor is not rendered as a bottleneck in a system
US9990382B1 (en) * 2013-04-10 2018-06-05 Amazon Technologies, Inc. Secure erasure and repair of non-mechanical storage media
US9552176B2 (en) * 2013-04-12 2017-01-24 Microsoft Technology Licensing, Llc Block storage using a hybrid memory device
TWI489296B (en) * 2013-05-17 2015-06-21 Wistron Corp Computer
US10127166B2 (en) * 2013-05-21 2018-11-13 Sandisk Technologies Llc Data storage controller with multiple pipelines
US9336166B1 (en) * 2013-05-30 2016-05-10 Emc Corporation Burst buffer appliance with operating system bypass functionality to facilitate remote direct memory access
JP2014235531A (en) * 2013-05-31 2014-12-15 株式会社東芝 Data transfer device, data transfer system, and program
US9009375B2 (en) 2013-06-11 2015-04-14 Lsi Corporation Sharing of bypassed I/O transaction information
US9058267B2 (en) 2013-06-11 2015-06-16 Avago Technologies General IP Singapore) Pte Ltd I/O path selection
US9159437B2 (en) 2013-06-11 2015-10-13 Sandisk Enterprise IP LLC. Device and method for resolving an LM flag issue
US9697358B2 (en) * 2013-06-13 2017-07-04 Google Inc. Non-volatile memory operations
US9136876B1 (en) 2013-06-13 2015-09-15 Densbits Technologies Ltd. Size limited multi-dimensional decoding
CN104238638A (en) * 2013-06-17 2014-12-24 中兴通讯股份有限公司 Miniaturized calculate storage combination system
CN103336671B (en) * 2013-06-17 2016-07-13 北京奇虎科技有限公司 The method and apparatus obtaining data from network
US9519591B2 (en) 2013-06-22 2016-12-13 Microsoft Technology Licensing, Llc Latch-free, log-structured storage for multiple access methods
US9785356B2 (en) 2013-06-26 2017-10-10 Cnex Labs, Inc. NVM express controller for remote access of memory and I/O over ethernet-type networks
US10063638B2 (en) 2013-06-26 2018-08-28 Cnex Labs, Inc. NVM express controller for remote access of memory and I/O over ethernet-type networks
US9785355B2 (en) 2013-06-26 2017-10-10 Cnex Labs, Inc. NVM express controller for remote access of memory and I/O over ethernet-type networks
US9430412B2 (en) 2013-06-26 2016-08-30 Cnex Labs, Inc. NVM express controller for remote access of memory and I/O over Ethernet-type networks
US9122712B1 (en) * 2013-06-28 2015-09-01 Emc Corporation Compressing container files
US9311110B2 (en) * 2013-07-08 2016-04-12 Intel Corporation Techniques to initialize from a remotely accessible storage device
US9030883B2 (en) * 2013-07-16 2015-05-12 Freescale Semiconductor, Inc. Adaptive erase recovery for non-volatile memory (NVM) systems
US8949486B1 (en) 2013-07-17 2015-02-03 Mellanox Technologies Ltd. Direct memory access to storage devices
US9336313B1 (en) 2013-07-24 2016-05-10 NXGN Data, Inc. Systems and methods for performing single and multi threaded searches and complex pattern matching in a solid state drive
US9021189B2 (en) * 2013-07-24 2015-04-28 NXGN Data, Inc. System and method for performing efficient processing of data stored in a storage node
US9092321B2 (en) 2013-07-24 2015-07-28 NXGN Data, Inc. System and method for performing efficient searches and queries in a storage node
US9336135B1 (en) 2013-07-24 2016-05-10 NXGN Data, Inc. Systems and methods for performing search and complex pattern matching in a solid state drive
US9524235B1 (en) 2013-07-25 2016-12-20 Sandisk Technologies Llc Local hash value generation in non-volatile data storage systems
US9384126B1 (en) 2013-07-25 2016-07-05 Sandisk Technologies Inc. Methods and systems to avoid false negative results in bloom filters implemented in non-volatile data storage systems
WO2015016883A1 (en) * 2013-07-31 2015-02-05 Hewlett-Packard Development Company, L.P. Off-memory-module ecc-supplemental memory system
US9448896B2 (en) 2013-08-07 2016-09-20 Seagate Technology Llc Torn write mitigation
KR102081588B1 (en) 2013-08-08 2020-02-26 삼성전자 주식회사 the method of ECC decoder operation and the memory controller including it
US9639463B1 (en) 2013-08-26 2017-05-02 Sandisk Technologies Llc Heuristic aware garbage collection scheme in storage systems
US9361221B1 (en) 2013-08-26 2016-06-07 Sandisk Technologies Inc. Write amplification reduction through reliable writes during garbage collection
GB201315435D0 (en) 2013-08-30 2013-10-16 Ibm Cache management in a computerized system
US9684686B1 (en) * 2013-09-04 2017-06-20 Amazon Technologies, Inc. Database system recovery using non-volatile system memory
WO2015032666A1 (en) * 2013-09-04 2015-03-12 Zentrum Mikroelektronik Dresden Ag Fpga power management system
US9298534B2 (en) * 2013-09-05 2016-03-29 Kabushiki Kaisha Toshiba Memory system and constructing method of logical block
US9313274B2 (en) * 2013-09-05 2016-04-12 Google Inc. Isolating clients of distributed storage systems
US20150082063A1 (en) * 2013-09-18 2015-03-19 Lenovo (Singapore) Pte. Ltd. Baseboard management controller state transitions
CN103488435B (en) * 2013-09-24 2017-08-04 华为技术有限公司 RAID sub-system and its data read-write method
WO2015047240A1 (en) * 2013-09-25 2015-04-02 Hewlett Packard Development Company, L.P. Baseboard management controller providing peer system identification
US9658799B2 (en) 2013-09-25 2017-05-23 International Business Machines Corporation Data storage device deferred secure delete
US9413491B1 (en) 2013-10-08 2016-08-09 Avago Technologies General Ip (Singapore) Pte. Ltd. System and method for multiple dimension decoding and encoding a message
US9786388B1 (en) 2013-10-09 2017-10-10 Avago Technologies General Ip (Singapore) Pte. Ltd. Detecting and managing bad columns
US9397706B1 (en) 2013-10-09 2016-07-19 Avago Technologies General Ip (Singapore) Pte. Ltd. System and method for irregular multiple dimension decoding and encoding
US9348694B1 (en) 2013-10-09 2016-05-24 Avago Technologies General Ip (Singapore) Pte. Ltd. Detecting and managing bad columns
US10019352B2 (en) 2013-10-18 2018-07-10 Sandisk Technologies Llc Systems and methods for adaptive reserve storage
US9298608B2 (en) 2013-10-18 2016-03-29 Sandisk Enterprise Ip Llc Biasing for wear leveling in storage systems
US9442662B2 (en) 2013-10-18 2016-09-13 Sandisk Technologies Llc Device and method for managing die groups
US9690515B2 (en) * 2013-10-25 2017-06-27 Sandisk Technologies Llc Delayed automation to maximize the utilization of read and write cache
CN103530417B (en) * 2013-10-29 2016-08-17 北京视博数字电视科技有限公司 file unpacking method and device
US9436831B2 (en) 2013-10-30 2016-09-06 Sandisk Technologies Llc Secure erase in a memory device
US9263156B2 (en) 2013-11-07 2016-02-16 Sandisk Enterprise Ip Llc System and method for adjusting trip points within a storage device
TWI510910B (en) * 2013-11-11 2015-12-01 Wistron Corp Computer system and remote control method thereof
US9244785B2 (en) 2013-11-13 2016-01-26 Sandisk Enterprise Ip Llc Simulated power failure and data hardening
US9703816B2 (en) 2013-11-19 2017-07-11 Sandisk Technologies Llc Method and system for forward reference logging in a persistent datastore
US9520197B2 (en) 2013-11-22 2016-12-13 Sandisk Technologies Llc Adaptive erase of a storage device
US9218891B2 (en) * 2013-11-27 2015-12-22 Silicon Motion, Inc. Data storage device and flash memory control method
US9520162B2 (en) 2013-11-27 2016-12-13 Sandisk Technologies Llc DIMM device controller supervisor
US9582058B2 (en) 2013-11-29 2017-02-28 Sandisk Technologies Llc Power inrush management of storage devices
US9235245B2 (en) 2013-12-04 2016-01-12 Sandisk Enterprise Ip Llc Startup performance and power isolation
US9129665B2 (en) 2013-12-17 2015-09-08 Sandisk Enterprise Ip Llc Dynamic brownout adjustment in a storage device
US9998359B2 (en) 2013-12-18 2018-06-12 Mellanox Technologies, Ltd. Simultaneous operation of remote management and link aggregation
CN103858479A (en) * 2013-12-20 2014-06-11 华为技术有限公司 Data transmitting method and device
US9678678B2 (en) 2013-12-20 2017-06-13 Lyve Minds, Inc. Storage network data retrieval
US9684568B2 (en) 2013-12-26 2017-06-20 Silicon Motion, Inc. Data storage device and flash memory control method
TWI524183B (en) * 2014-01-09 2016-03-01 群聯電子股份有限公司 Data writing method, memory control circuit unit and memory storage apparatus
US20150205534A1 (en) * 2014-01-17 2015-07-23 Kabushiki Kaisha Toshiba Controller, solid-state drive and control method
US9536612B1 (en) 2014-01-23 2017-01-03 Avago Technologies General Ip (Singapore) Pte. Ltd Digital signaling processing for three dimensional flash memory arrays
US10148746B2 (en) 2014-01-28 2018-12-04 Mellanox Technologies, Ltd. Multi-host network interface controller with host management
US9946616B2 (en) * 2014-01-29 2018-04-17 Hitachi, Ltd. Storage apparatus
US10120792B1 (en) 2014-01-29 2018-11-06 Avago Technologies General Ip (Singapore) Pte. Ltd. Programming an embedded flash storage device
US9798620B2 (en) 2014-02-06 2017-10-24 Sandisk Technologies Llc Systems and methods for non-blocking solid-state memory
US10521387B2 (en) * 2014-02-07 2019-12-31 Toshiba Memory Corporation NAND switch
US9286208B2 (en) * 2014-02-07 2016-03-15 Kabushiki Kaisha Toshiba Controller controlling an interleave operation, solid-state drive including the controller, and control method controlling an interleave operation
US9933980B2 (en) 2014-02-24 2018-04-03 Toshiba Memory Corporation NAND raid controller for connection between an SSD controller and multiple non-volatile storage units
KR102188062B1 (en) * 2014-02-28 2020-12-07 삼성전자 주식회사 Method for operating data storage device and method for operating system having the device
US9703636B2 (en) 2014-03-01 2017-07-11 Sandisk Technologies Llc Firmware reversion trigger and control
US9666244B2 (en) * 2014-03-01 2017-05-30 Fusion-Io, Inc. Dividing a storage procedure
US10031933B2 (en) * 2014-03-02 2018-07-24 Netapp, Inc. Peer to peer ownership negotiation
US9958178B2 (en) * 2014-03-06 2018-05-01 Dell Products, Lp System and method for providing a server rack management controller
US20150254082A1 (en) * 2014-03-10 2015-09-10 Plx Technology, Inc. Remote booting over pci express using synthetic remote boot capability
US9639285B2 (en) * 2014-03-13 2017-05-02 Aupera Technologies, Inc. Distributed raid in a flash based memory system
US10296371B2 (en) 2014-03-17 2019-05-21 International Business Machines Corporation Passive two-phase commit system for high-performance distributed transaction execution
US9696942B2 (en) 2014-03-17 2017-07-04 Mellanox Technologies, Ltd. Accessing remote storage devices using a local bus protocol
US9727503B2 (en) 2014-03-17 2017-08-08 Mellanox Technologies, Ltd. Storage system and server
US9448876B2 (en) 2014-03-19 2016-09-20 Sandisk Technologies Llc Fault detection and prediction in storage devices
US9390814B2 (en) 2014-03-19 2016-07-12 Sandisk Technologies Llc Fault detection and prediction for data storage elements
US9454448B2 (en) 2014-03-19 2016-09-27 Sandisk Technologies Llc Fault testing in storage devices
US9626400B2 (en) 2014-03-31 2017-04-18 Sandisk Technologies Llc Compaction of information in tiered data structure
US9390021B2 (en) 2014-03-31 2016-07-12 Sandisk Technologies Llc Efficient cache utilization in a tiered data structure
US9626399B2 (en) 2014-03-31 2017-04-18 Sandisk Technologies Llc Conditional updates for reducing frequency of data modification operations
US9697267B2 (en) 2014-04-03 2017-07-04 Sandisk Technologies Llc Methods and systems for performing efficient snapshots in tiered data structures
US9781027B1 (en) * 2014-04-06 2017-10-03 Parallel Machines Ltd. Systems and methods to communicate with external destinations via a memory network
US10078604B1 (en) 2014-04-17 2018-09-18 Bitmicro Networks, Inc. Interrupt coalescing
US10055150B1 (en) 2014-04-17 2018-08-21 Bitmicro Networks, Inc. Writing volatile scattered memory metadata to flash device
US10042792B1 (en) 2014-04-17 2018-08-07 Bitmicro Networks, Inc. Method for transferring and receiving frames across PCI express bus for SSD device
US10025736B1 (en) 2014-04-17 2018-07-17 Bitmicro Networks, Inc. Exchange message protocol message transmission between two devices
US9952991B1 (en) 2014-04-17 2018-04-24 Bitmicro Networks, Inc. Systematic method on queuing of descriptors for multiple flash intelligent DMA engine operation
US9911477B1 (en) * 2014-04-18 2018-03-06 Altera Corporation Memory controller architecture with improved memory scheduling efficiency
KR102318478B1 (en) 2014-04-21 2021-10-27 삼성전자주식회사 Storage controller, storage system and method of operation of the storage controller
US9354872B2 (en) * 2014-04-24 2016-05-31 Xitore, Inc. Apparatus, system, and method for non-volatile data storage and retrieval
US10048962B2 (en) 2014-04-24 2018-08-14 Xitore, Inc. Apparatus, system, and method for non-volatile data storage and retrieval
JP6213366B2 (en) * 2014-04-25 2017-10-18 富士通株式会社 Arithmetic processing apparatus and control method thereof
JP5936152B2 (en) 2014-05-17 2016-06-15 インターナショナル・ビジネス・マシーンズ・コーポレーションＩｎｔｅｒｎａｔｉｏｎａｌ Ｂｕｓｉｎｅｓｓ Ｍａｃｈｉｎｅｓ Ｃｏｒｐｏｒａｔｉｏｎ Memory access trace method
US9891993B2 (en) 2014-05-23 2018-02-13 International Business Machines Corporation Managing raid parity stripe contention
US9280293B2 (en) * 2014-05-23 2016-03-08 Lenovo Enterprise Solutions (Singapore) Pte. Ltd. RAID 1 mirror meshed into a co-existing RAID 5 parity stream
CN104020962B (en) * 2014-05-27 2018-03-13 华为技术有限公司 A kind of method, cpu system and the storage device of the write-in of the data of RAID 1
US9542262B1 (en) 2014-05-29 2017-01-10 Avago Technologies General Ip (Singapore) Pte. Ltd. Error correction
US9093160B1 (en) 2014-05-30 2015-07-28 Sandisk Technologies Inc. Methods and systems for staggered memory operations
US10146448B2 (en) 2014-05-30 2018-12-04 Sandisk Technologies Llc Using history of I/O sequences to trigger cached read ahead in a non-volatile storage device
US10656842B2 (en) 2014-05-30 2020-05-19 Sandisk Technologies Llc Using history of I/O sizes and I/O sequences to trigger coalesced writes in a non-volatile storage device
US9070481B1 (en) 2014-05-30 2015-06-30 Sandisk Technologies Inc. Internal current measurement for age measurements
US10372613B2 (en) 2014-05-30 2019-08-06 Sandisk Technologies Llc Using sub-region I/O history to cache repeatedly accessed sub-regions in a non-volatile storage device
US10162748B2 (en) 2014-05-30 2018-12-25 Sandisk Technologies Llc Prioritizing garbage collection and block allocation based on I/O history for logical address regions
US10656840B2 (en) 2014-05-30 2020-05-19 Sandisk Technologies Llc Real-time I/O pattern recognition to enhance performance and endurance of a storage device
US10114557B2 (en) 2014-05-30 2018-10-30 Sandisk Technologies Llc Identification of hot regions to enhance performance and endurance of a non-volatile storage device
US9703491B2 (en) 2014-05-30 2017-07-11 Sandisk Technologies Llc Using history of unaligned writes to cache data and avoid read-modify-writes in a non-volatile storage device
GB2526873A (en) * 2014-06-06 2015-12-09 Roke Manor Research System and method for mitigating remanence in volatile memory
US9594571B2 (en) 2014-06-10 2017-03-14 Cisco Technology, Inc. Mechanism for obviating the need for host-side basic input/output system (BIOS) or boot serial peripheral interface (SPI) device(s)
WO2015191048A1 (en) * 2014-06-10 2015-12-17 Hewlett-Packard Development Company, L.P. Replicating data using remote direct memory access (rdma)
US9652381B2 (en) 2014-06-19 2017-05-16 Sandisk Technologies Llc Sub-block garbage collection
US9892033B1 (en) 2014-06-24 2018-02-13 Avago Technologies General Ip (Singapore) Pte. Ltd. Management of memory units
US10747888B2 (en) * 2014-06-30 2020-08-18 Nicira, Inc. Method and apparatus for differently encrypting data messages for different logical networks
US9972393B1 (en) 2014-07-03 2018-05-15 Avago Technologies General Ip (Singapore) Pte. Ltd. Accelerating programming of a flash memory module
US9584159B1 (en) 2014-07-03 2017-02-28 Avago Technologies General Ip (Singapore) Pte. Ltd. Interleaved encoding
US9417804B2 (en) 2014-07-07 2016-08-16 Microsemi Storage Solutions (Us), Inc. System and method for memory block pool wear leveling
US9449702B1 (en) 2014-07-08 2016-09-20 Avago Technologies General Ip (Singapore) Pte. Ltd. Power management
US9588843B2 (en) 2014-07-14 2017-03-07 International Business Machines Corporation System and method for transferring traditional RAID to distributed array
US9514211B2 (en) 2014-07-20 2016-12-06 Microsoft Technology Licensing, Llc High throughput data modifications using blind update operations
TWI505078B (en) 2014-07-28 2015-10-21 Ibm System management controller, computer system and method of system management
US9442798B2 (en) * 2014-07-31 2016-09-13 Winbond Electronics Corporation NAND flash memory having an enhanced buffer read capability and method of operation thereof
WO2016018383A1 (en) 2014-07-31 2016-02-04 Hewlett-Packard Development Company Live migration of data
US9367392B2 (en) 2014-08-01 2016-06-14 Winbond Electronics Corporation NAND flash memory having internal ECC processing and method of operation thereof
WO2016032548A1 (en) * 2014-08-25 2016-03-03 Hewlett Packard Enterprise Development Lp Providing transactional support to a data storage system
FR3025333B1 (en) * 2014-08-26 2017-12-08 Bull Sas SERVER COMPRISING A PLURALITY OF MODULES
US10540109B2 (en) 2014-09-02 2020-01-21 Hewlett Packard Enterprise Development Lp Serializing access to fault tolerant memory
US9443601B2 (en) 2014-09-08 2016-09-13 Sandisk Technologies Llc Holdup capacitor energy harvesting
US9542118B1 (en) 2014-09-09 2017-01-10 Radian Memory Systems, Inc. Expositive flash memory control
US10552085B1 (en) 2014-09-09 2020-02-04 Radian Memory Systems, Inc. Techniques for directed data migration
KR102330391B1 (en) 2014-09-11 2021-11-24 삼성전자주식회사 Storage device, data storage system having the same, and garbage collection method thereof
US20160077959A1 (en) * 2014-09-12 2016-03-17 Qualcomm Incorporated System and Method for Sharing a Solid-State Non-Volatile Memory Resource
US10275171B2 (en) * 2014-09-16 2019-04-30 Kove Ip, Llc Paging of external memory
US10146468B2 (en) * 2014-09-20 2018-12-04 Netronome Systems, Inc. Addressless merge command with data item identifier
US9720789B2 (en) * 2014-10-15 2017-08-01 Netapp, Inc. Multicast transport configuration
US10666682B2 (en) * 2014-10-15 2020-05-26 Marvell Asia Pte, Ltd. Systems and methods for allowing flexible chip configuration by external entity while maintaining secured boot environment
US10635504B2 (en) 2014-10-16 2020-04-28 Microsoft Technology Licensing, Llc API versioning independent of product releases
US9984768B2 (en) 2014-10-20 2018-05-29 Sandisk Technologies Llc Distributing storage of ECC code words
US9959059B2 (en) * 2014-10-20 2018-05-01 Sandisk Technologies Llc Storage error management
WO2016064417A1 (en) 2014-10-24 2016-04-28 Hewlett Packard Enterprise Development Lp End-to-end negative acknowledgment
US9519442B2 (en) * 2014-10-27 2016-12-13 Aeroflex Colorado Springs Inc. Method for concurrent system management and error detection and correction requests in integrated circuits through location aware avoidance logic
CN104391805B (en) * 2014-10-27 2017-12-05 浪潮集团有限公司 A kind of data structure for being used to encrypt solid-state storage
US9712382B2 (en) 2014-10-27 2017-07-18 Quanta Computer Inc. Retrieving console messages after device failure
CN104281499B (en) * 2014-10-28 2017-10-13 苏州工业职业技术学院 RAID stripe mirror image data location mode based on even-odd check
US11157200B2 (en) * 2014-10-29 2021-10-26 Hewlett-Packard Development Company, L.P. Communicating over portions of a communication medium
US10210107B2 (en) 2014-10-29 2019-02-19 Hewlett Packard Enterprise Development Lp Trans-fabric instruction set for a communication fabric
US9712619B2 (en) 2014-11-04 2017-07-18 Pavilion Data Systems, Inc. Virtual non-volatile memory express drive
US9565269B2 (en) 2014-11-04 2017-02-07 Pavilion Data Systems, Inc. Non-volatile memory express over ethernet
US9524211B1 (en) 2014-11-18 2016-12-20 Avago Technologies General Ip (Singapore) Pte. Ltd. Codeword management
US20160162186A1 (en) * 2014-12-09 2016-06-09 San Disk Technologies Inc. Re-Ordering NAND Flash Commands for Optimal Throughput and Providing a Specified Quality-of-Service
US9582463B2 (en) 2014-12-09 2017-02-28 Intel Corporation Heterogeneous input/output (I/O) using remote direct memory access (RDMA) and active message
US9519429B2 (en) * 2014-12-09 2016-12-13 Intel Corporation Techniques to manage multiple sequential write streams to a solid state drive
KR102301937B1 (en) 2014-12-22 2021-09-15 삼성전자주식회사 Input and output method in virtual machine environment
US9846576B2 (en) * 2014-12-27 2017-12-19 Intel Corporation Technologies for reprogramming network interface cards over a network
US20160191508A1 (en) * 2014-12-31 2016-06-30 Nexenta Systems, Inc. Methods and Systems for Block Sharding of Objects Stored in Distributed Storage System
US10423670B1 (en) * 2015-01-05 2019-09-24 Amazon Technologies, Inc. Object coding in a host-side processing device
US9853873B2 (en) 2015-01-10 2017-12-26 Cisco Technology, Inc. Diagnosis and throughput measurement of fibre channel ports in a storage area network environment
US9542320B2 (en) * 2015-01-12 2017-01-10 Avago Technologies General Ip (Singapore) Pte. Ltd. Multi-node cache coherency with input output virtualization
US9933950B2 (en) 2015-01-16 2018-04-03 Sandisk Technologies Llc Storage operation interrupt
CN112214424B (en) 2015-01-20 2024-04-05 乌尔特拉塔有限责任公司 Object memory architecture, processing node, memory object storage and management method
US11782601B2 (en) 2015-01-20 2023-10-10 Ultrata, Llc Object memory instruction set
US9529580B2 (en) * 2015-01-21 2016-12-27 Ford Global Technologies, Llc Vehicle control update methods and systems
US10229085B2 (en) 2015-01-23 2019-03-12 Hewlett Packard Enterprise Development Lp Fibre channel hardware card port assignment and management method for port names
WO2016122610A1 (en) 2015-01-30 2016-08-04 Hewlett Packard Enterprise Development Lp Preventing data corruption and single point of failure in a fault-tolerant memory
WO2016122637A1 (en) 2015-01-30 2016-08-04 Hewlett Packard Enterprise Development Lp Non-idempotent primitives in fault-tolerant memory
WO2016122642A1 (en) 2015-01-30 2016-08-04 Hewlett Packard Enterprise Development Lp Determine failed components in fault-tolerant memory
US10305515B1 (en) 2015-02-02 2019-05-28 Avago Technologies International Sales Pte. Limited System and method for encoding using multiple linear feedback shift registers
US9729440B2 (en) 2015-02-22 2017-08-08 Mellanox Technologies, Ltd. Differentiating among multiple management control instances using IP addresses
US9985820B2 (en) 2015-02-22 2018-05-29 Mellanox Technologies, Ltd. Differentiating among multiple management control instances using addresses
WO2016135872A1 (en) * 2015-02-25 2016-09-01 株式会社日立製作所 Storage unit and storage device
WO2016137402A1 (en) * 2015-02-26 2016-09-01 Agency For Science, Technology And Research Data stripping, allocation and reconstruction
US10440115B2 (en) * 2015-02-27 2019-10-08 Pure Storage, Inc. Write intent messaging in a dispersed storage network
US11188665B2 (en) 2015-02-27 2021-11-30 Pure Storage, Inc. Using internal sensors to detect adverse interference and take defensive actions
US9728245B2 (en) * 2015-02-28 2017-08-08 Intel Corporation Precharging and refreshing banks in memory device with bank group architecture
KR102398213B1 (en) 2015-03-09 2022-05-17 삼성전자주식회사 Storage device, host system having the same and map table updating method thereof
US20160266813A1 (en) * 2015-03-09 2016-09-15 Unisys Corporation Storage subsystem technologies
US20160267050A1 (en) * 2015-03-09 2016-09-15 Unisys Corporation Storage subsystem technologies
US20160266802A1 (en) * 2015-03-10 2016-09-15 Kabushiki Kaisha Toshiba Storage device, memory system and method of managing data
US9600181B2 (en) 2015-03-11 2017-03-21 Microsoft Technology Licensing, Llc Live configurable storage
US9900250B2 (en) 2015-03-26 2018-02-20 Cisco Technology, Inc. Scalable handling of BGP route information in VXLAN with EVPN control plane
US9940234B2 (en) * 2015-03-26 2018-04-10 Pure Storage, Inc. Aggressive data deduplication using lazy garbage collection
US9830093B2 (en) * 2015-03-27 2017-11-28 Intel Corporation Method and apparatus for improving immunity to defects in a non-volatile memory
WO2016159996A1 (en) 2015-03-31 2016-10-06 Hewlett Packard Enterprise Development Lp Preventing data corruption and single point of failure in fault-tolerant memory fabrics
KR102309798B1 (en) * 2015-04-16 2021-10-06 삼성전자주식회사 SR-IOV based non volatile memory controller and method for dynamically allocating resources to queues by the non volatile memory controller
US9800547B2 (en) 2015-04-16 2017-10-24 International Business Machines Corporation Preventing network attacks on baseboard management controllers
US9979799B2 (en) * 2015-04-27 2018-05-22 Lenovo Enterprise Solutions (Singapore) Pte. Ltd. Impersonating a specific physical hardware configuration on a standard server
EP3230879B1 (en) 2015-05-02 2023-11-01 Hewlett Packard Enterprise Development LP Storage memory direct access
US10121013B2 (en) * 2015-05-07 2018-11-06 Samsung Electronics Co., Ltd. XOR-based scrambler/descrambler for SSD communication protocols
US9519433B2 (en) 2015-05-13 2016-12-13 VSector Security Technologies, LLC Secure virtual sector erasure method and system
US10222986B2 (en) 2015-05-15 2019-03-05 Cisco Technology, Inc. Tenant-level sharding of disks with tenant-specific storage modules to enable policies per tenant in a distributed storage system
US10332613B1 (en) 2015-05-18 2019-06-25 Microsemi Solutions (Us), Inc. Nonvolatile memory system with retention monitor
US10244250B2 (en) 2015-05-29 2019-03-26 Samsung Electronics Co., Ltd. Variable-rate texture compression using fixed-rate codes
US9760314B2 (en) 2015-05-29 2017-09-12 Netapp, Inc. Methods for sharing NVM SSD across a cluster group and devices thereof
US20160357456A1 (en) * 2015-06-03 2016-12-08 Kabushiki Kaisha Toshiba Memory device that divides write data into a plurality of data portions for data writing
US10698628B2 (en) 2015-06-09 2020-06-30 Ultrata, Llc Infinite memory fabric hardware implementation with memory
US9886210B2 (en) 2015-06-09 2018-02-06 Ultrata, Llc Infinite memory fabric hardware implementation with router
US9971542B2 (en) 2015-06-09 2018-05-15 Ultrata, Llc Infinite memory fabric streams and APIs
US11588783B2 (en) 2015-06-10 2023-02-21 Cisco Technology, Inc. Techniques for implementing IPV6-based distributed storage space
US10628255B1 (en) 2015-06-11 2020-04-21 Avago Technologies International Sales Pte. Limited Multi-dimensional decoding
TWI553477B (en) * 2015-06-12 2016-10-11 群聯電子股份有限公司 Memory management method, memory control circuit unit and memory storage device
US10048898B2 (en) * 2015-06-15 2018-08-14 Sandisk Technologies Llc Data retention in a memory block based on local heating
US10248610B2 (en) * 2015-06-23 2019-04-02 Mellanox Technologies, Ltd. Enforcing transaction order in peer-to-peer interactions
EP3268865B1 (en) * 2015-06-26 2021-08-04 Hewlett Packard Enterprise Development LP Self-tune controller
US9910791B1 (en) * 2015-06-30 2018-03-06 EMC IP Holding Company LLC Managing system-wide encryption keys for data storage systems
US9857986B2 (en) 2015-06-30 2018-01-02 International Business Machines Corporation Wear leveling of a memory array
CN105159851A (en) * 2015-07-02 2015-12-16 浪潮(北京)电子信息产业有限公司 Multi-controller storage system
US9851921B1 (en) 2015-07-05 2017-12-26 Avago Technologies General Ip (Singapore) Pte. Ltd. Flash memory chip processing
KR102036514B1 (en) * 2015-07-13 2019-10-28 엘에스산전 주식회사 Data access apparatus using memory device
US10089196B2 (en) * 2015-07-14 2018-10-02 Shannon Systems Ltd. Methods for reconfiguring a storage controller when control logic fails and apparatuses using the same
US10303647B2 (en) 2015-07-15 2019-05-28 Mellanox Technologies, Ltd. Access control in peer-to-peer transactions over a peripheral component bus
US10778765B2 (en) 2015-07-15 2020-09-15 Cisco Technology, Inc. Bid/ask protocol in scale-out NVMe storage
US9799405B1 (en) 2015-07-29 2017-10-24 Ip Gem Group, Llc Nonvolatile memory system with read circuit for performing reads using threshold voltage shift read instruction
US10579519B2 (en) 2015-07-30 2020-03-03 Hewlett Packard Enterprise Development Lp Interleaved access of memory
US10257273B2 (en) 2015-07-31 2019-04-09 Netapp, Inc. Systems, methods and devices for RDMA read/write operations
US9952797B2 (en) 2015-07-31 2018-04-24 Netapp, Inc. Systems, methods and devices for addressing data blocks in mass storage filing systems
US10078614B2 (en) 2015-08-10 2018-09-18 Sandisk Technologies Llc Systems and methods of data transfer
KR102401600B1 (en) * 2015-08-31 2022-05-25 삼성전자주식회사 Storage device configured to manage a plurality of data streams based on data amount
US9484954B1 (en) * 2015-09-10 2016-11-01 Intel Corporation Methods and apparatus to parallelize data decompression
US10736239B2 (en) 2015-09-22 2020-08-04 Z-Impact, Inc. High performance computing rack and storage system with forced cooling
US10078494B2 (en) * 2015-09-25 2018-09-18 Arizona Board Of Regents On Behalf Of Arizona State University Secure true random number generation using 1.5-T transistor flash memory
US10013323B1 (en) 2015-09-29 2018-07-03 EMC IP Holding Company LLC Providing resiliency to a raid group of storage devices
US10853266B2 (en) * 2015-09-30 2020-12-01 Pure Storage, Inc. Hardware assisted data lookup methods
US10459891B2 (en) * 2015-09-30 2019-10-29 Western Digital Technologies, Inc. Replicating data across data storage devices of a logical volume
EP3262515B1 (en) * 2015-09-30 2019-08-07 Hewlett-Packard Enterprise Development LP Cryptographic-based initialization of memory content
US10320905B2 (en) 2015-10-02 2019-06-11 Oracle International Corporation Highly available network filer super cluster
US10360119B2 (en) * 2015-10-06 2019-07-23 Netapp, Inc. Data recovery in a distributed storage system
US20170102952A1 (en) * 2015-10-07 2017-04-13 Dell Products, L.P. Accessing data stored in a remote target using a baseboard management controler (bmc) independently of the status of the remote target's operating system (os)
US9678682B2 (en) 2015-10-13 2017-06-13 International Business Machines Corporation Backup storage of vital debug information
JP6567683B2 (en) * 2015-10-16 2019-08-28 国立大学法人東北大学 Information processing system, information processing apparatus, information processing method, and program
US9886196B2 (en) 2015-10-21 2018-02-06 Western Digital Technologies, Inc. Method and system for efficient common processing in memory device controllers
US10108340B2 (en) 2015-10-21 2018-10-23 Western Digital Technologies, Inc. Method and system for a common processing framework for memory device controllers
US9934094B2 (en) * 2015-10-30 2018-04-03 Seagate Technology Llc Process for verification of randomly generated I/O requests
US20170123700A1 (en) 2015-11-03 2017-05-04 Samsung Electronics Co., Ltd. Io redirection methods with cost estimation
US10254998B2 (en) 2015-11-03 2019-04-09 Samsung Electronics Co., Ltd. Coordinated garbage collection of flash devices in a distributed storage system
KR102314137B1 (en) * 2015-11-04 2021-10-18 삼성전자 주식회사 Non-volatile Memory Device performing selective recovery operation and Operating Method thereof
TWI559155B (en) * 2015-11-26 2016-11-21 英業達股份有限公司 Input/output switching method, electrical device and system
US9811259B2 (en) * 2015-11-27 2017-11-07 Netapp, Inc. Read I/O completions outside file operating system domain
US10303372B2 (en) 2015-12-01 2019-05-28 Samsung Electronics Co., Ltd. Nonvolatile memory device and operation method thereof
WO2017100288A1 (en) 2015-12-08 2017-06-15 Ultrata, Llc. Memory fabric operations and coherency using fault tolerant objects
CA3006773A1 (en) 2015-12-08 2017-06-15 Ultrata, Llc Memory fabric software implementation
US9892075B2 (en) 2015-12-10 2018-02-13 Cisco Technology, Inc. Policy driven storage in a microserver computing environment
US9886214B2 (en) 2015-12-11 2018-02-06 Ip Gem Group, Llc Nonvolatile memory system with erase suspend circuit and method for erase suspend management
US10437483B2 (en) * 2015-12-17 2019-10-08 Samsung Electronics Co., Ltd. Computing system with communication mechanism and method of operation thereof
US10339098B2 (en) * 2015-12-22 2019-07-02 Spectra Logic, Corp. Container-level array storage
US10063422B1 (en) * 2015-12-29 2018-08-28 Amazon Technologies, Inc. Controlled bandwidth expansion in compressed disaggregated storage systems
US9892794B2 (en) 2016-01-04 2018-02-13 Ip Gem Group, Llc Method and apparatus with program suspend using test mode
US10713211B2 (en) * 2016-01-13 2020-07-14 Red Hat, Inc. Pre-registering memory regions for remote direct memory access in a distributed file system
US10901937B2 (en) 2016-01-13 2021-01-26 Red Hat, Inc. Exposing pre-registered memory regions for remote direct memory access in a distributed file system
US9899092B2 (en) 2016-01-27 2018-02-20 Ip Gem Group, Llc Nonvolatile memory system with program step manager and method for program step management
US10157153B2 (en) * 2016-02-03 2018-12-18 Qualcomm Incorporated Inline cryptographic engine (ICE) for peripheral component interconnect express (PCIe) systems
CN107145459B (en) * 2016-03-01 2021-05-18 华为技术有限公司 System and method for remote shared access of cascade plate and SSD
US10776272B2 (en) 2016-03-02 2020-09-15 Mellanox Technologies, Ltd. Control of persistent memory via a computer bus
US9954558B1 (en) 2016-03-03 2018-04-24 Avago Technologies General Ip (Singapore) Pte. Ltd. Fast decoding of data stored in a flash memory
US10409719B2 (en) 2016-03-17 2019-09-10 Samsung Electronics Co., Ltd. User configurable passive background operation
US10230810B1 (en) 2016-03-18 2019-03-12 Barefoot Networks, Inc. Storing packet data in mirror buffer
US9583182B1 (en) * 2016-03-22 2017-02-28 Intel Corporation Multi-level memory management
US10303646B2 (en) 2016-03-25 2019-05-28 Microsoft Technology Licensing, Llc Memory sharing for working data using RDMA
US10404676B2 (en) * 2016-03-29 2019-09-03 Intel Corporation Method and apparatus to coordinate and authenticate requests for data
US9852025B2 (en) * 2016-03-29 2017-12-26 Alibaba Group Holding Limited Protecting data stored on a solid state drive
US20170300249A1 (en) * 2016-04-15 2017-10-19 Western Digital Technologies, Inc. Validity tracking for garbage collection
US10140172B2 (en) 2016-05-18 2018-11-27 Cisco Technology, Inc. Network-aware storage repairs
KR102643467B1 (en) 2016-05-31 2024-03-06 에스케이하이닉스 주식회사 Memory system and operating method of memory system
US20170351639A1 (en) 2016-06-06 2017-12-07 Cisco Technology, Inc. Remote memory access using memory mapped addressing among multiple compute nodes
US10664169B2 (en) 2016-06-24 2020-05-26 Cisco Technology, Inc. Performance of object storage system by reconfiguring storage devices based on latency that includes identifying a number of fragments that has a particular storage device as its primary storage device and another number of fragments that has said particular storage device as its replica storage device
CN106201338B (en) 2016-06-28 2019-10-22 华为技术有限公司 Date storage method and device
KR102635134B1 (en) 2016-06-30 2024-02-08 에스케이하이닉스 주식회사 Memory controller, asynchronous memory buffer chip and memory system including the same
US9690886B1 (en) * 2016-06-30 2017-06-27 Zerto Ltd. System and method for a simulation of a block storage system on an object storage system
CN106201352B (en) * 2016-07-07 2019-11-29 广东高云半导体科技股份有限公司 The secrecy system and decryption method of non-volatile FPGA on piece data streaming file
TWI620074B (en) * 2016-07-12 2018-04-01 緯創資通股份有限公司 Server system and control method for storage unit
US10120702B2 (en) * 2016-07-12 2018-11-06 American Megatrends, Inc. Platform simulation for management controller development projects
US10534716B2 (en) * 2016-07-13 2020-01-14 Seagate Technology Llc Limiting access operations in a data storage device
US10037150B2 (en) * 2016-07-15 2018-07-31 Advanced Micro Devices, Inc. Memory controller with virtual controller mode
US10739996B1 (en) * 2016-07-18 2020-08-11 Seagate Technology Llc Enhanced garbage collection
US10034407B2 (en) * 2016-07-22 2018-07-24 Intel Corporation Storage sled for a data center
US10291263B2 (en) 2016-07-28 2019-05-14 Ip Gem Group, Llc Auto-learning log likelihood ratio
US10283215B2 (en) 2016-07-28 2019-05-07 Ip Gem Group, Llc Nonvolatile memory system with background reference positioning and local reference positioning
US10236915B2 (en) 2016-07-29 2019-03-19 Microsemi Solutions (U.S.), Inc. Variable T BCH encoding
US20180039427A1 (en) * 2016-08-08 2018-02-08 Nuvoton Technology Corporation Reducing programming time of memory devices using data encoding
US10387303B2 (en) 2016-08-16 2019-08-20 Western Digital Technologies, Inc. Non-volatile storage system with compute engine to accelerate big data applications
US10379778B2 (en) * 2016-08-18 2019-08-13 International Business Machines Corporation Using a master encryption key to sanitize a dispersed storage network memory
US10798073B2 (en) 2016-08-26 2020-10-06 Nicira, Inc. Secure key management protocol for distributed network encryption
US10152393B2 (en) 2016-08-28 2018-12-11 Microsoft Technology Licensing, Llc Out-of-band data recovery in computing systems
US11563695B2 (en) 2016-08-29 2023-01-24 Cisco Technology, Inc. Queue protection using a shared global memory reserve
CN109690490A (en) * 2016-09-05 2019-04-26 三菱电机株式会社 Embedded system, embedded system control method and data matching determination method
US10236917B2 (en) * 2016-09-15 2019-03-19 Qualcomm Incorporated Providing memory bandwidth compression in chipkill-correct memory architectures
US10193634B2 (en) 2016-09-19 2019-01-29 Hewlett Packard Enterprise Development Lp Optical driver circuits
US10162752B2 (en) 2016-09-22 2018-12-25 Qualcomm Incorporated Data storage at contiguous memory addresses
US9824034B1 (en) * 2016-09-27 2017-11-21 International Business Machines Corporation Parallel ordering queue using encoded command types
US10031050B2 (en) 2016-10-13 2018-07-24 International Business Machines Corporation Universal manufacturing test platform
KR20180045220A (en) * 2016-10-25 2018-05-04 삼성전자주식회사 Data storage system for implementing data rebuild operation with reduced read request
US10459644B2 (en) 2016-10-28 2019-10-29 Western Digital Techologies, Inc. Non-volatile storage system with integrated compute engine and optimized use of local fast memory
US10545770B2 (en) 2016-11-14 2020-01-28 Intel Corporation Configurable client hardware
US10685710B2 (en) * 2016-11-17 2020-06-16 Toshiba Memory Corporation Memory controller
US10198378B2 (en) * 2016-11-18 2019-02-05 Microsoft Technology Licensing, Llc Faster data transfer with simultaneous alternative remote direct memory access communications
US10198397B2 (en) 2016-11-18 2019-02-05 Microsoft Technology Licensing, Llc Flow control in remote direct memory access data communications with mirroring of ring buffers
RU168565U1 (en) * 2016-11-21 2017-02-08 Федеральное государственное унитарное предприятие "Научно-исследовательский институт "Квант" RECONFIGURABLE COMPUTER MODULE
US20180150256A1 (en) * 2016-11-29 2018-05-31 Intel Corporation Technologies for data deduplication in disaggregated architectures
CN106775874B (en) * 2016-12-20 2020-08-25 珠海全志科技股份有限公司 System upgrading method of terminal equipment
US11461273B1 (en) 2016-12-20 2022-10-04 Pure Storage, Inc. Modifying storage distribution in a storage system that includes one or more storage devices
US10397144B2 (en) * 2016-12-22 2019-08-27 Intel Corporation Receive buffer architecture method and apparatus
WO2018125031A1 (en) * 2016-12-27 2018-07-05 Intel Corporation Cross-component health monitoring and improved repair for self-healing platforms
US10275179B2 (en) 2017-01-16 2019-04-30 Oracle International Corporation Distributed virtual block storage network
US10545914B2 (en) 2017-01-17 2020-01-28 Cisco Technology, Inc. Distributed object storage
US10579377B2 (en) 2017-01-19 2020-03-03 International Business Machines Corporation Guarded storage event handling during transactional execution
US10496311B2 (en) 2017-01-19 2019-12-03 International Business Machines Corporation Run-time instrumentation of guarded storage event processing
US10452288B2 (en) 2017-01-19 2019-10-22 International Business Machines Corporation Identifying processor attributes based on detecting a guarded storage event
US10725685B2 (en) * 2017-01-19 2020-07-28 International Business Machines Corporation Load logical and shift guarded instruction
US10732858B2 (en) 2017-01-19 2020-08-04 International Business Machines Corporation Loading and storing controls regulating the operation of a guarded storage facility
US10496292B2 (en) 2017-01-19 2019-12-03 International Business Machines Corporation Saving/restoring guarded storage controls in a virtualized environment
US10979223B2 (en) * 2017-01-31 2021-04-13 Pure Storage, Inc. Separate encryption for a solid-state drive
US10243823B1 (en) 2017-02-24 2019-03-26 Cisco Technology, Inc. Techniques for using frame deep loopback capabilities for extended link diagnostics in fibre channel storage area networks
US10713203B2 (en) 2017-02-28 2020-07-14 Cisco Technology, Inc. Dynamic partition of PCIe disk arrays based on software configuration / policy distribution
US10254991B2 (en) 2017-03-06 2019-04-09 Cisco Technology, Inc. Storage area network based extended I/O metrics computation for deep insight into application performance
US11003381B2 (en) * 2017-03-07 2021-05-11 Samsung Electronics Co., Ltd. Non-volatile memory storage device capable of self-reporting performance capabilities
CN106843989A (en) * 2017-03-10 2017-06-13 郑州云海信息技术有限公司 It is a kind of to realize the system and method that program updates
US10079612B1 (en) 2017-03-15 2018-09-18 Alibaba Group Holding Limited Distributed erasure coding pool deployed in hyperscale infrastructure
US10664406B2 (en) 2017-03-21 2020-05-26 International Business Machines Corporation Coordinated utilization of parallel paths to improve efficiency
CN114089915B (en) * 2017-03-27 2022-12-20 珠海极海半导体有限公司 File additional writing operation method and device based on FLASH memory
CN108665939B (en) * 2017-03-31 2021-01-05 厦门旌存半导体技术有限公司 Method and apparatus for providing ECC for memory
US10552050B1 (en) 2017-04-07 2020-02-04 Bitmicro Llc Multi-dimensional computer storage system
US10565123B2 (en) 2017-04-10 2020-02-18 Western Digital Technologies, Inc. Hybrid logical to physical address translation for non-volatile storage devices with integrated compute module
US10795836B2 (en) * 2017-04-17 2020-10-06 Microsoft Technology Licensing, Llc Data processing performance enhancement for neural networks using a virtualized data iterator
US10705911B2 (en) * 2017-04-24 2020-07-07 Hewlett Packard Enterprise Development Lp Storing data in a distributed storage system
US10524022B2 (en) 2017-05-02 2019-12-31 Seagate Technology Llc Data storage system with adaptive data path routing
US10594759B2 (en) * 2017-05-09 2020-03-17 EMC IP Holding Company LLC Efficiently executing concurrent operations that depend on each other in a streaming data environment
US20180329634A1 (en) * 2017-05-10 2018-11-15 Strato Scale Ltd. Object overlay for storage-area network (san) appliances
US10459807B2 (en) 2017-05-23 2019-10-29 International Business Machines Corporation Determining modified portions of a RAID storage array
US10725859B2 (en) * 2017-05-25 2020-07-28 Western Digital Technologies, Inc. Parity generation offload using peer-to-peer data transfers in data storage system
US10635529B2 (en) * 2017-05-25 2020-04-28 Western Digital Technologies, Inc. Parity offload for multiple data storage devices
US10860508B2 (en) * 2017-05-25 2020-12-08 Western Digital Technologies, Inc. Offloaded disaggregated storage architecture
US10915405B2 (en) * 2017-05-26 2021-02-09 Netapp, Inc. Methods for handling storage element failures to reduce storage device failure rates and devices thereof
JP7087279B2 (en) * 2017-05-26 2022-06-21 富士通株式会社 Information processing equipment and programs
CN107145428A (en) * 2017-05-26 2017-09-08 郑州云海信息技术有限公司 A kind of server and server monitoring method
KR102234725B1 (en) * 2017-05-30 2021-04-02 에스케이하이닉스 주식회사 Controller and memory system and operating method of memory system
US10616076B2 (en) * 2017-05-30 2020-04-07 International Business Machines Corporation Network asset management
US10223318B2 (en) * 2017-05-31 2019-03-05 Hewlett Packard Enterprise Development Lp Hot plugging peripheral connected interface express (PCIe) cards
US10152422B1 (en) 2017-06-13 2018-12-11 Seagate Technology Llc Page-based method for optimizing cache metadata updates
US11003532B2 (en) * 2017-06-16 2021-05-11 Microsoft Technology Licensing, Llc Distributed data object management system operations
KR102077283B1 (en) * 2017-06-27 2020-02-14 주식회사 케이티 Remote back-up device
US10389342B2 (en) 2017-06-28 2019-08-20 Hewlett Packard Enterprise Development Lp Comparator
US10216685B1 (en) * 2017-07-19 2019-02-26 Agiga Tech Inc. Memory modules with nonvolatile storage and rapid, sustained transfer rates
US10303534B2 (en) 2017-07-20 2019-05-28 Cisco Technology, Inc. System and method for self-healing of application centric infrastructure fabric memory
US10785301B2 (en) * 2017-08-03 2020-09-22 Toshiba Memory Corporation NVM express over fabrics
US20190042781A1 (en) * 2017-08-04 2019-02-07 Bitdefender IPR Management Ltd. Secure Storage Device
CN107506138B (en) * 2017-08-11 2020-12-18 东莞记忆存储科技有限公司 Method for prolonging service life of solid state disk
US10831935B2 (en) * 2017-08-31 2020-11-10 Pure Storage, Inc. Encryption management with host-side data reduction
WO2019049224A1 (en) * 2017-09-06 2019-03-14 株式会社日立製作所 Distributed storage system and distributed storage control method
US10949199B1 (en) 2017-09-14 2021-03-16 Barefoot Networks, Inc. Copying packet data to mirror buffer
US10503590B2 (en) * 2017-09-21 2019-12-10 International Business Machines Corporation Storage array comprising a host-offloaded storage function
US10379948B2 (en) 2017-10-02 2019-08-13 Western Digital Technologies, Inc. Redundancy coding stripe based on internal addresses of storage devices
US10474528B2 (en) 2017-10-02 2019-11-12 Western Digital Technologies, Inc. Redundancy coding stripe based on coordinated internal address scheme across multiple devices
US10404596B2 (en) 2017-10-03 2019-09-03 Cisco Technology, Inc. Dynamic route profile storage in a hardware trie routing table
US10469367B2 (en) 2017-10-04 2019-11-05 Cisco Technology, Inc. Segment routing network processing of packets including operations signaling and processing of packets in manners providing processing and/or memory efficiencies
US10353606B2 (en) * 2017-10-12 2019-07-16 International Business Machines Corporation Partial data replay in a distributed memory buffer system
EP3495939B1 (en) * 2017-10-13 2021-06-30 Huawei Technologies Co., Ltd. Method and device for storing data in distributed block storage system, and computer readable storage medium
CN107748704A (en) * 2017-10-13 2018-03-02 郑州云海信息技术有限公司 The method and device that memory mirror based on FPGA is realized
US10942666B2 (en) 2017-10-13 2021-03-09 Cisco Technology, Inc. Using network device replication in distributed storage clusters
US11502948B2 (en) 2017-10-16 2022-11-15 Mellanox Technologies, Ltd. Computational accelerator for storage operations
US11005771B2 (en) 2017-10-16 2021-05-11 Mellanox Technologies, Ltd. Computational accelerator for packet payload operations
CN109697017B (en) * 2017-10-20 2022-03-15 上海宝存信息科技有限公司 Data storage device and non-volatile memory operation method
KR102427323B1 (en) * 2017-11-08 2022-08-01 삼성전자주식회사 Semiconductor memory module, semiconductor memory system, and access method of accessing semiconductor memory module
CN108062358B (en) * 2017-11-28 2020-12-29 厦门市美亚柏科信息股份有限公司 Offline recovery method for deletion records of Innodb engine and storage medium
US10708240B2 (en) 2017-12-14 2020-07-07 Mellanox Technologies, Ltd. Offloading communication security operations to a network interface controller
WO2019119212A1 (en) * 2017-12-18 2019-06-27 华为技术有限公司 Method and device for identifying osd sub-health, and data storage system
FR3075413B1 (en) * 2017-12-20 2020-01-10 Bull Sas METHOD FOR PRE-LOADING DATA
KR102032878B1 (en) * 2017-12-22 2019-10-16 한국외국어대학교 연구산학협력단 Method for correcting error of flash storage controller
CN109976663B (en) * 2017-12-27 2021-12-28 浙江宇视科技有限公司 Distributed storage response method and system
US10592173B2 (en) * 2018-01-10 2020-03-17 International Business Machines Corporation Increasing storage efficiency of a data protection technique
CN110096451B (en) * 2018-01-29 2023-08-04 华为技术有限公司 Data storage method and device
CN110096220B (en) * 2018-01-31 2020-06-26 华为技术有限公司 Distributed storage system, data processing method and storage node
US10608939B1 (en) 2018-02-13 2020-03-31 Barefoot Networks, Inc. Identifying congestion in a network
US11157356B2 (en) 2018-03-05 2021-10-26 Samsung Electronics Co., Ltd. System and method for supporting data protection across FPGA SSDs
US10909066B2 (en) * 2018-04-03 2021-02-02 Microsoft Technology Licensing, Llc Virtual RDMA switching for containerized applications
CN108804027B (en) * 2018-04-10 2021-06-08 四川中电昆辰科技有限公司 Compression storage method for single-bit specific bit time slot allocation table
CN115174733B (en) * 2018-04-28 2024-09-24 华为技术有限公司 Interface display method, device and equipment
US10579606B2 (en) * 2018-05-03 2020-03-03 Samsung Electronics Co., Ltd Apparatus and method of data analytics in key-value solid state device (KVSSD) including data and analytics containers
US11003537B2 (en) * 2018-05-29 2021-05-11 Micron Technology, Inc. Determining validity of data read from memory by a controller
US10558565B2 (en) * 2018-05-29 2020-02-11 Microsoft Technology Licensing, Llc Garbage collection implementing erasure coding
CN110597451B (en) * 2018-06-12 2021-02-23 华为技术有限公司 Method for realizing virtualized cache and physical machine
US10785024B2 (en) 2018-06-20 2020-09-22 International Business Machines Corporation Encryption key structure within block based memory
US10515042B1 (en) 2018-06-20 2019-12-24 Quanta Computer Inc. DAS storage cable identification
US11509606B2 (en) * 2018-06-29 2022-11-22 Intel Corporation Offload of storage node scale-out management to a smart network interface controller
US10409511B1 (en) 2018-06-30 2019-09-10 Western Digital Technologies, Inc. Multi-device storage system with distributed read/write processing
CN110659234B (en) * 2018-06-30 2024-02-02 联想企业解决方案(新加坡)有限公司 Filling method for server main board and main board DIMM slot
US10725941B2 (en) 2018-06-30 2020-07-28 Western Digital Technologies, Inc. Multi-device storage system with hosted services on peer storage devices
US10725862B2 (en) * 2018-07-06 2020-07-28 Macronix International Co., Ltd. Data recovery method to error correction code in memory
US11194588B2 (en) * 2018-07-09 2021-12-07 Dell Products L.P. Information handling systems and method to provide secure shared memory access at OS runtime
CN110729006B (en) * 2018-07-16 2022-07-05 超威半导体(上海)有限公司 Refresh scheme in a memory controller
KR102495539B1 (en) * 2018-07-16 2023-02-06 에스케이하이닉스 주식회사 Memory system and operating method thereof
US11238005B2 (en) 2018-07-20 2022-02-01 Samsung Electronics Co., Ltd. SFF-TA-100X based multi-mode protocols solid state devices
US10831411B2 (en) 2018-07-24 2020-11-10 International Business Machines Corporation Storage controller with OCS for managing active-passive backend storage arrays
US10825477B2 (en) * 2018-08-02 2020-11-03 Western Digital Technologies, Inc. RAID storage system with logical data group priority
US10824526B2 (en) 2018-08-03 2020-11-03 Western Digital Technologies, Inc. Using failed storage device in peer-to-peer storage system to perform storage-centric task
US11132256B2 (en) 2018-08-03 2021-09-28 Western Digital Technologies, Inc. RAID storage system with logical data group rebuild
US10831603B2 (en) 2018-08-03 2020-11-10 Western Digital Technologies, Inc. Rebuild assist using failed storage device
US10649843B2 (en) 2018-08-03 2020-05-12 Western Digital Technologies, Inc. Storage systems with peer data scrub
US10592144B2 (en) 2018-08-03 2020-03-17 Western Digital Technologies, Inc. Storage system fabric with multichannel compute complex
US10901848B2 (en) * 2018-08-03 2021-01-26 Western Digital Technologies, Inc. Storage systems with peer data recovery
KR20200021819A (en) * 2018-08-21 2020-03-02 에스케이하이닉스 주식회사 Memory controller, storage system and operating method thereof
CN109240608B (en) * 2018-08-22 2021-08-31 郑州云海信息技术有限公司 Configuration information synchronization method and device
CN109362236A (en) * 2018-08-31 2019-02-19 深圳大学 Secure storage method of data, device, equipment and storage medium based on double clouds
JP7091203B2 (en) 2018-09-19 2022-06-27 キオクシア株式会社 Memory system and control method
US11030316B2 (en) 2018-09-20 2021-06-08 Samsung Electronics Co., Ltd. System and method for providing security protection for FPGA based solid state drives
DE102018007628A1 (en) * 2018-09-26 2020-03-26 Giesecke+Devrient Mobile Security Gmbh Decentralized identity management solution
US10877810B2 (en) 2018-09-29 2020-12-29 Western Digital Technologies, Inc. Object storage system with metadata operation priority processing
US10956071B2 (en) * 2018-10-01 2021-03-23 Western Digital Technologies, Inc. Container key value store for data storage devices
US10817430B2 (en) 2018-10-02 2020-10-27 Micron Technology, Inc. Access unit and management segment memory operations
US10652208B2 (en) * 2018-10-03 2020-05-12 Axonius Solutions Ltd. System and method for managing network connected devices
TWI679532B (en) * 2018-10-05 2019-12-11 緯穎科技服務股份有限公司 Monitoring system and method
US20200117722A1 (en) * 2018-10-12 2020-04-16 Goke Us Research Laboratory Efficient file storage and retrieval system, method and apparatus
CN109586931B (en) * 2018-10-18 2021-01-15 招商证券股份有限公司 Multicast method and terminal equipment
KR20200046495A (en) * 2018-10-24 2020-05-07 에스케이하이닉스 주식회사 Memory system and operating method thereof
US10761932B2 (en) * 2018-10-25 2020-09-01 Hewlett Packard Enterprise Development Lp Data and metadata storage in storage devices
US11023155B2 (en) 2018-10-29 2021-06-01 International Business Machines Corporation Processing event messages for changed data objects to determine a storage pool to store the changed data objects
US10983985B2 (en) * 2018-10-29 2021-04-20 International Business Machines Corporation Determining a storage pool to store changed data objects indicated in a database
GB2578600B (en) * 2018-10-31 2021-10-13 Advanced Risc Mach Ltd Memory transaction request management
US10936295B2 (en) * 2018-11-01 2021-03-02 Dell Products L.P. Software update system
US11409900B2 (en) 2018-11-15 2022-08-09 International Business Machines Corporation Processing event messages for data objects in a message queue to determine data to redact
US11429674B2 (en) 2018-11-15 2022-08-30 International Business Machines Corporation Processing event messages for data objects to determine data to redact from a database
CN109683809B (en) * 2018-11-19 2021-08-31 深圳市艾锐达光电有限公司 Data storage method and terminal
US10749758B2 (en) 2018-11-21 2020-08-18 International Business Machines Corporation Cognitive data center management
US10951403B2 (en) * 2018-12-03 2021-03-16 Winbond Electronics Corporation Updating cryptographic keys stored in non-volatile memory
CN109788697B (en) 2018-12-04 2021-04-09 华为技术有限公司 Electronic equipment and storage equipment with parallel back plate
US10949297B2 (en) * 2018-12-05 2021-03-16 Micron Technology, Inc. NAND device mixed parity management
US11734192B2 (en) 2018-12-10 2023-08-22 International Business Machines Corporation Identifying location of data granules in global virtual address space
US11016908B2 (en) * 2018-12-11 2021-05-25 International Business Machines Corporation Distributed directory of named data elements in coordination namespace
US11204819B2 (en) 2018-12-21 2021-12-21 Samsung Electronics Co., Ltd. System and method for offloading application functions to a device
CN111367466B (en) * 2018-12-26 2023-08-15 深圳市茁壮网络股份有限公司 Disk retirement method and device
CN109710547B (en) * 2018-12-29 2020-12-08 浙江理工大学 Buffer memory management design and implementation method in industrial Internet of things
US11182258B2 (en) 2019-01-04 2021-11-23 Western Digital Technologies, Inc. Data rebuild using dynamic peer work allocation
US11455402B2 (en) 2019-01-30 2022-09-27 Seagate Technology Llc Non-volatile memory with precise write-once protection
KR20200095130A (en) 2019-01-31 2020-08-10 에스케이하이닉스 주식회사 Memory controller and operating method thereof
US11513984B2 (en) * 2019-02-04 2022-11-29 American Megatrends International, Llc Common server san core solution to enable software defined storage
CN109947447A (en) * 2019-02-25 2019-06-28 南京百敖软件有限公司 A kind of server sensor monitoring online updating method
KR101995034B1 (en) * 2019-02-26 2019-07-02 에스케이하이닉스 주식회사 Data storage device and operating method thereof
US10997029B2 (en) * 2019-03-07 2021-05-04 International Business Machines Corporation Core repair with failure analysis and recovery probe
WO2020185623A1 (en) 2019-03-08 2020-09-17 Mobileye Vision Technologies Ltd. Priority based management of access to shared resources
US11151093B2 (en) * 2019-03-29 2021-10-19 International Business Machines Corporation Distributed system control for on-demand data access in complex, heterogenous data storage
US11184439B2 (en) 2019-04-01 2021-11-23 Mellanox Technologies, Ltd. Communication with accelerator via RDMA-based network adapter
US11494107B2 (en) * 2019-04-11 2022-11-08 Apple Inc. Managing parity information for data stored on a storage device
TWI704567B (en) 2019-04-18 2020-09-11 大陸商上海川源信息科技有限公司 Data recovery method for raid system
US11316904B2 (en) * 2019-04-25 2022-04-26 Super Micro Computer, Inc. Network switches with secured switch ports to baseboard management controllers
US20200342109A1 (en) * 2019-04-29 2020-10-29 Hewlett Packard Enterprise Development Lp Baseboard management controller to convey data
CN111857547B (en) * 2019-04-29 2024-05-24 伊姆西Ip控股有限责任公司 Method, apparatus and computer readable medium for managing data storage
KR20200126531A (en) * 2019-04-30 2020-11-09 에스케이하이닉스 주식회사 Memory system and method of performing command operation thereof
CN113874848A (en) * 2019-05-23 2021-12-31 慧与发展有限责任合伙企业 System and method for facilitating management of operations on accelerators in a Network Interface Controller (NIC)
US11487616B2 (en) * 2019-05-24 2022-11-01 Texas Instruments Incorporated Write control for read-modify-write operations in cache memory
US11620389B2 (en) 2019-06-24 2023-04-04 University Of Maryland Baltimore County Method and system for reducing false positives in static source code analysis reports using machine learning and classification techniques
JP7438246B2 (en) * 2019-07-02 2024-02-26 マイクロソフト テクノロジー ライセンシング，エルエルシー Hardware-based memory compression
US11075656B2 (en) 2019-07-16 2021-07-27 Microsoft Technology Licensing, Llc Bit error reduction of communication systems using error correction
US11172455B2 (en) 2019-07-16 2021-11-09 Microsoft Technology Licensing, Llc Peak to average power output reduction of RF systems utilizing error correction
US11086719B2 (en) 2019-07-16 2021-08-10 Microsoft Technology Licensing, Llc Use of error correction codes to prevent errors in neighboring storage
US11983277B2 (en) 2019-07-16 2024-05-14 Hewlett Packard Enterprise Development Lp Identifying a security vulnerability in a computer system
US11063696B2 (en) 2019-07-16 2021-07-13 Microsoft Technology Licensing, Llc Increasing average power levels to reduce peak-to-average power levels using error correction codes
US11044044B2 (en) 2019-07-16 2021-06-22 Microsoft Technology Licensing, Llc Peak to average power ratio reduction of optical systems utilizing error correction
US11031961B2 (en) 2019-07-16 2021-06-08 Microsoft Technology Licensing, Llc Smart symbol changes for optimization of communications using error correction
US10911284B1 (en) 2019-07-16 2021-02-02 Microsoft Technology Licensing, Llc Intelligent optimization of communication systems utilizing error correction
CN110489367B (en) * 2019-07-29 2020-10-02 苏州浪潮智能科技有限公司 Method and system for flexibly allocating and easily managing backplane by CPLD (complex programmable logic device)
US10911141B1 (en) 2019-07-30 2021-02-02 Microsoft Technology Licensing, Llc Dynamically selecting a channel model for optical communications
KR102650809B1 (en) 2019-08-02 2024-03-26 삼성전자주식회사 Storage device and operating method thereof
US11200106B2 (en) 2019-08-12 2021-12-14 Advanced Micro Devices, Inc. Data integrity for persistent memory systems and the like
US11487908B2 (en) * 2019-08-16 2022-11-01 Macronix International Co., Ltd. Secure memory
US11150812B2 (en) 2019-08-20 2021-10-19 Micron Technology, Inc. Predictive memory management
CN110569262A (en) * 2019-08-21 2019-12-13 广州汇思信息科技有限公司 Electronic test paper generation method, electronic device and storage medium
US10817460B2 (en) * 2019-08-28 2020-10-27 Advanced New Technologies Co., Ltd. RDMA data sending and receiving methods, electronic device, and readable storage medium
KR102316271B1 (en) * 2019-08-29 2021-10-22 동국대학교 산학협력단 Method for managing of memory address mapping table for data storage device
US10866861B1 (en) * 2019-08-29 2020-12-15 Micron Technology, Inc. Deferred error-correction parity calculations
US10942857B1 (en) 2019-09-11 2021-03-09 International Business Machines Corporation Dynamically adjusting a number of memory copy and memory mapping windows to optimize I/O performance
JP2021043708A (en) * 2019-09-11 2021-03-18 キオクシア株式会社 Memory system
US11016692B2 (en) 2019-09-11 2021-05-25 International Business Machines Corporation Dynamically switching between memory copy and memory mapping to optimize I/O performance
CN110688328B (en) * 2019-09-27 2023-03-14 山东华芯半导体有限公司 Configurable remapping realization method for AXI bus sub-host mapping set
US11360949B2 (en) * 2019-09-30 2022-06-14 Dell Products L.P. Method and system for efficient updating of data in a linked node system
US11604771B2 (en) 2019-09-30 2023-03-14 Dell Products L.P. Method and system for data placement in a linked node system
US11481293B2 (en) 2019-09-30 2022-10-25 Dell Products L.P. Method and system for replica placement in a linked node system
US11288372B2 (en) 2019-10-07 2022-03-29 Microsoft Technology Licensing, Llc Secure installation of baseboard management controller firmware via a physical interface
US11243859B2 (en) 2019-10-09 2022-02-08 Microsoft Technology Licensing, Llc Baseboard management controller that initiates a diagnostic operation to collect host information
US11151041B2 (en) * 2019-10-15 2021-10-19 Micron Technology, Inc. Tokens to indicate completion of data storage
CN110753121A (en) * 2019-10-25 2020-02-04 北京浪潮数据技术有限公司 Mirror image warehouse deployment method, device, equipment and medium
CN110990324A (en) * 2019-10-25 2020-04-10 苏州浪潮智能科技有限公司 Method and device for realizing output control, computer storage medium and terminal
US11251979B2 (en) * 2019-10-30 2022-02-15 International Business Machines Corporation Control of information units for encryption
CN110795508B (en) * 2019-11-04 2023-04-07 中国建设银行股份有限公司 Data copying method, device, equipment and storage medium
US11580233B1 (en) * 2019-11-13 2023-02-14 Meta Platforms, Inc. Baseboard-management-controller storage module
US11016905B1 (en) 2019-11-13 2021-05-25 Western Digital Technologies, Inc. Storage class memory access
WO2021095232A1 (en) 2019-11-15 2021-05-20 キオクシア株式会社 Storage system and wafer
CN110866291B (en) * 2019-11-15 2023-03-24 北京工业大学 Waste electronic product information clearing method based on dual security mechanisms
EP4060720A4 (en) 2019-11-15 2023-08-16 Kioxia Corporation Storage device and storage system
CN111080840B (en) * 2019-12-04 2022-02-18 中国直升机设计研究所 Helicopter flight control system data sending and reproducing method
US12099746B2 (en) * 2019-12-16 2024-09-24 Micron Technology, Inc. Interrupt signaling for a memory device
US11256448B2 (en) 2019-12-16 2022-02-22 Samsung Electronics Co., Ltd. Network storage gateway
CN111211944B (en) * 2020-01-07 2021-11-12 深圳市吉祥腾达科技有限公司 Router-WAN multi-dialing stability test system and test method
US10978097B1 (en) 2020-01-16 2021-04-13 International Business Machines Corporation Indicating tracks as erased without deleting data for the tracks
KR20210094178A (en) * 2020-01-20 2021-07-29 삼성전자주식회사 Computing system for transmitting completion early between serially connected electronic devices
US11210002B2 (en) 2020-01-29 2021-12-28 Samsung Electronics Co., Ltd. Offloaded device-driven erasure coding
US11316917B2 (en) * 2020-03-04 2022-04-26 Samsung Electronics Co., Ltd. Methods and apparatus for peer-to-peer data channels for storage devices
US11231934B2 (en) 2020-03-05 2022-01-25 Samsung Electronics Co., Ltd. System and method for controlling the order of instruction execution by a target device
KR102289834B1 (en) * 2020-03-09 2021-08-12 한림대학교 산학협력단 Virtual storage system using storage space of sensor device and operating method of the same
KR102289835B1 (en) * 2020-03-10 2021-08-12 한림대학교 산학협력단 Virtual storage system transmitting and receiving stored data in block unit and operating method of the same
CN113495681B (en) * 2020-04-07 2024-09-24 杭州萤石软件有限公司 NAND FLASH file data access method, NAND FLASH file data access device and storage medium
US20210342169A1 (en) * 2020-04-29 2021-11-04 Hewlett Packard Enterprise Development Lp Emulating physical security devices
US11481203B2 (en) 2020-04-30 2022-10-25 Forcepoint Llc Shared pipeline for multiple services
US11586385B1 (en) 2020-05-06 2023-02-21 Radian Memory Systems, Inc. Techniques for managing writes in nonvolatile memory
US11249921B2 (en) 2020-05-06 2022-02-15 Western Digital Technologies, Inc. Page modification encoding and caching
US20210349781A1 (en) * 2020-05-11 2021-11-11 Samsung Electronics Co., Ltd. Systems, methods, and devices for data recovery using parity space as recovery space
WO2021232024A1 (en) * 2020-05-15 2021-11-18 Rey Bruce Artificial intelligence-based hybrid raid controller device
CN111835610B (en) * 2020-05-29 2022-05-03 中车株洲电力机车研究所有限公司 Data sharing method, system, storage medium and electronic device
US11962518B2 (en) 2020-06-02 2024-04-16 VMware LLC Hardware acceleration techniques using flow selection
US11307782B2 (en) * 2020-06-03 2022-04-19 Micron Technology, Inc. Host identification and verification system and method for a memory system
US11262919B2 (en) * 2020-06-05 2022-03-01 Vmware, Inc. Efficient segment cleaning employing remapping of data blocks in log-structured file systems of distributed data systems
US11334497B2 (en) * 2020-06-05 2022-05-17 Vmware, Inc. Efficient segment cleaning employing local copying of data blocks in log-structured file systems of distributed data systems
US11263146B2 (en) * 2020-06-05 2022-03-01 Vmware, Inc. Efficient accessing methods for bypassing second layer mapping of data blocks in file systems of distributed data systems
US11507544B2 (en) 2020-06-05 2022-11-22 Vmware, Inc. Efficient erasure-coded storage in distributed data systems
JP7475989B2 (en) * 2020-06-26 2024-04-30 キオクシア株式会社 MEMORY SYSTEM AND CONTROL METHOD - Patent application
KR102208497B1 (en) * 2020-07-01 2021-01-27 주식회사 파두 Memory controller and storage device including the same
US11283719B2 (en) 2020-07-13 2022-03-22 Google Llc Content addressable memory (CAM) based hardware architecture for datacenter networking
EP4185944A4 (en) * 2020-07-22 2024-09-04 Analog Devices Inc Synchronizing communication channels between digital front-end processors
US11567831B2 (en) 2020-07-28 2023-01-31 Micron Technology, Inc. Generating a protected and balanced codeword
US11237906B1 (en) * 2020-07-28 2022-02-01 Micron Technology, Inc. Generating a balanced codeword protected by an error correction code
US11494264B2 (en) 2020-07-28 2022-11-08 Micron Technology, Inc. Generating a protected and balanced codeword
CN114095153A (en) 2020-08-05 2022-02-25 迈络思科技有限公司 Cipher data communication device
IL276538B2 (en) 2020-08-05 2023-08-01 Mellanox Technologies Ltd Cryptographic data communication apparatus
US20220046080A1 (en) * 2020-08-06 2022-02-10 Dell Products L.P. Systems and methods for shared access among host information handling system and multiple client information handling systems via management controller
US11327858B2 (en) * 2020-08-11 2022-05-10 Seagate Technology Llc Preserving data integrity during controller failure
JP7175944B2 (en) * 2020-08-31 2022-11-21 楽天グループ株式会社 Communication system, transmitter, receiver, communication method, and program
TWI817039B (en) * 2020-09-08 2023-10-01 以色列商無比視視覺科技有限公司 Method and system for managing access of multiple initiators to shared resources and related computer program product
EP4202707A4 (en) * 2020-09-17 2023-08-23 Huawei Technologies Co., Ltd. Communication method and apparatus employing inter-integrated circuit
CN111930517B (en) * 2020-09-18 2023-07-14 北京中科立维科技有限公司 High-performance self-adaptive garbage collection method and computer system
US11636053B2 (en) 2020-09-28 2023-04-25 Vmware, Inc. Emulating a local storage by accessing an external storage through a shared port of a NIC
US11606310B2 (en) 2020-09-28 2023-03-14 Vmware, Inc. Flow processing offload using virtual port identifiers
US11829793B2 (en) 2020-09-28 2023-11-28 Vmware, Inc. Unified management of virtual machines and bare metal computers
US11824931B2 (en) 2020-09-28 2023-11-21 Vmware, Inc. Using physical and virtual functions associated with a NIC to access an external storage through network fabric driver
US11593278B2 (en) 2020-09-28 2023-02-28 Vmware, Inc. Using machine executing on a NIC to access a third party storage not supported by a NIC or host
US12021759B2 (en) 2020-09-28 2024-06-25 VMware LLC Packet processing with hardware offload units
US12061583B1 (en) * 2020-09-29 2024-08-13 Amazon Technologies, Inc. Systems for processing data using stages
US11809282B2 (en) * 2020-09-29 2023-11-07 EMC IP Holding Company LLC Optimized pipeline to boost de-dup system performance
US11914492B2 (en) * 2020-10-13 2024-02-27 Dell Products, L.P. System and method for highly granular power/thermal control in information handling systems
US11327909B1 (en) 2020-10-26 2022-05-10 Mellanox Technologies, Ltd. System for improving input / output performance
US11544205B2 (en) 2020-11-20 2023-01-03 Western Digital Technologies, Inc. Peer storage devices sharing host control data
US11531498B2 (en) * 2020-11-20 2022-12-20 Western Digital Technologies, Inc. Peer storage device messaging over control bus
TWI754473B (en) * 2020-11-27 2022-02-01 中強光電股份有限公司 Electronic device and method for spectral model explanation
US11543992B2 (en) * 2020-12-09 2023-01-03 Western Digital Technologies, Inc. Decreasing physical secure erase times in solid state drives
CN112380071B (en) * 2020-12-09 2023-10-27 成都傲梅科技有限公司 Method for quickly backing up NTFS file system
TWI758013B (en) * 2020-12-15 2022-03-11 技嘉科技股份有限公司 Baseboard management control system, electronic device and baseboard management control method
CN112698697A (en) * 2020-12-30 2021-04-23 湖南博匠信息科技有限公司 Software-defined VPX case
US11556424B2 (en) 2021-01-19 2023-01-17 Western Digital Technologies, Inc. Non-volatile storage device having fast boot code transfer with low speed fallback
US11606422B2 (en) * 2021-01-20 2023-03-14 Samsung Electronics Co., Ltd. Server for controlling data transmission through data pipeline and operation method thereof
CN114817121A (en) * 2021-01-22 2022-07-29 伊姆西Ip控股有限责任公司 Method, electronic device and computer program product for processing data
CN112765223B (en) * 2021-01-26 2023-07-14 红云红河烟草(集团)有限责任公司 Equipment parameter data alignment method based on queue
US11645219B2 (en) * 2021-02-02 2023-05-09 American Megatrends International, Llc Method for generating a hybrid BMC system and hybrid BMC system
JP2022122478A (en) * 2021-02-10 2022-08-23 株式会社日立製作所 Network interface of storage controller
US11573718B2 (en) * 2021-02-12 2023-02-07 Western Digital Technologies, Inc. Disaggregation of control path and data path
US11934658B2 (en) 2021-03-25 2024-03-19 Mellanox Technologies, Ltd. Enhanced storage protocol emulation in a peripheral device
US11940935B2 (en) * 2021-04-19 2024-03-26 Mellanox Technologies, Ltd. Apparatus, method and computer program product for efficient software-defined network accelerated processing using storage devices which are local relative to a host
WO2022225788A1 (en) * 2021-04-21 2022-10-27 Rambus Inc. Integrated circuit memory devices with unidirectional ports for concurrent interface operations
US12081526B2 (en) * 2021-05-19 2024-09-03 Western Digital Technologies, Inc. Data storage device data recovery using remote network storage
US12040988B2 (en) 2021-05-25 2024-07-16 Google Llc Acknowledgement coalescing module utilized in content addressable memory (CAM) based hardware architecture for data center networking
KR20230097169A (en) 2021-06-01 2023-06-30 양쯔 메모리 테크놀로지스 씨오., 엘티디. Power management of memory systems
US11783866B2 (en) 2021-06-02 2023-10-10 Western Digital Technologies, Inc. Data storage device and method for legitimized data transfer
CN113538754B (en) * 2021-06-08 2023-04-07 福建新大陆通信科技股份有限公司 CTID intelligent door lock authorization data management method and system
US11782641B2 (en) * 2021-06-09 2023-10-10 International Business Machines Corporation Backend aware virtualized storage
CN117616378A (en) * 2021-06-24 2024-02-27 净睿存储股份有限公司 Efficient writing of data in a partitioned drive storage system
US11625189B2 (en) * 2021-06-28 2023-04-11 Western Digital Technologies, Inc. Systems and methods for fragmentation management in host buffers
US11321178B1 (en) * 2021-06-29 2022-05-03 Dell Products, L. P. Automated recovery from raid double failure
US11726666B2 (en) 2021-07-11 2023-08-15 Mellanox Technologies, Ltd. Network adapter with efficient storage-protocol emulation
US11675602B2 (en) 2021-07-28 2023-06-13 International Business Machines Corporation Methods and systems for creating root-of-trust for computing system components
CN113590043B (en) * 2021-07-29 2024-08-16 北京沃东天骏信息技术有限公司 Data storage method, device, equipment and storage medium
US20230049602A1 (en) * 2021-08-10 2023-02-16 Samsung Electronics Co., Ltd. Systems, methods, and apparatus for hierarchical aggregation for computational storage
US12074962B2 (en) 2021-08-10 2024-08-27 Samsung Electronics Co., Ltd. Systems, methods, and apparatus for dividing and encrypting data
US11609700B2 (en) 2021-08-11 2023-03-21 Mellanox Technologies, Ltd. Pacing in a storage sub-system
CN115905056A (en) 2021-08-11 2023-04-04 迈络思科技有限公司 Improving pacing in a storage subsystem
CN115906722A (en) * 2021-08-16 2023-04-04 富联精密电子(天津)有限公司 Server system and method for improving multiplexing rate of pins of programmable device
US12112200B2 (en) 2021-09-13 2024-10-08 International Business Machines Corporation Pipeline parallel computing using extended memory
US20230121562A1 (en) * 2021-10-15 2023-04-20 Dell Products, L.P. Telemetry of artificial intelligence (ai) and/or machine learning (ml) workloads
WO2023068463A1 (en) * 2021-10-21 2023-04-27 서울대학교산학협력단 Storage device system for quantum circuit simulation
CN114143276B (en) * 2021-11-23 2024-10-01 青芯半导体科技(上海)有限公司 PCI-e switch and method for configuring branch mode thereof
JP2023091307A (en) * 2021-12-20 2023-06-30 キオクシア株式会社 Semiconductor device and control method
US11863376B2 (en) 2021-12-22 2024-01-02 Vmware, Inc. Smart NIC leader election
US11995024B2 (en) 2021-12-22 2024-05-28 VMware LLC State sharing between smart NICs
US11971771B2 (en) 2022-01-25 2024-04-30 Western Digital Technologies, Inc. Peer storage device messaging for power management
US11921602B2 (en) 2022-02-14 2024-03-05 Cribl, Inc. Edge-based data collection system for an observability pipeline system
US20230351019A1 (en) * 2022-04-27 2023-11-02 Dell Products L.P. Secure smart network interface controller firmware update
US11853201B2 (en) 2022-05-25 2023-12-26 Micron Technology, Inc. Selective single-level memory cell operation
KR102537770B1 (en) * 2022-06-08 2023-05-30 삼성전자주식회사 Method of writing data in storage device using write throttling and storage device performing the same
US11899594B2 (en) 2022-06-21 2024-02-13 VMware LLC Maintenance of data message classification cache on smart NIC
US11928062B2 (en) 2022-06-21 2024-03-12 VMware LLC Accelerating data message classification with smart NICs
US11928367B2 (en) 2022-06-21 2024-03-12 VMware LLC Logical memory addressing for network devices
US12079084B2 (en) * 2022-08-01 2024-09-03 Microsoft Technology Licensing, Llc Distributed raid for parity-based flash storage devices
US12081450B2 (en) * 2022-08-30 2024-09-03 Xerox Corporation System and method using improved message queue and packing scheme for electronic device
US12117948B2 (en) 2022-10-31 2024-10-15 Mellanox Technologies, Ltd. Data processing unit with transparent root complex
US12007921B2 (en) 2022-11-02 2024-06-11 Mellanox Technologies, Ltd. Programmable user-defined peripheral-bus device implementation using data-plane accelerator (DPA)
CN115657963B (en) * 2022-11-14 2023-04-11 苏州浪潮智能科技有限公司 Sequential writing method and device based on solid state disk, electronic equipment and storage medium
CN115801633B (en) * 2023-02-08 2023-04-28 湖南国科亿存信息科技有限公司 Multi-client sharing concurrency performance testing method and system for SAN storage
US12093220B1 (en) * 2023-06-27 2024-09-17 International Business Machines Corporation Controlling layers in container images to reduce redundant content between layers
US11979459B1 (en) * 2023-10-12 2024-05-07 International Business Machines Corporation Configuration of data connections between a host and a shared network adapter
CN117407324B (en) * 2023-12-12 2024-03-15 深圳市银闪科技有限公司 Data storage method and device based on solid state disk and solid state disk controller
CN117667465B (en) * 2024-01-31 2024-04-16 苏州元脑智能科技有限公司 Code sharing method, device, switch, multi-host system, equipment and medium

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002001365A2 (en) * 2000-06-23 2002-01-03 Intel Corporation Non-volatile cache
US20050177687A1 (en) * 2004-02-10 2005-08-11 Sun Microsystems, Inc. Storage system including hierarchical cache metadata

Family Cites Families (1283)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
USRE20535E (en) 1937-10-19 Valve for aerated liquid vessels
GB123416A (en) 1918-02-28 1919-02-27 John Buchanan Composite Valve for all Classes of Internal Combustion Engines.
SE347103B (en) 1964-10-30 1972-07-24 Olivetti & Co Spa
US4092732A (en) * 1977-05-31 1978-05-30 International Business Machines Corporation System for recovering data stored in failed memory unit
US4290105A (en) * 1979-04-02 1981-09-15 American Newspaper Publishers Association Method and apparatus for testing membership in a set through hash coding with allowable errors
NL8201847A (en) * 1982-05-06 1983-12-01 Philips Nv DEVICE FOR PROTECTION AGAINST UNAUTHORIZED READING OF PROGRAM WORDS TO BE MEMORIZED IN A MEMORY.
US4571674A (en) 1982-09-27 1986-02-18 International Business Machines Corporation Peripheral storage system having multiple data transfer rates
US4598361A (en) * 1985-01-11 1986-07-01 Burroughs Corporation Allocator for a reduction processor evaluating programs stored as binary directed graphs employing variable-free applicative language codes
US5043871A (en) 1986-03-26 1991-08-27 Hitachi, Ltd. Method and apparatus for database update/recovery
US4761785B1 (en) * 1986-06-12 1996-03-12 Ibm Parity spreading to enhance storage access
US4980861A (en) 1987-01-16 1990-12-25 Microchip Technology Incorporated NAND stack ROM
US4858070A (en) 1987-04-24 1989-08-15 Racal Data Communications Inc. Modular expandable housing arrangement for electronic apparatus
JPH02105730A (en) * 1988-10-14 1990-04-18 Sony Corp Data recording method
JPH02148235A (en) 1988-11-30 1990-06-07 Toshiba Corp Data drawback system
US5359726A (en) 1988-12-22 1994-10-25 Thomas Michael E Ferroelectric storage device used in place of a rotating disk drive unit in a computer system
US5394531A (en) 1989-04-03 1995-02-28 International Business Machines Corporation Dynamic storage allocation system for a prioritized cache
US7190617B1 (en) * 1989-04-13 2007-03-13 Sandisk Corporation Flash EEprom system
US5535328A (en) 1989-04-13 1996-07-09 Sandisk Corporation Non-volatile memory system card with flash erasable sectors of EEprom cells including a mechanism for substituting defective cells
US5371885A (en) 1989-08-29 1994-12-06 Microsoft Corporation High performance file system
US5247658A (en) 1989-10-31 1993-09-21 Microsoft Corporation Method and system for traversing linked list record based upon write-once predetermined bit value of secondary pointers
US5111463A (en) 1989-11-09 1992-05-05 Exabyte Corporation Error correction method and apparatus
US5197130A (en) 1989-12-29 1993-03-23 Supercomputer Systems Limited Partnership Cluster architecture for a highly parallel scalar/vector multiprocessor system
US5124987A (en) 1990-04-16 1992-06-23 Storage Technology Corporation Logical track write scheduling system for a parallel disk drive array data storage subsystem
US5261068A (en) 1990-05-25 1993-11-09 Dell Usa L.P. Dual path memory retrieval system for an interleaved dynamic RAM memory unit
US5193184A (en) 1990-06-18 1993-03-09 Storage Technology Corporation Deleted data file space release system for a dynamically mapped virtual data storage subsystem
US5307497A (en) 1990-06-25 1994-04-26 International Business Machines Corp. Disk operating system loadable from read only memory using installable file system interface
DE59102665D1 (en) * 1990-08-14 1994-09-29 Siemens Ag INTERRUPT DISTRIBUTION DEVICE IN A MULTIPLE COMPUTER SYSTEM.
US5544347A (en) 1990-09-24 1996-08-06 Emc Corporation Data storage system controlled remote data mirroring with respectively maintained data indices
US5291496A (en) * 1990-10-18 1994-03-01 The United States Of America As Represented By The United States Department Of Energy Fault-tolerant corrector/detector chip for high-speed data processing
JP3227707B2 (en) 1990-12-29 2001-11-12 日本電気株式会社 Cache memory control method for each driving mode
GB2251324B (en) 1990-12-31 1995-05-10 Intel Corp File structure for a non-volatile semiconductor memory
US5274799A (en) 1991-01-04 1993-12-28 Array Technology Corporation Storage device array architecture with copyback cache
US5325509A (en) * 1991-03-05 1994-06-28 Zitel Corporation Method of operating a cache memory including determining desirability of cache ahead or cache behind based on a number of available I/O operations
US5325523A (en) 1991-04-10 1994-06-28 International Business Machines Corporation Method for deleting objects from library resident optical disks by accumulating pending delete requests
US5438671A (en) * 1991-07-19 1995-08-01 Dell U.S.A., L.P. Method and system for transferring compressed bytes of information between separate hard disk drive units
US5465355A (en) * 1991-09-04 1995-11-07 International Business Machines Corporation Establishing and restoring paths in a data processing I/O system
US5313475A (en) * 1991-10-31 1994-05-17 International Business Machines Corporation ECC function with self-contained high performance partial write or read/modify/write and parity look-ahead interface scheme
US5263003A (en) 1991-11-12 1993-11-16 Allen-Bradley Company, Inc. Flash memory circuit and method of operation
US5323489A (en) * 1991-11-14 1994-06-21 Bird Peter L Method and apparatus employing lookahead to reduce memory bank contention for decoupled operand references
US5499367A (en) 1991-11-15 1996-03-12 Oracle Corporation System for database integrity with multiple logs assigned to client subsets
US5469555A (en) * 1991-12-19 1995-11-21 Opti, Inc. Adaptive write-back method and apparatus wherein the cache system operates in a combination of write-back and write-through modes for a cache-based microprocessor system
JP3058743B2 (en) 1992-01-21 2000-07-04 株式会社日立製作所 Disk array controller
US6256642B1 (en) * 1992-01-29 2001-07-03 Microsoft Corporation Method and system for file system management using a flash-erasable, programmable, read-only memory
US5481708A (en) * 1992-06-05 1996-01-02 Borland International, Inc. System and methods for optimizing object-oriented compilations
JP3328321B2 (en) 1992-06-22 2002-09-24 株式会社日立製作所 Semiconductor storage device
US5414840A (en) 1992-06-25 1995-05-09 Digital Equipment Corporation Method and system for decreasing recovery time for failed atomic transactions by keeping copies of altered control structures in main memory
JPH0628108A (en) * 1992-07-09 1994-02-04 Hitachi Ltd Data storage system
US5596736A (en) * 1992-07-22 1997-01-21 Fujitsu Limited Data transfers to a backing store of a dynamically mapped data storage system in which data has nonsequential logical addresses
JPH0644139A (en) * 1992-07-22 1994-02-18 Ricoh Co Ltd Disk cache system and its page rewrite control method
US5381528A (en) 1992-10-15 1995-01-10 Maxtor Corporation Demand allocation of read/write buffer partitions favoring sequential read cache
US5388108A (en) * 1992-10-23 1995-02-07 Ncr Corporation Delayed initiation of read-modify-write parity operations in a raid level 5 disk array
US5337275A (en) 1992-10-30 1994-08-09 Intel Corporation Method for releasing space in flash EEPROM memory array to allow the storage of compressed data
US5357475A (en) * 1992-10-30 1994-10-18 Intel Corporation Method for detaching sectors in a flash EEPROM memory array
US5416915A (en) 1992-12-11 1995-05-16 International Business Machines Corporation Method and system for minimizing seek affinity and enhancing write sensitivity in a DASD array
US5579474A (en) * 1992-12-28 1996-11-26 Hitachi, Ltd. Disk array system and its control method
US5845329A (en) * 1993-01-29 1998-12-01 Sanyo Electric Co., Ltd. Parallel computer
EP0612015A1 (en) * 1993-02-16 1994-08-24 International Business Machines Corporation Improved disk array system having special parity groups for data blocks with high update activity
US5459850A (en) 1993-02-19 1995-10-17 Conner Peripherals, Inc. Flash solid state drive that emulates a disk drive and stores variable length and fixed lenth data blocks
JP2856621B2 (en) 1993-02-24 1999-02-10 インターナショナル・ビジネス・マシーンズ・コーポレイション Batch erase nonvolatile memory and semiconductor disk device using the same
JP3594626B2 (en) 1993-03-04 2004-12-02 株式会社ルネサステクノロジ Non-volatile memory device
US5404485A (en) * 1993-03-08 1995-04-04 M-Systems Flash Disk Pioneers Ltd. Flash file system
US5761402A (en) * 1993-03-08 1998-06-02 Hitachi, Ltd. Array type disk system updating redundant data asynchronously with data access
US5479638A (en) * 1993-03-26 1995-12-26 Cirrus Logic, Inc. Flash memory mass storage architecture incorporation wear leveling technique
US5388083A (en) * 1993-03-26 1995-02-07 Cirrus Logic, Inc. Flash memory mass storage architecture
US5485595A (en) 1993-03-26 1996-01-16 Cirrus Logic, Inc. Flash memory mass storage architecture incorporating wear leveling technique without using cam cells
US6078520A (en) 1993-04-08 2000-06-20 Hitachi, Ltd. Flash memory control method and information processing system therewith
JP2784440B2 (en) 1993-04-14 1998-08-06 インターナショナル・ビジネス・マシーンズ・コーポレイション Data page transfer control method
CA2121852A1 (en) * 1993-04-29 1994-10-30 Larry T. Jost Disk meshing and flexible storage mapping with enhanced flexible caching
US5499354A (en) * 1993-05-19 1996-03-12 International Business Machines Corporation Method and means for dynamic cache management by variable space and time binding and rebinding of cache extents to DASD cylinders
US5765207A (en) 1993-06-22 1998-06-09 International Business Machines Corporation Recursive hardware state machine
US5592641A (en) 1993-06-30 1997-01-07 Intel Corporation Method and device for selectively locking write access to blocks in a memory array using write protect inputs and block enabled status
US5682497A (en) 1993-09-28 1997-10-28 Intel Corporation Managing file structures for a flash memory file system in a computer
US5535399A (en) 1993-09-30 1996-07-09 Quantum Corporation Solid state disk drive unit having on-board backup non-volatile memory
JPH07110784A (en) 1993-10-14 1995-04-25 Fujitsu Ltd Method and device for storing additional form record
US5809527A (en) 1993-12-23 1998-09-15 Unisys Corporation Outboard file cache system
JPH086854A (en) 1993-12-23 1996-01-12 Unisys Corp Outboard-file-cache external processing complex
GB9326499D0 (en) 1993-12-24 1994-03-02 Deas Alexander R Flash memory system with arbitrary block size
US5559988A (en) * 1993-12-30 1996-09-24 Intel Corporation Method and circuitry for queuing snooping, prioritizing and suspending commands
US5379304A (en) 1994-01-28 1995-01-03 International Business Machines Corporation Method and structure for providing error correction code and parity for each byte on SIMM's
JP3378874B2 (en) 1994-03-18 2003-02-17 富士通株式会社 Information processing device and memory board
US5553261A (en) 1994-04-01 1996-09-03 Intel Corporation Method of performing clean-up of a solid state disk while executing a read command
US5596708A (en) * 1994-04-04 1997-01-21 At&T Global Information Solutions Company Method and apparatus for the protection of write data in a disk array
US5603001A (en) * 1994-05-09 1997-02-11 Kabushiki Kaisha Toshiba Semiconductor disk system having a plurality of flash memories
US5434994A (en) 1994-05-23 1995-07-18 International Business Machines Corporation System and method for maintaining replicated data coherency in a data processing system
US5696917A (en) 1994-06-03 1997-12-09 Intel Corporation Method and apparatus for performing burst read operations in an asynchronous nonvolatile memory
US5504882A (en) 1994-06-20 1996-04-02 International Business Machines Corporation Fault tolerant data storage subsystem employing hierarchically arranged controllers
IT1274925B (en) 1994-09-21 1997-07-29 Texas Instruments Italia Spa MEMORY ARCHITECTURE FOR SOLID STATE DISCS
US5845331A (en) 1994-09-28 1998-12-01 Massachusetts Institute Of Technology Memory system including guarded pointers
US5664187A (en) * 1994-10-26 1997-09-02 Hewlett-Packard Company Method and system for selecting data for migration in a hierarchic data storage system using frequency distribution tables
JPH08153014A (en) 1994-11-30 1996-06-11 Hitachi Ltd Client server system
DE19540915A1 (en) 1994-11-10 1996-05-15 Raymond Engineering Redundant arrangement of solid state memory modules
US6002411A (en) * 1994-11-16 1999-12-14 Interactive Silicon, Inc. Integrated video and memory controller with data processing and graphical processing capabilities
US6170047B1 (en) 1994-11-16 2001-01-02 Interactive Silicon, Inc. System and method for managing system memory and/or non-volatile memory using a memory controller with integrated compression and decompression capabilities
JP3011035B2 (en) * 1994-12-08 2000-02-21 株式会社日立製作所 Computer system
US5586291A (en) * 1994-12-23 1996-12-17 Emc Corporation Disk controller with volatile and non-volatile cache memories
US5541886A (en) 1994-12-27 1996-07-30 Intel Corporation Method and apparatus for storing control information in multi-bit non-volatile memory arrays
US5566315A (en) 1994-12-30 1996-10-15 Storage Technology Corporation Process of predicting and controlling the use of cache memory in a computer system
US5651133A (en) 1995-02-01 1997-07-22 Hewlett-Packard Company Methods for avoiding over-commitment of virtual capacity in a redundant hierarchic data storage system
US5745671A (en) * 1995-02-28 1998-04-28 International Business Machines Corporation Data storage system with localized XOR function
US5574882A (en) * 1995-03-03 1996-11-12 International Business Machines Corporation System and method for identifying inconsistent parity in an array of storage
US5701434A (en) 1995-03-16 1997-12-23 Hitachi, Ltd. Interleave memory controller with a common access queue
US5742787A (en) 1995-04-10 1998-04-21 Intel Corporation Hardware reset of a write state machine for flash memory
US5889795A (en) 1995-04-21 1999-03-30 International Business Machines Corporation Disk array system and method for storing data
DE69615278T2 (en) * 1995-06-06 2002-06-27 Hewlett-Packard Co. (N.D.Ges.D.Staates Delaware), Palo Alto SDRAM data allocation arrangement and method
US5682499A (en) * 1995-06-06 1997-10-28 International Business Machines Corporation Directory rebuild method and apparatus for maintaining and rebuilding directory information for compressed data on direct access storage device (DASD)
JP3732869B2 (en) * 1995-06-07 2006-01-11 株式会社日立製作所 External storage device
US5721874A (en) 1995-06-16 1998-02-24 International Business Machines Corporation Configurable cache with variable, dynamically addressable line sizes
JPH096706A (en) 1995-06-22 1997-01-10 Hitachi Ltd Loosely coupled computer system
JP3062050B2 (en) 1995-07-21 2000-07-10 インターナショナル・ビジネス・マシーンズ・コーポレ−ション Disk drive control method and apparatus
US5838614A (en) 1995-07-31 1998-11-17 Lexar Microsystems, Inc. Identification and verification of a sector within a block of mass storage flash memory
US6757800B1 (en) 1995-07-31 2004-06-29 Lexar Media, Inc. Increasing the memory performance of flash memory devices by writing sectors simultaneously to multiple flash memory devices
US8171203B2 (en) * 1995-07-31 2012-05-01 Micron Technology, Inc. Faster write operations to nonvolatile memory using FSInfo sector manipulation
US5845313A (en) * 1995-07-31 1998-12-01 Lexar Direct logical block addressing flash memory mass storage architecture
US6978342B1 (en) 1995-07-31 2005-12-20 Lexar Media, Inc. Moving sectors within a block of information in a flash memory mass storage architecture
US6728851B1 (en) * 1995-07-31 2004-04-27 Lexar Media, Inc. Increasing the memory performance of flash memory devices by writing sectors simultaneously to multiple flash memory devices
US6081878A (en) 1997-03-31 2000-06-27 Lexar Media, Inc. Increasing the memory performance of flash memory devices by writing sectors simultaneously to multiple flash memory devices
US6801979B1 (en) 1995-07-31 2004-10-05 Lexar Media, Inc. Method and apparatus for memory control circuit
US5930815A (en) * 1995-07-31 1999-07-27 Lexar Media, Inc. Moving sequential sectors within a block of information in a flash memory mass storage architecture
US5907856A (en) * 1995-07-31 1999-05-25 Lexar Media, Inc. Moving sectors within a block of information in a flash memory mass storage architecture
US5754563A (en) * 1995-09-11 1998-05-19 Ecc Technologies, Inc. Byte-parallel system for implementing reed-solomon error-correcting codes
US5835935A (en) 1995-09-13 1998-11-10 Lexar Media, Inc. Method of and architecture for controlling system data with automatic wear leveling in a semiconductor non-volatile mass storage memory
GB2291991A (en) * 1995-09-27 1996-02-07 Memory Corp Plc Disk drive emulation with a block-erasable memory
US5799200A (en) 1995-09-28 1998-08-25 Emc Corporation Power failure responsive apparatus and method having a shadow dram, a flash ROM, an auxiliary battery, and a controller
US5933847A (en) 1995-09-28 1999-08-03 Canon Kabushiki Kaisha Selecting erase method based on type of power supply for flash EEPROM
US5893138A (en) 1995-10-02 1999-04-06 International Business Machines Corporation System and method for improving channel hardware performance for an array controller
JP3363292B2 (en) * 1995-10-12 2003-01-08 株式会社日立製作所 Database management system
US6470405B2 (en) * 1995-10-19 2002-10-22 Rambus Inc. Protocol for communication with dynamic memory
US6014724A (en) 1995-10-27 2000-01-11 Scm Microsystems (U.S.) Inc. Flash translation layer block indication map revision system and method
US6330688B1 (en) * 1995-10-31 2001-12-11 Intel Corporation On chip error correction for devices in a solid state drive
US5758118A (en) * 1995-12-08 1998-05-26 International Business Machines Corporation Methods and data storage devices for RAID expansion by on-line addition of new DASDs
US6745292B1 (en) 1995-12-08 2004-06-01 Ncr Corporation Apparatus and method for selectively allocating cache lines in a partitioned cache shared by multiprocessors
US5734861A (en) * 1995-12-12 1998-03-31 International Business Machines Corporation Log-structured disk array with garbage collection regrouping of tracks to preserve seek affinity
US5787486A (en) 1995-12-15 1998-07-28 International Business Machines Corporation Bus protocol for locked cycle cache hit
US5720025A (en) * 1996-01-18 1998-02-17 Hewlett-Packard Company Frequently-redundant array of independent disks
JPH09198336A (en) 1996-01-22 1997-07-31 Nec Corp Remote access method for secondary storage device
US5757567A (en) 1996-02-08 1998-05-26 International Business Machines Corporation Method and apparatus for servo control with high efficiency gray code for servo track ID
US6385710B1 (en) * 1996-02-23 2002-05-07 Sun Microsystems, Inc. Multiple-mode external cache subsystem
US5835964A (en) 1996-04-29 1998-11-10 Microsoft Corporation Virtual memory system with hardware TLB and unmapped software TLB updated from mapped task address maps using unmapped kernel address map
US5805501A (en) 1996-05-22 1998-09-08 Macronix International Co., Ltd. Flash memory device with multiple checkpoint erase suspend logic
US5922080A (en) 1996-05-29 1999-07-13 Compaq Computer Corporation, Inc. Method and apparatus for performing error detection and correction with memory devices
JP3545535B2 (en) * 1996-05-29 2004-07-21 株式会社アドバンテスト Semiconductor memory test method and apparatus
US5778070A (en) * 1996-06-28 1998-07-07 Intel Corporation Method and apparatus for protecting flash memory
US6424872B1 (en) 1996-08-23 2002-07-23 Fieldbus Foundation Block oriented control system
US5768152A (en) * 1996-08-28 1998-06-16 International Business Machines Corp. Performance monitoring through JTAG 1149.1 interface
TW338165B (en) 1996-09-09 1998-08-11 Sony Co Ltd Semiconductor nand type flash memory with incremental step pulse programming
US5832515A (en) 1996-09-12 1998-11-03 Veritas Software Log device layered transparently within a filesystem paradigm
US5996054A (en) 1996-09-12 1999-11-30 Veritas Software Corp. Efficient virtualized mapping space for log device data storage system
JP3608694B2 (en) * 1996-09-18 2005-01-12 株式会社アドバンテスト Memory test equipment
US6201739B1 (en) 1996-09-20 2001-03-13 Intel Corporation Nonvolatile writeable memory with preemption pin
US5798968A (en) 1996-09-24 1998-08-25 Sandisk Corporation Plane decode/virtual sector architecture
US5960462A (en) * 1996-09-26 1999-09-28 Intel Corporation Method and apparatus for analyzing a main memory configuration to program a memory controller
US5754567A (en) 1996-10-15 1998-05-19 Micron Quantum Devices, Inc. Write reduction in flash memory systems through ECC usage
TW349196B (en) 1996-10-18 1999-01-01 Ibm Cached synchronous DRAM architecture having a mode register programmable cache policy
US5890192A (en) 1996-11-05 1999-03-30 Sandisk Corporation Concurrent write of multiple chunks of data into multiple subarrays of flash EEPROM
US6148377A (en) 1996-11-22 2000-11-14 Mangosoft Corporation Shared memory computer networks
US5822759A (en) * 1996-11-22 1998-10-13 Versant Object Technology Cache system
JPH10154101A (en) * 1996-11-26 1998-06-09 Toshiba Corp Data storage system and cache controlling method applying to the system
US5867430A (en) * 1996-12-20 1999-02-02 Advanced Micro Devices Inc Bank architecture for a non-volatile memory enabling simultaneous reading and writing
US5933824A (en) 1996-12-23 1999-08-03 Lsi Logic Corporation Methods and apparatus for locking files within a clustered storage environment
US6073218A (en) * 1996-12-23 2000-06-06 Lsi Logic Corp. Methods and apparatus for coordinating shared multiple raid controller access to common storage devices
US6279069B1 (en) 1996-12-26 2001-08-21 Intel Corporation Interface for flash EEPROM memory arrays
DE19700112C2 (en) 1997-01-03 1999-03-04 Fraunhofer Ges Forschung Device for redirecting light by means of total reflection
US5802602A (en) 1997-01-17 1998-09-01 Intel Corporation Method and apparatus for performing reads of related data from a set-associative cache memory
US6182188B1 (en) 1997-04-06 2001-01-30 Intel Corporation Method of performing reliable updates in a symmetrically blocked nonvolatile memory having a bifurcated storage architecture
US6311290B1 (en) 1997-02-14 2001-10-30 Intel Corporation Methods of reliably allocating, de-allocating, re-allocating, and reclaiming objects in a symmetrically blocked nonvolatile memory having a bifurcated storage architecture
TW465234B (en) 1997-02-18 2001-11-21 Discovision Ass Single chip VLSI implementation of a digital receiver employing orthogonal frequency division multiplexing
US6073232A (en) * 1997-02-25 2000-06-06 International Business Machines Corporation Method for minimizing a computer's initial program load time after a system reset or a power-on using non-volatile storage
US5961660A (en) 1997-03-03 1999-10-05 International Business Machines Corporation Method and apparatus for optimizing ECC memory performance
US6311305B1 (en) 1997-03-06 2001-10-30 T.T.R. Technologies Ltd. Method and system for overriding error correction
US5953737A (en) 1997-03-31 1999-09-14 Lexar Media, Inc. Method and apparatus for performing erase operations transparent to a solid state storage system
US6034897A (en) 1999-04-01 2000-03-07 Lexar Media, Inc. Space management for managing high capacity nonvolatile memory
JPH10301719A (en) * 1997-04-28 1998-11-13 Yamaha Corp Disk array device and information processing system using the same
JPH10320270A (en) 1997-05-15 1998-12-04 Matsushita Electric Ind Co Ltd Memory module
JP3459868B2 (en) * 1997-05-16 2003-10-27 日本電気株式会社 Group replacement method in case of memory failure
US6038619A (en) * 1997-05-29 2000-03-14 International Business Machines Corporation Disk drive initiated data transfers responsive to sequential or near sequential read or write requests
US6578113B2 (en) 1997-06-02 2003-06-10 At&T Corp. Method for cache validation for proxy caches
US6092158A (en) * 1997-06-13 2000-07-18 Intel Corporation Method and apparatus for arbitrating between command streams
US6047334A (en) 1997-06-17 2000-04-04 Intel Corporation System for delaying dequeue of commands received prior to fence command until commands received before fence command are ordered for execution in a fixed sequence
US6311256B2 (en) * 1997-06-30 2001-10-30 Emc Corporation Command insertion and reordering at the same storage controller
US6044438A (en) 1997-07-10 2000-03-28 International Business Machiness Corporation Memory controller for controlling memory accesses across networks in distributed shared memory processing systems
US5893086A (en) * 1997-07-11 1999-04-06 International Business Machines Corporation Parallel file system and method with extensible hashing
US6298401B1 (en) * 1997-08-11 2001-10-02 Seagate Technology Llc Object oriented storage device having a disc drive controller providing an interface exposing methods which are invoked to access objects stored in a storage media
US6000006A (en) * 1997-08-25 1999-12-07 Bit Microsystems, Inc. Unified re-map and cache-index table with dual write-counters for wear-leveling of non-volatile flash RAM mass storage
US6092215A (en) * 1997-09-29 2000-07-18 International Business Machines Corporation System and method for reconstructing data in a storage array system
US6014747A (en) 1997-09-30 2000-01-11 Intel Corporation Method and apparatus for system's and chassis protection utilizing system management interrupts
US6418478B1 (en) 1997-10-30 2002-07-09 Commvault Systems, Inc. Pipelined high speed data transfer mechanism
US6061678A (en) 1997-10-31 2000-05-09 Oracle Corporation Approach for managing access to large objects in database systems using large object indexes
US6205521B1 (en) 1997-11-03 2001-03-20 Compaq Computer Corporation Inclusion map for accelerated cache flush
US6334173B1 (en) 1997-11-17 2001-12-25 Hyundai Electronics Industries Co. Ltd. Combined cache with main memory and a control method thereof
US6470238B1 (en) 1997-11-26 2002-10-22 Intel Corporation Method and apparatus to control device temperature
US6237059B1 (en) 1997-11-26 2001-05-22 Compaq Computer Corporation Method for estimating statistics of properties of memory system interactions among contexts in a computer system
US6567889B1 (en) 1997-12-19 2003-05-20 Lsi Logic Corporation Apparatus and method to provide virtual solid state disk in cache memory in a storage controller
US6374336B1 (en) 1997-12-24 2002-04-16 Avid Technology, Inc. Computer system and process for transferring multiple high bandwidth streams of data between multiple storage units and multiple applications in a scalable and reliable manner
US6415373B1 (en) * 1997-12-24 2002-07-02 Avid Technology, Inc. Computer system and process for transferring multiple high bandwidth streams of data between multiple storage units and multiple applications in a scalable and reliable manner
US6725331B1 (en) 1998-01-07 2004-04-20 Emc Corporation Method and apparatus for managing the dynamic assignment resources in a data storage system
US6748487B1 (en) 1998-02-04 2004-06-08 Hitachi, Ltd. Disk cache control method, disk array system, and storage system
US6115793A (en) 1998-02-11 2000-09-05 Ati Technologies, Inc. Mapping logical cache indexes to physical cache indexes to reduce thrashing and increase cache size
US6292844B1 (en) 1998-02-12 2001-09-18 Sony Corporation Media storage device with embedded data filter for dynamically processing data during read and write operations
US7200623B2 (en) 1998-11-24 2007-04-03 Oracle International Corp. Methods to perform disk writes in a distributed shared disk system needing consistency across failures
US6112319A (en) * 1998-02-20 2000-08-29 Micron Electronics, Inc. Method and system for verifying the accuracy of stored data
US6295581B1 (en) 1998-02-20 2001-09-25 Ati Technologies, Inc. Method and apparatus for assuring cache coherency
US5969986A (en) * 1998-06-23 1999-10-19 Invox Technology High-bandwidth read and write architectures for non-volatile memories
US6295577B1 (en) 1998-02-24 2001-09-25 Seagate Technology Llc Disc storage system having a non-volatile cache to store write data in the event of a power failure
US6170042B1 (en) 1998-02-24 2001-01-02 Seagate Technology Llc Disc drive data storage system and method for dynamically scheduling queued commands
US6170063B1 (en) 1998-03-07 2001-01-02 Hewlett-Packard Company Method for performing atomic, concurrent read and write operations on multiple storage devices
US7188001B2 (en) * 1998-03-23 2007-03-06 Cepheid System and method for temperature control
US6157963A (en) * 1998-03-24 2000-12-05 Lsi Logic Corp. System controller with plurality of memory queues for prioritized scheduling of I/O requests from priority assigned clients
US6138125A (en) * 1998-03-31 2000-10-24 Lsi Logic Corporation Block coding method and system for failure recovery in disk arrays
ATE210878T1 (en) * 1998-04-01 2001-12-15 Hewlett Packard Co DATA STORAGE DEVICE AND METHOD
US6209003B1 (en) 1998-04-15 2001-03-27 Inktomi Corporation Garbage collection in an object cache
US6467022B1 (en) * 1998-04-16 2002-10-15 International Business Machines Corporation Extending adapter memory with solid state disks in JBOD and RAID environments
US6101601A (en) * 1998-04-20 2000-08-08 International Business Machines Corporation Method and apparatus for hibernation within a distributed data processing system
US6219751B1 (en) * 1998-04-28 2001-04-17 International Business Machines Corporation Device level coordination of access operations among multiple raid control units
US5957158A (en) 1998-05-11 1999-09-28 Automatic Switch Company Visual position indicator
US6321263B1 (en) * 1998-05-11 2001-11-20 International Business Machines Corporation Client-based application availability
US6061511A (en) * 1998-06-12 2000-05-09 Ikos Systems, Inc. Reconstruction engine for a hardware circuit emulator
US6883063B2 (en) * 1998-06-30 2005-04-19 Emc Corporation Method and apparatus for initializing logical objects in a data storage system
JP2000020490A (en) * 1998-07-01 2000-01-21 Fujitsu Ltd Computer having remote procedure calling mechanism or object request broker mechanism, data transfer method and transfer method storage medium
US6505305B1 (en) * 1998-07-16 2003-01-07 Compaq Information Technologies Group, L.P. Fail-over of multiple memory blocks in multiple memory modules in computer system
US6185654B1 (en) * 1998-07-17 2001-02-06 Compaq Computer Corporation Phantom resource memory address mapping system
KR100385370B1 (en) 1998-07-21 2003-05-27 시게이트 테크놀로지 엘엘씨 Improved memory system apparatus and method
US6507911B1 (en) 1998-07-22 2003-01-14 Entrust Technologies Limited System and method for securely deleting plaintext data
US7170906B2 (en) 1998-07-22 2007-01-30 Synchrodyne Networks, Inc. Time-based grooming and degrooming methods with common time reference for optical networks
US6374266B1 (en) * 1998-07-28 2002-04-16 Ralph Shnelvar Method and apparatus for storing information in a data processing system
US20010042195A1 (en) 1998-08-04 2001-11-15 Ralph M. Kling Method and apparatus for performing predicate prediction
US6353878B1 (en) 1998-08-13 2002-03-05 Emc Corporation Remote control of backup media in a secondary storage subsystem through access to a primary storage subsystem
JP2000076117A (en) * 1998-08-31 2000-03-14 Kano Densan Hongkong Yugenkoshi Electronic device, control method therefor and storage medium
US6269382B1 (en) 1998-08-31 2001-07-31 Microsoft Corporation Systems and methods for migration and recall of data from local and remote storage
US6209088B1 (en) * 1998-09-21 2001-03-27 Microsoft Corporation Computer hibernation implemented by a computer operating system
KR100331542B1 (en) * 1998-10-09 2002-06-20 윤종용 Semiconductor memory device including address decoder capable of skipping defective memory cell array blocks and merged memory with logic device using the same
JP2000122814A (en) * 1998-10-15 2000-04-28 Hitachi Ltd Method and device for secondarily storing expanded network connection
KR100285967B1 (en) 1998-10-20 2001-04-16 윤덕용 Data storage device and method using flash memory
FR2785693B1 (en) 1998-11-06 2000-12-15 Bull Sa DEVICE AND METHOD FOR WRITE SECURE WRITE DISC FOR HARD DISCS IN MASS MEMORY SUBSYSTEM
US6928505B1 (en) * 1998-11-12 2005-08-09 Edwin E. Klingman USB device controller
US6279041B1 (en) 1998-11-13 2001-08-21 International Business Machines Corporation Methods, systems and computer program products for differencing data communications using a message queue
US6034882A (en) * 1998-11-16 2000-03-07 Matrix Semiconductor, Inc. Vertically stacked field programmable nonvolatile memory and method of fabrication
EP1135727A1 (en) 1998-11-25 2001-09-26 Sun Microsystems, Inc. A method for enabling comprehensive profiling of garbage-collected memory systems
US6470436B1 (en) 1998-12-01 2002-10-22 Fast-Chip, Inc. Eliminating memory fragmentation and garbage collection from the process of managing dynamically allocated memory
US7233977B2 (en) 1998-12-18 2007-06-19 Emc Corporation Messaging mechanism employing mailboxes for inter processor communications
US6189078B1 (en) 1998-12-22 2001-02-13 Unisys Corporation System and method for increasing data transfer throughput for cache purge transactions using multiple data response indicators to maintain processor consistency
US6629112B1 (en) * 1998-12-31 2003-09-30 Nortel Networks Limited Resource management for CORBA-based applications
US6601151B1 (en) * 1999-02-08 2003-07-29 Sun Microsystems, Inc. Apparatus and method for handling memory access requests in a data processing system
US6618451B1 (en) 1999-02-13 2003-09-09 Altocom Inc Efficient reduced state maximum likelihood sequence estimator
GB9903490D0 (en) 1999-02-17 1999-04-07 Memory Corp Plc Memory system
US6571312B1 (en) * 1999-02-19 2003-05-27 Mitsubishi Denki Kabushiki Kaisha Data storage method and data processing device using an erasure block buffer and write buffer for writing and erasing data in memory
US6795890B1 (en) 1999-02-19 2004-09-21 Mitsubishi Denki Kabushiki Kaisha Data storage method, and data processing device using an erasure block buffer and write buffer for writing and erasing data in memory
US6347341B1 (en) * 1999-02-22 2002-02-12 International Business Machines Corporation Computer program product used for exchange and transfer of data having a siga vector and utilizing a queued direct input-output device
US6412080B1 (en) 1999-02-23 2002-06-25 Microsoft Corporation Lightweight persistent storage system for flash memory devices
US6321345B1 (en) * 1999-03-01 2001-11-20 Seachange Systems, Inc. Slow response in redundant arrays of inexpensive disks
MY122279A (en) * 1999-03-03 2006-04-29 Sony Corp Nonvolatile memory and nonvolatile memory reproducing apparatus
JP2000259525A (en) 1999-03-10 2000-09-22 Nec Corp Response returning method for communication protocol, and communication controller
US6295571B1 (en) 1999-03-19 2001-09-25 Times N Systems, Inc. Shared memory apparatus and method for multiprocessor systems
US6535869B1 (en) 1999-03-23 2003-03-18 International Business Machines Corporation Increasing efficiency of indexing random-access files composed of fixed-length data blocks by embedding a file index therein
US6141249A (en) 1999-04-01 2000-10-31 Lexar Media, Inc. Organization of blocks within a nonvolatile memory unit to effectively decrease sector write operation time
ATE340405T1 (en) * 1999-04-01 2006-10-15 Lexar Media Inc SPACE MANAGEMENT IN HIGH-CAPACITY NON-VOLATILE MEMORY
US6412030B1 (en) 1999-04-16 2002-06-25 Koninklijke Philips Electronics N.V. System and method to optimize read performance while accepting write data in a PCI bus architecture
US6535949B1 (en) 1999-04-19 2003-03-18 Research In Motion Limited Portable electronic device having a log-structured file system in flash memory
US6105076A (en) 1999-04-23 2000-08-15 International Business Machines Corporation Method, system, and program for performing data transfer operations on user data
KR100330164B1 (en) 1999-04-27 2002-03-28 윤종용 A method for simultaneously programming plural flash memories having invalid blocks
US6341289B1 (en) * 1999-05-06 2002-01-22 International Business Machines Corporation Object identity and partitioning for user defined extents
US6849480B1 (en) 1999-05-07 2005-02-01 Seagate Technology Llc Surface mount IC stacking method and device
US6535997B1 (en) 1999-05-19 2003-03-18 International Business Machines Corporation Data integrity in smartcard transactions
US7194740B1 (en) 1999-05-28 2007-03-20 Oracle International Corporation System for extending an addressable range of memory
JP4106811B2 (en) 1999-06-10 2008-06-25 富士通株式会社 Semiconductor memory device and electronic device
TW443083B (en) 1999-06-23 2001-06-23 Asustek Comp Inc Printed circuit board structure
US6557084B2 (en) 1999-07-13 2003-04-29 International Business Machines Corporation Apparatus and method to improve performance of reads from and writes to shared memory locations
US6513112B1 (en) 1999-07-26 2003-01-28 Microsoft Corporation System and apparatus for administration of configuration information using a catalog server object to describe and manage requested configuration information to be stored in a table object
US20040230710A1 (en) 1999-07-27 2004-11-18 Inline Connection Corporation System and method of automatic installation of computer peripherals
JP2001043031A (en) * 1999-07-30 2001-02-16 Toshiba Corp Disk array controller provided with distributed parity generating function
EP1073064A1 (en) * 1999-07-30 2001-01-31 STMicroelectronics S.r.l. Non-volatile memory with the functional capability of simultaneous modification of the contents and burst mode read or page mode read
US7620769B2 (en) 2000-01-06 2009-11-17 Super Talent Electronics, Inc. Recycling partially-stale flash blocks using a sliding window for multi-level-cell (MLC) flash memory
US7457897B1 (en) * 2004-03-17 2008-11-25 Suoer Talent Electronics, Inc. PCI express-compatible controller and interface for flash memory
US7889544B2 (en) * 2004-04-05 2011-02-15 Super Talent Electronics, Inc. High-speed controller for phase-change memory peripheral device
US8078794B2 (en) 2000-01-06 2011-12-13 Super Talent Electronics, Inc. Hybrid SSD using a combination of SLC and MLC flash memory arrays
US7934074B2 (en) 1999-08-04 2011-04-26 Super Talent Electronics Flash module with plane-interleaved sequential writes to restricted-write flash chips
US7660941B2 (en) 2003-09-10 2010-02-09 Super Talent Electronics, Inc. Two-level RAM lookup table for block and page allocation and wear-leveling in limited-write flash-memories
US6336174B1 (en) 1999-08-09 2002-01-01 Maxtor Corporation Hardware assisted memory backup system and method
KR100577380B1 (en) 1999-09-29 2006-05-09 삼성전자주식회사 A flash-memory and a it's controling method
JP3756708B2 (en) * 1999-09-30 2006-03-15 株式会社東芝 Information processing terminal device and file management method thereof
US6779145B1 (en) * 1999-10-01 2004-08-17 Stmicroelectronics Limited System and method for communicating with an integrated circuit
US6401175B1 (en) * 1999-10-01 2002-06-04 Sun Microsystems, Inc. Shared write buffer for use by multiple processor units
US6742078B1 (en) 1999-10-05 2004-05-25 Feiya Technology Corp. Management, data link structure and calculating method for flash memory
EP1100001B1 (en) 1999-10-25 2003-08-13 Sun Microsystems, Inc. Storage system supporting file-level and block-level accesses
AU2746001A (en) 1999-10-25 2001-05-08 Infolibria, Inc. Fast indexing of web objects
US6496366B1 (en) 1999-10-26 2002-12-17 Rackable Systems, Llc High density computer equipment storage system
US6850408B1 (en) 1999-10-26 2005-02-01 Rackable Systems, Inc. High density computer equipment storage systems
US6278633B1 (en) 1999-11-05 2001-08-21 Multi Level Memory Technology High bandwidth flash memory that selects programming parameters according to measurements of previous programming operations
US6684274B1 (en) 1999-11-09 2004-01-27 Sun Microsystems, Inc. Host bus adapter based scalable performance storage architecture
US20020049883A1 (en) 1999-11-29 2002-04-25 Eric Schneider System and method for restoring a computer system after a failure
US6405201B1 (en) * 1999-12-02 2002-06-11 Sun Microsystems, Inc. Method and apparatus for reducing network traffic for remote file append operations
DE19961499A1 (en) 1999-12-20 2001-07-05 Ericsson Telefon Ab L M Caching objects in disk-based databases
US7024695B1 (en) * 1999-12-30 2006-04-04 Intel Corporation Method and apparatus for secure remote system management
US20060161725A1 (en) 2005-01-20 2006-07-20 Lee Charles C Multiple function flash memory system
US20080195798A1 (en) 2000-01-06 2008-08-14 Super Talent Electronics, Inc. Non-Volatile Memory Based Computer Systems and Methods Thereof
US8266367B2 (en) 2003-12-02 2012-09-11 Super Talent Electronics, Inc. Multi-level striping and truncation channel-equalization for flash-memory system
US20050204187A1 (en) 2004-03-11 2005-09-15 Lee Charles C. System and method for managing blocks in flash memory
US8171204B2 (en) 2000-01-06 2012-05-01 Super Talent Electronics, Inc. Intelligent solid-state non-volatile memory device (NVMD) system with multi-level caching of multiple channels
US20080320209A1 (en) 2000-01-06 2008-12-25 Super Talent Electronics, Inc. High Performance and Endurance Non-volatile Memory Based Storage Systems
US8452912B2 (en) 2007-10-11 2013-05-28 Super Talent Electronics, Inc. Flash-memory system with enhanced smart-storage switch and packed meta-data cache for mitigating write amplification by delaying and merging writes until a host read
US6779080B2 (en) * 2000-01-11 2004-08-17 International Business Machines Corporation Serial data storage system with automatically adjusted data protection to implement worm media with limited overwrite allowing write appending
TW504694B (en) * 2000-01-12 2002-10-01 Hitachi Ltd Non-volatile semiconductor memory device and semiconductor disk device
US6671757B1 (en) * 2000-01-26 2003-12-30 Fusionone, Inc. Data transfer and synchronization system
US6785835B2 (en) * 2000-01-25 2004-08-31 Hewlett-Packard Development Company, L.P. Raid memory
US6757291B1 (en) * 2000-02-10 2004-06-29 Simpletech, Inc. System for bypassing a server to achieve higher throughput between data network and data storage system
USD475705S1 (en) 2000-02-18 2003-06-10 Rackable Systems, Inc. Computer chassis for dual, opposing main boards
EP1128267A1 (en) * 2000-02-25 2001-08-29 Hewlett-Packard Company, A Delaware Corporation Disk storage system having redundant solid state data storage devices
EP1130516A1 (en) 2000-03-01 2001-09-05 Hewlett-Packard Company, A Delaware Corporation Address mapping in solid state storage device
JP2001250044A (en) * 2000-03-07 2001-09-14 Nec Corp System and method for electronic commercial transaction and recording medium for recording electronic commercial transaction program
US6609212B1 (en) 2000-03-09 2003-08-19 International Business Machines Corporation Apparatus and method for sharing predictive failure information on a computer network
US6240040B1 (en) * 2000-03-15 2001-05-29 Advanced Micro Devices, Inc. Multiple bank simultaneous operation for a flash memory
US6823398B1 (en) * 2000-03-31 2004-11-23 Dphi Acquisitions, Inc. File system management embedded in a storage device
US6587937B1 (en) 2000-03-31 2003-07-01 Rockwell Collins, Inc. Multiple virtual machine system with efficient cache memory design
JP2001297316A (en) 2000-04-14 2001-10-26 Mitsubishi Electric Corp Memory card and control method therefor
US6523102B1 (en) 2000-04-14 2003-02-18 Interactive Silicon, Inc. Parallel compression/decompression system and method for implementation of in-memory compressed cache improving storage density and access speed for industry standard memory subsystems and in-line memory modules
US7089391B2 (en) * 2000-04-14 2006-08-08 Quickshift, Inc. Managing a codec engine for memory compression/decompression operations using a data movement engine
US6643748B1 (en) * 2000-04-20 2003-11-04 Microsoft Corporation Programmatic masking of storage units
US6487636B1 (en) * 2000-04-24 2002-11-26 Hewlett-Packard Co. Method and apparatus for mapping data in a heterogeneous disk array storage system
US6697797B1 (en) 2000-04-28 2004-02-24 Micro Data Base Systems, Inc. Method and apparatus for tracking data in a database, employing last-known location registers
US6420215B1 (en) 2000-04-28 2002-07-16 Matrix Semiconductor, Inc. Three-dimensional memory array and method of fabrication
JP4601119B2 (en) * 2000-05-02 2010-12-22 株式会社アドバンテスト Memory test method and memory test equipment
KR100399034B1 (en) 2000-05-02 2003-09-22 한국과학기술원 The Efficient Management of Memory Cell Array
US6675349B1 (en) * 2000-05-11 2004-01-06 International Business Machines Corporation Error correction coding of data blocks with included parity bits
US6775790B2 (en) 2000-06-02 2004-08-10 Hewlett-Packard Development Company, L.P. Distributed fine-grained enhancements for distributed table driven I/O mapping
US6865657B1 (en) 2000-06-02 2005-03-08 Sun Microsystems, Inc. Garbage collector for a virtual heap
US6763440B1 (en) 2000-06-02 2004-07-13 Sun Microsystems, Inc. Garbage collection using nursery regions for new objects in a virtual heap
US6751769B2 (en) 2000-06-06 2004-06-15 International Business Machines Corporation (146,130) error correction code utilizing address information
US6804755B2 (en) 2000-06-19 2004-10-12 Storage Technology Corporation Apparatus and method for performing an instant copy of data based on a dynamically changeable virtual mapping scheme
US6532527B2 (en) 2000-06-19 2003-03-11 Storage Technology Corporation Using current recovery mechanisms to implement dynamic mapping operations
US6779094B2 (en) * 2000-06-19 2004-08-17 Storage Technology Corporation Apparatus and method for instant copy of data by writing new data to an additional physical storage area
US6912537B2 (en) 2000-06-20 2005-06-28 Storage Technology Corporation Dynamically changeable virtual mapping scheme
US6813686B1 (en) 2000-06-27 2004-11-02 Emc Corporation Method and apparatus for identifying logical volumes in multiple element computer storage domains
US6859824B1 (en) 2000-06-30 2005-02-22 Hitachi, Ltd. Storage system connected to a data network with data integrity
US6525926B1 (en) 2000-07-11 2003-02-25 Racklogic Technologies, Inc. Multinode high density computing apparatus
US6981070B1 (en) * 2000-07-12 2005-12-27 Shun Hang Luk Network storage device having solid-state non-volatile memory
US6567307B1 (en) 2000-07-21 2003-05-20 Lexar Media, Inc. Block management for mass storage
US7167944B1 (en) 2000-07-21 2007-01-23 Lexar Media, Inc. Block management for mass storage
US6675318B1 (en) * 2000-07-25 2004-01-06 Sun Microsystems, Inc. Two-dimensional storage array with prompt parity in one dimension and delayed parity in a second dimension
US6892298B2 (en) 2000-07-26 2005-05-10 Times N Systems, Inc. Load/store micropacket handling system
US6883044B1 (en) 2000-07-28 2005-04-19 Micron Technology, Inc. Synchronous flash memory with simultaneous access to one or more banks
US7085445B2 (en) 2000-08-04 2006-08-01 Seungug Koh Micro-opto-electro-mechanical waveguide switches
JP2002056671A (en) * 2000-08-14 2002-02-22 Hitachi Ltd Method for holding data for dynamic ram and semiconductor integrated circuit device
JP4397109B2 (en) * 2000-08-14 2010-01-13 富士通株式会社 Information processing apparatus and crossbar board unit / back panel assembly manufacturing method
US6658438B1 (en) 2000-08-14 2003-12-02 Matrix Semiconductor, Inc. Method for deleting stored digital data from write-once memory device
EP1312120A1 (en) 2000-08-14 2003-05-21 Matrix Semiconductor, Inc. Dense arrays and charge storage devices, and methods for making same
JP3671138B2 (en) 2000-08-17 2005-07-13 ジャパンコンポジット株式会社 Breathable waterproof covering structure and construction method thereof
US6636879B1 (en) 2000-08-18 2003-10-21 Network Appliance, Inc. Space allocation in a write anywhere file system
US6404647B1 (en) * 2000-08-24 2002-06-11 Hewlett-Packard Co. Solid-state mass memory storage device
US7155559B1 (en) 2000-08-25 2006-12-26 Lexar Media, Inc. Flash memory architecture with separate storage of overhead and user data
US6728866B1 (en) 2000-08-31 2004-04-27 International Business Machines Corporation Partitioned issue queue and allocation strategy
US6883079B1 (en) 2000-09-01 2005-04-19 Maxtor Corporation Method and apparatus for using data compression as a means of increasing buffer bandwidth
AU2001290547A1 (en) 2000-09-11 2002-03-26 Jinglong F. Zhang A method and apparatus employing one-way transforms
US20040236798A1 (en) 2001-09-11 2004-11-25 Sudhir Srinivasan Migration of control in a distributed segmented file system
US6625685B1 (en) 2000-09-20 2003-09-23 Broadcom Corporation Memory controller with programmable configuration
US6725342B1 (en) 2000-09-26 2004-04-20 Intel Corporation Non-volatile mass storage cache coherency apparatus
JP3922516B2 (en) 2000-09-28 2007-05-30 株式会社ルネサステクノロジ Nonvolatile memory and writing method of nonvolatile memory
US6745284B1 (en) * 2000-10-02 2004-06-01 Sun Microsystems, Inc. Data storage subsystem including a storage disk array employing dynamic data striping
JP4413406B2 (en) 2000-10-03 2010-02-10 株式会社東芝 Nonvolatile semiconductor memory and test method thereof
US7039727B2 (en) 2000-10-17 2006-05-02 Microsoft Corporation System and method for controlling mass storage class digital imaging devices
DE60041263D1 (en) * 2000-10-18 2009-02-12 St Microelectronics Srl Nested memory device with random and sequential access
US20030021417A1 (en) * 2000-10-20 2003-01-30 Ognjen Vasic Hidden link dynamic key manager for use in computer systems with database structure for storage of encrypted data and method for storage and retrieval of encrypted data
US6594712B1 (en) * 2000-10-20 2003-07-15 Banderacom, Inc. Inifiniband channel adapter for performing direct DMA between PCI bus and inifiniband link
US6779088B1 (en) * 2000-10-24 2004-08-17 International Business Machines Corporation Virtual uncompressed cache size control in compressed memory systems
US7185162B1 (en) 2000-10-26 2007-02-27 Cypress Semiconductor Corporation Method and apparatus for programming a flash memory
US7248691B1 (en) 2000-10-31 2007-07-24 Microsoft Corporation Hashing using multiple sub-hashes
US6694453B1 (en) 2000-11-14 2004-02-17 Hewlett-Packard Development Company, L.P. Apparatus and method to handle power supply failures for a peripheral device
US6549987B1 (en) 2000-11-16 2003-04-15 Intel Corporation Cache structure for storing variable length data
US20020154633A1 (en) 2000-11-22 2002-10-24 Yeshik Shin Communications architecture for storage-based devices
US6564288B2 (en) 2000-11-30 2003-05-13 Hewlett-Packard Company Memory controller with temperature sensors
JP4216457B2 (en) 2000-11-30 2009-01-28 富士通マイクロエレクトロニクス株式会社 Semiconductor memory device and semiconductor device
US6745310B2 (en) 2000-12-01 2004-06-01 Yan Chiew Chow Real time local and remote management of data files and directories and method of operating the same
US6976060B2 (en) 2000-12-05 2005-12-13 Agami Sytems, Inc. Symmetric shared file storage system
US7020739B2 (en) 2000-12-06 2006-03-28 Tdk Corporation Memory controller, flash memory system having memory controller and method for controlling flash memory device
JP2002184190A (en) 2000-12-11 2002-06-28 Toshiba Corp Non-volatile semiconductor memory
US20020103819A1 (en) 2000-12-12 2002-08-01 Fresher Information Corporation Technique for stabilizing data in a non-log based information storage and retrieval system
US20020108016A1 (en) * 2000-12-13 2002-08-08 Seagate Technology Llc System for characterizing performance of data handling systems under particular stimuli
US6938252B2 (en) 2000-12-14 2005-08-30 International Business Machines Corporation Hardware-assisted method for scheduling threads using data cache locality
US7013376B2 (en) 2000-12-20 2006-03-14 Hewlett-Packard Development Company, L.P. Method and system for data block sparing in a solid-state storage device
SE0004736D0 (en) * 2000-12-20 2000-12-20 Ericsson Telefon Ab L M Mapping system and method
US7107480B1 (en) 2000-12-22 2006-09-12 Simpletech, Inc. System and method for preventing data corruption in solid-state memory devices after a power failure
US6611836B2 (en) 2000-12-26 2003-08-26 Simdesk Technologies, Inc. Server-side recycle bin system
KR100365725B1 (en) 2000-12-27 2002-12-26 한국전자통신연구원 Ranked Cleaning Policy and Error Recovery Method for File Systems Using Flash Memory
EP1220228B1 (en) 2000-12-29 2008-12-24 STMicroelectronics S.r.l. Method for storing data in a nonvolatile memory
KR100708475B1 (en) 2001-01-08 2007-04-18 삼성전자주식회사 Pre-Decoder for recovering a punctured turbo code and a method therefor
US6553472B2 (en) 2001-01-12 2003-04-22 Sun Microsystems, Inc. Method for programming clock delays, command delays, read command parameter delays, and write command parameter delays of a memory controller in a high performance microprocessor
US6763424B2 (en) 2001-01-19 2004-07-13 Sandisk Corporation Partial block data programming and reading operations in a non-volatile memory
JP4818812B2 (en) 2006-05-31 2011-11-16 株式会社日立製作所 Flash memory storage system
GB2383853A (en) * 2001-01-26 2003-07-09 Xmg Ltd A method system and apparatus for networking devices over an asynchronous network such as the internet
US6990547B2 (en) * 2001-01-29 2006-01-24 Adaptec, Inc. Replacing file system processors by hot swapping
US20020174295A1 (en) * 2001-01-29 2002-11-21 Ulrich Thomas R. Enhanced file system failure tolerance
US6862692B2 (en) * 2001-01-29 2005-03-01 Adaptec, Inc. Dynamic redistribution of parity groups
US6516380B2 (en) * 2001-02-05 2003-02-04 International Business Machines Corporation System and method for a log-based non-volatile write cache in a storage controller
US6606690B2 (en) * 2001-02-20 2003-08-12 Hewlett-Packard Development Company, L.P. System and method for accessing a storage area network as network attached storage
US20040233910A1 (en) 2001-02-23 2004-11-25 Wen-Shyen Chen Storage area network using a data communication protocol
US6795895B2 (en) * 2001-03-07 2004-09-21 Canopy Group Dual axis RAID systems for enhanced bandwidth and reliability
US6802023B2 (en) * 2001-03-15 2004-10-05 Hewlett-Packard Development Company, L.P. Redundant controller data storage system having hot insertion system and method
US6779045B2 (en) * 2001-03-21 2004-08-17 Intel Corporation System and apparatus for increasing the number of operations per transmission for a media management system
US6965638B2 (en) 2001-04-17 2005-11-15 Texas Instruments Incorporated Increasing performance in modems in presence of noise
US7260820B1 (en) 2001-04-26 2007-08-21 Vm Ware, Inc. Undefeatable transformation for virtual machine I/O operations
US6742081B2 (en) * 2001-04-30 2004-05-25 Sun Microsystems, Inc. Data storage array employing block checksums and dynamic striping
WO2002091586A2 (en) 2001-05-08 2002-11-14 International Business Machines Corporation 8b/10b encoding and decoding for high speed applications
US9077760B2 (en) * 2001-05-22 2015-07-07 Accenture Global Services Limited Broadband communications
US6824393B2 (en) * 2001-05-29 2004-11-30 International Business Machines Corporation Fragmented backplane system for I/O applications
US7062644B2 (en) * 2001-05-30 2006-06-13 International Business Machines Corporation Method, system, and program for initializing a storage device comprising multiple storage units through a storage controller
US6684301B1 (en) 2001-05-31 2004-01-27 Lsi Logic Corporation Out of order execution memory access request FIFO
US6731447B2 (en) 2001-06-04 2004-05-04 Xerox Corporation Secure data file erasure
US6876656B2 (en) * 2001-06-15 2005-04-05 Broadcom Corporation Switch assisted frame aliasing for storage virtualization
JP3976227B2 (en) * 2001-06-18 2007-09-12 日立ソフトウエアエンジニアリング株式会社 Terminal data erasure management method and program.
JP4256600B2 (en) * 2001-06-19 2009-04-22 Ｔｄｋ株式会社 MEMORY CONTROLLER, FLASH MEMORY SYSTEM PROVIDED WITH MEMORY CONTROLLER, AND FLASH MEMORY CONTROL METHOD
US7107430B2 (en) 2001-06-19 2006-09-12 Massachusetts Institute Of Technology Mechanism to reduce the cost of forwarding pointer aliasing
JP2003006041A (en) 2001-06-20 2003-01-10 Hitachi Ltd Semiconductor device
US6839808B2 (en) * 2001-07-06 2005-01-04 Juniper Networks, Inc. Processing cluster having multiple compute engines and shared tier one caches
US6694281B2 (en) * 2001-07-12 2004-02-17 Seagate Technology Llc Real time signal analysis of a remote block data storage device
US7076510B2 (en) * 2001-07-12 2006-07-11 Brown William P Software raid methods and apparatuses including server usage based write delegation
US6950966B2 (en) * 2001-07-17 2005-09-27 Seachange International, Inc. Data transmission from raid services
US7036068B2 (en) 2001-07-25 2006-04-25 Hewlett-Packard Development Company, L.P. Error correction coding and decoding in a solid-state storage device
US6785776B2 (en) 2001-07-26 2004-08-31 International Business Machines Corporation DMA exclusive cache state providing a fully pipelined input/output DMA write mechanism
US6556440B2 (en) 2001-07-26 2003-04-29 Dell Products L.P. Dishrack shroud for shielding and cooling
JP4156817B2 (en) 2001-07-27 2008-09-24 株式会社日立製作所 Storage system
US6996668B2 (en) 2001-08-06 2006-02-07 Seagate Technology Llc Synchronized mirrored data in a data storage device
US20030033463A1 (en) * 2001-08-10 2003-02-13 Garnett Paul J. Computer system storage
US6525953B1 (en) * 2001-08-13 2003-02-25 Matrix Semiconductor, Inc. Vertically-stacked, field-programmable, nonvolatile memory and method of fabrication
US7165005B2 (en) * 2001-08-14 2007-01-16 National Instruments Corporation Measurement module interface protocol database and registration system
US7013232B2 (en) * 2001-08-15 2006-03-14 National Insurance Corporation Network-based system for configuring a measurement system using configuration information generated based on a user specification
JP4583755B2 (en) 2001-08-30 2010-11-17 富士通株式会社 Printed board unit and electronic device
US6735546B2 (en) 2001-08-31 2004-05-11 Matrix Semiconductor, Inc. Memory device and method for temperature-based control over write and/or read operations
US7275135B2 (en) 2001-08-31 2007-09-25 Intel Corporation Hardware updated metadata for non-volatile mass storage cache
US6760805B2 (en) 2001-09-05 2004-07-06 M-Systems Flash Disk Pioneers Ltd. Flash management system for large page size
US7177197B2 (en) 2001-09-17 2007-02-13 Sandisk Corporation Latched programming of memory and method
US6845465B2 (en) * 2001-09-17 2005-01-18 Sun Microsystems, Inc. Method and system for leveraging spares in a data storage system including a plurality of disk drives
KR100437610B1 (en) 2001-09-20 2004-06-30 주식회사 하이닉스반도체 A low power semiconductor memory device with normal mode and partial array self refresh mode
US20030061296A1 (en) 2001-09-24 2003-03-27 International Business Machines Corporation Memory semantic storage I/O
US20030058681A1 (en) 2001-09-27 2003-03-27 Intel Corporation Mechanism for efficient wearout counters in destructive readout memory
US6938133B2 (en) 2001-09-28 2005-08-30 Hewlett-Packard Development Company, L.P. Memory latency and bandwidth optimizations
GB0123415D0 (en) 2001-09-28 2001-11-21 Memquest Ltd Method of writing data to non-volatile memory
GB0123416D0 (en) 2001-09-28 2001-11-21 Memquest Ltd Non-volatile memory control
US6823417B2 (en) * 2001-10-01 2004-11-23 Hewlett-Packard Development Company, L.P. Memory controller for memory card manages file allocation table
US6892264B2 (en) 2001-10-05 2005-05-10 International Business Machines Corporation Storage area network methods and apparatus for associating a logical identification with a physical identification
US6515909B1 (en) 2001-10-05 2003-02-04 Micron Technology Inc. Flash memory device with a variable erase pulse
US7000063B2 (en) 2001-10-05 2006-02-14 Matrix Semiconductor, Inc. Write-many memory device and method for limiting a number of writes to the write-many memory device
US6643181B2 (en) 2001-10-24 2003-11-04 Saifun Semiconductors Ltd. Method for erasing a memory cell
US6552955B1 (en) 2001-10-30 2003-04-22 Mitsubishi Denki Kabushiki Kaisha Semiconductor memory device with reduced power consumption
US6710901B2 (en) 2001-11-02 2004-03-23 Canadian Production Promotion Group Inc. Method and apparatus for two-photon, volumetric spatially resolved holographic data storage in photosensitive glass
US6754800B2 (en) 2001-11-14 2004-06-22 Sun Microsystems, Inc. Methods and apparatus for implementing host-based object storage schemes
US20030093741A1 (en) 2001-11-14 2003-05-15 Cenk Argon Parallel decoder for product codes
US6977847B2 (en) 2001-11-23 2005-12-20 M-Systems Flash Disk Pioneers Ltd. Detecting partially erased units in flash devices
US7136436B2 (en) 2001-11-28 2006-11-14 Texas Instruments Incorporated Boundary detection using multiple correlations
US6715046B1 (en) * 2001-11-29 2004-03-30 Cisco Technology, Inc. Method and apparatus for reading from and writing to storage using acknowledged phases of sets of data
US7173929B1 (en) 2001-12-10 2007-02-06 Incipient, Inc. Fast path for performing data operations
US7013379B1 (en) 2001-12-10 2006-03-14 Incipient, Inc. I/O primitives
US6883068B2 (en) 2001-12-17 2005-04-19 Sun Microsystems, Inc. Methods and apparatus for implementing a chche replacement scheme
US7548975B2 (en) 2002-01-09 2009-06-16 Cisco Technology, Inc. Methods and apparatus for implementing virtualization of storage within a storage area network through a virtual enclosure
US7036043B2 (en) 2001-12-28 2006-04-25 Storage Technology Corporation Data management with virtual recovery mapping and backward moves
US6839819B2 (en) 2001-12-28 2005-01-04 Storage Technology Corporation Data management appliance
US6697076B1 (en) 2001-12-31 2004-02-24 Apple Computer, Inc. Method and apparatus for address re-mapping
US6925573B2 (en) 2002-01-02 2005-08-02 Intel Corporation Method and apparatus to manage use of system power within a given specification
US6785078B2 (en) * 2002-01-04 2004-08-31 International Business Machines Corporation Concurrent read and write access to simulated sequential data of a removable random access data storage medium
JP4061272B2 (en) 2002-01-09 2008-03-12 株式会社ルネサステクノロジ Memory system and memory card
US20030130969A1 (en) 2002-01-10 2003-07-10 Intel Corporation Star intelligent platform management bus topology
US7069349B2 (en) * 2002-01-10 2006-06-27 Intel Corporation IPMI dual-domain controller
TWI257085B (en) 2002-01-21 2006-06-21 Koninkl Philips Electronics Nv Method of encoding and decoding
JP4154893B2 (en) 2002-01-23 2008-09-24 株式会社日立製作所 Network storage virtualization method
US20030145230A1 (en) * 2002-01-31 2003-07-31 Huimin Chiu System for exchanging data utilizing remote direct memory access
US6839826B2 (en) 2002-02-06 2005-01-04 Sandisk Corporation Memory device with pointer structure to map logical to physical addresses
US6748504B2 (en) 2002-02-15 2004-06-08 International Business Machines Corporation Deferred copy-on-write of a snapshot
US6724640B1 (en) 2002-02-15 2004-04-20 Steve Cooper Blade armor shielding
US6871257B2 (en) 2002-02-22 2005-03-22 Sandisk Corporation Pipelined parallel programming operation in a non-volatile memory system
US7010662B2 (en) 2002-02-27 2006-03-07 Microsoft Corporation Dynamic data structures for tracking file system free space in a flash memory device
US6901499B2 (en) 2002-02-27 2005-05-31 Microsoft Corp. System and method for tracking data stored in a flash memory device
US20030163633A1 (en) 2002-02-27 2003-08-28 Aasheim Jered Donald System and method for achieving uniform wear levels in a flash memory device
US7533214B2 (en) 2002-02-27 2009-05-12 Microsoft Corporation Open architecture flash driver
US7085879B2 (en) 2002-02-27 2006-08-01 Microsoft Corporation Dynamic data structures for tracking data stored in a flash memory device
US7197567B1 (en) 2002-02-28 2007-03-27 Cisco Technology, Inc. Devices, softwares and methods for enabling SIP devices to operate in H.323 networks and H.323 devices to operate in sip networks
JP3722767B2 (en) * 2002-03-13 2005-11-30 三菱電機インフォメーションテクノロジー株式会社 Hard disk drive, computer
JP2003281071A (en) 2002-03-20 2003-10-03 Seiko Epson Corp Data transfer controller, electronic equipment and data transfer control method
US7010663B2 (en) 2002-03-22 2006-03-07 Sun Microsystems, Inc. Method and system for dividing a plurality of existing volumes of storage into a plurality of virtual logical units of storage
US6850969B2 (en) * 2002-03-27 2005-02-01 International Business Machined Corporation Lock-free file system
JP4042841B2 (en) * 2002-03-29 2008-02-06 富士通株式会社 Matrix arithmetic processing unit
US7421642B2 (en) 2002-04-05 2008-09-02 Seagate Technology Llc Method and apparatus for error detection
JP4050548B2 (en) 2002-04-18 2008-02-20 株式会社ルネサステクノロジ Semiconductor memory device
US6948102B2 (en) * 2002-04-29 2005-09-20 International Business Machines Corporation Predictive failure analysis for storage networks
US6707748B2 (en) 2002-05-07 2004-03-16 Ritek Corporation Back up power embodied non-volatile memory device
US7293196B2 (en) 2002-05-08 2007-11-06 Xiotech Corporation Method, apparatus, and system for preserving cache data of redundant storage controllers
US7149857B2 (en) * 2002-05-14 2006-12-12 Micron Technology, Inc. Out of order DRAM sequencer
US6751129B1 (en) 2002-05-21 2004-06-15 Sandisk Corporation Efficient read, write methods for multi-state memory
US6898667B2 (en) * 2002-05-23 2005-05-24 Hewlett-Packard Development Company, L.P. Managing data in a multi-level raid storage array
US6766432B2 (en) 2002-05-24 2004-07-20 Sun Microsystems, Inc. Memory management system supporting object deletion in non-volatile memory
US7013364B2 (en) * 2002-05-27 2006-03-14 Hitachi, Ltd. Storage subsystem having plural storage systems and storage selector for selecting one of the storage systems to process an access request
US7318173B1 (en) 2002-06-03 2008-01-08 National Semiconductor Corporation Embedded controller based BIOS boot ROM select
US20030229689A1 (en) 2002-06-06 2003-12-11 Microsoft Corporation Method and system for managing stored data on a computer network
US20040010612A1 (en) * 2002-06-11 2004-01-15 Pandya Ashish A. High performance IP processor using RDMA
JP2004021811A (en) * 2002-06-19 2004-01-22 Hitachi Ltd Disk controller using nonvolatile memory
US7043599B1 (en) 2002-06-20 2006-05-09 Rambus Inc. Dynamic memory supporting simultaneous refresh and data-access transactions
US6894931B2 (en) 2002-06-20 2005-05-17 Kabushiki Kaisha Toshiba Nonvolatile semiconductor memory device
US7562089B2 (en) * 2002-06-26 2009-07-14 Seagate Technology Llc Systems and methods for storing information to allow users to manage files
US6737675B2 (en) * 2002-06-27 2004-05-18 Matrix Semiconductor, Inc. High density 3D rail stack arrays
US7081377B2 (en) 2002-06-27 2006-07-25 Sandisk 3D Llc Three-dimensional memory
US7082495B2 (en) 2002-06-27 2006-07-25 Microsoft Corporation Method and apparatus to reduce power consumption and improve read/write performance of hard disk drives using non-volatile memory
JP2004030438A (en) 2002-06-27 2004-01-29 Renesas Technology Corp Microcomputer
JP4001516B2 (en) 2002-07-05 2007-10-31 富士通株式会社 Degeneration control device and method
US7305668B2 (en) * 2002-07-31 2007-12-04 Intel Corporation Secure method to perform computer system firmware updates
US6950952B2 (en) * 2002-08-01 2005-09-27 Intel Corporation Dynamic power level control based on a board latch state
US7051152B1 (en) * 2002-08-07 2006-05-23 Nvidia Corporation Method and system of improving disk access time by compression
US7043610B2 (en) 2002-08-19 2006-05-09 Aristos Logic Corporation System and method for maintaining cache coherency without external controller intervention
JP2004086295A (en) 2002-08-23 2004-03-18 Megawin Technology Co Ltd Nand type flash memory disk drive and method for logical address detection
KR100505638B1 (en) 2002-08-28 2005-08-03 삼성전자주식회사 Apparatus and method for saving and restoring of working context
US7130979B2 (en) 2002-08-29 2006-10-31 Micron Technology, Inc. Dynamic volume management
US7103731B2 (en) 2002-08-29 2006-09-05 International Business Machines Corporation Method, system, and program for moving data among storage units
US7882081B2 (en) * 2002-08-30 2011-02-01 Netapp, Inc. Optimized disk repository for the storage and retrieval of mostly sequential data
US20040054867A1 (en) * 2002-09-13 2004-03-18 Paulus Stravers Translation lookaside buffer
US7051174B2 (en) 2002-09-24 2006-05-23 International Business Machines Corporation Method, system, and program for restoring data in cache
US20040064558A1 (en) 2002-09-26 2004-04-01 Hitachi Ltd. Resource distribution management method over inter-networks
US7219169B2 (en) * 2002-09-30 2007-05-15 Sun Microsystems, Inc. Composite DMA disk controller for efficient hardware-assisted data transfer operations
JP4005895B2 (en) 2002-09-30 2007-11-14 株式会社東芝 Nonvolatile semiconductor memory device
JP4130615B2 (en) 2003-07-02 2008-08-06 株式会社日立製作所 Fault information management method and management server in a network having a storage device
US7200758B2 (en) * 2002-10-09 2007-04-03 Intel Corporation Encapsulation of a TCPA trusted platform module functionality within a server management coprocessor subsystem
US6822878B2 (en) 2002-10-09 2004-11-23 Hewlett-Packard Development Company, L.P. Circuit board support arrangement, method, and method for using the same
US7225247B2 (en) * 2002-10-17 2007-05-29 Intel Corporation Serial port redirection using a management controller
US20040260947A1 (en) * 2002-10-21 2004-12-23 Brady Gerard Anthony Methods and systems for analyzing security events
US7340566B2 (en) 2002-10-21 2008-03-04 Microsoft Corporation System and method for initializing a memory device from block oriented NAND flash
US6973531B1 (en) 2002-10-28 2005-12-06 Sandisk Corporation Tracking the most frequently erased blocks in non-volatile memory systems
US7171536B2 (en) 2002-10-28 2007-01-30 Sandisk Corporation Unusable block management within a non-volatile memory system
JP3929872B2 (en) 2002-10-30 2007-06-13 株式会社東芝 Cache memory, processor and cache control method
US7415565B2 (en) 2002-10-31 2008-08-19 Ring Technology Enterprises, Llc Methods and systems for a storage system with a program-controlled switch for routing data
US7085953B1 (en) * 2002-11-01 2006-08-01 International Business Machines Corporation Method and means for tolerating multiple dependent or arbitrary double disk failures in a disk array
JP4199519B2 (en) 2002-11-05 2008-12-17 パナソニック株式会社 Memory management device and memory management method
US7035974B2 (en) * 2002-11-06 2006-04-25 Synology Inc. RAID-5 disk having cache memory implemented using non-volatile RAM
US6996676B2 (en) 2002-11-14 2006-02-07 International Business Machines Corporation System and method for implementing an adaptive replacement cache policy
US7254676B2 (en) * 2002-11-15 2007-08-07 Intel Corporation Processor cache memory as RAM for execution of boot code
US6845053B2 (en) 2002-11-15 2005-01-18 Micron Technology, Inc. Power throughput adjustment in flash memory
US20040098544A1 (en) * 2002-11-15 2004-05-20 Gaither Blaine D. Method and apparatus for managing a memory system
CN100550155C (en) 2002-11-18 2009-10-14 松下电器产业株式会社 The method of error correction, Error Correction of Coding, data reproduction and data recording and circuit thereof
US7093101B2 (en) * 2002-11-21 2006-08-15 Microsoft Corporation Dynamic data structures for tracking file system free space in a flash memory device
JP2004171411A (en) 2002-11-21 2004-06-17 Hitachi Global Storage Technologies Netherlands Bv Data storage device and management method of buffer memory
US6836434B2 (en) 2002-11-21 2004-12-28 Micron Technology, Inc. Mode selection in a flash memory device
US7003620B2 (en) 2002-11-26 2006-02-21 M-Systems Flash Disk Pioneers Ltd. Appliance, including a flash memory, that is robust under power failure
US7152942B2 (en) 2002-12-02 2006-12-26 Silverbrook Research Pty Ltd Fixative compensation
US6922754B2 (en) 2002-12-09 2005-07-26 Infabric Technologies, Inc. Data-aware data flow manager
US7324614B2 (en) * 2002-12-18 2008-01-29 Texas Instruments Incorporated High speed decoder
US7552192B2 (en) 2002-12-18 2009-06-23 Ronnie Gerome Carmichael Massively parallel computer network-utilizing MPACT and multipoint parallel server (MPAS) technologies
US7069307B1 (en) * 2002-12-20 2006-06-27 Network Appliance, Inc. System and method for inband management of a virtual disk
KR100680626B1 (en) 2002-12-20 2007-02-09 인터내셔널 비지네스 머신즈 코포레이션 Secure system and method for san management in a non-trusted server environment
US6957158B1 (en) 2002-12-23 2005-10-18 Power Measurement Ltd. High density random access memory in an intelligent electric device
US6849905B2 (en) 2002-12-23 2005-02-01 Matrix Semiconductor, Inc. Semiconductor device with localized charge storage dielectric and method of making same
KR100502608B1 (en) 2002-12-24 2005-07-20 한국전자통신연구원 A Simplified Massage-Passing Decoder for Low-Density Parity-Check Codes
US7010645B2 (en) 2002-12-27 2006-03-07 International Business Machines Corporation System and method for sequentially staging received data to a write cache in advance of storing the received data
US6973551B1 (en) 2002-12-30 2005-12-06 Emc Corporation Data storage system having atomic memory operation
US7505321B2 (en) 2002-12-31 2009-03-17 Sandisk 3D Llc Programmable memory array structure incorporating series-connected transistor strings and methods for fabrication and operation of same
US7005350B2 (en) 2002-12-31 2006-02-28 Matrix Semiconductor, Inc. Method for fabricating programmable memory array structures incorporating series-connected transistor strings
EP1435576B1 (en) 2003-01-03 2013-03-20 Austria Card Plastikkarten und Ausweissysteme GmbH Method and apparatus for block-oriented memory management provided in smart card controllers
US7024551B2 (en) * 2003-01-07 2006-04-04 Sun Microsystems, Inc. Method and apparatus for updating boot code using a system controller
US6816917B2 (en) 2003-01-15 2004-11-09 Hewlett-Packard Development Company, L.P. Storage system with LUN virtualization
JP2004227098A (en) * 2003-01-20 2004-08-12 Hitachi Ltd Control method of storage device controller and storage device controller
US7664909B2 (en) * 2003-04-18 2010-02-16 Nextio, Inc. Method and apparatus for a shared I/O serial ATA controller
US7698483B2 (en) 2003-01-21 2010-04-13 Nextio, Inc. Switching apparatus and method for link initialization in a shared I/O environment
US20040148360A1 (en) 2003-01-24 2004-07-29 Hewlett-Packard Development Company Communication-link-attached persistent memory device
WO2004077219A2 (en) 2003-01-30 2004-09-10 Vaman Technologies (R & D) Limited System and method of mapping patterns of data, optimising disk read and write, verifying data integrity across clients and servers of different functionality having shared resources
US7065618B1 (en) 2003-02-14 2006-06-20 Google Inc. Leasing scheme for data-modifying operations
US7107419B1 (en) 2003-02-14 2006-09-12 Google Inc. Systems and methods for performing record append operations
US7181569B2 (en) 2003-02-26 2007-02-20 International Business Machines Corporation Method, system, and article of manufacture for writing on sequential storage media
US7526598B2 (en) 2003-03-03 2009-04-28 Sandisk Il, Ltd. Efficient flash memory device driver
JP2004265162A (en) * 2003-03-03 2004-09-24 Renesas Technology Corp Storage device and address management method
US6959369B1 (en) 2003-03-06 2005-10-25 International Business Machines Corporation Method, system, and program for data backup
US7227959B2 (en) 2003-03-10 2007-06-05 Shure Incorporated Multi-channel digital feedback reducer system
WO2004081794A1 (en) 2003-03-10 2004-09-23 Sharp Kabushiki Kaisha Data processing device, data processing program, and recording medium
US7076723B2 (en) 2003-03-14 2006-07-11 Quantum Corporation Error correction codes
JP2004278439A (en) 2003-03-17 2004-10-07 Toshiba Kyaria Kk Fluid machine
US8041878B2 (en) * 2003-03-19 2011-10-18 Samsung Electronics Co., Ltd. Flash file system
JP2004280752A (en) 2003-03-19 2004-10-07 Sony Corp Date storage device, management information updating method for data storage device, and computer program
KR100526178B1 (en) 2003-03-31 2005-11-03 삼성전자주식회사 Access apparatus and method using flash memory
US7197657B1 (en) 2003-04-03 2007-03-27 Advanced Micro Devices, Inc. BMC-hosted real-time clock and non-volatile RAM replacement
US7293165B1 (en) * 2003-04-03 2007-11-06 Advanced Micro Devices, Inc. BMC-hosted boot ROM interface
US7987249B2 (en) 2003-04-09 2011-07-26 Intel Corporation Soft system failure recovery for management consoles supporting ASF RMCP
JP2004310621A (en) 2003-04-10 2004-11-04 Hitachi Ltd File access method, and program for file access in storage system
US6865122B2 (en) * 2003-04-11 2005-03-08 Intel Corporation Reclaiming blocks in a block-alterable memory
CN100342377C (en) 2003-04-16 2007-10-10 华为技术有限公司 Method of raising officiency of data processing
US20040207440A1 (en) * 2003-04-17 2004-10-21 Naysen Robertson Electrical circuit for controling another circuit or system
WO2004095304A1 (en) * 2003-04-23 2004-11-04 Dot Hill Systems Corporation Network storage appliance with integrated redundant servers and storage controllers
US20040230866A1 (en) * 2003-04-30 2004-11-18 Hewlett-Packard Development Company, L.P. Test system for testing components of an open architecture modular computing system
US7281076B2 (en) 2003-04-30 2007-10-09 Hewlett-Packard Development Company, L.P. Form factor converter and tester in an open architecture modular computing system
US7610348B2 (en) 2003-05-07 2009-10-27 International Business Machines Distributed file serving architecture system with metadata storage virtualization and data access at the data server connection speed
JP4270371B2 (en) * 2003-05-09 2009-05-27 インターナショナル・ビジネス・マシーンズ・コーポレーション Storage system, control device, control method, and program
JP2004348818A (en) * 2003-05-20 2004-12-09 Sharp Corp Method and system for controlling writing in semiconductor memory device, and portable electronic device
US7320100B2 (en) 2003-05-20 2008-01-15 Cray Inc. Apparatus and method for memory with bit swapping on the fly and testing
US7035111B1 (en) 2003-05-23 2006-04-25 Hewlett-Packard Development Company, L.P. Circuit board orientation with different width portions
US7412449B2 (en) * 2003-05-23 2008-08-12 Sap Aktiengesellschaft File object storage and retrieval using hashing techniques
US7388904B2 (en) 2003-06-03 2008-06-17 Vativ Technologies, Inc. Near-end, far-end and echo cancellers in a multi-channel transceiver system
US7434097B2 (en) * 2003-06-05 2008-10-07 Copan System, Inc. Method and apparatus for efficient fault-tolerant disk drive replacement in raid storage systems
US7380081B2 (en) 2003-06-06 2008-05-27 Hewlett-Packard Development Company, L.P. Asynchronous data redundancy technique
US7380198B2 (en) * 2003-06-11 2008-05-27 International Business Machines Corporation System and method for detecting write errors in a storage device
US7263607B2 (en) * 2003-06-12 2007-08-28 Microsoft Corporation Categorizing electronic messages based on trust between electronic messaging entities
US7454555B2 (en) * 2003-06-12 2008-11-18 Rambus Inc. Apparatus and method including a memory device having multiple sets of memory banks with duplicated data emulating a fast access time, fixed latency memory device
US7243203B2 (en) * 2003-06-13 2007-07-10 Sandisk 3D Llc Pipeline circuit for low latency memory
US7047366B1 (en) 2003-06-17 2006-05-16 Emc Corporation QOS feature knobs
US7237141B2 (en) 2003-06-19 2007-06-26 Lsi Corporation Method for recovering data from a redundant storage object
US20060153026A1 (en) 2003-06-23 2006-07-13 Koninklijke Philips Electronics, N.V. Device and method for recording information
US6906961B2 (en) * 2003-06-24 2005-06-14 Micron Technology, Inc. Erase block data splitting
US7493226B2 (en) * 2003-06-26 2009-02-17 Hewlett-Packard Development Company, L.P. Method and construct for enabling programmable, integrated system margin testing
US7117326B2 (en) 2003-06-26 2006-10-03 Intel Corporation Tracking modifications to a memory
US20040267483A1 (en) * 2003-06-26 2004-12-30 Percer Benjamin Thomas Methods and systems for masking faults in a margin testing environment
US7437258B2 (en) * 2003-06-26 2008-10-14 Hewlett-Packard Development Company, L.P. Use of I2C programmable clock generator to enable frequency variation under BMC control
US7400996B2 (en) * 2003-06-26 2008-07-15 Benjamin Thomas Percer Use of I2C-based potentiometers to enable voltage rail variation under BMC control
US7275098B1 (en) 2003-06-27 2007-09-25 Emc Corporation Methods and apparatus for administering software modules in a storage area network management application
US20040268359A1 (en) * 2003-06-27 2004-12-30 Hanes David H. Computer-readable medium, method and computer system for processing input/output requests
US7010630B2 (en) * 2003-06-30 2006-03-07 International Business Machines Corporation Communicating to system management in a data processing system
US7373514B2 (en) 2003-07-23 2008-05-13 Intel Corporation High-performance hashing system
NZ544882A (en) * 2003-07-24 2008-06-30 Lucidyne Technologies Inc Wood tracking system by identification of surface characteristics
GB0320142D0 (en) 2003-08-28 2003-10-01 Ibm Data storage systems
US7149947B1 (en) 2003-09-04 2006-12-12 Emc Corporation Method of and system for validating an error correction code and parity information associated with a data word
US20050055495A1 (en) * 2003-09-05 2005-03-10 Nokia Corporation Memory wear leveling
JP2005108304A (en) 2003-09-29 2005-04-21 Toshiba Corp Semiconductor memory and its control method
US7483974B2 (en) 2003-09-24 2009-01-27 Intel Corporation Virtual management controller to coordinate processing blade management in a blade server environment
US7487235B2 (en) 2003-09-24 2009-02-03 Dell Products L.P. Dynamically varying a raid cache policy in order to optimize throughput
US20050091215A1 (en) 2003-09-29 2005-04-28 Chandra Tushar D. Technique for provisioning storage for servers in an on-demand environment
US20050071461A1 (en) * 2003-09-30 2005-03-31 Intel Corporation Proxy alerting
US7299354B2 (en) * 2003-09-30 2007-11-20 Intel Corporation Method to authenticate clients and hosts to provide secure network boot
IES20030722A2 (en) 2003-10-01 2005-04-06 Yqa Now Ltd A data storage device
US7173852B2 (en) * 2003-10-03 2007-02-06 Sandisk Corporation Corrected data storage and handling methods
JP4492084B2 (en) * 2003-10-07 2010-06-30 株式会社日立製作所 Storage path control method
JP2005115600A (en) * 2003-10-07 2005-04-28 Hitachi Ltd Information processor and method
US7337201B1 (en) 2003-10-08 2008-02-26 Sun Microsystems, Inc. System and method to increase memory allocation efficiency
US20050080887A1 (en) * 2003-10-08 2005-04-14 Chun-Liang Lee Redundant management control arbitration system
TWI238325B (en) 2003-10-09 2005-08-21 Quanta Comp Inc Apparatus of remote server console redirection
US7127560B2 (en) 2003-10-14 2006-10-24 International Business Machines Corporation Method of dynamically controlling cache size
US7096321B2 (en) 2003-10-21 2006-08-22 International Business Machines Corporation Method and system for a cache replacement technique with adaptive skipping
US20050091452A1 (en) * 2003-10-28 2005-04-28 Ying Chen System and method for reducing data loss in disk arrays by establishing data redundancy on demand
JP4379079B2 (en) * 2003-10-30 2009-12-09 ソニー株式会社 Data reproduction processing apparatus, information processing apparatus, information processing method, and computer program
US7143240B2 (en) 2003-10-31 2006-11-28 International Business Machines Corporation System and method for providing a cost-adaptive cache
US7428691B2 (en) * 2003-11-12 2008-09-23 Norman Ken Ouchi Data recovery from multiple failed data blocks and storage units
CA2544063C (en) 2003-11-13 2013-09-10 Commvault Systems, Inc. System and method for combining data streams in pilelined storage operations in a storage network
US7412583B2 (en) * 2003-11-14 2008-08-12 International Business Machines Corporation Virtual incremental storage method
EP1686482B1 (en) 2003-11-18 2013-03-06 Panasonic Corporation File recording device
JP4493321B2 (en) * 2003-11-19 2010-06-30 株式会社日立製作所 Disk array device and data saving method
US7171514B2 (en) 2003-11-20 2007-01-30 International Business Machines Corporation Apparatus and method to control access to logical volumes using parallel access volumes
US20050114595A1 (en) 2003-11-26 2005-05-26 Veritas Operating Corporation System and method for emulating operating system metadata to provide cross-platform access to storage volumes
US8112574B2 (en) 2004-02-26 2012-02-07 Super Talent Electronics, Inc. Swappable sets of partial-mapping tables in a flash-memory system with a command queue for combining flash writes
US7162571B2 (en) 2003-12-09 2007-01-09 Emc Corporation Methods and apparatus for parsing a content address to facilitate selection of a physical storage location in a data storage system
US8892821B2 (en) 2003-12-10 2014-11-18 International Business Machines Corporation Method and system for thread-based memory speculation in a memory subsystem of a data processing system
US7350127B2 (en) * 2003-12-12 2008-03-25 Hewlett-Packard Development Company, L.P. Error correction method and system
US20050149819A1 (en) 2003-12-15 2005-07-07 Daewoo Electronics Corporation Three-dimensional error correction method
US7500000B2 (en) 2003-12-17 2009-03-03 International Business Machines Corporation Method and system for assigning or creating a resource
US7822790B2 (en) * 2003-12-23 2010-10-26 International Business Machines Corporation Relative positioning and access of memory objects
US20050149618A1 (en) 2003-12-23 2005-07-07 Mobile Action Technology Inc. System and method of transmitting electronic files over to a mobile phone
US7464100B2 (en) 2003-12-24 2008-12-09 Sap Ag Reorganization-free mapping of objects in databases using a mapping chain
US7281114B2 (en) 2003-12-26 2007-10-09 Tdk Corporation Memory controller, flash memory system, and method of controlling operation for data exchange between host system and flash memory
JP4111910B2 (en) * 2003-12-26 2008-07-02 富士通株式会社 Disk cache device
US7418490B1 (en) * 2003-12-29 2008-08-26 Sun Microsystems, Inc. System using multiple sets of device management policies for managing network devices connected on different network interfaces
US7631138B2 (en) * 2003-12-30 2009-12-08 Sandisk Corporation Adaptive mode switching of flash memory address mapping based on host usage characteristics
US7139864B2 (en) * 2003-12-30 2006-11-21 Sandisk Corporation Non-volatile memory and method with block management system
US8504798B2 (en) * 2003-12-30 2013-08-06 Sandisk Technologies Inc. Management of non-volatile memory systems having large erase blocks
US7162560B2 (en) 2003-12-31 2007-01-09 Intel Corporation Partitionable multiprocessor system having programmable interrupt controllers
US8250295B2 (en) 2004-01-05 2012-08-21 Smart Modular Technologies, Inc. Multi-rank memory module that emulates a memory module having a different number of ranks
JP2005196410A (en) * 2004-01-06 2005-07-21 Sony Corp Data communication device and memory management method for data communication device
JP4401788B2 (en) * 2004-01-06 2010-01-20 株式会社日立製作所 Storage controller
US20050154786A1 (en) * 2004-01-09 2005-07-14 International Business Machines Corporation Ordering updates in remote copying of data
US7188229B2 (en) 2004-01-17 2007-03-06 Sun Microsystems, Inc. Method and apparatus for memory management in a multi-processor computer system
US7328307B2 (en) 2004-01-22 2008-02-05 Tquist, Llc Method and apparatus for improving update performance of non-uniform access time persistent storage media
US7042664B2 (en) 2004-01-26 2006-05-09 Seagate Technology Llc Method and system for host programmable data storage device self-testing
JP4496790B2 (en) * 2004-01-26 2010-07-07 ソニー株式会社 Data storage device and method, and recording / reproducing system
JP4477365B2 (en) 2004-01-29 2010-06-09 株式会社日立製作所 Storage device having a plurality of interfaces and control method of the storage device
US7305520B2 (en) 2004-01-30 2007-12-04 Hewlett-Packard Development Company, L.P. Storage system with capability to allocate virtual storage segments among a plurality of controllers
US7356651B2 (en) 2004-01-30 2008-04-08 Piurata Technologies, Llc Data-aware cache state machine
US7064994B1 (en) 2004-01-30 2006-06-20 Sun Microsystems, Inc. Dynamic memory throttling for power and thermal limitations
US7389465B2 (en) 2004-01-30 2008-06-17 Micron Technology, Inc. Error detection and correction scheme for a memory device
JP4524120B2 (en) 2004-02-03 2010-08-11 富士通株式会社 Blade type optical transmission equipment
JP2005222234A (en) 2004-02-04 2005-08-18 Seiko Epson Corp Media converter, network type direct output system, and method for transferring output processing instruction
US7130957B2 (en) 2004-02-10 2006-10-31 Sun Microsystems, Inc. Storage system structure for storing relational cache metadata
US7231590B2 (en) 2004-02-11 2007-06-12 Microsoft Corporation Method and apparatus for visually emphasizing numerical data contained within an electronic document
US7873693B1 (en) * 2004-02-13 2011-01-18 Habanero Holdings, Inc. Multi-chassis fabric-backplane enterprise servers
CN100468362C (en) * 2004-02-20 2009-03-11 西门子能量及自动化公司 Method for initializing and utilizing a memory device for a plc
US7394271B2 (en) * 2004-02-27 2008-07-01 Wells-Cti, Llc Temperature sensing and prediction in IC sockets
DE102004011201B4 (en) * 2004-03-04 2006-10-12 Siemens Ag Method for managing and monitoring the operation of multiple distributed in at least one communication network integrated hardware and / or software systems and system for performing the method
US7289386B2 (en) 2004-03-05 2007-10-30 Netlist, Inc. Memory module decoder
US7532537B2 (en) 2004-03-05 2009-05-12 Netlist, Inc. Memory module with a circuit providing load isolation and memory domain translation
US7916574B1 (en) 2004-03-05 2011-03-29 Netlist, Inc. Circuit providing load isolation and memory domain translation for memory module
JP2005250938A (en) 2004-03-05 2005-09-15 Hitachi Ltd Storage control system and method
US7260695B2 (en) 2004-03-05 2007-08-21 International Business Machines Corporation Scanning modified data during power loss
US20080082736A1 (en) 2004-03-11 2008-04-03 Chow David Q Managing bad blocks in various flash memory cells for electronic data flash card
US20050201306A1 (en) * 2004-03-15 2005-09-15 Engel Glenn R. Method and system for supplying power to multiple devices using power-transmitting network connections
US7165144B2 (en) 2004-03-19 2007-01-16 Intel Corporation Managing input/output (I/O) requests in a cache memory system
US7720864B1 (en) 2004-03-25 2010-05-18 Symantec Operating Corporation Expiration of access tokens for quiescing a distributed system
JP2005316951A (en) * 2004-03-30 2005-11-10 Seiko Epson Corp Information terminal, information processing system, and control method therefor
JP2005293774A (en) 2004-04-02 2005-10-20 Hitachi Global Storage Technologies Netherlands Bv Control method of disk unit
US7281192B2 (en) 2004-04-05 2007-10-09 Broadcom Corporation LDPC (Low Density Parity Check) coded signal decoding using parallel and simultaneous bit node and check node processing
US7788460B2 (en) * 2004-04-13 2010-08-31 Intel Corporation Defragmenting objects in a storage medium
US7224545B2 (en) * 2004-04-15 2007-05-29 Quantum Corporation Methods and systems for overwrite protected storage media
KR100647370B1 (en) * 2004-04-20 2006-11-23 주식회사 하이닉스반도체 Multi-protocol serial interface system
US7725628B1 (en) * 2004-04-20 2010-05-25 Lexar Media, Inc. Direct secondary device interface by a host
US20050240713A1 (en) 2004-04-22 2005-10-27 V-Da Technology Flash memory device with ATA/ATAPI/SCSI or proprietary programming interface on PCI express
CA2564844C (en) * 2004-04-26 2014-12-09 Storewiz, Inc. Method and system for compression of files for storage and operation on compressed files
US8374175B2 (en) * 2004-04-27 2013-02-12 Hewlett-Packard Development Company, L.P. System and method for remote direct memory access over a network switch fabric
US7412614B2 (en) 2004-04-29 2008-08-12 Hewlett-Packard Development Company, L.P. Power management using a pre-determined thermal characteristic of a memory module
US7773521B2 (en) 2004-04-30 2010-08-10 Emc Corporation Storage switch traffic bandwidth control
US7430571B2 (en) 2004-04-30 2008-09-30 Network Appliance, Inc. Extension of write anywhere file layout write allocation
US7644239B2 (en) * 2004-05-03 2010-01-05 Microsoft Corporation Non-volatile memory cache performance improvement
US7370163B2 (en) 2004-05-03 2008-05-06 Gemini Storage Adaptive cache engine for storage area network including systems and methods related thereto
US7360015B2 (en) 2004-05-04 2008-04-15 Intel Corporation Preventing storage of streaming accesses in a cache
US7386663B2 (en) 2004-05-13 2008-06-10 Cousins Robert E Transaction-based storage system and method that uses variable sized objects to store data
US20050257017A1 (en) * 2004-05-14 2005-11-17 Hideki Yagi Method and apparatus to erase hidden memory in a memory card
US7512830B2 (en) 2004-05-14 2009-03-31 International Business Machines Corporation Management module failover across multiple blade center chassis
US7831561B2 (en) 2004-05-18 2010-11-09 Oracle International Corporation Automated disk-oriented backups
TWI255426B (en) 2004-05-18 2006-05-21 Carry Computer Eng Co Ltd Storage control apparatus capable of analyzing volume information and the control method thereof
EP1769395A2 (en) * 2004-05-21 2007-04-04 Computer Associates Think, Inc. Object-based storage
JP2005339198A (en) 2004-05-27 2005-12-08 Internatl Business Mach Corp <Ibm> Caching hit ratio estimation system, caching hit ratio estimation method, program therefor, and recording medium therefor
US7009889B2 (en) 2004-05-28 2006-03-07 Sandisk Corporation Comprehensive erase verification for non-volatile memory
US7904181B2 (en) 2004-06-01 2011-03-08 Ils Technology Llc Model for communication between manufacturing and enterprise levels
US7502369B2 (en) * 2004-06-02 2009-03-10 Intel Corporation High speed interface systems and methods
JP2005346321A (en) 2004-06-02 2005-12-15 Hitachi Ltd Disk array apparatus and method for controlling battery output of disk array apparatus
US7590522B2 (en) * 2004-06-14 2009-09-15 Hewlett-Packard Development Company, L.P. Virtual mass storage device for server management information
US7386890B2 (en) 2004-06-30 2008-06-10 Intel Corporation Method and apparatus to preserve a hash value of an executable module
US7045717B2 (en) 2004-06-30 2006-05-16 International Business Machines Corporation High speed cable interconnect to a computer midplane
US7290116B1 (en) 2004-06-30 2007-10-30 Sun Microsystems, Inc. Level 2 cache index hashing to avoid hot spots
US7734643B1 (en) 2004-06-30 2010-06-08 Oracle America, Inc. Method for distributed storage of data
JP2006023854A (en) * 2004-07-06 2006-01-26 Sharp Corp Information processor, storage device, storage controller and program
JP2006031268A (en) * 2004-07-14 2006-02-02 Sharp Corp Information processor and storage controller
US7177883B2 (en) * 2004-07-15 2007-02-13 Hitachi, Ltd. Method and apparatus for hierarchical storage management based on data value and user interest
US7447847B2 (en) 2004-07-19 2008-11-04 Micron Technology, Inc. Memory device trims
US8607016B2 (en) 2004-07-21 2013-12-10 Sandisk Technologies Inc. FAT analysis for optimized sequential cluster management
US7395384B2 (en) * 2004-07-21 2008-07-01 Sandisk Corproation Method and apparatus for maintaining data on non-volatile memory systems
US7594471B2 (en) * 2004-07-21 2009-09-29 Detnet South Africa (Pty) Ltd. Blasting system and method of controlling a blasting operation
US20060020616A1 (en) 2004-07-22 2006-01-26 Geoffrey Hardy Indexing operational logs in a distributed processing system
US9264384B1 (en) 2004-07-22 2016-02-16 Oracle International Corporation Resource virtualization mechanism including virtual host bus adapters
US7366852B2 (en) * 2004-07-29 2008-04-29 Infortrend Technology, Inc. Method for improving data reading performance and storage system for performing the same
US7203815B2 (en) 2004-07-30 2007-04-10 International Business Machines Corporation Multi-level page cache for enhanced file system performance via read ahead
US8407396B2 (en) 2004-07-30 2013-03-26 Hewlett-Packard Development Company, L.P. Providing block data access for an operating system using solid-state memory
TWI300186B (en) 2004-07-30 2008-08-21 Mediatek Inc Method and apparatus for data recording with pseudo-merge
US7386700B2 (en) 2004-07-30 2008-06-10 Sandisk Il Ltd Virtual-to-physical address translation in a flash file system
US7213125B2 (en) 2004-07-31 2007-05-01 Hewlett-Packard Development Company, L.P. Method for patching virtually aliased pages by a virtual-machine monitor
JP2006048506A (en) * 2004-08-06 2006-02-16 Toshiba Corp Processor, memory management system, and memory management program
US7664239B2 (en) 2004-08-09 2010-02-16 Cox Communications, Inc. Methods and computer-readable media for managing and configuring options for the real-time notification and disposition of voice services in a cable services network
US20060036904A1 (en) * 2004-08-13 2006-02-16 Gemini Storage Data replication method over a limited bandwidth network by mirroring parities
JP4315876B2 (en) 2004-08-17 2009-08-19 富士通株式会社 File management program, file management method, and file management apparatus
US7340487B2 (en) 2004-08-18 2008-03-04 International Business Machines Corporation Delayed deletion of extended attributes
US7477570B2 (en) 2004-08-20 2009-01-13 Micron Technology, Inc. Sequential access memory with system and method
US7398348B2 (en) 2004-08-24 2008-07-08 Sandisk 3D Llc Method and apparatus for using a one-time or few-time programmable memory with a host device designed for erasable/rewritable memory
US20060047926A1 (en) 2004-08-25 2006-03-02 Zheng Calvin G Managing multiple snapshot copies of data
US20060075057A1 (en) 2004-08-30 2006-04-06 International Business Machines Corporation Remote direct memory access system and method
WO2006025322A1 (en) 2004-08-30 2006-03-09 Matsushita Electric Industrial Co., Ltd. Recorder
US7299339B2 (en) * 2004-08-30 2007-11-20 The Boeing Company Super-reconfigurable fabric architecture (SURFA): a multi-FPGA parallel processing architecture for COTS hybrid computing framework
JP4646574B2 (en) 2004-08-30 2011-03-09 株式会社日立製作所 Data processing system
US7241655B2 (en) 2004-08-30 2007-07-10 Micron Technology, Inc. Method of fabricating a vertical wrap-around-gate field-effect-transistor for high density, low voltage logic and memory array
JP4113170B2 (en) 2004-09-08 2008-07-09 株式会社東芝 Semiconductor device
JP4192129B2 (en) 2004-09-13 2008-12-03 株式会社東芝 Memory management device
WO2006030650A1 (en) 2004-09-16 2006-03-23 Nec Corporation Information processing device having a plurality of processing units sharing a resource
US7395452B2 (en) 2004-09-24 2008-07-01 Microsoft Corporation Method and system for improved reliability in storage devices
US7062624B2 (en) 2004-09-29 2006-06-13 Hitachi, Ltd. Method for managing volume groups considering storage tiers
US7444493B2 (en) * 2004-09-30 2008-10-28 Intel Corporation Address translation for input/output devices using hierarchical translation tables
JP4104586B2 (en) 2004-09-30 2008-06-18 株式会社東芝 File system having file management function and file management method
JP4648674B2 (en) 2004-10-01 2011-03-09 株式会社日立製作所 Storage control device, storage control system, and storage control method
US8655853B2 (en) 2004-10-01 2014-02-18 Sap Ag System and method for optimizing database transaction termination
GB2418769B (en) * 2004-10-02 2009-06-17 Hewlett Packard Development Co Method and system for storing data
US7603532B2 (en) 2004-10-15 2009-10-13 Netapp, Inc. System and method for reclaiming unused space from a thinly provisioned data container
US7257690B1 (en) 2004-10-15 2007-08-14 Veritas Operating Corporation Log-structured temporal shadow store
US20060090948A1 (en) 2004-10-18 2006-05-04 Allen Gregory T Driver side airbag detainment and containment device
US7308603B2 (en) 2004-10-18 2007-12-11 International Business Machines Corporation Method and system for reducing memory faults while running an operating system
US8131969B2 (en) 2004-10-20 2012-03-06 Seagate Technology Llc Updating system configuration information
US7328317B2 (en) * 2004-10-21 2008-02-05 International Business Machines Corporation Memory controller and method for optimized read/modify/write performance
US7565569B2 (en) 2004-10-22 2009-07-21 International Business Machines Corporation Data protection in a mass storage system
JP2006127028A (en) 2004-10-27 2006-05-18 Hitachi Ltd Memory system and storage controller
US7310711B2 (en) 2004-10-29 2007-12-18 Hitachi Global Storage Technologies Netherlands B.V. Hard disk drive with support for atomic transactions
ITMI20042072A1 (en) * 2004-10-29 2005-01-29 St Microelectronics Srl FLSH MEMORY DEVICE EQUIPPED WITH LOW PIN COUNT COMMUNICATION INTERFACE
US7318119B2 (en) * 2004-10-29 2008-01-08 International Business Machines Corporation System and method for fault tolerant controller for network RAID
KR100645058B1 (en) 2004-11-03 2006-11-10 삼성전자주식회사 Memory managing technique capable of improving data reliability
US7873782B2 (en) * 2004-11-05 2011-01-18 Data Robotics, Inc. Filesystem-aware block storage system, apparatus, and method
JP5116151B2 (en) 2004-11-05 2013-01-09 ドロボ， インコーポレイテッド A dynamically expandable and contractible fault-tolerant storage system using virtual hot spares
US20060106968A1 (en) 2004-11-15 2006-05-18 Wooi Teoh Gary C Intelligent platform management bus switch system
US7441067B2 (en) 2004-11-15 2008-10-21 Sandisk Corporation Cyclic flash memory wear leveling
US7430465B2 (en) * 2004-11-17 2008-09-30 Spx Corporation Open-ended PC host interface for vehicle data recorder
US7475274B2 (en) * 2004-11-17 2009-01-06 Raytheon Company Fault tolerance and recovery in a high-performance computing (HPC) system
US7337277B2 (en) 2004-11-18 2008-02-26 International Business Machines Corporation Apparatus, system, and method for flushing cache data
US7392428B2 (en) * 2004-11-19 2008-06-24 International Business Machines Corporation Method and system for recovering from abnormal interruption of a parity update operation in a disk array system
US7778984B2 (en) * 2004-11-19 2010-08-17 Microsoft Corporation System and method for a distributed object store
US8595459B2 (en) 2004-11-29 2013-11-26 Rambus Inc. Micro-threaded memory
JP4500318B2 (en) 2004-11-29 2010-07-14 富士通株式会社 Distributed transaction processing method, apparatus, and program
US7668883B2 (en) * 2004-11-30 2010-02-23 Kabushiki Kaisha Toshiba System for secure erasing of files
US7610307B2 (en) 2004-11-30 2009-10-27 Microsoft Corporation Method and system of detecting file system namespace changes and restoring consistency
US20060149954A1 (en) * 2004-12-03 2006-07-06 Matt Hageman Apparatus and method for accommodating different central processing units in a computer
JP2008523468A (en) * 2004-12-06 2008-07-03 テイアック エアロスペース テクノロジーズ インコーポレイテッド Non-volatile recording medium erasing system and method
US20060120235A1 (en) * 2004-12-06 2006-06-08 Teac Aerospace Technologies System and method of erasing non-volatile recording media
US8156281B1 (en) 2004-12-07 2012-04-10 Oracle America, Inc. Data storage system and method using storage profiles to define and modify storage pools
US8074041B2 (en) 2004-12-09 2011-12-06 International Business Machines Corporation Apparatus, system, and method for managing storage space allocation
US8495266B2 (en) 2004-12-10 2013-07-23 Hewlett-Packard Development Company, L.P. Distributed lock
US7694298B2 (en) * 2004-12-10 2010-04-06 Intel Corporation Method and apparatus for providing virtual server blades
US7120051B2 (en) 2004-12-14 2006-10-10 Sandisk Corporation Pipelined programming of non-volatile memories using early data
US7581118B2 (en) 2004-12-14 2009-08-25 Netapp, Inc. Disk sanitization using encryption
US7487320B2 (en) 2004-12-15 2009-02-03 International Business Machines Corporation Apparatus and system for dynamically allocating main memory among a plurality of applications
JP3810425B2 (en) 2004-12-16 2006-08-16 松下電器産業株式会社 Falsification detection data generation method, and falsification detection method and apparatus
US7366826B2 (en) 2004-12-16 2008-04-29 Sandisk Corporation Non-volatile memory and method with multi-stream update tracking
US20060136685A1 (en) 2004-12-17 2006-06-22 Sanrad Ltd. Method and system to maintain data consistency over an internet small computer system interface (iSCSI) network
US7739290B2 (en) 2004-12-17 2010-06-15 Sap (Ag) System and method for object persistence
KR100662256B1 (en) 2004-12-20 2006-12-28 한국전자통신연구원 Object-based Storage Device and its control method for having low process load
US7409473B2 (en) 2004-12-21 2008-08-05 Sandisk Corporation Off-chip data relocation
US8122193B2 (en) 2004-12-21 2012-02-21 Samsung Electronics Co., Ltd. Storage device and user device including the same
KR100684887B1 (en) 2005-02-04 2007-02-20 삼성전자주식회사 Data storing device including flash memory and merge method of thereof
KR100876084B1 (en) 2007-02-13 2008-12-26 삼성전자주식회사 Computing system capable of delivering deletion information to flash storage
US8301810B2 (en) 2004-12-21 2012-10-30 Infortrend Technology, Inc. SAS storage virtualization controller, subsystem and system using the same, and method therefor
US7392429B2 (en) 2004-12-22 2008-06-24 Microsoft Corporation System and method for maintaining persistent state data
US7472309B2 (en) 2004-12-22 2008-12-30 Intel Corporation Methods and apparatus to write a file to a nonvolatile memory
US20060136657A1 (en) 2004-12-22 2006-06-22 Intel Corporation Embedding a filesystem into a non-volatile device
US20060143396A1 (en) 2004-12-29 2006-06-29 Mason Cabot Method for programmer-controlled cache line eviction policy
US7441081B2 (en) 2004-12-29 2008-10-21 Lsi Corporation Write-back caching for disk drives
US20060139330A1 (en) * 2004-12-29 2006-06-29 Kutch Patrick G Adaptive mouse re-direction
US20060143209A1 (en) * 2004-12-29 2006-06-29 Zimmer Vincent J Remote management of a computer system
US7254672B1 (en) 2004-12-30 2007-08-07 Storage Technology Corporation Translation device driver for translating between disk device driver and tape device driver commands
US7246195B2 (en) 2004-12-30 2007-07-17 Intel Corporation Data storage management for flash memory devices
CN1277213C (en) * 2004-12-31 2006-09-27 大唐微电子技术有限公司 A flash memory file system management method
KR100725390B1 (en) 2005-01-06 2007-06-07 삼성전자주식회사 Apparatus and method for storing data in nonvolatile cache memory considering update ratio
KR100621631B1 (en) 2005-01-11 2006-09-13 삼성전자주식회사 Solid state disk controller apparatus
US20060159456A1 (en) 2005-01-18 2006-07-20 Fujitsu Limited System and method for conserving resources in an optical storage area network
US7689599B1 (en) 2005-01-31 2010-03-30 Symantec Operating Corporation Repair of inconsistencies between data and metadata stored on a temporal volume using transaction log replay
US9104315B2 (en) 2005-02-04 2015-08-11 Sandisk Technologies Inc. Systems and methods for a mass data storage system having a file-based interface to a host and a non-file-based interface to secondary storage
US20060184719A1 (en) 2005-02-16 2006-08-17 Sinclair Alan W Direct data file storage implementation techniques in flash memories
US7877539B2 (en) 2005-02-16 2011-01-25 Sandisk Corporation Direct data file storage in flash memories
US20060184718A1 (en) 2005-02-16 2006-08-17 Sinclair Alan W Direct file data programming and deletion in flash memories
US7426649B2 (en) 2005-02-09 2008-09-16 International Business Machines Corporation Power management via DIMM read operation limiter
EP1851861A2 (en) 2005-02-14 2007-11-07 Koninklijke Philips Electronics N.V. Block interleaving with memory table of reduced size
US20060184736A1 (en) 2005-02-17 2006-08-17 Benhase Michael T Apparatus, system, and method for storing modified data
US20060190552A1 (en) 2005-02-24 2006-08-24 Henze Richard H Data retention system with a plurality of access protocols
US7487343B1 (en) * 2005-03-04 2009-02-03 Netapp, Inc. Method and apparatus for boot image selection and recovery via a remote management module
US7747836B2 (en) 2005-03-08 2010-06-29 Netapp, Inc. Integrated storage virtualization and switch system
US7269534B2 (en) * 2005-03-11 2007-09-11 Dell Products L.P. Method to reduce IPMB traffic and improve performance for accessing sensor data
US8446892B2 (en) 2005-03-16 2013-05-21 Qualcomm Incorporated Channel structures for a quasi-orthogonal multiple-access communication system
US20060212644A1 (en) 2005-03-21 2006-09-21 Acton John D Non-volatile backup for data cache
US8745011B2 (en) 2005-03-22 2014-06-03 International Business Machines Corporation Method and system for scrubbing data within a data storage subsystem
US7254686B2 (en) 2005-03-31 2007-08-07 International Business Machines Corporation Switching between mirrored and non-mirrored volumes
US7522457B2 (en) 2005-03-31 2009-04-21 Sandisk Corporation Systems for erase voltage manipulation in non-volatile memory for controlled shifts in threshold voltage
US7408804B2 (en) 2005-03-31 2008-08-05 Sandisk Corporation Systems for soft programming non-volatile memory utilizing individual verification and additional soft programming of subsets of memory cells
US7457166B2 (en) 2005-03-31 2008-11-25 Sandisk Corporation Erase voltage manipulation in non-volatile memory for controlled shifts in threshold voltage
US7463521B2 (en) 2005-04-01 2008-12-09 Sandisk Corporation Method for non-volatile memory with managed execution of cached data
US7702928B2 (en) 2005-04-08 2010-04-20 Hewlett-Packard Development Company, L.P. Memory module with on-board power-consumption monitoring
US7451344B1 (en) 2005-04-08 2008-11-11 Western Digital Technologies, Inc. Optimizing order of error recovery steps in a disk drive
KR101077992B1 (en) 2005-04-11 2011-10-31 엘지전자 주식회사 Home Network Control System and Data Flow Control Method of Above the Home Network Control System
US7620773B2 (en) 2005-04-15 2009-11-17 Microsoft Corporation In-line non volatile memory disk read cache and write buffer
US20060236061A1 (en) 2005-04-18 2006-10-19 Creek Path Systems Systems and methods for adaptively deriving storage policy and configuration rules
US8452929B2 (en) * 2005-04-21 2013-05-28 Violin Memory Inc. Method and system for storage of data in non-volatile media
US9286198B2 (en) 2005-04-21 2016-03-15 Violin Memory Method and system for storage of data in non-volatile media
US7130960B1 (en) 2005-04-21 2006-10-31 Hitachi, Ltd. System and method for managing disk space in a thin-provisioned storage subsystem
US7620741B2 (en) * 2005-04-22 2009-11-17 Sun Microsystems, Inc. Proxy-based device sharing
US7702873B2 (en) 2005-04-25 2010-04-20 Network Appliance, Inc. Managing common storage by allowing delayed allocation of storage after reclaiming reclaimable space in a logical volume
US7366825B2 (en) 2005-04-26 2008-04-29 Microsoft Corporation NAND flash memory management
US7743210B1 (en) 2005-04-29 2010-06-22 Netapp, Inc. System and method for implementing atomic cross-stripe write operations in a striped volume set
US7523546B2 (en) 2005-05-04 2009-04-28 Nokia Corporation Method for manufacturing a composite layer for an electronic device
US7370261B2 (en) * 2005-05-09 2008-05-06 International Business Machines Corporation Convolution-encoded raid with trellis-decode-rebuild
US7707232B2 (en) 2005-05-13 2010-04-27 Microsoft Corporation Implementation for collecting unmanaged memory
JP2006324754A (en) 2005-05-17 2006-11-30 Fujitsu Ltd Maximum a posteriori probability decoding method and decoder thereof
US20060265636A1 (en) 2005-05-19 2006-11-23 Klaus Hummler Optimized testing of on-chip error correction circuit
US7752381B2 (en) 2005-05-24 2010-07-06 Micron Technology, Inc. Version based non-volatile memory translation layer
KR101268984B1 (en) 2005-05-26 2013-05-29 삼성전자주식회사 Storage medium including application for providing meta data, apparatus for providing meta data and method therefor
US20060293045A1 (en) 2005-05-27 2006-12-28 Ladue Christoph K Evolutionary synthesis of a modem for band-limited non-linear channels
JP2006331158A (en) 2005-05-27 2006-12-07 Hitachi Ltd Storage system
US7383392B2 (en) 2005-05-31 2008-06-03 Hewlett-Packard Development Company, L.P. Performing read-ahead operation for a direct input/output request
US7536529B1 (en) 2005-06-10 2009-05-19 American Megatrends, Inc. Method, system, apparatus, and computer-readable medium for provisioning space in a data storage system
US7444526B2 (en) 2005-06-16 2008-10-28 International Business Machines Corporation Performance conserving method for reducing power consumption in a server system
US7590799B2 (en) * 2005-06-16 2009-09-15 Seagate Technology Llc OSD deterministic object fragmentation optimization in a disc drive
US7930589B2 (en) 2005-06-17 2011-04-19 Analog Devices, Inc. Interrupt-responsive non-volatile memory system and method
US20060294300A1 (en) 2005-06-22 2006-12-28 Seagate Technology Llc Atomic cache transactions in a distributed storage system
US20070027948A1 (en) * 2005-06-23 2007-02-01 International Business Machines Corporation Server blades connected via a wireless network
US7590796B2 (en) 2006-07-31 2009-09-15 Metaram, Inc. System and method for power management in memory systems
US20080082763A1 (en) 2006-10-02 2008-04-03 Metaram, Inc. Apparatus and method for power management of memory circuits by a system or component thereof
US7533330B2 (en) * 2005-06-27 2009-05-12 Seagate Technology Llc Redundancy for storage data structures
US7340665B2 (en) 2005-06-28 2008-03-04 Seagate Technology Llc Shared redundancy in error correcting code
US20070006048A1 (en) 2005-06-29 2007-01-04 Intel Corporation Method and apparatus for predicting memory failure in a memory system
US7457910B2 (en) 2005-06-29 2008-11-25 Sandisk Corproation Method and system for managing partitions in a storage device
US7743217B2 (en) 2005-06-29 2010-06-22 Stmicroelectronics S.A. Cache consistency in a multiprocessor system with shared memory
US7797479B2 (en) * 2005-06-30 2010-09-14 Intel Corporation Technique to write to a non-volatile memory
US7774542B2 (en) 2005-07-06 2010-08-10 Ji Zhang System and method for adaptive operation of storage capacities of RAID systems
US7716387B2 (en) * 2005-07-14 2010-05-11 Canon Kabushiki Kaisha Memory control apparatus and method
US7555676B2 (en) * 2005-07-18 2009-06-30 Dell Products L.P. Systems and methods for providing remotely accessible in-system emulation and/or debugging
US7895398B2 (en) 2005-07-19 2011-02-22 Dell Products L.P. System and method for dynamically adjusting the caching characteristics for each logical unit of a storage array
WO2007013051A1 (en) * 2005-07-25 2007-02-01 Surf Communication Solutions, Ltd. Communication processor board
JP5162846B2 (en) 2005-07-29 2013-03-13 ソニー株式会社 Storage device, computer system, and storage system
US20070028051A1 (en) 2005-08-01 2007-02-01 Arm Limited Time and power reduction in cache accesses
US7552271B2 (en) * 2005-08-03 2009-06-23 Sandisk Corporation Nonvolatile memory with block management
US7984084B2 (en) 2005-08-03 2011-07-19 SanDisk Technologies, Inc. Non-volatile memory with scheduled reclaim operations
US7480766B2 (en) 2005-08-03 2009-01-20 Sandisk Corporation Interfacing systems operating through a logical address space and on a direct data file basis
US20070033371A1 (en) * 2005-08-04 2007-02-08 Andrew Dunshea Method and apparatus for establishing a cache footprint for shared processor logical partitions
US8417915B2 (en) 2005-08-05 2013-04-09 Arm Limited Alias management within a virtually indexed and physically tagged cache memory
US7480771B2 (en) 2005-08-17 2009-01-20 Sun Microsystems, Inc. Conditional synchronization mechanisms allowing multiple store operations to become visible while a flagged memory location is owned and remains unchanged
KR100739722B1 (en) 2005-08-20 2007-07-13 삼성전자주식회사 A method for managing a flash memory and a flash memory system
US7424577B2 (en) 2005-08-26 2008-09-09 Network Appliance, Inc. Dynamic optimization of cache memory
US7580287B2 (en) 2005-09-01 2009-08-25 Micron Technology, Inc. Program and read trim setting
JP5008845B2 (en) * 2005-09-01 2012-08-22 株式会社日立製作所 Storage system, storage apparatus and control method thereof
JP4701929B2 (en) * 2005-09-02 2011-06-15 株式会社日立製作所 Boot configuration change method, management server, and computer system
JP2007071805A (en) 2005-09-09 2007-03-22 Denso Corp Manufacturing method of dynamic quantity sensor
US7970015B2 (en) 2005-09-12 2011-06-28 Hob Gmbh & Co. Kg Method for transmitting a message by compressed data transmission between a sender and a receiver via a data network
US20070061508A1 (en) 2005-09-13 2007-03-15 Quantum Corporation Data storage cartridge with built-in tamper-resistant clock
US7934049B2 (en) 2005-09-14 2011-04-26 Sandisk Corporation Methods used in a secure yet flexible system architecture for secure devices with flash mass storage memory
US7979394B2 (en) 2005-09-20 2011-07-12 Teradata Us, Inc. Method of managing storage and retrieval of data objects
US7523378B2 (en) 2005-09-23 2009-04-21 Intel Corporation Techniques to determine integrity of information
US7424666B2 (en) * 2005-09-26 2008-09-09 Intel Corporation Method and apparatus to detect/manage faults in a system
KR100734629B1 (en) 2005-09-28 2007-07-03 한국전자통신연구원 Fractional caching method and adaptive content transmission method using the same
US7652922B2 (en) 2005-09-30 2010-01-26 Mosaid Technologies Incorporated Multiple independent serial link memory
US7437510B2 (en) 2005-09-30 2008-10-14 Intel Corporation Instruction-assisted cache management for efficient use of cache and memory
US8078588B2 (en) 2005-10-10 2011-12-13 Oracle International Corporation Recoverable execution
US7529905B2 (en) 2005-10-13 2009-05-05 Sandisk Corporation Method of storing transformed units of data in a memory system having fixed sized storage blocks
CN1863081B (en) * 2005-10-14 2010-05-05 华为技术有限公司 Managing system and method based on intelligent platform managing interface
US7631162B2 (en) 2005-10-27 2009-12-08 Sandisck Corporation Non-volatile memory with adaptive handling of data writes
US7457928B2 (en) 2005-10-28 2008-11-25 International Business Machines Corporation Mirroring system memory in non-volatile random access memory (NVRAM) for fast power on/off cycling
US20070100893A1 (en) 2005-10-31 2007-05-03 Sigmatel, Inc. System and method for accessing data from a memory device
US7516267B2 (en) * 2005-11-03 2009-04-07 Intel Corporation Recovering from a non-volatile memory failure
US7877554B2 (en) 2005-11-04 2011-01-25 Oracle America, Inc. Method and system for block reallocation
US7634585B2 (en) * 2005-11-04 2009-12-15 Sandisk Corporation In-line cache using nonvolatile memory between host and disk device
US8782186B2 (en) * 2005-11-12 2014-07-15 Hewlett-Packard Development Company, L.P. Systems and methods for addressing managed elements
US7624239B2 (en) 2005-11-14 2009-11-24 Sandisk Corporation Methods for the management of erase operations in non-volatile memories
US7739472B2 (en) 2005-11-22 2010-06-15 Sandisk Corporation Memory system for legacy hosts
US7366808B2 (en) 2005-11-23 2008-04-29 Hitachi, Ltd. System, method and apparatus for multiple-protocol-accessible OSD storage subsystem
US7526614B2 (en) 2005-11-30 2009-04-28 Red Hat, Inc. Method for tuning a cache
US8112513B2 (en) 2005-11-30 2012-02-07 Microsoft Corporation Multi-user display proxy server
US8799882B2 (en) 2005-12-07 2014-08-05 Microsoft Corporation Compiler support for optimizing decomposed software transactional memory operations
US7415575B1 (en) 2005-12-08 2008-08-19 Nvidia, Corporation Shared cache with client-specific replacement policy
US7877540B2 (en) 2005-12-13 2011-01-25 Sandisk Corporation Logically-addressed file storage methods
TW200722990A (en) * 2005-12-14 2007-06-16 Inventec Corp Power-on self test debugging system and method
US7814479B2 (en) * 2005-12-14 2010-10-12 International Business Machines Corporation Simultaneous download to multiple targets
US7376034B2 (en) 2005-12-15 2008-05-20 Stec, Inc. Parallel data storage system
JP4807063B2 (en) 2005-12-20 2011-11-02 ソニー株式会社 Decoding device, control method, and program
US8032745B2 (en) * 2005-12-20 2011-10-04 International Business Machines Corporation Authentication of I2C bus transactions
US7234964B1 (en) * 2005-12-20 2007-06-26 International Business Machines Corporation Systems, methods, and media for providing visual indication of a blade configuration
US20070143566A1 (en) 2005-12-21 2007-06-21 Gorobets Sergey A Non-volatile memories with data alignment in a directly mapped file storage system
US20070143567A1 (en) 2005-12-21 2007-06-21 Gorobets Sergey A Methods for data alignment in non-volatile memories with a directly mapped file storage system
US20070156998A1 (en) 2005-12-21 2007-07-05 Gorobets Sergey A Methods for memory allocation in non-volatile memories with a directly mapped file storage system
US7793068B2 (en) 2005-12-21 2010-09-07 Sandisk Corporation Dual mode access for non-volatile storage devices
US20070143560A1 (en) 2005-12-21 2007-06-21 Gorobets Sergey A Non-volatile memories with memory allocation for a directly mapped file storage system
US20070143561A1 (en) 2005-12-21 2007-06-21 Gorobets Sergey A Methods for adaptive file data handling in non-volatile memories with a directly mapped file storage system
US7747837B2 (en) 2005-12-21 2010-06-29 Sandisk Corporation Method and system for accessing non-volatile storage devices
US7831783B2 (en) 2005-12-22 2010-11-09 Honeywell International Inc. Effective wear-leveling and concurrent reclamation method for embedded linear flash file systems
US7440455B2 (en) 2005-12-22 2008-10-21 Level 3 Communications, Llc Registration of multiple VoIP devices
US7673111B2 (en) 2005-12-23 2010-03-02 Intel Corporation Memory system with both single and consolidated commands
US7907600B2 (en) 2005-12-23 2011-03-15 Qualcomm Incorporated System and method for optimizing robust header compression (ROHC) in high delay variance environment
US20070150663A1 (en) 2005-12-27 2007-06-28 Abraham Mendelson Device, system and method of multi-state cache coherence scheme
US8713551B2 (en) * 2006-01-03 2014-04-29 International Business Machines Corporation Apparatus, system, and method for non-interruptively updating firmware on a redundant hardware controller
US7849454B2 (en) * 2006-01-13 2010-12-07 Dell Products L.P. Automatic firmware corruption recovery and update
US7613898B2 (en) 2006-01-17 2009-11-03 Globalfoundries Inc. Virtualizing an IOMMU
US7793059B2 (en) 2006-01-18 2010-09-07 Apple Inc. Interleaving policies for flash memory
US8055979B2 (en) 2006-01-20 2011-11-08 Marvell World Trade Ltd. Flash memory with coding and signal processing
TWM298188U (en) 2006-01-23 2006-09-21 Genesys Logic Inc Control device for accessing Non-Volatile memory
US7827442B2 (en) * 2006-01-23 2010-11-02 Slt Logic Llc Shelf management controller with hardware/software implemented dual redundant configuration
US9002795B2 (en) 2006-01-26 2015-04-07 Seagate Technology Llc Object-based data storage device
US7676666B2 (en) * 2006-02-02 2010-03-09 Dell Products L.P. Virtual BIOS firmware hub
KR100746225B1 (en) 2006-02-13 2007-08-03 삼성전자주식회사 Semiconductor memory device and memory system comprising the same
KR100746033B1 (en) 2006-02-17 2007-08-06 삼성전자주식회사 Apparatus and method for measuring integrity
US20070220369A1 (en) * 2006-02-21 2007-09-20 International Business Machines Corporation Fault isolation and availability mechanism for multi-processor system
US8166539B2 (en) * 2006-02-24 2012-04-24 Dell Products L.P. Authentication of baseboard management controller users in a blade server system
KR100781520B1 (en) 2006-02-24 2007-12-03 삼성전자주식회사 Storage apparatus using non volatile memory as cache and mapping information recovering method for the same
EP1990727A4 (en) 2006-02-27 2009-08-05 Fujitsu Ltd Cache control apparatus and cache control program
KR20070089460A (en) 2006-02-28 2007-08-31 삼성전자주식회사 Apparatus and method for operating non-volatile memory according to priority
US7852873B2 (en) * 2006-03-01 2010-12-14 Lantronix, Inc. Universal computer management interface
JP2007233903A (en) * 2006-03-03 2007-09-13 Hitachi Ltd Storage controller and data recovery method for storage controller
US7344439B2 (en) 2006-03-06 2008-03-18 International Business Machines Corporation System, method, and apparatus for distributing air in a blade server
US20070208790A1 (en) 2006-03-06 2007-09-06 Reuter James M Distributed data-storage system
US7747925B2 (en) 2006-03-06 2010-06-29 Fujifilm Corporation Apparatus and method for error correction code striping
JP2007240904A (en) 2006-03-09 2007-09-20 Hitachi Ltd Plasma display device
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
US7562180B2 (en) 2006-03-28 2009-07-14 Nokia Corporation Method and device for reduced read latency of non-volatile memory
US20070245217A1 (en) 2006-03-28 2007-10-18 Stmicroelectronics S.R.L. Low-density parity check decoding
US7840398B2 (en) 2006-03-28 2010-11-23 Intel Corporation Techniques for unified management communication for virtualization systems
US7640249B2 (en) 2006-03-29 2009-12-29 Sap (Ag) System and method for transactional session management
US7551492B2 (en) 2006-03-29 2009-06-23 Mosaid Technologies, Inc. Non-volatile semiconductor memory with page erase
US7949863B2 (en) 2006-03-30 2011-05-24 Silicon Image, Inc. Inter-port communication in a multi-port memory device
US7831778B2 (en) 2006-03-30 2010-11-09 Silicon Image, Inc. Shared nonvolatile memory architecture
US7930439B2 (en) * 2006-03-31 2011-04-19 Panasonic Corporation Command output control apparatus
US7676628B1 (en) 2006-03-31 2010-03-09 Emc Corporation Methods, systems, and computer program products for providing access to shared storage by computing grids and clusters with large numbers of nodes
US20070233937A1 (en) 2006-03-31 2007-10-04 Coulson Richard L Reliability of write operations to a non-volatile memory
TW200739349A (en) 2006-04-12 2007-10-16 Giga Byte Tech Co Ltd Volatile storage device and serial connection type mixed storage device having the same
US7567472B2 (en) 2006-04-12 2009-07-28 Micron Technology, Inc. Memory block testing
JP4787055B2 (en) 2006-04-12 2011-10-05 富士通株式会社 Information processing apparatus with information division recording function
US7451264B2 (en) * 2006-04-13 2008-11-11 Sandisk Corporation Cycle count storage methods
US7395377B2 (en) 2006-04-20 2008-07-01 International Business Machines Corporation Method and system for adaptive back-off and advance for non-volatile storage (NVS) occupancy level management
US7636829B2 (en) 2006-05-02 2009-12-22 Intel Corporation System and method for allocating and deallocating memory within transactional code
US7509460B2 (en) 2006-05-04 2009-03-24 Sun Microsystems, Inc. DRAM remote access cache in local memory in a distributed shared memory system
US20070261030A1 (en) 2006-05-04 2007-11-08 Gaurav Wadhwa Method and system for tracking and prioritizing applications
US20070271468A1 (en) 2006-05-05 2007-11-22 Mckenney Paul E Method and Apparatus for Maintaining Data Integrity When Switching Between Different Data Protection Methods
US7653832B2 (en) 2006-05-08 2010-01-26 Emc Corporation Storage array virtualization using a storage block mapping protocol client and server
US7653778B2 (en) * 2006-05-08 2010-01-26 Siliconsystems, Inc. Systems and methods for measuring the useful life of solid-state storage devices
KR101202537B1 (en) 2006-05-12 2012-11-19 애플 인크. Combined distortion estimation and error correction coding for memory devices
US20070271495A1 (en) 2006-05-18 2007-11-22 Ian Shaeffer System to detect and identify errors in control information, read data and/or write data
US7424587B2 (en) 2006-05-23 2008-09-09 Dataram, Inc. Methods for managing data writes and reads to a hybrid solid-state disk drive
JP4681505B2 (en) 2006-05-23 2011-05-11 株式会社日立製作所 Computer system, management computer, and program distribution method
US7464240B2 (en) 2006-05-23 2008-12-09 Data Ram, Inc. Hybrid solid state disk drive with controller
CN101454685B (en) 2006-05-30 2012-09-05 皇家飞利浦电子股份有限公司 Detuning a radio-frequency coil
US8453147B2 (en) 2006-06-05 2013-05-28 Cisco Technology, Inc. Techniques for reducing thread overhead for systems with multiple multi-threaded processors
US20080005222A1 (en) * 2006-06-07 2008-01-03 Lambert Timothy M System and Method for Server Information Handling System Management Through Local I/O Devices
US7558913B2 (en) 2006-06-20 2009-07-07 Microsoft Corporation Atomic commit of cache transfer with staging area
US7694103B1 (en) 2006-06-23 2010-04-06 Emc Corporation Efficient use of memory and accessing of stored records
US7650458B2 (en) 2006-06-23 2010-01-19 Microsoft Corporation Flash memory driver
US8307148B2 (en) * 2006-06-23 2012-11-06 Microsoft Corporation Flash management techniques
US8429242B1 (en) 2006-06-26 2013-04-23 Emc Corporation Methods and apparatus for providing content
US7660937B2 (en) * 2006-06-28 2010-02-09 Hewlett-Packard Development Company, L.P. Emulating a USB host controller
US7853958B2 (en) 2006-06-28 2010-12-14 Intel Corporation Virtual machine monitor management from a management service processor in the host processing platform
JP4842719B2 (en) * 2006-06-28 2011-12-21 株式会社日立製作所 Storage system and data protection method thereof
US7810013B2 (en) 2006-06-30 2010-10-05 Intel Corporation Memory device that reflects back error detection signals
US7970989B2 (en) 2006-06-30 2011-06-28 Intel Corporation Write ordering on disk cached platforms
US7644206B2 (en) * 2006-06-30 2010-01-05 Seagate Technology Llc Command queue ordering by positionally pushing access commands
GB0613192D0 (en) 2006-07-01 2006-08-09 Ibm Methods, apparatus and computer programs for managing persistence
US7721059B2 (en) 2006-07-06 2010-05-18 Nokia Corporation Performance optimization in solid-state media
US20080052377A1 (en) 2006-07-11 2008-02-28 Robert Light Web-Based User-Dependent Customer Service Interaction with Co-Browsing
US7783956B2 (en) 2006-07-12 2010-08-24 Cronera Systems Incorporated Data recorder
US7395390B2 (en) 2006-07-12 2008-07-01 Inventec Corporation System for backing up cache memory in a double backup server structure
US8046629B1 (en) * 2006-07-24 2011-10-25 Marvell World Trade Ltd. File server for redundant array of independent disks (RAID) system
EP2047368A4 (en) 2006-07-31 2009-09-23 Toshiba Kk Nonvolatile memory system, and data read/write method for nonvolatile memory system
US7519830B2 (en) 2006-08-03 2009-04-14 Motorola, Inc. Secure storage of data
US8046660B2 (en) 2006-08-07 2011-10-25 Marvell World Trade Ltd. System and method for correcting errors in non-volatile memory using product codes
US8427489B2 (en) * 2006-08-10 2013-04-23 Avocent Huntsville Corporation Rack interface pod with intelligent platform control
US7478299B2 (en) * 2006-08-14 2009-01-13 International Business Machines Corporation Processor fault isolation
US7594144B2 (en) 2006-08-14 2009-09-22 International Business Machines Corporation Handling fatal computer hardware errors
US20080043769A1 (en) 2006-08-16 2008-02-21 Tyan Computer Corporation Clustering system and system management architecture thereof
US7899800B2 (en) 2006-08-18 2011-03-01 Isilon Systems, Inc. Systems and methods for providing nonlinear journaling
US7676625B2 (en) 2006-08-23 2010-03-09 Sun Microsystems, Inc. Cross-coupled peripheral component interconnect express switch
KR101128234B1 (en) 2006-08-23 2012-03-23 엘지전자 주식회사 Apparatus and method for controlling access of memory
US7500078B2 (en) 2006-08-25 2009-03-03 Dell Products L.P. Thermal control of memory modules using proximity information
WO2008026203A2 (en) 2006-08-27 2008-03-06 Anobit Technologies Estimation of non-linear distortion in memory devices
US7788513B2 (en) 2006-08-29 2010-08-31 Hewlett-Packard Development Company, L.P. Method of reducing power consumption of a computing system by evacuating selective platform memory components thereof
JP4932390B2 (en) 2006-08-31 2012-05-16 株式会社日立製作所 Virtualization system and area allocation control method
US7870306B2 (en) 2006-08-31 2011-01-11 Cisco Technology, Inc. Shared memory message switch and cache
JP4452261B2 (en) 2006-09-12 2010-04-21 株式会社日立製作所 Storage system logical volume management method, logical volume management program, and storage system
US7774392B2 (en) 2006-09-15 2010-08-10 Sandisk Corporation Non-volatile memory with management of a pool of update memory blocks based on each block's activity and data order
US20080077767A1 (en) 2006-09-27 2008-03-27 Khosravi Hormuzd M Method and apparatus for secure page swapping in virtual memory systems
US7761625B2 (en) 2006-09-28 2010-07-20 Virident Systems, Inc. Methods for main memory with non-volatile type memory modules, and related technologies
US7573744B2 (en) 2006-09-29 2009-08-11 Kabushiki Kaisha Toshiba Semiconductor memory device having different capacity areas
US7630225B2 (en) 2006-09-29 2009-12-08 Sandisk Corporation Apparatus combining once-writeable and rewriteable information storage to support data processing
US7752412B2 (en) 2006-09-29 2010-07-06 Sandisk Corporation Methods of managing file allocation table information
WO2008040080A1 (en) 2006-10-05 2008-04-10 Waratek Pty Limited Silent memory reclamation
JP4942446B2 (en) 2006-10-11 2012-05-30 株式会社日立製作所 Storage apparatus and control method thereof
US7499317B2 (en) 2006-10-13 2009-03-03 Sandisk Corporation System for partitioned erase and erase verification in a non-volatile memory to compensate for capacitive coupling
US7535766B2 (en) 2006-10-13 2009-05-19 Sandisk Corporation Systems for partitioned soft programming in non-volatile memory
US7499338B2 (en) 2006-10-13 2009-03-03 Sandisk Corporation Partitioned soft programming in non-volatile memory
US7495954B2 (en) 2006-10-13 2009-02-24 Sandisk Corporation Method for partitioned erase and erase verification to compensate for capacitive coupling effects in non-volatile memory
US9465823B2 (en) 2006-10-19 2016-10-11 Oracle International Corporation System and method for data de-duplication
KR100771519B1 (en) 2006-10-23 2007-10-30 삼성전자주식회사 Memory system including flash memory and merge method of thereof
JP4437489B2 (en) 2006-10-25 2010-03-24 株式会社日立製作所 Storage system having volatile cache memory and nonvolatile memory
KR100843543B1 (en) 2006-10-25 2008-07-04 삼성전자주식회사 System comprising flash memory device and data recovery method thereof
US7958280B2 (en) 2006-10-27 2011-06-07 Stec, Inc. Parallel data transfer in solid-state storage
US7822887B2 (en) 2006-10-27 2010-10-26 Stec, Inc. Multi-channel solid-state storage system
US8122196B2 (en) 2006-10-30 2012-02-21 Netapp, Inc. System and procedure for rapid decompression and/or decryption of securely stored data
US7685178B2 (en) 2006-10-31 2010-03-23 Netapp, Inc. System and method for examining client generated content stored on a data container exported by a storage system
KR100780773B1 (en) 2006-11-03 2007-11-30 주식회사 하이닉스반도체 Method of setting the program starting bias in flash memory device and method of programming the flash memory device using the same
US7606681B2 (en) 2006-11-03 2009-10-20 Air Products And Chemicals, Inc. System and method for process monitoring
US20080109647A1 (en) 2006-11-07 2008-05-08 Lee Merrill Gavens Memory controllers for performing resilient firmware upgrades to a functioning memory
US7970859B2 (en) * 2006-11-09 2011-06-28 Raritan Americas, Inc. Architecture and method for remote platform control management
US7567462B2 (en) 2006-11-16 2009-07-28 Micron Technology, Inc. Method and system for selectively limiting peak power consumption during programming or erase of non-volatile memory devices
US7877358B2 (en) 2006-11-21 2011-01-25 Microsoft Corporation Replacing system hardware
US20080120469A1 (en) 2006-11-22 2008-05-22 International Business Machines Corporation Systems and Arrangements for Cache Management
CN100530070C (en) 2006-11-24 2009-08-19 骆建军 Hard disk based on FLASH
US7904647B2 (en) 2006-11-27 2011-03-08 Lsi Corporation System for optimizing the performance and reliability of a storage controller cache offload circuit
US7924648B2 (en) 2006-11-28 2011-04-12 Anobit Technologies Ltd. Memory power and performance management
US7783830B2 (en) 2006-11-29 2010-08-24 Seagate Technology Llc Solid state device pattern for non-solid state storage media
US7624235B2 (en) 2006-11-30 2009-11-24 Apple Inc. Cache used both as cache and staging buffer
US8595573B2 (en) 2006-12-03 2013-11-26 Apple Inc. Automatic defect management in memory devices
JP4923990B2 (en) 2006-12-04 2012-04-25 株式会社日立製作所 Failover method and its computer system.
US8935302B2 (en) 2006-12-06 2015-01-13 Intelligent Intellectual Property Holdings 2 Llc Apparatus, system, and method for data block usage information synchronization for a non-volatile storage volume
US8151082B2 (en) 2007-12-06 2012-04-03 Fusion-Io, Inc. Apparatus, system, and method for converting a storage request into an append data storage command
US20080140724A1 (en) 2006-12-06 2008-06-12 David Flynn Apparatus, system, and method for servicing object requests within a storage controller
US8443134B2 (en) 2006-12-06 2013-05-14 Fusion-Io, Inc. Apparatus, system, and method for graceful cache device degradation
US9495241B2 (en) 2006-12-06 2016-11-15 Longitude Enterprise Flash S.A.R.L. Systems and methods for adaptive data storage
US9116823B2 (en) 2006-12-06 2015-08-25 Intelligent Intellectual Property Holdings 2 Llc Systems and methods for adaptive error-correction coding
US8074011B2 (en) 2006-12-06 2011-12-06 Fusion-Io, Inc. Apparatus, system, and method for storage space recovery after reaching a read count limit
US9104599B2 (en) 2007-12-06 2015-08-11 Intelligent Intellectual Property Holdings 2 Llc Apparatus, system, and method for destaging cached data
US8489817B2 (en) 2007-12-06 2013-07-16 Fusion-Io, Inc. Apparatus, system, and method for caching data
US8161353B2 (en) 2007-12-06 2012-04-17 Fusion-Io, Inc. Apparatus, system, and method for validating that a correct data segment is read from a data storage device
TW200825762A (en) 2006-12-06 2008-06-16 Inventec Corp Apparatus and method for computer management
CN101646994B (en) 2006-12-06 2016-06-15 才智知识产权控股公司(2) Utilize memory bank to interlock and manage the device of order of solid-state memory, system and method
US20080140737A1 (en) * 2006-12-08 2008-06-12 Apple Computer, Inc. Dynamic memory management
US20080140918A1 (en) 2006-12-11 2008-06-12 Pantas Sutardja Hybrid non-volatile solid state memory system
US7930425B2 (en) 2006-12-11 2011-04-19 International Business Machines Corporation Method of effectively establishing and maintaining communication linkages with a network interface controller
TW200825696A (en) 2006-12-15 2008-06-16 Inventec Corp Power management system
US7660911B2 (en) 2006-12-20 2010-02-09 Smart Modular Technologies, Inc. Block-based data striping to flash memory
US7913051B1 (en) 2006-12-22 2011-03-22 Emc Corporation Methods and apparatus for increasing the storage capacity of a zone of a storage system
US20080155051A1 (en) * 2006-12-23 2008-06-26 Simpletech, Inc. Direct file transfer system and method for a computer network
DE112006004185T5 (en) 2006-12-27 2009-11-19 Intel Corporation, Santa Clara Method for managing data in nonvolatile memory
KR100811274B1 (en) 2006-12-28 2008-03-07 주식회사 하이닉스반도체 Method for erasing data of nand type flash memory device
US20080162787A1 (en) 2006-12-28 2008-07-03 Andrew Tomlin System for block relinking
US8060482B2 (en) 2006-12-28 2011-11-15 Intel Corporation Efficient and consistent software transactional memory
US7978541B2 (en) 2007-01-02 2011-07-12 Marvell World Trade Ltd. High speed interface for multi-level memory
US8880480B2 (en) 2007-01-03 2014-11-04 Oracle International Corporation Method and apparatus for data rollback
US7769945B2 (en) 2007-01-18 2010-08-03 Sandisk Il Ltd. Method and system for facilitating fast wake-up of a flash memory system
US7564722B2 (en) 2007-01-22 2009-07-21 Micron Technology, Inc. Memory system and method having volatile and non-volatile memory devices at same hierarchical level
JP4813385B2 (en) 2007-01-29 2011-11-09 株式会社日立製作所 Control device that controls multiple logical resources of a storage system
US20080183968A1 (en) 2007-01-30 2008-07-31 Chi-Ting Huang Computer system having cache system directly connected to nonvolatile storage device and method thereof
KR100817087B1 (en) 2007-02-13 2008-03-27 삼성전자주식회사 Method for operating buffer cache of storage device including flash memory
US20080201535A1 (en) 2007-02-21 2008-08-21 Hitachi, Ltd. Method and Apparatus for Provisioning Storage Volumes
US20080205286A1 (en) 2007-02-26 2008-08-28 Inventec Corporation Test system using local loop to establish connection to baseboard management control and method therefor
WO2008106686A1 (en) 2007-03-01 2008-09-04 Douglas Dumitru Fast block device and methodology
US8190778B2 (en) * 2007-03-06 2012-05-29 Intel Corporation Method and apparatus for network filtering and firewall protection on a secure partition
US7502255B2 (en) 2007-03-07 2009-03-10 Sandisk Corporation Method for cache page copy in a non-volatile memory
US7499320B2 (en) 2007-03-07 2009-03-03 Sandisk Corporation Non-volatile memory with cache page copy
WO2008111058A2 (en) 2007-03-12 2008-09-18 Anobit Technologies Ltd. Adaptive estimation of memory cell read thresholds
US8490148B2 (en) * 2007-03-12 2013-07-16 Citrix Systems, Inc Systems and methods for managing application security profiles
US20080228862A1 (en) * 2007-03-12 2008-09-18 Timothy Mackey Systems and Methods for End-User Experience Monitoring
US20080229046A1 (en) 2007-03-13 2008-09-18 Microsoft Corporation Unified support for solid state storage
KR101395778B1 (en) 2007-03-14 2014-05-19 삼성전자주식회사 Memory card and memory system including the same and operating method thereof
US20080229045A1 (en) 2007-03-16 2008-09-18 Lsi Logic Corporation Storage system provisioning architecture
US7599967B2 (en) 2007-03-20 2009-10-06 Oracle International Corporation No data loss system with reduced commit latency
US9152349B2 (en) 2007-03-23 2015-10-06 Emc Corporation Automated information life-cycle management with thin provisioning
US7908501B2 (en) 2007-03-23 2011-03-15 Silicon Image, Inc. Progressive power control of a multi-port memory device
US8135900B2 (en) 2007-03-28 2012-03-13 Kabushiki Kaisha Toshiba Integrated memory management and memory management method
WO2008117520A1 (en) 2007-03-28 2008-10-02 Panasonic Corporation Memory controller, nonvolatile memory system and host device
US9632870B2 (en) 2007-03-29 2017-04-25 Violin Memory, Inc. Memory system with multiple striping of raid groups and method for performing the same
JP2008250961A (en) 2007-03-30 2008-10-16 Nec Corp Storage medium control device, data storage device, data storage system, method and control program
US20080244181A1 (en) 2007-03-30 2008-10-02 Michael Walz Dynamic run-time cache size management
US20080243966A1 (en) * 2007-04-02 2008-10-02 Croisettier Ramanakumari M System and method for managing temporary storage space of a database management system
US8427891B2 (en) 2007-04-17 2013-04-23 Rambus Inc. Hybrid volatile and non-volatile memory device with a shared interface circuit
US9207876B2 (en) 2007-04-19 2015-12-08 Microsoft Technology Licensing, Llc Remove-on-delete technologies for solid state drive optimization
US8429677B2 (en) 2007-04-19 2013-04-23 Microsoft Corporation Composite solid state drive identification and optimization technologies
US7853759B2 (en) 2007-04-23 2010-12-14 Microsoft Corporation Hints model for optimization of storage devices connected to host and write optimization schema for storage devices
US7876621B2 (en) 2007-04-23 2011-01-25 Sandisk Il Ltd. Adaptive dynamic reading of flash memories
US7606079B2 (en) 2007-04-25 2009-10-20 Sandisk Corporation Reducing power consumption during read operations in non-volatile storage
JP2008276646A (en) 2007-05-02 2008-11-13 Hitachi Ltd Storage device and data management method for storage device
US9009452B2 (en) 2007-05-14 2015-04-14 International Business Machines Corporation Computing system with transactional memory using millicode assists
US8175099B2 (en) * 2007-05-14 2012-05-08 Microsoft Corporation Embedded system development platform
US7752360B2 (en) 2007-05-16 2010-07-06 Nuova Systems, Inc. Method and system to map virtual PCIe I/O devices and resources to a standard I/O bus
US8301833B1 (en) 2007-06-01 2012-10-30 Netlist, Inc. Non-volatile memory module
US9396103B2 (en) 2007-06-08 2016-07-19 Sandisk Technologies Llc Method and system for storage address re-mapping for a memory device
US20080303692A1 (en) * 2007-06-08 2008-12-11 Tomonori Hirai Method and System for Assigning Identity Addresses to Local Management Modules
US20080320253A1 (en) 2007-06-19 2008-12-25 Andrew Tomlin Memory device with circuitry for writing data of an atomic transaction
US7752389B1 (en) * 2007-06-20 2010-07-06 Emc Corporation Techniques for determining physical data layout of RAID devices
US7865761B1 (en) 2007-06-28 2011-01-04 Emc Corporation Accessing multiple non-volatile semiconductor memory modules in an uneven manner
US7925936B1 (en) 2007-07-13 2011-04-12 Anobit Technologies Ltd. Memory device with non-uniform programming levels
US8046546B2 (en) 2007-07-25 2011-10-25 AGIGA Tech Variable partitioning in a hybrid memory subsystem
US8074034B2 (en) 2007-07-25 2011-12-06 Agiga Tech Inc. Hybrid nonvolatile ram
US8028198B2 (en) 2007-07-30 2011-09-27 Micron Technology, Inc. Devices, methods, and apparatuses for detection, sensing, and reporting functionality for semiconductor memory
US8001444B2 (en) 2007-08-08 2011-08-16 Intel Corporation ECC functional block placement in a multi-channel mass storage device
US7970919B1 (en) 2007-08-13 2011-06-28 Duran Paul A Apparatus and system for object-based storage solid-state drive and method for configuring same
US8850154B2 (en) 2007-09-11 2014-09-30 2236008 Ontario Inc. Processing system having memory partitioning
US20090070526A1 (en) 2007-09-12 2009-03-12 Tetrick R Scott Using explicit disk block cacheability attributes to enhance i/o caching efficiency
US7873803B2 (en) 2007-09-25 2011-01-18 Sandisk Corporation Nonvolatile memory with self recovery
TWI366828B (en) 2007-09-27 2012-06-21 Phison Electronics Corp Wear leveling method and controller using the same
US7934072B2 (en) 2007-09-28 2011-04-26 Lenovo (Singapore) Pte. Ltd. Solid state storage reclamation apparatus and method
US7773413B2 (en) 2007-10-08 2010-08-10 Anobit Technologies Ltd. Reliable data storage in analog memory cells in the presence of temperature variations
US8621605B2 (en) 2007-10-09 2013-12-31 International Business Machines Corporation Method for reducing the time to diagnose the cause of unexpected changes to system files
TWI578330B (en) 2007-10-09 2017-04-11 A-Data Technology Co Ltd Solid state semiconductor storage device with temperature control function and control method thereof
KR101433859B1 (en) 2007-10-12 2014-08-27 삼성전자주식회사 Nonvolatile memory system and method managing file data thereof
US8346912B2 (en) * 2007-10-15 2013-01-01 Dell Products, Lp System and method of emulating a network controller within an information handling system
US8156299B2 (en) 2007-10-19 2012-04-10 Virident Systems Inc. Managing memory systems containing components with asymmetric characteristics
US20090113235A1 (en) * 2007-10-30 2009-04-30 Selinger Robert D Raid with redundant parity
CN101971544B (en) 2007-11-05 2014-06-18 蜂窝通信设备有限责任公司 Buffer status reporting system and method
US7840839B2 (en) 2007-11-06 2010-11-23 Vmware, Inc. Storage handling for fault tolerance in virtual machines
US8572310B2 (en) 2007-11-06 2013-10-29 Samsung Electronics Co., Ltd. Invalidating storage area of non-volatile storage medium based on metadata
US8548953B2 (en) 2007-11-12 2013-10-01 F5 Networks, Inc. File deduplication using storage tiers
JP2009122850A (en) 2007-11-13 2009-06-04 Toshiba Corp Block device control device and access range management method
US8131927B2 (en) 2007-11-30 2012-03-06 Hitachi, Ltd. Fast accessible compressed thin provisioning volume
US8416657B2 (en) * 2007-12-03 2013-04-09 Mediatek Inc. Method and system for managing data from host to optical disc
US8001334B2 (en) 2007-12-06 2011-08-16 Silicon Image, Inc. Bank sharing and refresh in a shared multi-port memory device
US7836226B2 (en) 2007-12-06 2010-11-16 Fusion-Io, Inc. Apparatus, system, and method for coordinating storage requests in a multi-processor/multi-thread environment
US8195912B2 (en) 2007-12-06 2012-06-05 Fusion-io, Inc Apparatus, system, and method for efficient mapping of virtual and physical addresses
JP5238235B2 (en) 2007-12-07 2013-07-17 株式会社日立製作所 Management apparatus and management method
WO2009079478A1 (en) 2007-12-14 2009-06-25 Virident Systems, Inc. Distributing metadata across multiple different disruption regions within an asymmetric memory system
JP5428288B2 (en) 2007-12-25 2014-02-26 日本電気硝子株式会社 Glass plate manufacturing method and manufacturing equipment
US8621138B2 (en) 2007-12-27 2013-12-31 Sandisk Enterprise Ip Llc Flash storage controller execute loop
US8239611B2 (en) 2007-12-28 2012-08-07 Spansion Llc Relocating data in a memory device
US7917689B2 (en) 2007-12-28 2011-03-29 Intel Corporation Methods and apparatuses for nonvolatile memory wear leveling
WO2009100149A1 (en) 2008-02-10 2009-08-13 Rambus, Inc. Segmentation of flash memory for partial volatile storage
US8856464B2 (en) 2008-02-12 2014-10-07 Virident Systems, Inc. Systems for two-dimensional main memory including memory modules with read-writeable non-volatile memory devices
US20090216944A1 (en) 2008-02-22 2009-08-27 International Business Machines Corporation Efficient validation of writes for protection against dropped writes
KR101086855B1 (en) 2008-03-10 2011-11-25 주식회사 팍스디스크 Solid State Storage System with High Speed and Controlling Method thereof
US8175528B2 (en) 2008-03-18 2012-05-08 Spansion Llc Wireless mass storage flash memory
US8489820B1 (en) 2008-03-18 2013-07-16 Netapp, Inc Speculative copying of data from main buffer cache to solid-state secondary cache of a storage server
JP5040773B2 (en) 2008-03-31 2012-10-03 富士通株式会社 Memory buffer allocation device and program
US8516185B2 (en) 2009-07-16 2013-08-20 Netlist, Inc. System and method utilizing distributed byte-wise buffers on a memory module
US8001434B1 (en) 2008-04-14 2011-08-16 Netlist, Inc. Memory board with self-testing capability
US8051243B2 (en) 2008-04-30 2011-11-01 Hitachi, Ltd. Free space utilization in tiered storage systems
US20090276654A1 (en) 2008-05-02 2009-11-05 International Business Machines Corporation Systems and methods for implementing fault tolerant data processing services
US8266114B2 (en) 2008-09-22 2012-09-11 Riverbed Technology, Inc. Log structured content addressable deduplicating storage
JP5159421B2 (en) 2008-05-14 2013-03-06 株式会社日立製作所 Storage system and storage system management method using management device
US8775718B2 (en) 2008-05-23 2014-07-08 Netapp, Inc. Use of RDMA to access non-volatile solid-state memory in a network storage system
US8554983B2 (en) 2008-05-27 2013-10-08 Micron Technology, Inc. Devices and methods for operating a solid state drive
US8090909B2 (en) 2008-06-06 2012-01-03 Pivot3 Method and system for distributed raid implementation
US7917803B2 (en) 2008-06-17 2011-03-29 Seagate Technology Llc Data conflict resolution for solid-state memory devices
US8843691B2 (en) 2008-06-25 2014-09-23 Stec, Inc. Prioritized erasure of data blocks in a flash storage device
US8010738B1 (en) 2008-06-27 2011-08-30 Emc Corporation Techniques for obtaining a specified lifetime for a data storage device
US8135907B2 (en) 2008-06-30 2012-03-13 Oracle America, Inc. Method and system for managing wear-level aware file systems
US8019953B2 (en) 2008-07-01 2011-09-13 Lsi Corporation Method for providing atomicity for host write input/outputs (I/Os) in a continuous data protection (CDP)-enabled volume using intent log
JP5242264B2 (en) 2008-07-07 2013-07-24 株式会社東芝 Data control apparatus, storage system, and program
US9772936B2 (en) 2008-07-10 2017-09-26 Micron Technology, Inc. Data collection and compression in a solid state storage device
US20100017556A1 (en) 2008-07-19 2010-01-21 Nanostar Corporationm U.S.A. Non-volatile memory storage system with two-stage controller architecture
KR101086857B1 (en) 2008-07-25 2011-11-25 주식회사 팍스디스크 Control Method of Solid State Storage System for Data Merging
US7941591B2 (en) 2008-07-28 2011-05-10 CacheIQ, Inc. Flash DIMM in a standalone cache appliance system and methodology
JP5216463B2 (en) 2008-07-30 2013-06-19 株式会社日立製作所 Storage device, storage area management method thereof, and flash memory package
US8046551B1 (en) 2008-08-14 2011-10-25 Emc Corporation Techniques for processing I/O requests
KR100977709B1 (en) 2008-08-20 2010-08-24 주식회사 셀픽 A flash memory storage device and a manage method using the same
US8209439B2 (en) 2008-08-25 2012-06-26 Sandisk Il Ltd. Managing multiple concurrent operations with various priority levels in a local storage device
KR101487190B1 (en) 2008-09-11 2015-01-28 삼성전자주식회사 Flash memory integrated circuit with compression/decompression codec
US8335889B2 (en) 2008-09-11 2012-12-18 Nec Laboratories America, Inc. Content addressable storage systems and methods employing searchable blocks
US8914567B2 (en) 2008-09-15 2014-12-16 Vmware, Inc. Storage management system for virtual machines
US8417928B2 (en) 2008-09-24 2013-04-09 Marvell International Ltd. Turbo boot systems and methods for subsequent booting from a captured data stored in a non-volatile semiconductor memory
US20100082922A1 (en) 2008-09-30 2010-04-01 Vmware, Inc. Virtual machine migration using local storage
US8327066B2 (en) 2008-09-30 2012-12-04 Samsung Electronics Co., Ltd. Method of managing a solid state drive, associated systems and implementations
US8407427B2 (en) 2008-10-29 2013-03-26 Silicon Image, Inc. Method and system for improving serial port memory communication latency and reliability
US7777652B2 (en) 2008-10-29 2010-08-17 Silicon Image, Inc. Coding system for memory systems employing high-speed serial links
US8990573B2 (en) 2008-11-10 2015-03-24 Citrix Systems, Inc. System and method for using variable security tag location in network communications
KR101541812B1 (en) 2008-11-19 2015-08-06 삼성전자주식회사 Nonvolatile memory device
US20100146187A1 (en) 2008-12-05 2010-06-10 Grimsrud Knut S Endurance management technique
US8205060B2 (en) 2008-12-16 2012-06-19 Sandisk Il Ltd. Discardable files
US9015209B2 (en) 2008-12-16 2015-04-21 Sandisk Il Ltd. Download management of discardable files
US8266365B2 (en) 2008-12-17 2012-09-11 Sandisk Il Ltd. Ruggedized memory device
US8645641B2 (en) 2008-12-17 2014-02-04 Seagate Technology Llc Intelligent storage device controller
US8205063B2 (en) 2008-12-30 2012-06-19 Sandisk Technologies Inc. Dynamic mapping of logical ranges to write blocks
EP2382637B1 (en) 2008-12-30 2016-01-06 Micron Technology, Inc. Enhanced addressability for serial non-volatile memory
US8347041B2 (en) 2009-01-02 2013-01-01 Lsi Corporation System and method to preserve and recover unwritten data present in data cache of a disk subsystem across power outages
US8037364B2 (en) * 2009-01-09 2011-10-11 International Business Machines Corporation Forced management module failover by BMC impeachment consensus
US20100199020A1 (en) 2009-02-04 2010-08-05 Silicon Storage Technology, Inc. Non-volatile memory subsystem and a memory controller therefor
WO2010090745A1 (en) 2009-02-06 2010-08-12 Osr Open Systems Resources, Inc. Methods and systems for data storage
US8032708B2 (en) 2009-02-11 2011-10-04 Oracle America, Inc. Method and system for caching data in a storgae system
CN101819564B (en) 2009-02-26 2013-04-17 国际商业机器公司 Method and device for assisting communication between virtual machines
US8589700B2 (en) 2009-03-04 2013-11-19 Apple Inc. Data whitening for writing and reading data to and from a non-volatile memory
US8375195B2 (en) 2009-03-05 2013-02-12 Oracle America, Inc. Accessing memory locations for paged memory objects in an object-addressed memory system
US8296628B2 (en) 2009-03-06 2012-10-23 Texas Instruments Incorporated Data path read/write sequencing for reduced power consumption
US20100235597A1 (en) 2009-03-10 2010-09-16 Hiroshi Arakawa Method and apparatus for conversion between conventional volumes and thin provisioning with automated tier management
US8423710B1 (en) 2009-03-23 2013-04-16 Marvell International Ltd. Sequential writes to flash memory
US8418021B2 (en) 2009-03-27 2013-04-09 Mediatek Inc. Storage controller with encoding/decoding circuit programmable to support different ECC requirements and related method thereof
US8364923B2 (en) 2009-03-30 2013-01-29 Oracle America, Inc. Data storage system manager and method for managing a data storage system
US8566507B2 (en) 2009-04-08 2013-10-22 Google Inc. Data storage device capable of recognizing and controlling multiple types of memory chips
US8447918B2 (en) * 2009-04-08 2013-05-21 Google Inc. Garbage collection for failure prediction and repartitioning
US20100262979A1 (en) 2009-04-08 2010-10-14 Google Inc. Circular command queues for communication between a host and a data storage device
US8055816B2 (en) 2009-04-09 2011-11-08 Micron Technology, Inc. Memory controllers, memory systems, solid state drives and methods for processing a number of commands
US8214663B2 (en) 2009-04-15 2012-07-03 International Business Machines Corporation Using power proxies combined with on-chip actuators to meet a defined power target
KR101573722B1 (en) 2009-04-20 2015-12-03 삼성전자주식회사 Memory system including nonvolatile memory device and controller
US20100281207A1 (en) 2009-04-30 2010-11-04 Miller Steven C Flash-based data archive storage system
US8402069B2 (en) 2009-05-04 2013-03-19 Microsoft Corporation Use of delete notifications by file systems and applications to release storage space
US8095770B2 (en) 2009-05-08 2012-01-10 Oracle America Inc. Method and system for mapping data to a process
KR101606453B1 (en) 2009-05-13 2016-04-01 삼성전자주식회사 Method of read/write performance of non-volatile data storage device
US8095738B2 (en) 2009-06-15 2012-01-10 International Business Machines Corporation Differential caching mechanism based on media I/O speed
US8230257B2 (en) 2009-06-26 2012-07-24 Seagate Technology Llc Systems, methods and devices for controlling backup power provided to memory devices and used for storing of sensitive data
US20100332871A1 (en) 2009-06-30 2010-12-30 International Buisness Machines Corporation Capping power consumption in a data storage system
US8291131B2 (en) 2009-07-06 2012-10-16 Micron Technology, Inc. Data transfer management
US8234450B2 (en) 2009-07-10 2012-07-31 Via Technologies, Inc. Efficient data prefetching in the presence of load hits
US8214610B2 (en) 2009-07-15 2012-07-03 Lsi Corporation Managing backup device metadata in a high availability disk subsystem
US8516219B2 (en) 2009-07-24 2013-08-20 Apple Inc. Index cache tree
US20110029728A1 (en) 2009-07-28 2011-02-03 Lsi Corporation Methods and apparatus for reducing input/output operations in a raid storage system
JP5265023B2 (en) 2009-08-04 2013-08-14 株式会社日立製作所 Storage system and control method thereof
US20110035562A1 (en) 2009-08-10 2011-02-10 Hewlett-Packard Development Company, L.P. Providing mirroring write data
US7856528B1 (en) 2009-08-11 2010-12-21 Texas Memory Systems, Inc. Method and apparatus for protecting data using variable size page stripes in a FLASH-based storage system
US7818525B1 (en) 2009-08-12 2010-10-19 Texas Memory Systems, Inc. Efficient reduction of read disturb errors in NAND FLASH memory
US8688894B2 (en) 2009-09-03 2014-04-01 Pioneer Chip Technology Ltd. Page based management of flash storage
US8560765B2 (en) 2009-09-08 2013-10-15 Lsi Corporation Systems and methods for variable level use of a multi-level flash memory
US9122579B2 (en) 2010-01-06 2015-09-01 Intelligent Intellectual Property Holdings 2 Llc Apparatus, system, and method for a storage layer
US8429436B2 (en) 2009-09-09 2013-04-23 Fusion-Io, Inc. Apparatus, system, and method for power reduction in a storage device
KR101644125B1 (en) 2009-09-22 2016-07-29 삼성전자주식회사 an apparatus and method for logging optimization using non-volatile memory
CN102640227B (en) 2009-09-23 2016-06-01 纳姆迪兰斯有限公司 A kind of flash memory and control method
US10360039B2 (en) 2009-09-28 2019-07-23 Nvidia Corporation Predicted instruction execution in parallel processors with reduced per-thread state information including choosing a minimum or maximum of two operands based on a predicate value
TW201111986A (en) 2009-09-29 2011-04-01 Silicon Motion Inc Memory apparatus and data access method for memories
CA2680601C (en) 2009-10-16 2010-11-02 Ibm Canada Limited - Ibm Canada Limitee Managing multiple speculative assist threads at differing cache levels
US9753847B2 (en) 2009-10-27 2017-09-05 Western Digital Technologies, Inc. Non-volatile semiconductor memory segregating sequential, random, and system data to reduce garbage collection for page based mapping
US8103910B2 (en) 2009-11-13 2012-01-24 International Business Machines Corporation Local rollback for fault-tolerance in parallel computing systems
US8327106B2 (en) 2009-11-16 2012-12-04 International Business Machines Corporation Selective device access control
US8250324B2 (en) 2009-11-30 2012-08-21 International Business Machines Corporation Method to efficiently locate meta-data structures on a flash-based storage device
US9150155B2 (en) 2010-01-13 2015-10-06 Magna Electronics Inc. Vehicular camera and method for periodic calibration of vehicular camera
WO2011094454A2 (en) 2010-01-27 2011-08-04 Fusion-Io, Inc. Apparatus, system, and method for determining a read voltage threshold for solid-state storage media
US8478945B2 (en) 2010-02-01 2013-07-02 International Business Machines Corporation Dynamic management of destage tasks in a storage controller
US8285937B2 (en) 2010-02-24 2012-10-09 Apple Inc. Fused store exclusive/memory barrier operation
US8589766B2 (en) 2010-02-24 2013-11-19 Apple Inc. Codeword remapping schemes for non-volatile memories
US8850113B2 (en) 2010-02-27 2014-09-30 Cleversafe, Inc. Data migration between a raid memory and a dispersed storage network memory
US8712984B2 (en) 2010-03-04 2014-04-29 Microsoft Corporation Buffer pool extension for database server
US8438361B2 (en) 2010-03-10 2013-05-07 Seagate Technology Llc Logical block storage in a storage device
US8130551B2 (en) 2010-03-31 2012-03-06 Sandisk Technologies Inc. Extra dummy erase pulses after shallow erase-verify to avoid sensing deep erased threshold voltage
WO2011126993A2 (en) 2010-04-06 2011-10-13 D Naddor Hd barcode
US8463846B2 (en) 2010-05-06 2013-06-11 Cdnetworks Co., Ltd. File bundling for cache servers of content delivery networks
WO2011143628A2 (en) 2010-05-13 2011-11-17 Fusion-Io, Inc. Apparatus, system, and method for conditional and atomic storage operations
US8738724B2 (en) 2010-05-25 2014-05-27 Microsoft Corporation Totally ordered log on appendable storage
EP2577470A4 (en) 2010-06-04 2013-12-25 Sandisk Entpr Ip Llc Cache management and acceleration of storage media
US20110314071A1 (en) 2010-06-17 2011-12-22 Openwave Systems Inc. Metadata-based data access and control
US8402226B1 (en) 2010-06-18 2013-03-19 Emc Corporation Rate proportional cache write-back in a storage server
US8725934B2 (en) 2011-12-22 2014-05-13 Fusion-Io, Inc. Methods and appratuses for atomic storage operations
EP2598996B1 (en) 2010-07-28 2019-07-10 SanDisk Technologies LLC Apparatus, system, and method for conditional and atomic storage operations
US8713268B2 (en) 2010-08-05 2014-04-29 Ut-Battelle, Llc Coordinated garbage collection for raid array of solid state disks
US8850114B2 (en) 2010-09-07 2014-09-30 Daniel L Rosenband Storage array controller for flash-based storage devices
US8688899B2 (en) 2010-09-28 2014-04-01 Fusion-Io, Inc. Apparatus, system, and method for an interface between a memory controller and a non-volatile memory controller using a command protocol
US8452911B2 (en) 2010-09-30 2013-05-28 Sandisk Technologies Inc. Synchronized maintenance operations in a multi-bank storage system
US8738846B2 (en) 2010-10-15 2014-05-27 Arkologic Limited File system-aware solid-state storage management system
US10558705B2 (en) 2010-10-20 2020-02-11 Microsoft Technology Licensing, Llc Low RAM space, high-throughput persistent key-value store using secondary memory
US8396936B2 (en) 2010-10-28 2013-03-12 Hewlett-Packard Development Company, L.P. Computer system with cooperative cache
US8990538B2 (en) 2010-11-05 2015-03-24 Microsoft Corporation Managing memory with limited write cycles in heterogeneous memory systems
US9208071B2 (en) 2010-12-13 2015-12-08 SanDisk Technologies, Inc. Apparatus, system, and method for accessing memory
US8527693B2 (en) 2010-12-13 2013-09-03 Fusion IO, Inc. Apparatus, system, and method for auto-commit memory
JP2012128660A (en) 2010-12-15 2012-07-05 Toshiba Corp Semiconductor memory device
WO2012083308A2 (en) 2010-12-17 2012-06-21 Fusion-Io, Inc. Apparatus, system, and method for persistent data management on a non-volatile storage media
US8458145B2 (en) 2011-01-20 2013-06-04 Infinidat Ltd. System and method of storage optimization
US8364888B2 (en) 2011-02-03 2013-01-29 Stec, Inc. Erase-suspend system and method
US9063862B2 (en) 2011-05-17 2015-06-23 Sandisk Technologies Inc. Expandable data cache
US8904091B1 (en) 2011-12-22 2014-12-02 Western Digital Technologies, Inc. High performance media transport manager architecture for data storage systems
US10133662B2 (en) 2012-06-29 2018-11-20 Sandisk Technologies Llc Systems, methods, and interfaces for managing persistent data of atomic storage operations
US9274937B2 (en) 2011-12-22 2016-03-01 Longitude Enterprise Flash S.A.R.L. Systems, methods, and interfaces for vector input/output operations
JP2013137713A (en) 2011-12-28 2013-07-11 Toshiba Corp Memory controller, memory system, and memory write method
US9779038B2 (en) 2013-01-31 2017-10-03 Apple Inc. Efficient suspend-resume operation in memory devices
US9666244B2 (en) 2014-03-01 2017-05-30 Fusion-Io, Inc. Dividing a storage procedure
US10656864B2 (en) 2014-03-20 2020-05-19 Pure Storage, Inc. Data replication within a flash storage array

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002001365A2 (en) * 2000-06-23 2002-01-03 Intel Corporation Non-volatile cache
US20050177687A1 (en) * 2004-02-10 2005-08-11 Sun Microsystems, Inc. Storage system including hierarchical cache metadata

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"Windows PC Accelerators", 5 December 2006 (2006-12-05), pages 1 - 16, XP002476842, Retrieved from the Internet <URL:http://download.microsoft.com/download/9/c/5/9c5b2167-8017-4bae-9fde-d599bac8184a/perfaccel.doc> [retrieved on 20080416] *

Cited By (127)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11640359B2 (en) 2006-12-06 2023-05-02 Unification Technologies Llc Systems and methods for identifying storage resources that are not in use
US11960412B2 (en) 2006-12-06 2024-04-16 Unification Technologies Llc Systems and methods for identifying storage resources that are not in use
US8443134B2 (en) 2006-12-06 2013-05-14 Fusion-Io, Inc. Apparatus, system, and method for graceful cache device degradation
US11847066B2 (en) 2006-12-06 2023-12-19 Unification Technologies Llc Apparatus, system, and method for managing commands of solid-state storage using bank interleave
US8756375B2 (en) 2006-12-06 2014-06-17 Fusion-Io, Inc. Non-volatile cache
US9734086B2 (en) 2006-12-06 2017-08-15 Sandisk Technologies Llc Apparatus, system, and method for a device shared between multiple independent hosts
US11573909B2 (en) 2006-12-06 2023-02-07 Unification Technologies Llc Apparatus, system, and method for managing commands of solid-state storage using bank interleave
US9104599B2 (en) 2007-12-06 2015-08-11 Intelligent Intellectual Property Holdings 2 Llc Apparatus, system, and method for destaging cached data
US8489817B2 (en) 2007-12-06 2013-07-16 Fusion-Io, Inc. Apparatus, system, and method for caching data
US9519540B2 (en) 2007-12-06 2016-12-13 Sandisk Technologies Llc Apparatus, system, and method for destaging cached data
US8706968B2 (en) 2007-12-06 2014-04-22 Fusion-Io, Inc. Apparatus, system, and method for redundant write caching
US9600184B2 (en) 2007-12-06 2017-03-21 Sandisk Technologies Llc Apparatus, system, and method for coordinating storage requests in a multi-processor/multi-thread environment
EP2350830A1 (en) * 2008-10-30 2011-08-03 LSI Corporation Storage controller data redistribution
EP2350830A4 (en) * 2008-10-30 2013-05-22 Lsi Corp Storage controller data redistribution
EP2359248A1 (en) * 2008-12-19 2011-08-24 Hewlett-Packard Development Company, L.P. Redundant data storage for uniform read latency
KR20110106307A (en) * 2008-12-19 2011-09-28 휴렛-팩커드 디벨롭먼트 컴퍼니, 엘.피. Redundant data storage for uniform read latency
CN102257482A (en) * 2008-12-19 2011-11-23 惠普开发有限公司 Redundant data storage for uniform read latency
KR101638764B1 (en) 2008-12-19 2016-07-22 휴렛 팩커드 엔터프라이즈 디벨롭먼트 엘피 Redundant data storage for uniform read latency
JP2012513060A (en) * 2008-12-19 2012-06-07 ヒューレット−パッカード デベロップメント カンパニー エル．ピー． Redundant data storage for uniform read latency
WO2010071655A1 (en) 2008-12-19 2010-06-24 Hewlett-Packard Development Company, L.P. Redundant data storage for uniform read latency
EP2359248A4 (en) * 2008-12-19 2012-06-13 Hewlett Packard Development Co Redundant data storage for uniform read latency
JP2012517644A (en) * 2009-02-13 2012-08-02 インディリンクス カンパニー リミテッド Storage system using high-speed storage device as cache
KR101023883B1 (en) * 2009-02-13 2011-03-22 (주)인디링스 Storage system using high speed storage divece as cache
WO2010093108A1 (en) * 2009-02-13 2010-08-19 (주)인디링스 Storage system using a rapid storage device as a cache
US8195878B2 (en) 2009-02-19 2012-06-05 Pmc-Sierra, Inc. Hard disk drive with attached solid state drive cache
EP2728488A3 (en) * 2009-04-08 2014-06-11 Google, Inc. Data storage device
US9244842B2 (en) 2009-04-08 2016-01-26 Google Inc. Data storage device with copy command
US8195874B2 (en) 2009-04-10 2012-06-05 Hitachi, Ltd. Storage apparatus and method for shredding storage medium
WO2010116419A1 (en) * 2009-04-10 2010-10-14 Hitachi, Ltd. Storage apparatus and method for shredding storage medium
US8214621B2 (en) 2009-04-29 2012-07-03 Microsoft Corporation Storage optimization across media with differing capabilities
US8161251B2 (en) 2009-05-27 2012-04-17 Microsoft Corporation Heterogeneous storage array optimization through eviction
KR101345572B1 (en) 2009-06-08 2014-01-06 엘에스아이 코포레이션 Method and apparatus for protecting the integrity of cached data in a direct-attached storage (das) system
EP2264607A3 (en) * 2009-06-08 2011-07-20 LSI Corporation Method and apparatus for protecting the integrity of cached data in a direct-attached storage (DAS) system
JP2010282628A (en) * 2009-06-08 2010-12-16 Lsi Corp Method and device for protecting maintainability of data cached in direct attached storage (das) system
US10664166B2 (en) 2009-06-15 2020-05-26 Microsoft Technology Licensing, Llc Application-transparent hybridized caching for high-performance storage
US9110783B1 (en) 2009-06-15 2015-08-18 Microsoft Technology Licensing, Llc Application-transparent hybridized caching for high-performance storage
WO2010147827A1 (en) * 2009-06-16 2010-12-23 Sandisk Corporation Multi-bank non-volatile memory system with satellite file system
US8291131B2 (en) 2009-07-06 2012-10-16 Micron Technology, Inc. Data transfer management
WO2011005763A3 (en) * 2009-07-06 2011-04-14 Micron Technology, Inc. Data transfer management
US9047273B2 (en) 2009-07-06 2015-06-02 Micron Technology, Inc. Data transfer management
US8706929B2 (en) 2009-07-06 2014-04-22 Micron Technology, Inc. Data transfer management
KR101600467B1 (en) 2009-07-06 2016-03-14 마이크론 테크놀로지, 인크. Data transfer management
KR20120058506A (en) * 2009-07-06 2012-06-07 마이크론 테크놀로지, 인크. Data transfer management
EP2452266A1 (en) * 2009-07-07 2012-05-16 LSI Corporation Systems and methods for tiered non-volatile storage
EP2452266A4 (en) * 2009-07-07 2013-12-04 Lsi Corp Systems and methods for tiered non-volatile storage
WO2011028802A1 (en) * 2009-09-01 2011-03-10 Marvell World Trade Ltd. Systems and methods for compressing data in non-volatile semiconductor memory drives
US8407562B2 (en) 2009-09-01 2013-03-26 Marvell World Trade Ltd. Systems and methods for compressing data in non-volatile semiconductor memory drives
US8806299B2 (en) 2009-09-01 2014-08-12 Marvell World Trade Ltd. Method and apparatus for compressing data sectors in storage drive
US8719501B2 (en) 2009-09-08 2014-05-06 Fusion-Io Apparatus, system, and method for caching data on a solid-state storage device
EP2476079A4 (en) * 2009-09-09 2013-07-03 Fusion Io Inc Apparatus, system, and method for allocating storage
EP2476079A2 (en) * 2009-09-09 2012-07-18 Fusion-io, Inc. Apparatus, system, and method for allocating storage
WO2011070526A1 (en) * 2009-12-11 2011-06-16 International Business Machines Corporation Flash memory controller
US8996794B2 (en) 2009-12-11 2015-03-31 International Business Machines Corporation Flash memory controller
GB2488259A (en) * 2009-12-11 2012-08-22 Ibm Flash memory controller
CN102652313A (en) * 2009-12-11 2012-08-29 国际商业机器公司 Flash memory controller
CN102652313B (en) * 2009-12-11 2015-04-15 国际商业机器公司 Flash memory controller and operation method
US8533558B2 (en) 2009-12-23 2013-09-10 Sandisk Technologies Inc. System and method of error correction of control data at a memory device
CN102713855A (en) * 2009-12-23 2012-10-03 桑迪士克科技股份有限公司 System and method of error correction of control data at a memory device
EP2713274A3 (en) * 2009-12-23 2014-04-30 SanDisk Technologies, Inc. System and method of error correction of control data at a memory device
US8533564B2 (en) 2009-12-23 2013-09-10 Sandisk Technologies Inc. System and method of error correction of control data at a memory device
WO2011087602A1 (en) * 2009-12-23 2011-07-21 Sandisk Corporation System and method of error correction of control data at a memory device
CN102110481A (en) * 2009-12-24 2011-06-29 海力士半导体有限公司 Semiconductor memory system having ECC circuit and method of controlling thereof
US9122579B2 (en) 2010-01-06 2015-09-01 Intelligent Intellectual Property Holdings 2 Llc Apparatus, system, and method for a storage layer
US8321630B1 (en) 2010-01-28 2012-11-27 Microsoft Corporation Application-transparent hybridized caching for high-performance storage
EP2372521A3 (en) * 2010-04-02 2013-04-24 Intel Corporation Remote direct storage access
US9015268B2 (en) 2010-04-02 2015-04-21 Intel Corporation Remote direct storage access
US8751904B2 (en) 2010-07-22 2014-06-10 Silicon Motion Inc. Controlling methods and controllers utilized in flash memory device for referring to data compression result to adjust ECC protection capability
TWI455144B (en) * 2010-07-22 2014-10-01 Silicon Motion Inc Controlling methods and controllers utilized in flash memory device
WO2012100257A3 (en) * 2011-01-21 2012-10-04 Fusion-Io, Inc. Apparatus, system, and method for destaging cached data
WO2012100257A2 (en) * 2011-01-21 2012-07-26 Fusion-Io, Inc. Apparatus, system, and method for destaging cached data
US8966184B2 (en) 2011-01-31 2015-02-24 Intelligent Intellectual Property Holdings 2, LLC. Apparatus, system, and method for managing eviction of data
US9092337B2 (en) 2011-01-31 2015-07-28 Intelligent Intellectual Property Holdings 2 Llc Apparatus, system, and method for managing eviction of data
US9141527B2 (en) 2011-02-25 2015-09-22 Intelligent Intellectual Property Holdings 2 Llc Managing cache pools
US8825937B2 (en) 2011-02-25 2014-09-02 Fusion-Io, Inc. Writing cached data forward on read
US8966191B2 (en) 2011-03-18 2015-02-24 Fusion-Io, Inc. Logical interface for contextual storage
US9563555B2 (en) 2011-03-18 2017-02-07 Sandisk Technologies Llc Systems and methods for storage allocation
US9250817B2 (en) 2011-03-18 2016-02-02 SanDisk Technologies, Inc. Systems and methods for contextual storage
CN102223510A (en) * 2011-06-03 2011-10-19 杭州华三通信技术有限公司 Method and device for scheduling cache
US8806108B2 (en) 2011-06-07 2014-08-12 Hitachi, Ltd. Semiconductor storage apparatus and method of controlling semiconductor storage apparatus
WO2012168960A1 (en) * 2011-06-07 2012-12-13 Hitachi, Ltd. Semiconductor storage apparatus and method of controlling semiconductor storage apparatus
US9753674B2 (en) 2011-07-12 2017-09-05 Violin Memory Inc. RAIDed memory system
US9417823B2 (en) 2011-07-12 2016-08-16 Violin Memory Inc. Memory system management
EP2732375A4 (en) * 2011-07-12 2015-01-28 Violin Memory Inc Raided memory system
EP2732375A2 (en) * 2011-07-12 2014-05-21 Violin Memory Inc. Raided memory system
US9335939B2 (en) 2011-07-12 2016-05-10 Violin Memory Inc. RAIDed memory system
US9274937B2 (en) 2011-12-22 2016-03-01 Longitude Enterprise Flash S.A.R.L. Systems, methods, and interfaces for vector input/output operations
US9251052B2 (en) 2012-01-12 2016-02-02 Intelligent Intellectual Property Holdings 2 Llc Systems and methods for profiling a non-volatile cache having a logical-to-physical translation layer
US10102117B2 (en) 2012-01-12 2018-10-16 Sandisk Technologies Llc Systems and methods for cache and storage device coordination
US8782344B2 (en) 2012-01-12 2014-07-15 Fusion-Io, Inc. Systems and methods for managing cache admission
WO2013105960A1 (en) * 2012-01-12 2013-07-18 Fusion-Io, Inc. Systems and methods for managing cache admission
US9767032B2 (en) 2012-01-12 2017-09-19 Sandisk Technologies Llc Systems and methods for cache endurance
US9251086B2 (en) 2012-01-24 2016-02-02 SanDisk Technologies, Inc. Apparatus, system, and method for managing a cache
US10013444B2 (en) * 2012-03-02 2018-07-03 International Business Machines Corporation Modifying an index node of a hierarchical dispersed storage index
US20130232153A1 (en) * 2012-03-02 2013-09-05 Cleversafe, Inc. Modifying an index node of a hierarchical dispersed storage index
WO2013134347A1 (en) * 2012-03-07 2013-09-12 Netapp, Inc. Deduplicating hybrid storage aggregate
WO2013134345A1 (en) * 2012-03-07 2013-09-12 Netapp, Inc. Hybrid storage aggregate block tracking
WO2013142667A1 (en) * 2012-03-23 2013-09-26 DSSD, Inc. Solid state data storage system and methods therefor
US8819304B2 (en) 2012-03-23 2014-08-26 DSSD, Inc. Storage system with multicast DMA and unified address space
US8554963B1 (en) * 2012-03-23 2013-10-08 DSSD, Inc. Storage system with multicast DMA and unified address space
EP2842271B1 (en) * 2012-04-25 2024-04-17 Hewlett Packard Enterprise Development LP Network management
US10509776B2 (en) 2012-09-24 2019-12-17 Sandisk Technologies Llc Time sequence data management
US10318495B2 (en) 2012-09-24 2019-06-11 Sandisk Technologies Llc Snapshots for a non-volatile device
WO2014102879A1 (en) * 2012-12-28 2014-07-03 Hitachi, Ltd. Data storage apparatus and control method thereof
EP2949084A4 (en) * 2013-01-23 2016-09-07 Nexenta Systems Inc Scalable transport for multicast replication and scalable object storage using multicast transport
WO2014116875A2 (en) 2013-01-23 2014-07-31 Nexenta Systems, Inc. Scalable transport for multicast replication and scalable object storage using multicast transport
US10102144B2 (en) 2013-04-16 2018-10-16 Sandisk Technologies Llc Systems, methods and interfaces for data virtualization
US10558561B2 (en) 2013-04-16 2020-02-11 Sandisk Technologies Llc Systems and methods for storage metadata management
US9842128B2 (en) 2013-08-01 2017-12-12 Sandisk Technologies Llc Systems and methods for atomic storage operations
US10019320B2 (en) 2013-10-18 2018-07-10 Sandisk Technologies Llc Systems and methods for distributed atomic storage operations
US10444998B1 (en) 2013-10-24 2019-10-15 Western Digital Technologies, Inc. Data storage device providing data maintenance services
EP3061008A1 (en) * 2013-10-24 2016-08-31 Western Digital Technologies, Inc. Data storage device supporting accelerated database operations
EP3061008A4 (en) * 2013-10-24 2017-05-03 Western Digital Technologies, Inc. Data storage device supporting accelerated database operations
WO2015061629A1 (en) 2013-10-24 2015-04-30 Western Digital Technologies, Inc. Data storage device supporting accelerated database operations
US10073630B2 (en) 2013-11-08 2018-09-11 Sandisk Technologies Llc Systems and methods for log coordination
US9141291B2 (en) 2013-11-26 2015-09-22 Sandisk Technologies Inc. Adaptive context disbursement for improved performance in non-volatile memory systems
US9389958B2 (en) 2014-01-17 2016-07-12 Netapp, Inc. File system driven raid rebuild technique
US10013311B2 (en) 2014-01-17 2018-07-03 Netapp, Inc. File system driven raid rebuild technique
WO2015108670A1 (en) * 2014-01-17 2015-07-23 Netapp, Inc. File system driven raid rebuild technique
US9454434B2 (en) 2014-01-17 2016-09-27 Netapp, Inc. File system driven raid rebuild technique
US9946607B2 (en) 2015-03-04 2018-04-17 Sandisk Technologies Llc Systems and methods for storage error management
US11416447B2 (en) 2017-06-08 2022-08-16 Hitachi Vantara Llc Deduplicating distributed erasure coded objects
US11526462B2 (en) 2018-08-06 2022-12-13 Oracle International Corporation One-sided reliable remote direct memory operations
US11449458B2 (en) * 2018-08-06 2022-09-20 Oracle International Corporation One-sided reliable remote direct memory operations
US11379403B2 (en) 2018-08-06 2022-07-05 Oracle International Corporation One-sided reliable remote direct memory operations
US11347678B2 (en) 2018-08-06 2022-05-31 Oracle International Corporation One-sided reliable remote direct memory operations
EP4155940A1 (en) * 2021-09-27 2023-03-29 Graid Technology Inc. Direct memory access data path for raid storage
US12079521B2 (en) 2021-09-27 2024-09-03 GRAID Technology Inc. Direct memory access data path for RAID storage

Also Published As

Publication number Publication date
EP2109822B1 (en) 2014-06-25
US11573909B2 (en) 2023-02-07
US20130097367A1 (en) 2013-04-18
US8015440B2 (en) 2011-09-06
US20130124791A1 (en) 2013-05-16
KR101490327B1 (en) 2015-02-05
US8495292B2 (en) 2013-07-23
US20110258512A1 (en) 2011-10-20
WO2008070812A3 (en) 2009-12-23
US10146700B2 (en) 2018-12-04
US10387328B2 (en) 2019-08-20
EP2126680A2 (en) 2009-12-02
US20190370185A1 (en) 2019-12-05
CN101689131A (en) 2010-03-31
KR20090087119A (en) 2009-08-14
US20130304872A1 (en) 2013-11-14
US8533569B2 (en) 2013-09-10
JP2010512584A (en) 2010-04-22
US20080183953A1 (en) 2008-07-31
KR20090102789A (en) 2009-09-30
US11960412B2 (en) 2024-04-16
CN101689130A (en) 2010-03-31
US20120215961A1 (en) 2012-08-23
US20130024642A1 (en) 2013-01-24
US20080256183A1 (en) 2008-10-16
WO2008070802A3 (en) 2008-10-09
US20130067294A1 (en) 2013-03-14
US8189407B2 (en) 2012-05-29
WO2008070174A3 (en) 2009-09-11
US7934055B2 (en) 2011-04-26
WO2008070811A3 (en) 2008-08-07
US20120324311A1 (en) 2012-12-20
US20110179225A1 (en) 2011-07-21
WO2008070814A2 (en) 2008-06-12
US8412979B2 (en) 2013-04-02
WO2008070798A1 (en) 2008-06-12
WO2008070813A3 (en) 2009-12-23
US20080140932A1 (en) 2008-06-12
US9632727B2 (en) 2017-04-25
WO2008070802A2 (en) 2008-06-12
US8266496B2 (en) 2012-09-11
ES2507072T3 (en) 2014-10-14
WO2008070172A2 (en) 2008-06-12
US8417774B2 (en) 2013-04-09
US20080140724A1 (en) 2008-06-12
EP2108143A2 (en) 2009-10-14
EP2100214B1 (en) 2013-10-30
EP2109812A2 (en) 2009-10-21
CN103049058B (en) 2018-01-02
US11847066B2 (en) 2023-12-19
US20080229079A1 (en) 2008-09-18
US20170185347A1 (en) 2017-06-29
CA2672035A1 (en) 2008-06-12
WO2008070812A2 (en) 2008-06-12
US8402201B2 (en) 2013-03-19
US8019940B2 (en) 2011-09-13
JP5523835B2 (en) 2014-06-18
US8214591B2 (en) 2012-07-03
WO2008070799A3 (en) 2008-10-23
CN101681282A (en) 2010-03-24
US20170147241A1 (en) 2017-05-25
JP5611597B2 (en) 2014-10-22
CN101715575A (en) 2010-05-26
WO2008127458A2 (en) 2008-10-23
US8261005B2 (en) 2012-09-04
WO2008070800B1 (en) 2008-07-31
US9824027B2 (en) 2017-11-21
KR20140133923A (en) 2014-11-20
WO2008070172A3 (en) 2008-07-24
CA2672100A1 (en) 2008-06-12
US20140372679A1 (en) 2014-12-18
US20080313364A1 (en) 2008-12-18
KR20090087498A (en) 2009-08-17
WO2008127458A3 (en) 2010-01-07
US20080140910A1 (en) 2008-06-12
US8296337B2 (en) 2012-10-23
US20120179869A1 (en) 2012-07-12
US8762658B2 (en) 2014-06-24
US20080168304A1 (en) 2008-07-10
US20080256292A1 (en) 2008-10-16
US20230144287A1 (en) 2023-05-11
US20210294753A1 (en) 2021-09-23
US20080313312A1 (en) 2008-12-18
US20110296277A1 (en) 2011-12-01
EP2126709A2 (en) 2009-12-02
WO2008070796A3 (en) 2009-12-10
EP2115563A2 (en) 2009-11-11
WO2008070799A2 (en) 2008-06-12
US20190171581A1 (en) 2019-06-06
US20120331206A1 (en) 2012-12-27
US20230134374A1 (en) 2023-05-04
WO2008070191A2 (en) 2008-06-12
KR20090097906A (en) 2009-09-16
US20090132760A1 (en) 2009-05-21
WO2008070811A2 (en) 2008-06-12
US11640359B2 (en) 2023-05-02
US9575902B2 (en) 2017-02-21
US8412904B2 (en) 2013-04-02
WO2008070174A2 (en) 2008-06-12
JP2010512586A (en) 2010-04-22
WO2008070814A3 (en) 2008-11-13
US11061825B2 (en) 2021-07-13
US20080141043A1 (en) 2008-06-12
WO2008070800A1 (en) 2008-06-12
WO2008070191B1 (en) 2008-09-04
WO2008070813A2 (en) 2008-06-12
US20170003902A1 (en) 2017-01-05
EP2100214A1 (en) 2009-09-16
JP2010512568A (en) 2010-04-22
US9519594B2 (en) 2016-12-13
EP2126679A2 (en) 2009-12-02
US10387327B2 (en) 2019-08-20
US8482993B2 (en) 2013-07-09
US20110047356A2 (en) 2011-02-24
US8601211B2 (en) 2013-12-03
CN101622594B (en) 2013-03-13
WO2008070803A1 (en) 2008-06-12
US9454492B2 (en) 2016-09-27
US20160342366A1 (en) 2016-11-24
EP2109822A1 (en) 2009-10-21
KR20090095641A (en) 2009-09-09
US20080183882A1 (en) 2008-07-31
US20110252190A1 (en) 2011-10-13
EP2126698A2 (en) 2009-12-02
CN101689131B (en) 2013-03-20
KR20090102788A (en) 2009-09-30
WO2008070796A2 (en) 2008-06-12
WO2008070191A3 (en) 2008-07-24
US20080140909A1 (en) 2008-06-12
JP2010515116A (en) 2010-05-06
CN101690068A (en) 2010-03-31
KR101532951B1 (en) 2015-07-09
CN101622594A (en) 2010-01-06
US8285927B2 (en) 2012-10-09
US8533406B2 (en) 2013-09-10
US8019938B2 (en) 2011-09-13
US20110157992A1 (en) 2011-06-30
CN103049058A (en) 2013-04-17
US20110289267A1 (en) 2011-11-24
US9734086B2 (en) 2017-08-15

Similar Documents

Publication Publication Date Title
EP2109822B1 (en) Apparatus, system, and method for solid-state storage as cache for high-capacity, non-volatile storage

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 200780050973.4

Country of ref document: CN

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

Ref document number: 07867661

Country of ref document: EP

Kind code of ref document: A1

DPE1 Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101)
ENP Entry into the national phase

Ref document number: 2009540309

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2672100

Country of ref document: CA

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 3894/CHENP/2009

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 1020097014058

Country of ref document: KR

Ref document number: 2007867661

Country of ref document: EP

DPE1 Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101)
DPE1 Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101)