EP1351126B1 - Open-architecture flash driver and method therefor - Google Patents

Open-architecture flash driver and method therefor Download PDF

Info

Publication number
EP1351126B1
EP1351126B1 EP20030000542 EP03000542A EP1351126B1 EP 1351126 B1 EP1351126 B1 EP 1351126B1 EP 20030000542 EP20030000542 EP 20030000542 EP 03000542 A EP03000542 A EP 03000542A EP 1351126 B1 EP1351126 B1 EP 1351126B1
Authority
EP
Grant status
Grant
Patent type
Prior art keywords
flash
data
sector
medium
memory
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP20030000542
Other languages
German (de)
French (fr)
Other versions
EP1351126A3 (en )
EP1351126A2 (en )
Inventor
Jered Donald Aasheim
Yongqi Yang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Microsoft Technology Licensing LLC
Original Assignee
Microsoft Technology Licensing LLC
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
Grant date

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F17/00Digital computing or data processing equipment or methods, specially adapted for specific functions
    • G06F17/30Information retrieval; Database structures therefor ; File system structures therefor
    • G06F17/30067File systems; File servers
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1415Saving, restoring, recovering or retrying at system level
    • G06F11/1435Saving, restoring, recovering or retrying at system level using file system or storage system metadata
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1415Saving, restoring, recovering or retrying at system level
    • G06F11/1441Resetting or repowering
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1474Saving, restoring, recovering or retrying in transactions
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00Accessing, addressing or allocating within memory systems or architectures
    • G06F12/02Addressing or allocation; Relocation
    • G06F12/0223User address space allocation, e.g. contiguous or non contiguous base addressing
    • G06F12/023Free address space management
    • G06F12/0238Memory management in non-volatile memory, e.g. resistive RAM or ferroelectric memory
    • G06F12/0246Memory management in non-volatile memory, e.g. resistive RAM or ferroelectric memory in block erasable memory, e.g. flash memory
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input 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/06Digital input from or digital output to record carriers, e.g. RAID, emulated record carriers, networked record carriers
    • G06F3/0601Dedicated interfaces to storage systems
    • G06F3/0602Dedicated interfaces to storage systems specifically adapted to achieve a particular effect
    • G06F3/0614Improving the reliability of storage systems
    • G06F3/0619Improving the reliability of storage systems in relation to data integrity, e.g. data losses, bit errors
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input 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/06Digital input from or digital output to record carriers, e.g. RAID, emulated record carriers, networked record carriers
    • G06F3/0601Dedicated interfaces to storage systems
    • G06F3/0628Dedicated interfaces to storage systems making use of a particular technique
    • G06F3/0638Organizing or formatting or addressing of data
    • G06F3/0643Management of files
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input 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/06Digital input from or digital output to record carriers, e.g. RAID, emulated record carriers, networked record carriers
    • G06F3/0601Dedicated interfaces to storage systems
    • G06F3/0668Dedicated interfaces to storage systems adopting a particular infrastructure
    • G06F3/0671In-line storage system
    • G06F3/0673Single storage device
    • G06F3/0679Non-volatile semiconductor memory device, e.g. flash memory, one time programmable memory [OTP]
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1471Saving, restoring, recovering or retrying involving logging of persistent data for recovery
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2212/00Indexing scheme relating to accessing, addressing or allocation within memory systems or architectures
    • G06F2212/72Details relating to flash memory management
    • G06F2212/7201Logical to physical mapping or translation of blocks or pages
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2212/00Indexing scheme relating to accessing, addressing or allocation within memory systems or architectures
    • G06F2212/72Details relating to flash memory management
    • G06F2212/7207Details relating to flash memory management management of metadata or control data
    • YGENERAL 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
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THIR OWN ENERGY USE
    • Y02D10/00Energy efficient computing
    • Y02D10/10Reducing energy consumption at the single machine level, e.g. processors, personal computers, peripherals or power supply
    • Y02D10/13Access, addressing or allocation within memory systems or architectures, e.g. to reduce power consumption or heat production or to increase battery life
    • YGENERAL 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
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99951File or database maintenance
    • Y10S707/99952Coherency, e.g. same view to multiple users
    • Y10S707/99953Recoverability
    • YGENERAL 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
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99951File or database maintenance
    • Y10S707/99952Coherency, e.g. same view to multiple users
    • Y10S707/99955Archiving or backup

Description

  • [0001]
    This invention relates to flash memory drivers, and more particularly, to an open architecture flash memory driver.
  • [0002]
    Flash memory is a nonvolatile storage medium that can retain information without power and can be erased and reprogrammed. Many portable computer devices, such as laptop computers, portable digital assistants (PDAs), portable communication/computer devices, and many other types of related devices use flash memory as the primary medium for the storage of information, because flash memory takes-up very little real estate in a computer device and does not require continuous power to retain its memory. Additionally, flash memory is resilient to shaking and accidental dropping that is a frequent occurrence with many portable computer devices. As a result flash memory is increasingly becoming the storage medium of choice for most portable computer devices.
  • [0003]
    Most flash memory manufacturers sell flash memory with proprietary controllers, commonly referred to as flash drivers. Typically, these flash drivers are not compatible with flash memories manufactured by other manufacturers. This reduces flexibility for manufacturers of portable computer devices, because the operating systems and/or file systems deployed by the manufactures are often tied to a particular proprietary flash driver. Changing the flash memory medium often requires tedious modification of the file systems, to ensure compatibility with the particular flash driver associated with flash memory medium. In certain circumstances, some operating as well as file systems are not compatible with certain flash mediums, which may force some manufacturers of portable computer devices to become locked-in, to a certain extent, to a particular flash memory due to a lack of driver compatibility.
  • [0004]
    WO-A-9737296 is concerned with repeatedly storing information in different locations of a memory while ensuring that in the event of an unexpected power loss, the stored information can be recovered. There is provided a memory device comprising a user interface, a controller, a store, and address mapping means.
  • [0005]
    GB-A-2 291 991 describes a solid state memory comprising means for translating a logic sector address to a main memory address and a main memory composed of non-volatile memory cells erasable in blocks.
  • [0006]
    It is the object of the present invention to improve the compatibility of operating systems and/or file systems with regard to different types of flash memory media.
  • [0007]
    The object is solved by the subject matter of the independent claims.
    Preferred embodiments of the present invention are defined by the dependent claims.
  • [0008]
    An open architecture flash driver is described. The flash driver is openly compatible to operate as an interface between most types of file systems and flash memory media regardless of the manufacturer. In one described implementation, a flash memory driver when executed by a computer provides an interface between a file system and one or more flash memory media. The flash memory driver uses flash abstraction logic that is invokable by the file system to manage flash memory operations without regard to the type of the one or more flash memory media. The flash memory driver also uses flash media logic configured to interact with different types of the flash memory media. The flash abstraction logic invokes the flash media logic to perform memory operations that are potentially performed in different ways depending on the type of the flash memory media.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • [0009]
    The detailed description is described with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears.
    • FIG. 1 illustrates a logical representation of a NAND flash memory medium.
    • FIG. 2 illustrates a logical representation of a NOR flash memory medium.
    • FIG. 3 illustrates pertinent components of a computer device, which uses one or more flash memory devices to store information.
    • FIG. 4 illustrates a block diagram of flash abstraction logic.
    • FIG. 5 illustrates an exemplary block diagram of a flash medium logic.
    • FIG. 6A shows a data structure used to store a corresponding relationship between logical sector addresses and physical sector addresses.
    • FIG. 6B shows a data structure which is the same as the data structure in FIG. 6B, except its contents have been updated.
    • FIG. 7 illustrates a process used to track data on the flash memory medium when the file system issues write requests to the flash driver.
    • FIG. 8 illustrates a process for safeguarding mapping of logical-to-physical sector address information stored in volatile data structures, such as the data structures shown in FIGS. 6A and 6B.
    • FIG. 9 illustrates a location within the flash memory medium in which the logical sector address can be stored for safeguarding in the event of a power failure.
    • FIG. 10 illustrates a dynamic look-up data structure to track data stored in the flash memory medium.
    • FIG. 11 illustrates a process for dynamically allocating look-up data structures for tracking data on the flash memory medium.
    • FIG. 12 is a diagram of the flash memory medium viewed and/or treated as a continuous circle by the flash driver.
    • FIG. 13 depicts another illustration of the media viewed as a continuous circle.
    • FIG. 14 illustrates a process used by the sector manager to determine the next available free sector location for the flash driver to store data on the medium.
    • FIG. 15 illustrates another view of media treated as a continuous circle.
    • FIG. 16 is a flow chart illustrating a process used by the compactor to recycle sectors.
    • FIG. 17 shows one exemplary result from the process illustrated in FIG. 16.
    • FIG. 18 illustrates a logical representation of a NOR flash memory medium divided in way to better support the processes and techniques implemented by the flash driver.
    DETAILED DESCRIPTION
  • [0010]
    The following discussion is directed to flash drivers.
  • Overview
  • [0011]
    This discussion assumes that the reader is familiar with basic operating principles of flash memory media. Nevertheless, a general introduction to two common types of nonvolatile random access memory, NAND and NOR Flash memory media, is provided to better understand the exemplary implementations described herein. These two example flash memory media were selected for their current popularity, but their description is not intended to limit the described implementations to these types of flash media. Other electrically erasable and programmable read-only memories (EEPROMs) would work too. In most examples used throughout this Detailed Description numbers shown in data structures are in decimal format for illustrative purposes.
  • Universal Flash Medium Operating Characteristics
  • [0012]
    FIG. 1 and FIG. 2 illustrate logical representations of example NAND and NOR flash memory media 100, 200, respectively. Both media have universal operating characteristics that are common to each, respectively, regardless of the manufacturer. For example referring to FIG. 1, a NAND flash memory medium is generally split into contiguous blocks (0, 1, through N). Each block 0, 1, 2, etc. is further subdivided into K sectors 102; standard commercial NAND flash media commonly contain 8, 16, or 32 sectors per block. The amount of blocks and sectors can vary, however, depending on the manufacturer. Some manufacturers refer to "sectors" as "pages." Both terms as used herein are equivalent and interchangeable.
  • [0013]
    Each sector 102 is further divided into two distinct sections, a data area 103 used to store information and a spare area 104 which is used to store extra information such as error correction code (ECC). The data area 103 size is commonly implemented as 512 bytes, but again could be more or less depending on the manufacturer. At 512 bytes, the flash memory medium allows most file systems to treat the medium as a nonvolatile memory device, such as a fixed disk (hard drive). As used herein RAM refers generally to the random access memory family of memory devices such as DRAM, SRAM, VRAM, VDO, and so forth. Commonly, the size of the area spare 104 is implemented as 16 bytes of extra storage for NAND flash media devices. Again, other sizes, greater or smaller can be selected. In most instances, the spare area 104 is used for error correcting codes, and status information.
  • [0014]
    A NOR memory medium 200 is different than NAND memory medium in that blocks are not subdivided into physical sectors. Similar to RAM, each byte stored within a block of NOR memory medium is individually addressable. Practically, however, blocks on NOR memory medium can logically be subdivided into physical sectors with the accompanying spare area.
  • [0015]
    Aside from the overall layout and operational comparisons, some universal electrical characteristics (also referred to herein as "memory requirements" or "rules") of flash devices can be summarized as follows:
  1. 1. Write operations to a sector can change an individual bit from a logical '1' to a logical '0', but not from a logical '0' to logical '1' (except for case No. 2 below);
  2. 2. Erasing a block sets all of the bits in the block to a logical '1';
  3. 3. It is not generally possible to erase individual sectors/bytes/bits in a block without erasing all sectors/bytes within the same block;
  4. 4. Blocks have a limited erase lifetime of between approximately 100,000 to 1,000, 000 cycles;
  5. 5. NAND flash memory devices use ECC to safeguard against data corruption_due to leakage currents; and
  6. 6. Read operations do not count against the write/erase lifetime.
Flash Driver Architecture
  • [0016]
    FIG. 3 illustrates pertinent components of a computer device 300, which uses one or more flash memory devices to store information. Generally, various different general purpose or special purpose computing system configurations can be used for computer device 300, including but not limited to personal computers, server computers, hand-held or laptop devices, portable communication devices, multiprocessor systems, microprocessor systems, microprocessor-based systems, programmable consumer electronics, gaming systems, multimedia systems, the combination of any of the above example devices and/or systems, and the like.
  • [0017]
    Computer device 300 generally includes a processor 302, memory 304, and a flash memory media 100/200. The computer device 300 can include more than one of any of the aforementioned elements. Other elements such as power supplies, keyboards, touch pads, I/O interfaces, displays, LEDs, audio generators, vibrating devices, and so forth are not shown, but could easily be a part of the exemplary computer device 300.
  • [0018]
    Memory 304 generally includes both volatile memory (e.g., RAM) and non-volatile memory (e.g., ROM, PCMCIA cards, etc.). In most implementations described below, memory 304 is used as part of computer device's 302 cache, permitting application data to be accessed quickly without having to permanently store data on a non-volatile memory such as flash medium 100/200.
  • [0019]
    An operating system 309 is resident in the memory 304 and executes on the processor 302. An example operating system implementation includes the Windows®CE operating system from Microsoft Corporation, but other operation systems can be selected from one of many operating systems, such as DOS, UNIX, etc. For purposes of illustration, programs and other executable program components such as the operating system are illustrated herein as discrete blocks, although it is recognized that such programs and components reside at various times in different storage components of the computer, and are executed by the processor(s) of the computer device 300.
  • [0020]
    One or more application programs 307 are loaded into memory 304 and run on the operating system 309. Examples of applications include, but are not limited to, email programs, word processing programs, spreadsheets programs, Internet browser programs, as so forth.
  • [0021]
    Also loaded into memory 304 is a file system 305 that also runs on the operating system 309. The file system 305 is generally responsible for managing the storage and retrieval of data to memory devices, such as magnetic hard drives, and this exemplary implementation flash memory media 100/200. Most file systems 305 access and store information at a logical level in accordance with the conventions of the operating system the file system 305 is running. It is possible for the file system 305 to be part of the operating system 309 or embedded as code as a separate logical module.
  • [0022]
    Flash driver 306 is implemented to function as a direct interface between the file system 305 and flash medium 100/200. Flash driver 306 enables computer device 300 through the file system 305 to control flash medium 100/200 and ultimately send/retrieve data. As shall be described in more detail, however, flash driver 306 is responsible for more than read/write operations. Flash driver 306 is implemented to maintain data integrity, perform wear-leveling of the flash medium, minimize data loss during a power interruption to computer device 300 and permit OEMs of computer devices 300 to support their respective flash memory devices regardless of the manufacturer. The flash driver 306 is file system agnostic. That means that the flash driver 306 supports many different types of files systems, such as File Allocation Data structure File System (FAT16), (FAT32), and other file systems. Additionally, flash driver 306 is flash memory medium agnostic, which likewise means driver 306 supports flash memory devices regardless of the manufacturer of the flash memory device. That is, the flash driver 306 has the ability to read/write/erase data on a flash medium and can support most, if not all, flash devices.
  • [0023]
    In the exemplary implementation, flash driver 306 resides as a component within operating system 309, that when executed serves as a logical interface module between the file system 305 and flash medium 100/200. The flash driver 306 is illustrated as a separate box 306 for purposes of demonstrating that the flash driver when implemented serves as an interface. Nevertheless, flash driver 306 can reside in other applications, part of the file system 305 or independently as separate code on a computer-readable medium that executes in conjunction with a hardware/firmware device.
  • [0024]
    In one implementation, flash driver 306 includes: a flash abstraction logic 308 and a programmable flash medium logic 310. Flash abstraction logic 308 and programmable medium logic 310 are coded instructions that support various features performed by the flash driver 306. Although the exemplary implementation is shown to include these two elements, various features from each of the flash abstraction logic 308 and flash medium logic 310 may be selected to carry out some of the more specific implementations described below. So while the described implementation shows two distinct layers of logic 308/310, many of the techniques described below can be implemented without necessarily requiring all or a portion of the features from either layer of logic.
  • [0025]
    In one implementation, the Flash abstraction logic 308 manages those operating characteristics that are universally common to flash memory media. These universal memory requirements include wear-leveling, maintaining data integrity, and handling recovery of data after a power failure. Additionally, the flash abstraction logic 308 is responsible for mapping information stored at a physical sector domain on the flash memory medium 100/200 to a logical sector domain associated with the file system 305. That is, the flash abstraction logic 308 tracks data going from a logical-to-physical sector addresses and/or from a physical-to-logical sector addresses. Driver 306 uses logical-to-physical sector addresses for both read/write operations. Driver 306 goes from physical-to-logical sector addresses when creating a look-up table (to be described below) during driver initialization. Some of the more specific commands issued by the file system that are dependent upon a certain type of flash memory media are sent directly to the flash medium logic 310 for execution and translation. Thus, the flash abstraction logic 308 serves as a manager to those universal operations, which are common to flash memory media regardless of the manufacturer for the media, such as wear-leveling, maintaining data integrity, handling data recovery after a power failure and so forth.
  • [0026]
    FIG. 4 illustrates an exemplary block diagram of the flash abstraction logic 308. Flash abstraction logic 308 includes a sector manager 402, a logical-to-physical sector mapping module 404, and a compactor 406. Briefly, the sector manager 402 provides a pointer to a sector available, i.e., "free" to receive new data. The logical-to-physical sector mapping module 404 manages data as it goes from a file system domain of logical sector addressing to a flash medium domain of physical sector addressing. The compactor 406 provides a mechanism for clearing blocks of data (also commonly referred to in the industry as "erasing") to ensure that enough free sectors are available for writing data. Additionally, the compactor 406 helps the driver 306 system perform uniform and even wear leveling. All these elements shall be described in more detail below.
  • [0027]
    Referring back to FIG. 3, the flash medium logic 310 is used to translate logical commands, received from either the flash abstraction logic 308 or file system 305, to physical sector commands for issuance to the flash memory medium 100/200. For instance, the flash medium logic 310 reads, writes, and erases data to and/or from the flash memory medium. The flash medium logic 310 is also responsible for performing ECC (if necessary). In one implementation, the flash medium logic 310 is programmable to permit users to match particular flash medium requirements of a specific manufacturer. Thus, the flash medium logic 310 is configured to handle specific nuances, ECC, and specific commands associated with controlling physical aspects of flash medium 100/200.
  • [0028]
    FIG. 5 illustrates an exemplary block diagram of the flash medium logic 310. As shown, the flash medium logic 310 includes a programmable entry point module 502, I/O module 504 and an ECC module 506. The programmable entry point module 502 defines a set of programming interfaces to communicate between flash abstraction logic 308 and flash medium 100/200. In other words, the programmable entry points permit manufacturers of computer devices 300 to program the flash media logic 310 to interface with the actual flash memory medium 100/200 used in the computer device 300. The I/O module 504 contains specific code necessary for read/write/erase commands that are sent to the Flash memory medium 100/200. The user can program the ECC module 506 to function in accordance with any particular ECC algorithm selected by the user.
  • Tracking Data
  • [0029]
    File system 305 uses logical sector addressing to read and store information on flash memory medium 100/200. Logical sector addresses are address locations that the file system reads and writes data to. They are "logical" because they are relative to the file system. In actuality, data may be stored in completely different physical locations on the flash memory medium 100/200. These physical locations are referred to as physical sector addresses.
  • [0030]
    The flash driver 306 is responsible for linking all logical sector address requests (i.e., read & write) to physical sector address requests. The process of linking logical-to-physical sector addresses is also referred to herein as mapping. Going from logical to physical sector addresses permits flash driver 306 to have maximum flexibility when deciding where to store data on the flash memory medium 100/200. The logical-to-physical sector mapping module 404 permits data to be flexibly assigned to any physical location on the flash memory medium, which provides efficiency for other tasks, such as wear-leveling and recovering from a power failure. It also permits the file system 305 to store data in the fashion it is designed to do so, without needing intelligence to know that the data is actually being stored on a flash medium in a different fashion.
  • [0031]
    FIG. 6A shows an exemplary implementation of a data structure (i.e., a table) 600A generated by the flash driver 306. The data structure 600A is stored in a volatile portion of memory 304, e.g. RAM. The data structure 600A includes physical sector addresses 602 that have a corresponding logical sector address 604. An exemplary description of how table 600A is generated is described with reference to FIG. 7.
  • [0032]
    FIG. 7 illustrates a process 700 used to track data on the flash memory medium 100/200 when the file system 305 issues write requests to the flash driver 306. Process 700 includes steps 702-718. Referring to FIGS. 6A and 7, in step 702, flash abstraction logic 308 receives a request to write data to a specified logical sector address 604.
  • [0033]
    In step 704, the sector manager 402 ascertains a free physical sector address location on the flash medium 100/200 that can accept data associated with the write request (how the sector manager 402 chooses physical sector addresses will be explained in more detail below). A free physical sector is any sector that can accept data without the need to be erased first. Once the sector manager 402 receives the physical sector address associated with a free physical sector location, the logical-to-physical sector mapping module 404 assigns the physical sector address to the logical sector address 604 specified by write request forming a corresponding relationship. For example, a physical sector address of 0 through N can be assigned to any arbitrary logical sector address 0 through N.
  • [0034]
    Next, in step 706, the logical-to-physical sector mapping module 404 stores the corresponding relationship of the physical sector address to the logical sector address in a data structure, such as the exemplary table 600A in memory 304. As shown in the exemplary data structure 600A, three logical sector addresses 604 are assigned to corresponding physical sector addresses 602.
  • [0035]
    Next, in step 708 data associated with the logical sector address write request is stored on the flash medium 100/200 at the physical sector address location assigned in step 704. For example, data would be stored in physical sector address location of zero on the medium 100/200, which corresponds to the logical sector address of 11.
  • [0036]
    Now, in step 710, suppose for example purposes the file system 305 issues another write request, but in this case, to modify data associated with a logical sector address previously issued in step 702. Then, flash driver 306 performs steps 712 through 714, which are identical to steps 704 through 708, respectively, which are described above.
  • [0037]
    In step 718, however, after the updated data associated with step 710 is successfully stored on the flash medium 100/200, the logical-to-physical sector mapping module 404 marks the old physical sector address assigned in step 704 as "dirty." Old data is marked dirty after new data is written to the medium 100/200, so in the event there is a power failure in the middle of the write operation, the logical-to-physical sector mapping module 404 will not lose old data. It is possible to lose new or updated data from steps 702 or 710, but since there is no need to perform an erase operation only one item of new or modified data is lost in the event of a power failure.
  • [0038]
    FIG. 6B shows a data structure 600B which is the same as data structure 600A, except its contents have been updated. In this example the file system 305 has updated data associated with logical sector address 11. Accordingly, the flash driver 306 reassigns logical sector address 11 to physical sector address 3 and stores the reassigned corresponding relationship between the these two addresses in data structure 600B. As illustrated in data structure 600B, the contents of logical sector 11 are actually written to physical sector address 3 and the contents of sector 0 are marked "dirty" after the data contents are successfully written into physical sector address 3 as was described with reference to steps 710-718.
  • [0039]
    This process of reassigning logical-to-physical sector address when previously stored data is updated by the file system 305, permits write operations to take place without having to wait to move an entire block of data and perform an erase operation. So, process 700 permits the data structure to be quickly updated and then the physical write operation can occur on the actual physical medium 100/200. Flash abstraction logic 308 uses the data structures, such as 600A/600B, to correctly maintain logical-to-physical mapping relationships.
  • [0040]
    When there is a read request issued by the files system 305, the flash abstraction logic 308, through the logical-to-physical mapping module 404, searches the data structure 600A/600B to obtain the physical sector address which has a corresponding relationship with the logical sector address associated with read request. The flash medium logic 310 then uses that physical sector address as a basis to send data associated with the read request back to the file system 305. The file system 305 does not need intelligence to know that its requests to logical sector addresses are actually mapped to physical sector addresses.
  • Power-Interruption Protection
  • [0041]
    Write operations are performed at the sector-level as opposed to the block-level, which minimizes the potential for data loss during a power-failure situation. A sector worth of data is the finest level of granularity that is used with respect to most file systems 305. Therefore, if the flash driver 306 is implemented to operate at a per sector basis, the potential for data loss during a power failure is reduced.
  • [0042]
    As mentioned above, data structures 600A, 600B are stored in memory 304, which in one exemplary implementation is typically a volatile memory device subject to complete erasure in the event of a power failure. To safeguard data integrity on the flash medium 100/200, logical-to-physical mapping information stored in the data structures 600A/ 600B is backed-up on the flash memory medium.
  • [0043]
    In one exemplary implementation, to reduce the cost associated with storing the entire data structure on the flash memory medium 100/200, the logical sector address is stored in the spare 104 area of the medium with each physical sector in which the logical sector address has a corresponding relationship.
  • [0044]
    FIG. 8 illustrates a process 800 for safeguarding mapping of logical-to-physical sector address information stored in volatile data structures, such as exemplary data structures 600A and 600B. Process 800 includes steps 802-814. The order in which the process is described is not intended to be construed as a limitation. Furthermore, the process can be implemented in any suitable hardware, software, firmware, or combination thereof. In step 802, the logical sector address associated with the actual data is stored in the physical sector of the flash memory medium 100/200 at the physical sector address assigned to the logical sector address. In the case of a NAND flash memory medium 100, the logical sector address is stored in the spare area 104 of the medium. Using this scheme, the logical-to-physical sector mapping information is stored in a reverse lookup format. Thus, after a power failure situation, it is necessary to scan the spare area for each physical sector on the media, determine the corresponding logical sector address, and then update the in-memory lookup table accordingly. FIG. 9 illustrates a location with in media 100/200 in which the logical sector address can be stored. As previously mentioned, blocks of NOR flash memory can be logically subdivided into physical sectors each with a spare area (similar to NAND). Using this technique, the logical sector address is stored in the spare area for each the physical sector similar to the process used with NAND flash memory (shown in FIG. 15 as space 1504 to be described with reference to FIG. 15).
  • [0045]
    In the event there is a power interruption and the data structures 600A, 600B are lost, as indicated by the YES branch of decisional step 804 of FIG. 8, then flash abstraction logic 308 uses the flash medium logic 310 to scan the flash memory medium to locate the logical sector address stored with data in each physical address (see FIG. 9), as indicated in step 806. In step 808, the physical sector address in which data is contained is reassigned to the logical sector address located with the data on the medium. As the physical and logical sector address are reestablished they are stored back in the data structures 600A, 600B and the flash medium logic 310 goes to the next sector containing data as indicated in step 812. Steps 806-812 repeat until all sectors containing data have been are scanned and the data structure is reestablished. Normally, this occurs at initialization of the computer device 300.
  • [0046]
    Accordingly, when a power failure occurs, process 800 enables the flash abstraction logic 308 to scan the medium 100/200 and rebuild the logical-to-physical mapping in a data structure such as the exemplary data structure 600. Process 800 ensures that mapping information is not lost during a power failure and that integrity of the data is retained.
  • Dynamic Look-up Data structure for Tracking Data
  • [0047]
    FIG. 10 illustrates a dynamic look-up data structure 1000 to track data stored in the flash memory medium 100/200. Data structure 1000 includes a master data structure 1002 and one or more secondary data structures 1004, 1006. The data structures are generated and maintained by the flash driver 306. The data structures are stored in a volatile portion of memory 304. The one or more secondary tables 1004, 1006 contain mappings of logical-to-physical sector addresses. Each of the secondary data structures 1004, 1006, as will be explained, have a predetermined capacity of mappings. The master data structure 1002 contains a pointer to each of the one or more secondary data structures 1004, 1006. Each secondary data structure is allocated on as needed basis for mapping those logical-to-physical addresses that are used to store data. Once the capacity of a secondary data structure 1004, 1006, etc., is exceeded, another secondary data structure is allocated, and another, etc., until eventually all possible physical sector addresses on the flash medium 100/200 are mapped to logical sector addresses. Each time a secondary table is allocated, a pointer contained in the master data structure 1002 is enabled by the flash driver 306 to point to it.
  • [0048]
    Accordingly, the flash driver 306 dynamically allocates one or more secondary data structures 1004, 1006 based on the amount of permanent data stored on the flash medium itself. The size characteristics of the secondary data structures are computed at run-time using the specific attributes of the flash memory medium 100/200. Secondary data structures are not allocated unless the secondary data structure previously allocated is full or insufficient to handle the amount of logical address space required by the file system 305. Dynamic look-up data structure 1000, therefore, minimizes usage of memory 304. Dynamic look-up data structure 1000 lends itself to computer devices 300 that use calendars, inboxes, documents, etc. where most of the logical sector address space will not need to be mapped to a physical sector address. In these applications, only a finite range of logical sectors are repeatedly accessed and new logical sectors are only written when the application requires more storage area.
  • [0049]
    The master data structure 1002 contains an array of pointers, 0 through N that point to those secondary data structures that are allocated. In the example of FIG. 10, the pointers at location 0 and 1 point to secondary data structures 1004 and 1006, respectively. Also, in the example illustration of FIG. 10, pointers 2 through N do not point to any secondary data structures and would contain a default setting, "NULL", such that the logical-to-physical sector mapping module 404 knows that there are no further secondary data structures allocated.
  • [0050]
    Each secondary data structure 1004, 1006 is similar to data structures 600, but only a portion of the total possible medium is mapped in the secondary data structures. The secondary data structures permit the flash abstraction logic 308 to reduce the amount space needed in memory 304, to only those portions of logical sectors addresses issued by the file system. Each secondary data structure is (b*k) bytes in size, where k is the number of physical sector addresses contained in the data structure and b is the number of bytes used to store each physical sector address.
  • [0051]
    FIG. 11 illustrates a process 1100 for dynamically allocating look-up data structures for tracking data on the flash memory medium 100/200. Process 1100 includes steps 1102 through 1106. The order in which the process is described is not intended to be construed as a limitation. Furthermore, the process can be implemented in any suitable hardware, software, firmware, or combination thereof.
  • [0052]
    In step 1102, a master data structure 1002 containing the pointers to one or more secondary data structures 1004, 1006 is generated. The master data structure 1002 in this exemplary implementation is fixed in size. At the time the computer device 300 boots-up, the flash medium logic 310 determines the size of the flash memory medium 100/200 and relays this information to the flash abstraction logic 308. Based on the size of the flash medium, the flash abstraction logic 308 calculates a range of physical addresses. That is, suppose the size of the flash medium is 16 MB, then a NAND flash medium 100 will typically contain 32768 sectors each 512 bytes in size. This means that the flash abstraction logic 308 may need to map a total of 0 through 32768 logical sectors in a worse case scenario, assuming all the memory space is used on the flash medium. Knowing that there are 215 sectors on the medium, the flash abstraction logic 308 can use 2 bytes to store the physical sector address for each logical sector address. So the master data structure is implemented as an array of 256 DWORDs (N=256), which covers the maximum quantity of logical sector addresses (e.g., 32768) to be issued by the files system. So, there are a total of 256 potential secondary data structures.
  • [0053]
    In step 1104 the secondary data structure(s) are allocated. First, the flash abstraction logic determines the smallest possible size for each potential secondary data structure. Using simple division, 32768 / 256 = 128 logical sector addresses supported by each data structure. As mentioned above, the entire physical space can be mapped using 2 bytes, b=2, therefore, each secondary data structure will by 256 bytes in size or (b=2 * k=128).
  • [0054]
    Now, knowing the size of each secondary data structure, suppose that the file system 305 requests to write to logical sector addresses 50-79, also known as LS50-LS79. To satisfy the write requests from the files system 305, the flash abstraction logic 308 calculates that the first pointer in master data structure 1002 is used for logical sector addresses LS0-LS127 or data structure 1004. Assuming the first pointer is NULL, the flash abstraction logic 308 allocates data structure 1004 (which is 256 bytes in size) in memory 304. As indicated in step 1106, the flash abstraction logic 308 enables the pointer in position 0 of the master data structure to point to data structure 1004. So, in this example, data structure 1004 is used to store the mapping information for logical sectors LS50-LS79.
  • [0055]
    The flash abstraction logic 308 allocates a secondary data structure, if the file system 305 writes to the corresponding area in the flash medium 100/200. Typically, only the logical sector addresses that are used are mapped by the flash abstraction logic 308. So, in the worst case scenario, when the file system 305 accesses the entire logical address space, then all 256 secondary data structures (only two, 1004, 1006 are shown to be allocated in the example of FIG. 10), each 256 bytes in size will be allocated requiring a total of 64KB of space in memory 304.
  • [0056]
    When an allocated data structure 1004, for instance, becomes insufficient to store the logical sector address space issued by the file system 305, then the flash abstraction logic 308 allocates another data structure, like data structure 1006. This process of dynamically allocating secondary data structures also applies if data structure 1004 becomes sufficient at a later time to again handle all the logical sector address requests made by the file system. In this example, the pointer to data structure 1006 would be disabled by the flash abstraction logic 308; and data structure 1006 would become free space in memory 304.
  • Uniform Wear Leveling and Recycling of Sectors
  • [0057]
    FIG. 12 is a diagram of flash memory medium 100/200 viewed and/or treated as a continuous circle 1200 by the flash driver 306. Physically the flash memory media is the same as either media 100/200 shown in FIGS. 1 and 2, except the flash abstraction logic 308, organizes the flash memory medium as if it is a continuous circle 1200, containing 0-to-N blocks. Accordingly, the highest physical sector address (individual sectors are not shown in FIG. 12 to simplify the illustration, but may be seen in FIGS. 1 and 2) within block N and the lowest physical sector address within block 0 are viewed as being contiguous.
  • [0058]
    FIG. 13 illustrates another view of media 100/200 viewed as a continuous circle 1200. In this exemplary illustration, the sector manager 402 maintains a write pointer 1302, which indicates a next available free sector to receive data on the medium. The next available free sector is a sector that can accept data without the need to be erased first in a prescribed order. The write pointer 1302 is implemented as a combination of two counters: a sector counter 1306 that counts sectors and a block counter 1304 that counts blocks. Both counters combined indicate the next available free sector to receive data.
  • [0059]
    In an alternative implementation, the write pointer 1302 can be implemented as a single counter and indicate the next physical sector that is free to accept data during a write operation. According to this implementation, the sector manager 402 maintains a list of all physical sector addresses free to receive data on the medium. The sector manager 402 stores the first and last physical sector addresses (the contiguous addresses) on the medium and subtracts the two addresses to determine an entire list of free sectors. The write pointer 1302 then advances through the list in a circular and continuous fashion. This reduces the amount of information needed to be stored by the sector manager 402.
  • [0060]
    FIG. 14 illustrates a process 1400 used by the sector manager 402 to determine the next available free sector location for the flash driver 306 to store data on the medium 100/200. Process 1400 also enables the sector manager 402 to provide each physical sector address (for the next free sector) for assignment to each logical sector address write request by the file system 305 as described above. Process 1400 includes steps 1402-1418. The order in which the process is described is not intended to be construed as a limitation. Furthermore, the process can be implemented in any suitable hardware, software, firmware, or combination thereof.
  • [0061]
    In step 1402, the X block counter 1304 and Y sector counter 1306 are initially set to zero. At this point it is assumed that no data resides on the medium 100/200.
  • [0062]
    In step 1404, the driver 306 receives a write request and the sector manager 402 is queried to send the next available free physical sector address to the logical-to-physical sector mapping module 404. The write request may come from the file system 305 and/or internally from the compactor 406 for recycling sectors as shall be explained in more detail below.
  • [0063]
    In step 1406, the data is written to the sector indicated by the write pointer 1302. Since both counters are initially set to zero in this exemplary illustration, suppose that the write pointer 1302 points to sector zero, block zero.
  • [0064]
    In step 1408, the sector counter 1306 is advanced one valid sector. For example, the write pointer advances to sector one of block zero, following the example from step 1406.
  • [0065]
    Next, in decisional step 1410, the sector manager 402 checks whether the sector counter 1306 exceeds the number of sectors K in a block. If the Y count does not exceed the maximum sector size of the block, then according to the NO branch of decisional step 1410, steps 1404-1410 repeat for the next write request.
  • [0066]
    On the other hand, if the Y count does exceed the maximum sector size of the block, then the highest physical sector address of the block was written to and the block is full. Then according to the YES branch of step 1410, in step 1412 the Y counter is reset to zero. Next, in step 1414, X block counter 1304 is incremented by one, which advances the write pointer 1302 to the next block at the lowest valid physical sector address, zero, of that block.
  • [0067]
    Next, in decisional step 1416, the compactor 406 checks whether the X block counter is pointing to a bad block. If it is, X block counter 1304 is incremented by one. In one implementation, the compactor 406 is responsible for checking this condition. As mentioned above, the sector manager stores all of the physical sector addresses that are free to handle a write request. Entire blocks of physical sector addresses are always added by the compactor during a compaction or during initialization. So, the sector manager 402 does not have to check to see if blocks are bad, although the sector manager could be implemented to do so. It should also be noted that in other implementations step 1416 could be performed at the start of process 1400.
  • [0068]
    In step 1417, the X block counter 1304 is incremented until it is pointing to a good block. To avoid a continuous loop, if all the blocks are bad, then process 1400 stops at step 1416 and provides an indication to a user that all blocks are bad.
  • [0069]
    Next in decisional step 1418, the sector manager checks whether the X block counter 1304 exceeds the maximum numbers of blocks N. This would indicate that write pointer 1302 has arrived full circle (at the top of circle 1200). If that is the case, then according to the YES branch of step 1418, the process 1400 repeats and the X and Y counter are reset to zero. Otherwise, according to the NO branch of step 1418, the process 1400 returns to step 1404 and proceeds.
  • [0070]
    In this exemplary process 1400, the write pointer 1302 initially starts with the lowest physical sector address of the lowest addressed block. The write pointer 1302 advances a sector at a time through to the highest physical sector address of the highest addressed block and then back to the lowest, and so forth. This continuous and circular process 1400 ensures that data is written to each sector of the medium 100/200 fairly and evenly. No particular block or sector is written to more than any other, ensuring even wear-levels throughout the medium 100/200. Accordingly, process 1400 permits data to be written to the next available free sector extremely quickly without expensive processing algorithms used to determine where to write new data while maintaining even wear-levels. Such conventional algorithms can slow the write speed of a computer device.
  • [0071]
    In an alternative implementation, it is possible for the write pointer 1302 to move in a counter clock wise direction starting with highest physical sector address of the highest block address N and decrement its counters. In either case, bad blocks can be entirely skipped and ignored by the sector manager. Additionally, the counters can be set to any value and do not necessarily have to start with the highest or lowest values of for the counters.
  • [0072]
    FIG. 15 illustrates another view of media 100/200 viewed as a continuous circle 1200. As shown in FIG. 15, the write pointer 1302 has advanced through blocks 0 through 7 and is approximately half way through circle 1200. Accordingly, blocks 0 through 7 contain dirty, valid data, or bad blocks. That is, each good sector in blocks 0 through 7 is not free, and therefore, not available to receive new or modified data. Arrow 1504 represents that blocks 0 through 7 contain used sectors. Eventually, the write pointer 1302 will either run out of free sectors to write to unless sectors that are marked dirty or are not valid are cleared and recycled. To clear a sector means that sectors are reset to a writable state or in other words are "erased." In order to free sectors it is necessary to erase at least a block at a time. Before a block can be erased, however, the contents of all good sectors are copied to the free sectors to a different portion of the media. The sectors are then later marked "dirty" and the block is erased.
  • [0073]
    The compactor 406 is responsible for monitoring the condition of the medium 100/200 to determine when it is appropriate to erase blocks in order to recycle free sectors back to the sector manager 402. The compactor 406 is also responsible for carrying out the clear operation. To complete the clear operation, the compactor 406, like the sector manager 402, maintains a pointer. In this case, the compactor 406 maintains a clear pointer 1502, which is shown in FIG. 15. The clear pointer 1502 points to physical blocks and as will be explained enables the compactor 406 to keep track of sectors as the medium 100/200 as blocks are cleared. The compactor 406 can maintain a pointer to a block to compact next since an erase operation affects entire blocks. That is, when the compactor 406 is not compacting a block, the compactor 406 points to a block.
  • [0074]
    FIG. 16 is a flow chart illustrating a process 1600 used by the compactor to recycle sectors. Process 1600 includes steps 1602-1612. The order in which the process is described is not intended to be construed as a limitation. Furthermore, the process can be implemented in any suitable hardware, software, firmware, or combination thereof. In step 1602, the compactor 406 monitors how frequently the flash memory medium 100/200 is written to or updated by the file system. This is accomplished by specifically monitoring the quantities of free and dirty sectors on the medium 100/200. The number of free sectors and dirty sectors can be determined counting free and dirty sectors stored in tables 600 and/or 1000 described above.
  • [0075]
    In decisional step 1604, the compactor 406 performs two comparisons to determine whether it is prudent to recycle sectors. The first comparison involves comparing the amount of free sectors to dirty sectors. If the amount of dirty sectors outnumbers the free sectors, then the compactor 406 deems it warranted to perform a recycling operation, which in this case is referred to as a "service compaction." Thus a service compaction is indicated when the number of dirty sectors outnumbers the quantity of free sectors.
  • [0076]
    If a service compaction is deemed warranted, then in step 1606 the compactor waits for a low priority thread 1606, before seizing control of the medium to carry out steps 1608-1612 to clear blocks of dirty data. The service compaction could also be implemented to occur at other convenient times when it is optional to recycle dirty sectors into free sectors. For instance, in an alternative implementation, when one third of the total sectors are dirty, the flash abstraction logic 308 can perform a service compaction. In either implementation, usually the compactor 406 waits for higher priority threads to relinquish control of the processor 302 and/or flash medium 100/200. Once a low priority thread is available, the process proceeds to step 1608.
  • [0077]
    Referring back to step 1604, the second comparison involves comparing the amount of free sectors left on the medium, to determine if the write pointer 1302 is about to or has run out of free sectors to point to. If this is the situation, then the compactor 406 deems it warranted to order a "critical compaction" to recycle sectors. The compactor does not wait for a low priority thread and launches immediately into step 1608.
  • [0078]
    In step 1608, the compactor 406 operates at either a high priority thread or low priority thread depending on step 1604. If operating at a high level thread (critical compaction), the compactor 1102 is limited to recycling a small number, e.g., 16 dirty sectors, into free sectors and return control of the processor back to computer device 300 to avoid monopolizing the processor 302 during such an interruption.
  • [0079]
    Thirty two sectors per block is commonly manufactured for flash media, but other numbers of sectors, larger or smaller, could be selected for a critical compaction. Regardless of these size characteristics, the number of sectors recycled during a critical compaction is arbitrary but must be at least 1 (in order to satisfy the current WRITE request). A critical compaction stalls the file system 305 from being able to complete a write; therefore, it is important to complete the compaction as soon as possible. In the case of a critical compaction, the compactor 406 must recycle at least one dirty sector into a free sector so that there is space on the medium to fulfill the pending write request. Having more than one sector recycled at a time, such as 16, avoids the situation where there are multiple pending write requests and multiple critical compactions that are performed back-to-back, effectively blocking control of the processor indefinitely. So, while the number of sectors recycled chosen for a critical compaction can vary, a number sufficient to prevent back-to-back critical compactions is implemented in the exemplary description.
  • [0080]
    So, in step 1608, the compactor 406 will use the clear pointer 1502 to scan sectors for valid data, rewrite the data to free sectors, and mark a sector dirty after successfully moving data. Accordingly, when moving data, the compactor uses the same processes described with reference to process 700, which is the same code that is used when the file system 305 writes new and/or updates data. The compactor 406 queries the sector manager 402 for free sectors when moving data, in the same fashion as described with reference to process 1400.
  • [0081]
    In step 1610, the compactor 406 moves the clear pointer 1502 sector-by-sector using a sector counter like the write counter 1306 shown in Fig. 13, except this sector counter pertains to the location of the clear pointer 1502. The compactor 406 also keeps track of blocks through a counter in similar fashion as described with reference to the write pointer 1302. However, the amount of blocks cleared is determined by the number of dirty sectors with the exception of a critical compaction. In a critical compaction, the compactor only compacts enough blocks to recycle a small number of physical sectors (i.e. 16 sectors).
  • [0082]
    In step 1612, the compactor erases (clears) those blocks which contain good sectors that are fully marked dirty. FIG. 17 shows exemplary results from process 1600. In this example, blocks 0 and 1 were cleared and the clear pointer was moved to the first sector of block 2, in the event another compaction is deemed warranted. As a result, the compactor 406 recycled two blocks worth of the sectors from blocks 0 and 1, which provides more free sectors to the sector manager 402. Used sectors 1504 forms a data stream (hereinafter a "data stream" 1504) that rotates in this implementation in a clockwise fashion. The write pointer 1302 remains at the head of the data stream 1504 and the clear pointer 1502 remains at the end or "tail" of the data stream 1504. The data stream 1504 may shrink as data is deleted, or grow as new data is added, but the pointers always point to opposite ends of the data stream 1504: head and tail.
  • [0083]
    Treating the flash memory medium as if the physical sector addresses form a continuous circle 1200, and using the processes described above, enables the flash abstraction logic 308 to accomplish uniform wear-leveling throughout the medium 100/200. The compactor 406 selects a given block the same number times for recycling of sectors through erasure. Since flash blocks have a limited write/erase cycle, the compactor as well as the sector manager distributes these operations across blocks 0-N as evenly and as fairly as possible. In this regard, the data steam 1504 rotates in the circle 1200 (i.e. the medium 100/200) evenly providing perfect wear-levels on the flash memory medium 100/200.
  • [0084]
    In the event of power failure, the flash abstraction logic 310 contains simple coded logic that scans the flash memory medium 100/ 200 and determines what locations are marked free and dirty. The logic is then able to deduce that the data stream 1504 resides between the locations marked free and dirty, e.g.., the data stream 1106 portion of the circle 1200 described in FIG. 17. The head and tail of the data stream 1504 is easily determined by locating the highest of the physical sector addresses containing data for the head and by locating the lowest of the physical sector addresses containing data for the tail.
  • NOR Flash Devices
  • [0085]
    Although all the aforementioned sections in this Detailed Description section apply to NAND and NOR flash devices, if a NOR flash memory medium 200 is used, some additional implementation is needed for the flash medium logic to support the storing of data in each physical sector on the medium 200. Each NOR block 0, 1, 2, etc. can be treated like a NAND flash memory medium 100, by the flash medium logic 310. Specifically, each NOR block is subdivided into some number of pages where each page consists of a 512 byte "data area" for sector data and an 8 byte "spare area" for storing things like to the logical sector address, status bits, etc. (as described above).
  • [0086]
    FIG. 18 illustrates a logical representation of a NOR flash memory medium 200 divided in way to better support the processes and techniques implemented by the flash driver. In this implementation, sectors 1802 contain a 512 byte data area 1803 for the storage of sector related data and 8 bytes for a spare area 1804. Sections 1806 represent unused portions of NOR blocks, because a NOR Flash block is usually a power of 2 in size, which is not evenly divisible. For instance, consider a 16 MB NOR flash memory device that has 128 flash blocks each 128 KB in size. Using a page size equal to 520 bytes, each NOR flash block can be divided into 252 distinct sectors with 32 bytes remaining unused. Unfortunately, these 32 bytes per block are "wasted" by the flash medium logic 310 in the exemplary implementation and are not used to store sector data. The tradeoff, however, is the enhanced write throughput, uniform wear leveling, data loss minimization, etc. all provided by the flash abstraction logic 308 of the exemplary flash driver 306 as described above. Alternative implementations could be accomplished by dividing the medium 200 into different sector sizes.
  • Computer readable Media
  • [0087]
    An implementation of exemplary subject matter using a flash driver as described above may be stored on or transmitted across some form of computer-readable media. Computer-readable media can be any available media that can be accessed by a computer. By way of example, and not limitation, computer readable media may comprise "computer storage media" and "communications media."
  • [0088]
    "Computer storage media" include volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules, or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer.
  • [0089]
    "Communication media" typically embodies computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as carrier wave or other transport mechanism. Communication media also includes any information delivery media.
  • [0090]
    The term "modulated data signal" means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared, and other wireless media. Combinations of any of the above are also included within the scope of computer readable media.
  • Claims (10)

    1. A flash driver (306), interposed between a file system (305) and a flash memory medium (100/200; 100; 200) selected from one of a plurality of different flash memory media, comprising:
      a flash abstraction logic (308) for managing a set of operating characteristics that are common to a plurality of different flash memory media, said set of operating characteristics comprising managing wear-leveling operations associated with the flash memory medium, maintaining data integrity of the flash memory medium, and handling recovery of data associated with the flash memory medium (100/200; 100; 200) after a power failure, said flash abstraction logic comprising:
      a sector manager (402) adapted to maintain a write pointer which indicates a next available free sector to receive data on the flash memory medium;
      a logical-to-physical sector mapping module (404) adapted to manage data as it goes from a file system domain of logical sector addressing to a flash memory medium domain of physical sector addressing; and
      a compactor (406) adapted for clearing blocks of data on the flash memory medium; and
      a user-programmable flash medium logic (310) for performing physical sector operations to the flash memory medium, said physical sector operations comprising read, write and erase data operations to and from the flash memory medium, said user-programmable flash medium logic comprising:
      programmable entry point module (502) adapted to define a set of programming interfaces to communicate between the flash abstraction logic (308) and the flash memory medium (100/200; 100; 200), wherein programmable entry points (502) permit said user to program the user-programmable flash medium logic (310) to interface with the type of the flash memory medium selected from said plurality of different flash memory media;
      an input/output module (504) adapted for performing said read, write and erase operations; and
      an error correction code, ECC, module (506) adapted to perform error code correction in accordance with a user-selected ECC algorithm.
    2. The flash driver as recited in claim 1, wherein the flash abstraction logic (308) is configured to map a logical sector status from the file system (305) to a physical sector status of the flash memory medium (100/200; 100; 200).
    3. The flash driver as recited in claims 1 or 2, wherein the flash abstraction logic (308) is further adapted to pass commands issued by the file system that are dependent upon the type of the flash memory medium (100/200; 100; 200) directly to the flash medium logic (310).
    4. The flash driver as recited in any of claims 1 to 3, wherein the user-programmable flash medium logic (310) is further adapted to translate logical commands received from the flash abstraction logic (308) or the file system (305) to physical sector commands for performing the physical sector operations to then user-programmable flash memory medium (100/200; 100; 200).
    5. A method for driving a flash memory medium, comprising the steps of:
      providing an interface between a file system (305) and a flash memory medium (100/200; 100; 200) selected from a plurality of different flash memory media, the interface comprising a flash abstraction logic (308) and a user-programmable flash medium logic (310), the flash abstraction logic (308) comprising a sector manager (402), a logical-to-physical sector mapping module (404) and a compactor (406), the user-programmable flash medium logic (310) comprising a programmable entry point module (502), an input/output module (504) and an error correction, ECC, module (506);
      managing, at the flash abstraction logic (308), a set of operating characteristics that are common to the plurality of different flash memory media, said set of operating characteristics comprising managing wear-leveling operations associated with the flash memory medium, maintaining data integrity of the flash memory medium, and handling recovery of data associated with the flash memory medium (100/200; 100; 200) after a power failure;
      maintaining, by the sector manager (402), a write pointer which indicates a next available free sector to receive data on the flash memory medium;
      managing, by the logical-to-physical sector mapping module (404), data as it goes from a file system domain of logical sector addressing to a flash memory medium domain of physical sector addressing; and
      clearing, by the compactor (406); blocks of data on the flash memory medium;
      performing, at the user-programmable flash medium logic (310) physical sector operations to the flash memory medium, said physical sector operations comprising read, write and erase data operations to and from the flash memory medium; defining, by the programmable entry point module (502), a set of programming interfaces to communicate between the flash abstraction logic (308) and the flash memory medium (100/200; 100; 200); wherein programmable entry points (502) permit said user to program the user-programmable flash medium logic (310) to interface with the type of the flash memory medium selected from said plurality of different flash memory media;
      performing, by the input/output module (504), said read, write and erase operations; and
      performing, by the ECC module (506), error code correction in accordance with a user-selected ECC algorithm.
    6. The method as recited in claim 5, further comprising the step of mapping, by the flash abstraction logic (308) a logical sector status from the file system to a physical sector status of the flash memory medium.
    7. The method as recited in claims 5 or 6, further comprising the step of passing, by the flash abstraction logic, commands issued by the file system that are dependent upon the type of the flash memory medium directly to the user-programmable flash medium logic.
    8. The method as recited in any of claims 5 to 7, further comprising the step of translating, by the user-programmable flash medium logic, logical commands received from the flash abstraction logic or the file system to physical sector commands for performing the physical sector operations to the flash memory medium.
    9. A computer-readable medium for a flash driver comprising computer-executable instructions that, when executed, direct the flash driver to perform the method of one of claims 5 to 8.
    10. A processing device (300) that uses a flash memory medium (100/200; 100; 200) for storage of data, comprising:
      a file system (305), configured to control data storage for the processing device; and
      a flash driver (306) according to one of claims 1 to 4.
    EP20030000542 2002-02-27 2003-01-09 Open-architecture flash driver and method therefor Active EP1351126B1 (en)

    Priority Applications (2)

    Application Number Priority Date Filing Date Title
    US10087672 US7533214B2 (en) 2002-02-27 2002-02-27 Open architecture flash driver
    US87672 2002-02-27

    Publications (3)

    Publication Number Publication Date
    EP1351126A2 true EP1351126A2 (en) 2003-10-08
    EP1351126A3 true EP1351126A3 (en) 2003-10-22
    EP1351126B1 true EP1351126B1 (en) 2017-05-03

    Family

    ID=27753947

    Family Applications (1)

    Application Number Title Priority Date Filing Date
    EP20030000542 Active EP1351126B1 (en) 2002-02-27 2003-01-09 Open-architecture flash driver and method therefor

    Country Status (4)

    Country Link
    US (7) US7533214B2 (en)
    EP (1) EP1351126B1 (en)
    JP (1) JP4658455B2 (en)
    CN (1) CN1303498C (en)

    Families Citing this family (221)

    * Cited by examiner, † Cited by third party
    Publication number Priority date Publication date Assignee Title
    GB9925227D0 (en) * 1999-10-25 1999-12-22 Internet Limited Data storage retrieval and access system
    US7047257B2 (en) * 2001-04-03 2006-05-16 Qnx Software Systems Computer file management system
    US7440980B2 (en) * 2001-04-03 2008-10-21 Qnx Software Systems Gmbh & Co. Kg Computer file management system
    US7433900B2 (en) * 2001-04-03 2008-10-07 Qnx Software Systems Gmbh & Co. Kg Custom filesystem having file mappings to files of a real filesystem
    US6901499B2 (en) * 2002-02-27 2005-05-31 Microsoft Corp. System and method for tracking data stored in a flash memory device
    US7533214B2 (en) * 2002-02-27 2009-05-12 Microsoft Corporation Open architecture flash driver
    US7689626B2 (en) * 2002-05-31 2010-03-30 Microsoft Corporation System and method for locating log records in multiplexed transactional logs
    US6988163B2 (en) * 2002-10-21 2006-01-17 Microsoft Corporation Executing binary images from non-linear storage systems
    EP1475704A2 (en) * 2003-05-08 2004-11-10 Matsushita Electric Industrial Co., Ltd. Information processing apparatus
    US20080043366A1 (en) 2003-06-26 2008-02-21 Spectra Logic Corporation Tape cartridge auxiliary memeory based library
    KR100522724B1 (en) 2003-10-24 2005-10-18 주식회사 레인콤 System and method for driving a portable multimedia player, portable multimedia player and recording media
    US7188225B1 (en) * 2003-12-05 2007-03-06 Applied Micro Circuits Corporation Storage system with disk drive power-on-reset detection
    JP4534498B2 (en) * 2004-01-28 2010-09-01 ソニー株式会社 The semiconductor device and the activation treatment method
    DE602004003583T2 (en) * 2004-10-04 2007-11-22 Research In Motion Ltd., Waterloo System and method for backing up data in case of power failure
    JP2006107326A (en) 2004-10-08 2006-04-20 Oki Electric Ind Co Ltd Semiconductor integrated circuit
    US7480761B2 (en) * 2005-01-10 2009-01-20 Microsoft Corporation System and methods for an overlay disk and cache using portable flash memory
    JP4681900B2 (en) * 2005-02-04 2011-05-11 富士通株式会社 Stop status monitoring method of the computer, the information processing apparatus and program
    KR100684942B1 (en) * 2005-02-07 2007-02-20 삼성전자주식회사 Adaptive flash memory control device with multiple mapping schemes and flash memory system havintg the same
    CA2597551A1 (en) * 2005-02-11 2006-08-17 M-Systems Flash Disk Pioneers Ltd. Nand flash memory system architecture
    US8452929B2 (en) * 2005-04-21 2013-05-28 Violin Memory Inc. Method and system for storage of data in non-volatile media
    US8244958B2 (en) * 2005-05-09 2012-08-14 Sandisk Il Ltd. Method and system for facilitating fast wake-up of a flash memory system
    US7512838B2 (en) * 2005-05-10 2009-03-31 Spectra Logic Corporation Data integrity analysis for a data storage system
    JP4215746B2 (en) * 2005-05-20 2009-01-28 Necインフロンティア株式会社 Information processing apparatus and life monitoring methods
    US7644309B2 (en) * 2005-05-20 2010-01-05 Nokia Corporation Recovering a hardware module from a malfunction
    US7797479B2 (en) * 2005-06-30 2010-09-14 Intel Corporation Technique to write to a non-volatile memory
    US20070005874A1 (en) 2005-07-01 2007-01-04 Dan Dodge File system storing transaction records in flash-like media
    US7873683B2 (en) 2005-07-01 2011-01-18 Qnx Software Systems Gmbh & Co. Kg File system having transaction record coalescing
    US7970803B2 (en) * 2005-07-01 2011-06-28 Qnx Software Systems Gmbh & Co. Kg Optimized startup verification of file system integrity
    US7809777B2 (en) * 2005-07-01 2010-10-05 Qnx Software Systems Gmbh & Co. Kg File system having deferred verification of data integrity
    US8959125B2 (en) 2005-07-01 2015-02-17 226008 Ontario Inc. File system having inverted hierarchical structure
    KR100739722B1 (en) * 2005-08-20 2007-07-13 삼성전자주식회사 A method for managing a flash memory and a flash memory system
    JP5008845B2 (en) 2005-09-01 2012-08-22 株式会社日立製作所 Storage system and the storage device and control method thereof
    US8429326B2 (en) 2005-09-12 2013-04-23 Mediatek Inc. Method and system for NAND-flash identification without reading device ID table
    US20070089023A1 (en) * 2005-09-30 2007-04-19 Sigmatel, Inc. System and method for system resource access
    US9047344B2 (en) * 2005-10-17 2015-06-02 International Business Machines Corporation Guaranteeing data and metadata referential integrity in content management archival solutions
    WO2007056713A3 (en) * 2005-11-04 2007-11-22 Univ Columbia An optical network
    US7747812B2 (en) * 2005-12-22 2010-06-29 Pitney Bowes Inc. Method for manipulating state machine storage in a small memory space
    WO2007072313A3 (en) * 2005-12-22 2008-01-24 Nxp Bv Memory with block-erasable locations and a linked chain of pointers to locate blocks with pointer information
    KR100755702B1 (en) * 2005-12-27 2007-09-05 삼성전자주식회사 Storage apparatus using non volatile memory as cache and method for operating the same
    US20070156974A1 (en) * 2006-01-03 2007-07-05 Haynes John E Jr Managing internet small computer systems interface communications
    US7992128B2 (en) * 2006-01-27 2011-08-02 Sap Ag Computer software adaptation method and 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
    US7552148B2 (en) * 2006-02-28 2009-06-23 Microsoft Corporation Shutdown recovery
    KR100622113B1 (en) * 2006-03-03 2006-09-01 주식회사 퓨전소프트 Flash memory storing system for database system and method therefor
    JP2007237693A (en) * 2006-03-10 2007-09-20 Oki Data Corp Image processor
    US7779426B2 (en) * 2006-03-30 2010-08-17 Microsoft Corporation Describing and querying discrete regions of flash storage
    FI20060427A (en) * 2006-05-03 2007-11-04 Tellabs Oy A method and apparatus for processing a sequential
    US7716411B2 (en) 2006-06-07 2010-05-11 Microsoft Corporation Hybrid memory device with single interface
    FI120220B (en) * 2006-06-08 2009-07-31 Tellabs Oy Method and arrangement for processing transactions, the flash-type memory
    US8307148B2 (en) * 2006-06-23 2012-11-06 Microsoft Corporation Flash management techniques
    US7650458B2 (en) * 2006-06-23 2010-01-19 Microsoft Corporation Flash memory driver
    US7844878B2 (en) 2006-08-09 2010-11-30 Microsoft Corporation Dynamic electronic correction code feedback to extend memory device lifetime
    US7908276B2 (en) 2006-08-25 2011-03-15 Qnx Software Systems Gmbh & Co. Kg Filesystem having a filename cache
    US8566503B2 (en) * 2006-08-25 2013-10-22 Qnx Software Systems Limited Multimedia filesystem having unified representation of content on diverse multimedia devices
    US20080059510A1 (en) * 2006-08-31 2008-03-06 Daniel Cardamore Multimedia system framework having layer consolidating access to multiple media devices
    US20080077590A1 (en) * 2006-09-22 2008-03-27 Honeywell International Inc. Efficient journaling and recovery mechanism for embedded flash file systems
    KR100855467B1 (en) 2006-09-27 2008-09-01 삼성전자주식회사 Apparatus and method for mapping of nonvolatile non-volatile memory supporting separated cell type
    US7477535B2 (en) * 2006-10-05 2009-01-13 Nokia Corporation 3D chip arrangement including memory manager
    US20080086603A1 (en) * 2006-10-05 2008-04-10 Vesa Lahtinen Memory management method and system
    JP2008123473A (en) * 2006-10-20 2008-05-29 Toshiba Corp Memory device and its control method
    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
    US8296337B2 (en) 2006-12-06 2012-10-23 Fusion-Io, Inc. Apparatus, system, and method for managing data from a requesting device with an empty data token directive
    US9116823B2 (en) 2006-12-06 2015-08-25 Intelligent Intellectual Property Holdings 2 Llc Systems and methods for adaptive error-correction coding
    US9519540B2 (en) 2007-12-06 2016-12-13 Sandisk Technologies Llc Apparatus, system, and method for destaging cached data
    US8195912B2 (en) * 2007-12-06 2012-06-05 Fusion-io, Inc Apparatus, system, and method for efficient mapping of virtual and physical addresses
    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
    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
    US9495241B2 (en) 2006-12-06 2016-11-15 Longitude Enterprise Flash S.A.R.L. Systems and methods for adaptive data storage
    US8489817B2 (en) 2007-12-06 2013-07-16 Fusion-Io, Inc. Apparatus, system, and method for caching data
    KR101442145B1 (en) 2007-01-11 2014-09-23 삼성전자 주식회사 Apparatus and method for managing data
    US7966355B2 (en) * 2007-02-13 2011-06-21 Modu Ltd. Interface for extending functionality of memory cards
    JP4372168B2 (en) * 2007-02-19 2009-11-25 株式会社東芝 The semiconductor memory information storage apparatus and the accumulated data processing method
    US20080228992A1 (en) * 2007-03-01 2008-09-18 Douglas Dumitru System, method and apparatus for accelerating fast block devices
    WO2008106686A1 (en) * 2007-03-01 2008-09-04 Douglas Dumitru Fast block device and methodology
    US20080250194A1 (en) * 2007-04-03 2008-10-09 Ming-Sheng Chen Two-dimensional writing data method for flash memory and corresponding storage device
    US7870327B1 (en) * 2007-04-25 2011-01-11 Apple Inc. Controlling memory operations using a driver and flash memory type tables
    US7840837B2 (en) * 2007-04-27 2010-11-23 Netapp, Inc. System and method for protecting memory during system initialization
    US8041883B2 (en) * 2007-05-09 2011-10-18 Stmicroelectronics S.R.L. Restoring storage devices based on flash memories and related circuit, system, and method
    US7882301B2 (en) * 2007-05-09 2011-02-01 Stmicroelectronics S.R.L. Wear leveling in storage devices based on flash memories and related circuit, system, and method
    US20080282024A1 (en) * 2007-05-09 2008-11-13 Sudeep Biswas Management of erase operations in storage devices based on flash memories
    US7991942B2 (en) 2007-05-09 2011-08-02 Stmicroelectronics S.R.L. Memory block compaction method, circuit, and system in storage devices based on flash memories
    US7836331B1 (en) 2007-05-15 2010-11-16 Netapp, Inc. System and method for protecting the contents of memory during error conditions
    US7882337B2 (en) * 2007-05-19 2011-02-01 International Business Machines Corporation Method and system for efficient tentative tracing of software in multiprocessors
    US7676704B2 (en) 2007-06-29 2010-03-09 Symantec Corporation Resource management for scalable file system recovery
    WO2009025683A1 (en) * 2007-08-21 2009-02-26 Thomson Licensing Method and system for repairing damaged hard disk file systems
    US8214641B2 (en) * 2007-08-23 2012-07-03 Microsoft Corporation File access in multi-protocol environment
    US7719890B2 (en) * 2007-09-12 2010-05-18 Sandisk Corporation Data protection for write abort
    KR101345386B1 (en) * 2007-09-19 2013-12-24 삼성전자주식회사 Multimedia data editing method and apparatus
    US7805632B1 (en) * 2007-09-24 2010-09-28 Net App, Inc. Storage system and method for rapidly recovering from a system failure
    EP2043105A1 (en) 2007-09-26 2009-04-01 Siemens Aktiengesellschaft Copying method for NAND flash memory
    KR20090042039A (en) * 2007-10-25 2009-04-29 삼성전자주식회사 Data management method for nonvolatile memory device
    CN101452745B (en) 2007-11-30 2011-08-31 无锡华润矽科微电子有限公司 Programmer and programming method thereof
    US8533384B2 (en) 2007-12-27 2013-09-10 Sandisk Enterprise Ip Llc Flash memory controller garbage collection operations performed independently in multiple flash memory groups
    GB0725327D0 (en) * 2007-12-28 2008-02-06 Symbian Software Ltd File storage method and system
    CN101551779B (en) * 2008-04-02 2014-11-05 深圳市朗科科技股份有限公司 Computers and data storage method
    US9477587B2 (en) * 2008-04-11 2016-10-25 Micron Technology, Inc. Method and apparatus for a volume management system in a non-volatile memory device
    US20090271563A1 (en) * 2008-04-28 2009-10-29 Microsoft Corporation Flash memory transactioning
    US7979626B2 (en) * 2008-05-13 2011-07-12 Microsoft Corporation Flash recovery employing transaction log
    US8843691B2 (en) * 2008-06-25 2014-09-23 Stec, Inc. Prioritized erasure of data blocks in a flash storage device
    JP5029513B2 (en) * 2008-06-30 2012-09-19 ソニー株式会社 The information processing apparatus, a method of controlling an information processing apparatus, and program
    JP2010020586A (en) * 2008-07-11 2010-01-28 Nec Electronics Corp Data processing device
    US8055846B2 (en) 2008-08-15 2011-11-08 International Business Machines Corporation Data vaulting in emergency shutdown
    US9542431B2 (en) * 2008-10-24 2017-01-10 Microsoft Technology Licensing, Llc Cyclic commit transaction protocol
    KR101555022B1 (en) * 2008-12-02 2015-09-23 삼성전자주식회사 Memory device, memory system and how to restore it to its mapping information, including
    JP5317690B2 (en) * 2008-12-27 2013-10-16 株式会社東芝 Memory system
    US8266370B2 (en) * 2009-01-13 2012-09-11 Innostor Technology Corporation Method for processing data of flash memory by separating levels and flash memory device thereof
    CN101789259B (en) 2009-01-22 2013-05-08 银灿科技股份有限公司 Order-based layered data processing method and device applied to flash memory
    US8090899B1 (en) 2009-03-04 2012-01-03 Western Digital Technologies, Inc. Solid state drive power safe wear-leveling
    US8452734B2 (en) * 2009-04-30 2013-05-28 Texas Instruments Incorporated FAT file in reserved cluster with ready entry state
    US20100321811A1 (en) * 2009-06-19 2010-12-23 Spectra Logic Corporation Drive life cycle management
    WO2011031796A3 (en) 2009-09-08 2011-06-30 Fusion-Io, Inc. Apparatus, system, and method for caching data on a solid-state storage device
    US8984216B2 (en) 2010-09-09 2015-03-17 Fusion-Io, Llc Apparatus, system, and method for managing lifetime of a storage device
    US8601222B2 (en) 2010-05-13 2013-12-03 Fusion-Io, Inc. Apparatus, system, and method for conditional and atomic storage operations
    JP5518197B2 (en) 2009-09-09 2014-06-11 フュージョン−アイオー・インコーポレーテッド Apparatus for allocating storage, system, and method
    WO2011031899A3 (en) 2009-09-09 2011-06-16 Fusion-Io, Inc. Apparatus, system, and method for power reduction in a storage device
    US9223514B2 (en) 2009-09-09 2015-12-29 SanDisk Technologies, Inc. Erase suspend/resume for memory
    US9122579B2 (en) 2010-01-06 2015-09-01 Intelligent Intellectual Property Holdings 2 Llc Apparatus, system, and method for a storage layer
    EP2302637B1 (en) 2009-09-21 2014-09-03 STMicroelectronics (Rousset) SAS Method for writing data in a non-volatile memory, protected against removal
    FR2950464B1 (en) * 2009-09-21 2012-03-16 St Microelectronics Rousset wear leveling method in a nonvolatile memory
    US8171257B2 (en) * 2009-09-25 2012-05-01 International Business Machines Corporation Determining an end of valid log in a log of write records using a next pointer and a far ahead pointer
    US8990476B2 (en) * 2009-10-01 2015-03-24 Micron Technology, Inc. Power interrupt management
    US8271719B2 (en) * 2009-10-29 2012-09-18 Freescale Semiconductor, Inc. Non-volatile memory controller device and method therefor
    KR101043238B1 (en) * 2009-11-25 2011-06-30 주식회사 바우압텍 Electro-Static Discharge Protection Device for high voltage operation
    US8886870B2 (en) * 2010-05-25 2014-11-11 Marvell World Trade Ltd. Memory access table saving and restoring system and methods
    US8959284B1 (en) 2010-06-28 2015-02-17 Western Digital Technologies, Inc. Disk drive steering write data to write cache based on workload
    EP2598996A4 (en) 2010-07-28 2013-12-18 Fusion Io Inc Apparatus, system, and method for conditional and atomic storage operations
    US9058280B1 (en) 2010-08-13 2015-06-16 Western Digital Technologies, Inc. Hybrid drive migrating data from disk to non-volatile semiconductor memory based on accumulated access time
    US9268499B1 (en) 2010-08-13 2016-02-23 Western Digital Technologies, Inc. Hybrid drive migrating high workload data from disk to non-volatile semiconductor memory
    US8775720B1 (en) 2010-08-31 2014-07-08 Western Digital Technologies, Inc. Hybrid drive balancing execution times for non-volatile semiconductor memory and disk
    US8782334B1 (en) 2010-09-10 2014-07-15 Western Digital Technologies, Inc. Hybrid drive copying disk cache to non-volatile semiconductor memory
    US9208071B2 (en) 2010-12-13 2015-12-08 SanDisk Technologies, Inc. Apparatus, system, and method for accessing memory
    US9218278B2 (en) 2010-12-13 2015-12-22 SanDisk Technologies, Inc. Auto-commit memory
    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
    WO2012100087A3 (en) 2011-01-19 2012-09-20 Fusion-Io, Inc. Apparatus, system, and method for managing out-of-service conditions
    US8966184B2 (en) 2011-01-31 2015-02-24 Intelligent Intellectual Property Holdings 2, LLC. Apparatus, system, and method for managing eviction of data
    US9003104B2 (en) 2011-02-15 2015-04-07 Intelligent Intellectual Property Holdings 2 Llc Systems and methods for a file-level cache
    US8874823B2 (en) 2011-02-15 2014-10-28 Intellectual Property Holdings 2 Llc Systems and methods for managing data input/output operations
    WO2012116369A3 (en) 2011-02-25 2013-03-14 Fusion-Io, Inc. Apparatus, system, and method for managing contents of a cache
    WO2012129191A3 (en) 2011-03-18 2012-12-27 Fusion-Io, Inc. Logical interfaces for contextual storage
    US9563555B2 (en) 2011-03-18 2017-02-07 Sandisk Technologies Llc Systems and methods for storage allocation
    US20120246384A1 (en) * 2011-03-21 2012-09-27 Winbond Electronics Corp. Flash memory and flash memory accessing method
    WO2012143944A3 (en) * 2011-04-18 2013-01-03 Ineda Systems Pvt. Ltd Multi-host nand flash controller
    US9201677B2 (en) 2011-05-23 2015-12-01 Intelligent Intellectual Property Holdings 2 Llc Managing data input/output operations
    CN103164345B (en) * 2011-12-08 2016-04-27 光宝科技股份有限公司 The data storage method of the solid state storage device after the encounter off
    US8725934B2 (en) 2011-12-22 2014-05-13 Fusion-Io, Inc. Methods and appratuses for 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
    US9141308B2 (en) 2011-12-30 2015-09-22 Sandisk Technologies Inc. Controller and method for using a transaction flag for page protection
    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
    US9116812B2 (en) 2012-01-27 2015-08-25 Intelligent Intellectual Property Holdings 2 Llc Systems and methods for a de-duplication cache
    CN102662878B (en) * 2012-02-27 2015-01-21 深圳市硅格半导体有限公司 Identifying-driving method and device for software layer of storage device
    KR20130101776A (en) * 2012-03-06 2013-09-16 삼성전자주식회사 Apparatas and method of providing a file system function in a terminal
    US9075758B2 (en) 2012-03-19 2015-07-07 Samsung Electronics Co., Ltd. Removable storage device with transactional operation support and system including same
    US9135182B2 (en) * 2012-06-01 2015-09-15 Semiconductor Energy Laboratory Co., Ltd. Central processing unit and driving method thereof
    US9612966B2 (en) 2012-07-03 2017-04-04 Sandisk Technologies Llc Systems, methods and apparatus for a virtual machine cache
    US9699263B1 (en) 2012-08-17 2017-07-04 Sandisk Technologies Llc. Automatic read and write acceleration of data accessed by virtual machines
    US20140068183A1 (en) 2012-08-31 2014-03-06 Fusion-Io, Inc. Systems, methods, and interfaces for adaptive persistence
    US8959281B1 (en) 2012-11-09 2015-02-17 Western Digital Technologies, Inc. Data management for a storage device
    US8954694B2 (en) 2012-11-15 2015-02-10 Western Digital Technologies, Inc. Methods, data storage devices and systems for fragmented firmware table rebuild in a solid state drive
    US9047172B2 (en) 2012-11-29 2015-06-02 Intel Corporation Adaptive power control of memory map storage devices
    CN103049284A (en) * 2012-12-06 2013-04-17 深圳市金立通信设备有限公司 Electronic device, electronic terminal and method for protecting electronic terminal memory card
    US9690642B2 (en) * 2012-12-18 2017-06-27 Western Digital Technologies, Inc. Salvaging event trace information in power loss interruption scenarios
    US9501398B2 (en) 2012-12-26 2016-11-22 Sandisk Technologies Llc Persistent storage device with NVRAM for staging writes
    US9239751B1 (en) 2012-12-27 2016-01-19 Sandisk Enterprise Ip Llc Compressing data from multiple reads for error control management in memory systems
    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
    US9454420B1 (en) 2012-12-31 2016-09-27 Sandisk Technologies Llc Method and system of reading threshold voltage equalization
    CN103092727B (en) * 2013-01-18 2015-08-26 大唐移动通信设备有限公司 Method and apparatus for error correction data on a storage medium Flash
    US9870830B1 (en) 2013-03-14 2018-01-16 Sandisk Technologies Llc Optimal multilevel sensing for reading data from a storage medium
    US9478271B2 (en) 2013-03-14 2016-10-25 Seagate Technology Llc Nonvolatile memory data recovery after power failure
    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
    US9367246B2 (en) 2013-03-15 2016-06-14 Sandisk Technologies Inc. Performance optimization of data transfer for soft information generation
    US9218279B2 (en) 2013-03-15 2015-12-22 Western Digital Technologies, Inc. Atomic write command support in a solid state drive
    US9842053B2 (en) 2013-03-15 2017-12-12 Sandisk Technologies Llc Systems and methods for persistent cache logging
    US9236886B1 (en) 2013-03-15 2016-01-12 Sandisk Enterprise Ip Llc Universal and reconfigurable QC-LDPC encoder
    US20140297688A1 (en) * 2013-04-02 2014-10-02 Western Digital Technologies, Inc. Methods and systems for privileged execution support for file system commands on a storage device
    US20140310499A1 (en) * 2013-04-16 2014-10-16 Fusion-Io, Inc. Systems, methods and interfaces for data virtualization
    US9170938B1 (en) 2013-05-17 2015-10-27 Western Digital Technologies, Inc. Method and system for atomically writing scattered information in a solid state storage device
    US9159437B2 (en) 2013-06-11 2015-10-13 Sandisk Enterprise IP LLC. Device and method for resolving an LM flag issue
    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
    US9141176B1 (en) 2013-07-29 2015-09-22 Western Digital Technologies, Inc. Power management for data storage device
    US9842128B2 (en) 2013-08-01 2017-12-12 Sandisk Technologies Llc Systems and methods for atomic storage operations
    KR20150018682A (en) 2013-08-08 2015-02-24 삼성전자주식회사 Storage system and writing method thereof
    US9361221B1 (en) 2013-08-26 2016-06-07 Sandisk Technologies Inc. Write amplification reduction through reliable writes during garbage collection
    US9639463B1 (en) 2013-08-26 2017-05-02 Sandisk Technologies Llc Heuristic aware garbage collection scheme in storage systems
    US9070379B2 (en) 2013-08-28 2015-06-30 Western Digital Technologies, Inc. Data migration for data storage device
    WO2015047284A1 (en) * 2013-09-27 2015-04-02 Empire Technology Development Llc Flexible storage block for a solid state drive (ssd)-based file system
    US9442662B2 (en) 2013-10-18 2016-09-13 Sandisk Technologies Llc Device and method for managing die groups
    US9298608B2 (en) 2013-10-18 2016-03-29 Sandisk Enterprise Ip Llc Biasing for wear leveling in storage systems
    US8917471B1 (en) 2013-10-29 2014-12-23 Western Digital Technologies, Inc. Power management for data storage 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
    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
    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
    US20160343455A1 (en) * 2014-01-31 2016-11-24 Hewlett Packard Enterprise Development Lp Remapping memory locations in a memory array
    US9703636B2 (en) 2014-03-01 2017-07-11 Sandisk Technologies Llc Firmware reversion trigger and control
    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
    US9626399B2 (en) 2014-03-31 2017-04-18 Sandisk Technologies Llc Conditional updates for reducing frequency of data modification operations
    US9390021B2 (en) 2014-03-31 2016-07-12 Sandisk Technologies Llc Efficient cache utilization in a tiered data structure
    US9697267B2 (en) 2014-04-03 2017-07-04 Sandisk Technologies Llc Methods and systems for performing efficient snapshots in tiered data structures
    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
    US9652381B2 (en) 2014-06-19 2017-05-16 Sandisk Technologies Llc Sub-block garbage collection
    US9639646B2 (en) * 2014-07-22 2017-05-02 Xilinx, Inc. System-on-chip intellectual property block discovery
    US20160070486A1 (en) * 2014-09-04 2016-03-10 HGST Netherlands B.V. Debug data saving in host memory on pcie solid state drive
    US9443601B2 (en) 2014-09-08 2016-09-13 Sandisk Technologies Llc Holdup capacitor energy harvesting
    US9811456B2 (en) * 2014-11-26 2017-11-07 Advanced Micro Devices, Inc. Reliable wear-leveling for non-volatile memory and method therefor
    US9946607B2 (en) 2015-03-04 2018-04-17 Sandisk Technologies Llc Systems and methods for storage error management
    KR20160110832A (en) 2015-03-13 2016-09-22 삼성전자주식회사 Memory system and operating method having meta data manager
    KR20160111222A (en) * 2015-03-16 2016-09-26 에스케이하이닉스 주식회사 Memory system including semiconductor memory device and memory controller, and operating method thereof
    WO2017048228A1 (en) * 2015-09-14 2017-03-23 Hewlett Packard Enterprise Development Lp Memory location remapping and wear-levelling
    US20170221582A1 (en) 2016-01-28 2017-08-03 International Business Machines Corporation Sorting non-volatile memories
    KR20180003715A (en) * 2016-06-30 2018-01-10 에스케이하이닉스 주식회사 Memory system and operating method of memory system
    US20180095680A1 (en) * 2016-09-30 2018-04-05 Amazon Technologies, Inc. Physical media aware spacially coupled journaling and replay

    Family Cites Families (105)

    * Cited by examiner, † Cited by third party
    Publication number Priority date Publication date Assignee Title
    US4635254A (en) 1984-12-13 1987-01-06 United Technologies Corporation Coherent interface with wraparound receive memory
    JPH0682336B2 (en) * 1986-04-28 1994-10-19 日本電気株式会社 Rollback recovery system using block occlusion
    US5123104A (en) * 1988-04-08 1992-06-16 International Business Machines Corporation Method and apparatus for concurrent modification of an index tree in a transaction processing system utilizing selective indication of structural modification operations
    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
    WO1991016775A1 (en) * 1990-04-25 1991-10-31 Telxon Corporation Communication system with adaptive media access control
    US5276344A (en) * 1990-04-27 1994-01-04 Mitsubishi Denki Kabushiki Kaisha Field effect transistor having impurity regions of different depths and manufacturing method thereof
    GB2251323B (en) * 1990-12-31 1994-10-12 Intel Corp Disk emulation for a non-volatile semiconductor memory
    EP0506236A1 (en) * 1991-03-13 1992-09-30 International Business Machines Corporation Address translation mechanism
    US5663901A (en) * 1991-04-11 1997-09-02 Sandisk Corporation Computer memory cards using flash EEPROM integrated circuit chips and memory-controller systems
    US6347051B2 (en) * 1991-11-26 2002-02-12 Hitachi, Ltd. Storage device employing a flash memory
    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
    US5530626A (en) * 1992-01-31 1996-06-25 Leonard Bloom Athletic shoe and articles of clothing with replaceable unitary assembly for generating and broadcasting an audible signal
    JPH05233426A (en) * 1992-02-20 1993-09-10 Fujitsu Ltd Flash memory using method
    US5448719A (en) 1992-06-05 1995-09-05 Compaq Computer Corp. Method and apparatus for maintaining and retrieving live data in a posted write cache in case of power failure
    JP3328321B2 (en) * 1992-06-22 2002-09-24 株式会社日立製作所 A semiconductor memory device
    US5822781A (en) * 1992-10-30 1998-10-13 Intel Corporation Sector-based storage device emulator having variable-sized sector
    JP2856621B2 (en) * 1993-02-24 1999-02-10 インターナショナル・ビジネス・マシーンズ・コーポレイション Collective erasure type non-volatile memory and a semiconductor disk device using the same
    US5415350A (en) * 1993-03-06 1995-05-16 Goldstar Co., Ltd. Water spraying device for tableware washer
    JP3078946B2 (en) * 1993-03-11 2000-08-21 インターナショナル・ビジネス・マシーンズ・コーポレ−ション Management method and a semiconductor disk device of the batch erasable nonvolatile memory
    KR970008188B1 (en) * 1993-04-08 1997-05-21 가나이 쯔또무 Control method of flash memory and information processing apparatus using the same
    US5680618A (en) * 1993-05-26 1997-10-21 Borland International, Inc. Driver query and substitution for format independent native data access
    US5509134A (en) * 1993-06-30 1996-04-16 Intel Corporation Method and apparatus for execution of operations in a flash memory array
    US5682497A (en) * 1993-09-28 1997-10-28 Intel Corporation Managing file structures for a flash memory file system in a computer
    US5696917A (en) * 1994-06-03 1997-12-09 Intel Corporation Method and apparatus for performing burst read operations in an asynchronous nonvolatile memory
    US5627533A (en) 1994-08-05 1997-05-06 Hayes Microcomputer Products, Inc. Adjusting encoding table size and memory allocation for data compression in response to input data
    US5634060A (en) * 1994-08-09 1997-05-27 Unisys Corporation Method and apparatus for high-speed efficient bi-directional communication between multiple processor over a common bus
    JP3332619B2 (en) * 1994-11-29 2002-10-07 キヤノン株式会社 Decoding apparatus and method
    US5812775A (en) 1995-07-12 1998-09-22 3Com Corporation Method and apparatus for internetworking buffer management
    US5870757A (en) * 1995-09-11 1999-02-09 Sun Microsystems, Inc. Single transaction technique for a journaling file system of a computer operating system
    JP3604466B2 (en) 1995-09-13 2004-12-22 株式会社ルネサステクノロジ Flash disk card
    GB9519670D0 (en) 1995-09-27 1995-11-29 Memory Corp Plc Algorithm for an improved flash memory storage system
    US5933847A (en) * 1995-09-28 1999-08-03 Canon Kabushiki Kaisha Selecting erase method based on type of power supply for flash EEPROM
    US6014724A (en) * 1995-10-27 2000-01-11 Scm Microsystems (U.S.) Inc. Flash translation layer block indication map revision system and method
    US5867641A (en) * 1995-10-27 1999-02-02 Scm Microsystems (U.S.) Inc. Flash translation layer cleanup system and method
    US5987478A (en) * 1995-10-31 1999-11-16 Intel Corporation Virtual small block file manager for flash memory array
    US5799305A (en) * 1995-11-02 1998-08-25 Informix Software, Inc. Method of commitment in a distributed database transaction
    US5742818A (en) 1995-12-15 1998-04-21 Microsoft Corporation Method and system of converting data from a source file system to a target file system
    US5799168A (en) * 1996-01-05 1998-08-25 M-Systems Flash Disk Pioneers Ltd. Standardized flash controller
    GB9606928D0 (en) 1996-04-02 1996-06-05 Memory Corp Plc Memory devices
    US5696961A (en) * 1996-05-22 1997-12-09 Wang Laboratories, Inc. Multiple database access server for application programs
    US5832513A (en) * 1996-06-04 1998-11-03 Symantec Corporation Detecting significant file system alterations during execution of a storage media software utility
    JP3976839B2 (en) * 1996-07-09 2007-09-19 株式会社ルネサステクノロジ Non-volatile memory system and a non-volatile semiconductor memory
    KR100260028B1 (en) * 1996-08-13 2000-06-15 윤종용 Data recovery method in a file system
    GB2317721B (en) * 1996-09-30 2001-09-12 Nokia Mobile Phones Ltd Memory device
    US6047280A (en) * 1996-10-25 2000-04-04 Navigation Technologies Corporation Interface layer for navigation system
    US5956473A (en) * 1996-11-25 1999-09-21 Macronix International Co., Ltd. Method and system for managing a flash memory mass storage system
    US5745418A (en) * 1996-11-25 1998-04-28 Macronix International Co., Ltd. Flash memory mass storage system
    US5875478A (en) * 1996-12-03 1999-02-23 Emc Corporation Computer backup using a file system, network, disk, tape and remote archiving repository media system
    US6279069B1 (en) * 1996-12-26 2001-08-21 Intel Corporation Interface for flash EEPROM memory arrays
    US6035379A (en) * 1997-01-09 2000-03-07 Microsoft Corporation Transaction processing for user data employing both logging and shadow copying
    US5887198A (en) * 1997-04-07 1999-03-23 The United States Of America As Represented By The Secretary Of The Navy Programmable stand-alone drive apparatus for interfacing a host computer with PCMCIA memory cards having multiple formats
    US5974546A (en) * 1997-05-08 1999-10-26 Micron Electronics, Inc. Apparatus and method to determine cause of failed boot sequence to improve likelihood of successful subsequent boot attempt
    JPH117505A (en) * 1997-06-17 1999-01-12 Fujitsu Ltd Card type storage medium
    GB9713094D0 (en) * 1997-06-21 1997-08-27 Philips Electronics Nv Optical disc drive
    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
    US6233584B1 (en) * 1997-09-09 2001-05-15 International Business Machines Corporation Technique for providing a universal query for multiple different databases
    US5967425A (en) * 1997-09-22 1999-10-19 Wang; Shoei-Yuan Air blast apparatus for yarn drawing machines
    US5960434A (en) * 1997-09-26 1999-09-28 Silicon Graphics, Inc. System method and computer program product for dynamically sizing hash tables
    US5991778A (en) * 1997-09-30 1999-11-23 Stratfor Systems, Inc. Method and apparatus for real-time secure file deletion
    US6070174A (en) * 1997-09-30 2000-05-30 Infraworks Corporation Method and apparatus for real-time secure file deletion
    US6061788A (en) * 1997-10-02 2000-05-09 Siemens Information And Communication Networks, Inc. System and method for intelligent and reliable booting
    US5937425A (en) * 1997-10-16 1999-08-10 M-Systems Flash Disk Pioneers Ltd. Flash file system optimized for page-mode flash technologies
    JP3503448B2 (en) * 1997-11-04 2004-03-08 日本ビクター株式会社 Flash memory and its management device
    US6009520A (en) 1997-12-10 1999-12-28 Phoenix Technologies, Ltd Method and apparatus standardizing use of non-volatile memory within a BIOS-ROM
    US6148349A (en) * 1998-02-06 2000-11-14 Ncr Corporation Dynamic and consistent naming of fabric attached storage by a file system on a compute node storing information mapping API system I/O calls for data objects with a globally unique identification
    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
    US6067628A (en) * 1998-04-09 2000-05-23 Intel Corporation Method to monitor universal serial bus hub overcurrent
    US6226728B1 (en) * 1998-04-21 2001-05-01 Intel Corporation Dynamic allocation for efficient management of variable sized data within a nonvolatile memory
    US6223284B1 (en) * 1998-04-30 2001-04-24 Compaq Computer Corporation Method and apparatus for remote ROM flashing and security management for a computer system
    US6009620A (en) * 1998-07-15 2000-01-04 International Business Machines Corporation Method of making a printed circuit board having filled holes
    JP3519954B2 (en) * 1998-07-30 2004-04-19 富士通株式会社 Chip enable signal generation circuit and a memory device
    US6230285B1 (en) * 1998-09-08 2001-05-08 Symantec Corporation Boot failure recovery
    US6336158B1 (en) * 1998-10-30 2002-01-01 Intel Corporation Memory based I/O decode arrangement, and system and method using the same
    JP3311305B2 (en) * 1998-11-19 2002-08-05 沖電気工業株式会社 Synchronous burst nonvolatile semiconductor memory device
    US6421792B1 (en) 1998-12-03 2002-07-16 International Business Machines Corporation Data processing system and method for automatic recovery from an unsuccessful boot
    JP2000231483A (en) * 1999-02-08 2000-08-22 Digital Electronics Corp Computer with semiconductor recording medium
    GB9903490D0 (en) * 1999-02-17 1999-04-07 Memory Corp Plc Memory system
    US6427186B1 (en) 1999-03-30 2002-07-30 Frank (Fong-Long) Lin Memory, interface system and method for mapping logical block numbers to physical sector numbers in a flash memory, using a master index table and a table of physical sector numbers
    JP3389186B2 (en) * 1999-04-27 2003-03-24 松下電器産業株式会社 Semiconductor memory card and a reading device
    EP1058269B1 (en) * 1999-05-31 2006-03-29 SGS-THOMSON MICROELECTRONICS S.r.l. Synchronous multilevel non-volatile memory and related reading method
    US6493807B1 (en) * 1999-07-01 2002-12-10 Intel Corporation Updating flash blocks
    JP2001033846A (en) 1999-07-26 2001-02-09 Nidec Copal Corp Shutter for camera
    JP2001101071A (en) * 1999-09-29 2001-04-13 Victor Co Of Japan Ltd Data storage device using flash type memory and data managing method for the same memory
    US6377500B1 (en) * 1999-11-11 2002-04-23 Kabushiki Kaisha Toshiba Memory system with a non-volatile memory, having address translating function
    JP2001142774A (en) 1999-11-11 2001-05-25 Toshiba Corp Memory card and address converting method to be applied to it
    US6839623B1 (en) * 2000-02-16 2005-01-04 Telefonaktiebolaget Lm Ericsson (Publ) Positioning applications for an electronic reading device
    US6601073B1 (en) * 2000-03-22 2003-07-29 Navigation Technologies Corp. Deductive database architecture for geographic data
    US6633956B1 (en) * 2000-04-14 2003-10-14 Mitsubishi Denki Kabushiki Kaisha Memory card with task registers storing physical addresses
    JP2001325127A (en) * 2000-05-15 2001-11-22 Sony Corp Access method and recording or reproducing device
    JP2001338468A (en) * 2000-05-26 2001-12-07 Hitachi Ltd Control method of storage device and storage device
    JP2001356998A (en) * 2000-06-14 2001-12-26 Denso Corp Method for making device driver
    US6438638B1 (en) * 2000-07-06 2002-08-20 Onspec Electronic, Inc. Flashtoaster for reading several types of flash-memory cards with or without a PC
    US6510488B2 (en) * 2001-02-05 2003-01-21 M-Systems Flash Disk Pioneers Ltd. Method for fast wake-up of a flash memory system
    US6741603B2 (en) 2001-07-09 2004-05-25 Overture Networks, Inc. Use of a circular buffer to assure in-order delivery of packets
    JP2003036204A (en) 2001-07-23 2003-02-07 Matsushita Electric Ind Co Ltd Flash memory update method
    GB0123415D0 (en) * 2001-09-28 2001-11-21 Memquest Ltd Method of writing data to non-volatile memory
    US7533214B2 (en) 2002-02-27 2009-05-12 Microsoft Corporation Open architecture flash driver
    US6621746B1 (en) * 2002-02-27 2003-09-16 Microsoft Corporation Monitoring entropic conditions of a flash memory device as an indicator for invoking erasure operations
    US6901499B2 (en) * 2002-02-27 2005-05-31 Microsoft Corp. System and method for tracking data stored in a flash memory device
    US20050036387A1 (en) * 2002-04-24 2005-02-17 Seal Brian K. Method of using flash memory for storing metering data
    US7181611B2 (en) * 2002-10-28 2007-02-20 Sandisk Corporation Power management block for use in a non-volatile memory system
    US7174432B2 (en) 2003-08-19 2007-02-06 Nvidia Corporation Asynchronous, independent and multiple process shared memory system in an adaptive computing architecture
    US7480760B2 (en) * 2003-12-17 2009-01-20 Wegener Communications, Inc. Rotational use of memory to minimize write cycles
    US8032787B2 (en) 2004-09-02 2011-10-04 Intel Corporation Volatile storage based power loss recovery mechanism
    US7716464B2 (en) 2005-06-23 2010-05-11 Intel Corporation Method to have fault resilient booting

    Also Published As

    Publication number Publication date Type
    EP1351126A3 (en) 2003-10-22 application
    JP2003271444A (en) 2003-09-26 application
    US7340647B2 (en) 2008-03-04 grant
    US20060168474A1 (en) 2006-07-27 application
    US7533214B2 (en) 2009-05-12 grant
    US20050216653A1 (en) 2005-09-29 application
    US20040078666A1 (en) 2004-04-22 application
    CN1303498C (en) 2007-03-07 grant
    US7350105B2 (en) 2008-03-25 grant
    US20030163632A1 (en) 2003-08-28 application
    US7076599B2 (en) 2006-07-11 grant
    US7139883B2 (en) 2006-11-21 grant
    JP4658455B2 (en) 2011-03-23 grant
    US7620961B2 (en) 2009-11-17 grant
    US20030163594A1 (en) 2003-08-28 application
    CN1441338A (en) 2003-09-10 application
    US20030163635A1 (en) 2003-08-28 application
    US20060179211A1 (en) 2006-08-10 application
    US7178061B2 (en) 2007-02-13 grant
    EP1351126A2 (en) 2003-10-08 application

    Similar Documents

    Publication Publication Date Title
    US5479638A (en) Flash memory mass storage architecture incorporation wear leveling technique
    US6134151A (en) Space management for managing high capacity nonvolatile memory
    US5809558A (en) Method and data storage system for storing data in blocks without file reallocation before erasure
    US5860124A (en) Method for performing a continuous over-write of a file in nonvolatile memory
    US7552271B2 (en) Nonvolatile memory with block management
    US5598370A (en) Nonvolatile memory with cluster-erase flash capability and solid state file apparatus using the same
    US5630093A (en) Disk emulation for a non-volatile semiconductor memory utilizing a mapping table
    US20050166087A1 (en) Non-volatile memory and method with phased program failure handling
    US20050144367A1 (en) Data run programming
    US5953737A (en) Method and apparatus for performing erase operations transparent to a solid state storage system
    US6636941B1 (en) Enhanced stable disk storage
    US7096313B1 (en) Tracking the least frequently erased blocks in non-volatile memory systems
    US6571326B2 (en) Space allocation for data in a nonvolatile memory
    US20100023672A1 (en) Method And System For Virtual Fast Access Non-Volatile RAM
    US20140215129A1 (en) Cooperative flash memory control
    US20060282610A1 (en) Flash memory with programmable endurance
    US7426623B2 (en) System and method for configuring flash memory partitions as super-units
    EP0686976A2 (en) Data management system for programming-limited type semiconductor memory and IC memory card having the data management system
    US20070033362A1 (en) Mass data storage system
    US5937434A (en) Method of managing a symmetrically blocked nonvolatile memory having a bifurcated storage architecture
    US20080109590A1 (en) Flash memory system and garbage collection method thereof
    US7035967B2 (en) Maintaining an average erase count in a non-volatile storage system
    US7039788B1 (en) Method and apparatus for splitting a logical block
    US6831865B2 (en) Maintaining erase counts in non-volatile storage systems
    US5907854A (en) Flash memory file system for writing data files without rewriting an entire volume

    Legal Events

    Date Code Title Description
    AK Designated contracting states:

    Kind code of ref document: A2

    Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PT SE SI SK TR

    AX Request for extension of the european patent to

    Extension state: AL LT LV MK RO

    RIC1 Classification (correction)

    Ipc: 7G 06F 3/06 A

    Ipc: 7G 06F 11/14 B

    Ipc: 7G 06F 12/02 B

    AX Request for extension of the european patent to

    Extension state: AL LT LV MK RO

    AK Designated contracting states:

    Kind code of ref document: A3

    Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PT SE SI SK TR

    17P Request for examination filed

    Effective date: 20040406

    AKX Payment of designation fees

    Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PT SE SI SK TR

    17Q First examination report

    Effective date: 20041119

    RAP1 Transfer of rights of an ep published application

    Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC

    RIC1 Classification (correction)

    Ipc: G06F 17/30 20060101ALI20161215BHEP

    Ipc: G06F 11/14 20060101ALI20161215BHEP

    Ipc: G06F 12/02 20060101ALI20161215BHEP

    Ipc: G06F 3/06 20060101AFI20161215BHEP

    INTG Announcement of intention to grant

    Effective date: 20170105

    AK Designated contracting states:

    Kind code of ref document: B1

    Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PT SE SI SK TR

    REG Reference to a national code

    Ref country code: GB

    Ref legal event code: FG4D

    REG Reference to a national code

    Ref country code: AT

    Ref legal event code: REF

    Ref document number: 890681

    Country of ref document: AT

    Kind code of ref document: T

    Effective date: 20170515

    Ref country code: CH

    Ref legal event code: EP

    REG Reference to a national code

    Ref country code: IE

    Ref legal event code: FG4D

    REG Reference to a national code

    Ref country code: DE

    Ref legal event code: R096

    Ref document number: 60350179

    Country of ref document: DE

    REG Reference to a national code

    Ref country code: NL

    Ref legal event code: FP

    REG Reference to a national code

    Ref country code: AT

    Ref legal event code: MK05

    Ref document number: 890681

    Country of ref document: AT

    Kind code of ref document: T

    Effective date: 20170503

    PG25 Lapsed in a contracting state announced via postgrant inform. from nat. office to epo

    Ref country code: ES

    Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

    Effective date: 20170503

    Ref country code: GR

    Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

    Effective date: 20170804

    Ref country code: AT

    Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

    Effective date: 20170503

    Ref country code: FI

    Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

    Effective date: 20170503

    PG25 Lapsed in a contracting state announced via postgrant inform. from nat. office to epo

    Ref country code: SE

    Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

    Effective date: 20170503

    Ref country code: BG

    Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

    Effective date: 20170803

    REG Reference to a national code

    Ref country code: FR

    Ref legal event code: PLFP

    Year of fee payment: 16

    PGFP Postgrant: annual fees paid to national office

    Ref country code: FR

    Payment date: 20171211

    Year of fee payment: 16

    PG25 Lapsed in a contracting state announced via postgrant inform. from nat. office to epo

    Ref country code: DK

    Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

    Effective date: 20170503

    Ref country code: CZ

    Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

    Effective date: 20170503

    Ref country code: SK

    Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

    Effective date: 20170503

    Ref country code: EE

    Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

    Effective date: 20170503

    REG Reference to a national code

    Ref country code: DE

    Ref legal event code: R097

    Ref document number: 60350179

    Country of ref document: DE

    PG25 Lapsed in a contracting state announced via postgrant inform. from nat. office to epo

    Ref country code: IT

    Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

    Effective date: 20170503

    PGFP Postgrant: annual fees paid to national office

    Ref country code: NL

    Payment date: 20180115

    Year of fee payment: 16

    26N No opposition filed

    Effective date: 20180206

    PGFP Postgrant: annual fees paid to national office

    Ref country code: GB

    Payment date: 20180103

    Year of fee payment: 16

    Ref country code: DE

    Payment date: 20171228

    Year of fee payment: 16