Non-volatile solid-state storage system supporting high bandwidth and random access

Information

  • Patent Grant
  • 9164554
  • Patent Number
    9,164,554
  • Date Filed
    Monday, April 11, 2011
    13 years ago
  • Date Issued
    Tuesday, October 20, 2015
    9 years ago
Abstract
Approaches for a non-volatile, solid-state storage system that is capable of supporting high bandwidth and/or random read/write access. The storage system may include a chassis having a bus slot and a disk bay, a master card mounted in the bus slot, and a flash memory card stacked in the disk bay and cabled to the master card. The master card enables one or more flash memory cards to be communicatively coupled to a single PCI Express bus. The master card may split a multi-lane PCI Express bus into a plurality of lanes, where one or more of the flash memory cards communicate over each of the plurality of lanes. Alternately, the master card may includes active circuitry for processing, switching, routing, reformatting, and/or converting the PCI Express bus into one or more busses for a plurality of flash memory cards. The stacked flash memory card is not in an enclosure.
Description
FIELD OF THE INVENTION

Embodiments of the invention relate to a non-volatile, solid-state storage system that is capable of supporting high bandwidth and/or random read/write access.


BACKGROUND OF THE INVENTION

Processing nodes may be used to perform a variety of computational work. The composition of a processing node may include one or more of the following: one or more processors, memory (such as Dynamic Random Access Memory (DRAM) for example), one or more chips providing connectivity to the processors (such as Northbridge chips and/or Southbridge chips for example), one or more disk bays enabled to hold a respective disk (such as a 2.5″ or 3.5″ AT-compatible or SAT Compatible disk for example), peripherals (such as LEDs, microphones, speakers, and DVD drives), peripheral interfaces (such as USB slots), Input/Output (I/O) connections (such as Ethernet or RS-232 connections), and peripheral busses (such as a PCI bus and a PCI Express bus).


Some disk storage interfaces, such as the AT, ATA, SATA for example, are restrictive in bandwidth and/or capabilities. For example, AT and/or SATA disk interfaces are designed for block based transfers and are not optimized for random access.





BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the invention are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which like reference numerals refer to similar elements and in which:



FIG. 1 is an illustration of a processing node according to an embodiment of the invention;



FIG. 2A is an illustration of a memory sub-system according to an embodiment of the invention;



FIG. 2B is an illustration of memory sub-system controller according to an embodiment of the invention;



FIG. 2C is an illustration of a master card according to one embodiment of the invention;



FIG. 2D is an illustration of a master card according to another embodiment of the invention;



FIG. 3 is an illustration of a flash caddy for one or more NVM PCBs according to an embodiment of the invention;



FIG. 4 is an illustration of an example of techniques for using a spacer to mount a plurality of NVM PCBs according to an embodiment of the invention;



FIG. 5 is an illustration integrating one or more NVM PCBs into a flash caddy with PCB guides and formed bosses according to an embodiment of the invention;



FIG. 6 is an illustration of a rack-mounted chassis including a plurality of disk bays according to an embodiment of the invention; and



FIG. 7 is an illustration of the accessibility of a plurality of disk bays in a rack-mounted chassis according to an embodiment of the invention.





DETAILED DESCRIPTION OF THE INVENTION

Approaches for a non-volatile, solid-state storage system that is capable of supporting high bandwidth and/or random read/write access are described. In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the invention described herein. It will be apparent, however, that the embodiments of the invention described herein may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to avoid unnecessarily obscuring the embodiments of the invention described herein.


Techniques for designing, mounting, and fabricating a non-volatile, solid-state storage system are described. The non-volatile, solid-state storage system includes non-volatile memory, such as flash memory, for the persistent storage of data. According to various embodiments, the non-volatile, solid-state storage system interfaces uses one or more of: a high-speed, point-to-point interconnect, a PCI or PCI Express bus, a HyperTransport™ link (developed by the HyperTransport Consortium), and any similar bus or communication link. In some embodiments, the non-volatile, solid-state storage system uses disk slots (such as disk bays of a rack-mounted computer system) to hold one or more printed circuit boards (PCBs) containing at least a portion of the non-volatile, solid-state storage system. In various embodiments, the non-volatile, solid-state storage system is designed to support high bandwidth and/or provide for random access.



FIG. 1 illustrates processing node (180) according to an embodiment of the invention. The processing node includes one or more memory sub-systems (108, 108′). In various embodiments, the non-volatile, solid-state storage system includes the one or more memory sub-systems and optionally may include a battery back-up (125). The memory sub-systems include a memory sub-system controller (112) coupled to less-fine-grained memory 128 (such as flash memory) and optional fine-grained memory 124 (such as Dynamic Random Access Memory (DRAM)). Memory sub-system 108 is illustrated in further detail in FIG. 2A, and memory sub-system controller 112 is illustrated in further detail in FIG. 2B. In some embodiments, memory sub-system controller 112 is and/or includes an application specific integrated circuit (ASIC) and/or a field-programmable gate array (FPGA). In various embodiments, less-fine-grained memory 128 is a nonvolatile memory, such as flash memory. In further embodiments, less-fine-grained memory 128 is a page-based memory, such as NAND flash memory. As used herein, without limitation, the less-fine-grained memory is sometimes referred to as flash memory.


The processing node also includes a CPU complex (109) to execute software to control and/or to manage the processing node and to run application programs. The application programs, in some embodiments, advantageously use storage in the less-fine-grained memory 128. The processing node optionally includes peripheral devices (142) and/or connectivity to external devices (145). According to various embodiments, the software executed by the CPU complex is persistently stored in one or more of: a boot PROM or other non-volatile memory on a motherboard of the rack-mounted computer system, peripherals 142 (such as a PCMCIA card), external devices 145 (such as a hard disk drive in a disk bay), and less-fine-grained memory 128. The CPU complex includes CPU(s) 110, directly connected memory 134 coupled to the CPU(s) and serving, at least in part, as main memory of the CPU(s), and bridging 117 serving, at least in part, as external connectivity of the processors (such as a Northbridge and/or a Southbridge chip).


The processing node also may optionally includes switch 116 (including Network Interface Controller(s) 119) providing connectivity to other processing nodes (such as via external link(s) 146) to other nodes 148).


In order to provide a high-speed interface between processors and the non-volatile, solid-state storage system, a higher-performance and/or more flexible interface (as compared to some disk storage interfaces such as AT, ATA, and/or SATA) is used. For example, a PCI Express interface (and accordingly, a PCI Express bus) is used by certain embodiments, providing high bandwidths and a protocol suitable for both small (such as 64B) and large (such as many KB) data transfers. Using a PCI Express bus (or a similar bus) to communicate between the processors and the non-volatile, solid-state storage system provides an interface that is more optimized for accessing a high-speed, random-access memory. In various other embodiments, other busses and/or communications links, such as HyperTransport™ or InfiniBand®, may be used.


An issue in some rack-mounted computer systems is a lack of sufficient space, both on a motherboard and/or volumetrically in a chassis of the rack-mounted computer system. For example, some rack-mounted computer systems have a limitation as to a number of cards that can be plugged into a PCI (or PCI Express) bus on the motherboard, such as only having two PCI Express slots or connectors on the motherboard. Further, in some rack-mounted computer systems, the PCI Express slots have restrictions in card height and/or length. This limits the ability to provide the non-volatile, solid-state storage system (and/or to provide the non-volatile, solid-state storage system with a desired size) solely using the PCI Express bus slots.


To avoid the number and/or space limitations of the PCI Express slots, in some embodiments, the non-volatile, solid-state storage system uses physical space in the rack-mounted computer system that is intended for holding a disk drive. This physical space is termed a disk bay. A cable connects a master card (such as card 393 as illustrated in FIG. 2C or FIG. 2D) that is installed in one of the PCI Express slots on the motherboard to one or more flash memory cards in one or more of the disk bays. In various embodiments, the flash memory cards are same as or similar to memory subsystem 108 and include a controller (such as memory sub-system controller 112), a less fine-grained memory (such as less-fine-grained memory 128), and optionally a fine grained memory (such as fine-grained memory 124; of course, in various embodiments, the flash memory cards include any type or types of non-volatile memory, and calling these cards flash memory cards is not intended to be limiting).


The cable acts, for example, as a PCI Express extender cable and couples the flash memory cards to the PCI Express bus. In some embodiments, the PCI Express bus is represented, at least in part, via 133 as illustrated in FIGS. 1, 2C, and 2D, and the cable is represented as 133′ as illustrated in FIGS. 2A, 2B, 2C, and 2D. Each of the disk bays is capable of holding one or more of the flash memory cards. In some embodiments, the one or more flash memory cards are arranged in a stack in the disk bay and do not have an enclosure. A disk drive or a PCMCIA card have metal or plastic enclosures, such as a case that fully encloses circuitry of the disk drive or PCMCIA card, except for external connections and air ventilation. For example, in various embodiments, there are three flash memory cards stacked in one of the disk bays. In certain embodiments, the stacked flash memory cards are mounted in a flash caddy (such as illustrated in FIG. 3) which is installable in a disk bay.


In some embodiments, each of the flash memory cards is independently cabled to the master card. In other embodiments, a first group of one or more of the flash memory cards is cabled to the master card, and others of the flash memory cards are daisy chained to the first group of the flash memory cards. For example, in various embodiments, a first flash memory card in each of the disk bays holding the flash memory cards is cabled to the master card, and others of the flash memory cards in the disk bay are daisy chained to the first flash memory card. The flash memory cards that are not directly cabled to the master card are still visible and accessible on the PCI Express bus via a daisy chain connection (FIG. 2B illustrates one example of daisy chain connections (331 and 335) between flash memory cards). In some embodiments, the daisy chain connection forms a switched network among the flash memory cards. According to various embodiments, the daisy chain connection is configurable (for example, in a number of lanes and/or in bandwidth) and/or fault-tolerant.


In some embodiments, the master card and/or the flash memory cards are coupled in a hierarchical structure enabling a plurality of sub-controllers of flash memory chips and/or banks (such as logic 329.A, . . . , 329.Z as illustrated in FIG. 2A) on one or more flash memory cards to be accessed from as few as one PCI Express bus slot.


In an embodiment, the master card is a physical component that enables one or more flash memory cards to be communicatively coupled to a single PCI Express bus. In some embodiments, the master card (393 as illustrated in FIG. 2C) is passive, and, for example, just splits a multi-lane PCI Express bus (133) into sets of lanes (such as 133′) for one or more of the flash memory cards. In other embodiments, the master card is active (as illustrated in FIG. 2D) and includes active circuitry for one or more of processing, switching, routing, reformatting, and converting the PCI Express bus (133) into one or more busses (such as 133′) for the flash memory cards (the converted busses are optionally a different protocol and/or a different bandwidth than the PCI Express bus). If the master card is active, then the master card optionally includes circuitry for controlling and/or managing the flash memory cards.


In some embodiments, a battery back-up system (such as battery back-up 125 as illustrated in FIG. 1) is also located in the rack-mounted computer system. For example, the battery back-up system may be located in one of the disk bays, either separately from or in addition to one or more of the flash memory cards. In various embodiments, the battery back-up system replaces one of the flash memory cards. The battery back-up system is used to provide power to some or all of the non-volatile, solid-state storage system in the event of a power disruption to the rack-mounted computer system. According to various embodiments, the battery back-up system powers one or more of: (a) the flash memory cards in a same disk bay as the battery back-up system, (b) flash memory cards in any of the disk bays, and (c) any cards in the rack-mounted computer system, such as a portion of the non-volatile, solid-state storage system connected via a PCI Express slot (for example, the master card). Switching from normal power to power from the battery back-up system is done, in various embodiments, at various places, including but not limited to a backplane, at one or each of the flash memory cards, and at the master card. In some embodiments, the switching is a distributed and/or independent switching on each of the flash memory cards.


In some embodiments, a non-volatile, solid-state storage system comprises one or more non-volatile, solid-state memory (such as flash memory) printed circuit boards (NVM PCBs). In some embodiments, the NVM PCBs are flash memory cards. In various embodiments, the NVM PCBs are the same as or similar to memory sub-system 108 (as illustrated in FIG. 1 and FIG. 2A) and include a controller (such as memory subsystem controller 112), a less-tine-grained memory (such as less-fine-grained memory 128), and optionally a fine-grained memory (such as fine-grained memory 124).


The NVM PCBs are coupled to a PCI Express bus (or to a similar bus or communication link in a processing node). Across various embodiments, NVM PCBs may be implemented differently. To illustrate, the NVM PCBs may each coupled independently to the PCI Express bus, such as via a card on the PCI Express bus (such as card 393 as illustrated in FIG. 2C or FIG. 2D). Alternately, the NVM PCBs may be coupled together, such as in a daisy chain, with one or more of the NVM PCBs coupled to the PCI Express bus, such as via a card on the PCI Express bus, and zero or more of the NVM PCBs indirectly coupled to the PCI Express bus by coupling to another of the NVM PCBs. In other embodiments, the NVM PCBs may be each coupled to a backplane, where connectivity to the PCI Express bus, such as via a card on the PCI Express bus, is via the backplane. Alternately, the NVM PCBs may each be coupled to a backplane, where the backplane is and/or includes a card on the PCI Express bus.


According to various embodiments, the NVM PCBs are mounted in various fashions. To illustrate, in an embodiment, the NVM PCBs may be mounted one in a stack, such as a stack using mechanical spacers or electrical spacers (such as inter-board connectors). In other embodiments, the NVM PCBs may be mounted in a flash caddy, such as a caddy having, for each of the NVM PCBs, a respective one or more PCB guides.


According to various embodiments, the NVM PCBs are one or more of: a factory-replaceable unit; a field-replaceable unit; and a hot-swappable unit.


In some embodiments, a chassis (such as a rack-mounted chassis) includes one or more disk bays (such as disk bay 610 as illustrated in FIG. 6), and optionally houses a processing node. In various embodiments, one or more of the NVM PCBs are mounted in one or more of the disk bays of the chassis. In further embodiments, at least some of the disk bays are accessible from a front of the chassis, such as via a hinged (or sliding, or otherwise movable or removable) front panel. For example, as illustrated in FIG. 7, a hinged door (C in FIG. 7) provides access to a number of the disk bays, such as a proper subset of the disk bays. Accessing the proper subset of the disk bays via the front of the chassis enables, in some embodiments, removal and/or insertion, including hot-swapping, of ones of the NVM PCBs mounted in the proper subset of the disk bays. In various embodiments, the chassis may have any number of disk bays, such as one, two, four, eight, or twelve disk bays. In further embodiments, less than all of the disk bays are accessible from the front of the chassis, such as due to restrictions imposed by a design of the front panel.


In some embodiments, a battery back-up system is mounted in one or more of the disk bays. According to various embodiments, the battery back-up system (illustrated by G in FIG. 6 or 125 in FIG. 1) may be one or more of: (a) a factory-replaceable unit, (b) a field-replaceable unit, (c) a hot-swappable unit, (d) accessible from a front of the chassis, such as via a hinged (or sliding, or otherwise movable or removable) front panel, (e) used to provide back-up power to a card on the PCI Express bus, such as the card to which one or more of the NVM PCBs are coupled, (f) used to provide back-up power to one or more of the NVM PCBs, (g) coupled to the one or more NVM PCBs via one or more respective connectors, (h) coupled to the one or more NVM PCBs via a backplane, (i) coupled to the one or more NVM PCBs via a card on the PCI Express bus, such as the card to which one or more of the NVM PCBs are coupled, (j) mounted within the chassis, (k) substantially similar in mounting configuration to the NVM PCBs, and (l) substantially similar in mounting configuration to a flash caddy of the NVM PCBs.



FIG. 3 illustrates an example of using sheet metal, such as formed, perforated sheet metal, to act as a flash caddy for one or more NVM PCBs. Naturally occurring holes in the perforated sheet metal are used for one or more purposes, such as the venting of heat, holes for attaching PCB guides for sliding the NVM PCBs into and out of the assembly, and attachment of the PCB guides to the perforated sheet metal via one or more techniques (for example, by heat staking, ultrasonic deformation, snap fit, screws, and other mechanical fasteners).


In some embodiments, another technique that eliminates parts in the flash caddy (and reduces associated costs) is to make piercings, as illustrated in the lower right hand corner of FIG. 3.



FIG. 4 illustrates an example of techniques for using a specially designed spacer to mount, such as via Surface Mount Technology (SMT), a plurality of NVM PCBs. In some embodiments, the spacer simplifies joining of multiple NVM PCBs one to another and optionally to a caddy, such as a flash caddy. The spacer illustrated in FIG. 4 may be constructed using a variety of different materials. In an embodiment, the spacer may have tin plating on its exterior. The spacer of FIG. 4 allows NVM PCBs to be securely mounted in a substantially parallel fashion. The spacers of FIG. 4 also prevent the NVM PCBs from becoming dislocated if the NVM PCBs receive a mechanical shock as they firmly and securely maintain the NVM PCBs equidistant from each other.



FIG. 5 illustrates an example of techniques in which one or more NVM PCBs are integrated into a flash caddy with PCB guides and formed bosses. The NVM PCBs are optionally interconnected, such as with a board-to-board interconnect (for example, the spacer illustrated in FIG. 4) or a backplane interconnect, thereby reducing part count and/or minimizing space required to house the NVM PCBs. In the upper right hand corner, provision for board-to-board interconnection is illustrated via several techniques. For example, a card edge connector enables communication through a backplane and/or the board-to-board interconnect enables the daisy chain connection of two or more of the NVM PCBs.



FIG. 6 illustrates an example of a rack-mounted chassis including a plurality of disk bays (such as disk bay 610). The rack-mounted chassis (A in FIG. 6) includes a motherboard (C in FIG. 6), such as a PC motherboard. The motherboard has a PCI Express bus with connectors into which a PCI card (D in FIG. 6) is installed. The PCI card (for example, card 393 in FIG. 2C or FIG. 2D) is coupled to a backplane (B in FIG. 6), such as via a cable, for example 133′ as illustrated in FIG. 2C or 2D). The backplane is configured so that NVM PCBs (such as flash memory cards, E in FIG. 6) or a battery back-up card (G in FIG. 6) inserted into disk bays of the rack-mounted chassis are coupled to each other and/or to the PCI card via the backplane. The flash memory cards are optionally installed in a flash caddy (F in FIG. 6, similar to the flash caddy illustrated in FIG. 3 or to the flash caddy illustrated in FIG. 5). The flash memory cards assembled in the flash caddy are illustrated as H in FIG. 6. In some embodiments, the flash caddy is permanently installed within a disk bay, such as with screws to chassis metal. In other embodiments, the flash caddy slides into the disk bay and the flash caddy is removable. A removable flash caddy is optionally locked into place by snaps, screws, and/or other attachment systems.



FIG. 7 illustrates the accessibility of at least some of a plurality of disk bays in a rack-mounted chassis according to an embodiment. The rack-mounted chassis (A in FIG. 7) includes an optional removable bezel (B in FIG. 7) having a hinged door (C in FIG. 7) providing access to at least some of the disk bays.


Many embodiments are possible. Not all of these features need to be present in all embodiments, and many variations and sub-combinations of these features are contemplated by the inventor. The invention could be implemented in hardware, such as hardware logic gates and/or mechanical hardware, by a programmable processor either using firmware, software, or other code, or various combinations.


While the description above has used flash memory as an example, the techniques herein are applicable to any type of solid-state memory, such as NVRAM, FRAM, PRAM, or DRAM.


Embodiments of the invention may partition functions of a processing node and/or the non-volatile, solid-state storage system and/or a memory sub-system in a variety of fashions. In an embodiment, the processing node uses different types of CPUs, different peripherals, and/or different interfaces. In a different embodiment, the non-volatile, solid-state storage system includes one or more memory sub-systems and/or one or more cards (such as PCI Express cards) for coupling the one or more memory sub-systems to the CPU complex.


Embodiments of the invention may physically partition components of a processing node and/or the non-volatile, solid-state storage system and/or a memory sub-system differently. In one example, some or all of the non-volatile, solid-state storage system is located in disk bays of the processing node. In another example, a battery back-up is located in disk bays of the processing node and/or on a PCI Express card and/or on a motherboard. As another example, a first one of the flash memory cards is plugged into a PCI Express bus slot, and others of the flash memory cards are located in the disk bays of the processing node.


There are many ways of providing storage of electrical power in a battery back-up system. For example, the battery back-up system may include one or more of (a) a rechargeable battery, (b) a lithium-ion battery, (c) a lead-acid battery, (d) a capacitor, and (e) an ultra capacitor. Values can be inverted, offset, combined with other values, and manipulated in many ways using known mathematical properties. An inversion could be added to an XOR to generate an exclusive-NOR (XNOR), but this is simply a derivative of an XOR and within a family of XOR functions. Other logic tricks and manipulations are contemplated and considered to be within the scope of the invention.


In the foregoing specification, embodiments of the invention have been described with reference to numerous specific details that may vary from implementation to implementation. Thus, the sole and exclusive indicator of what is the invention, and is intended by the applicants to be the invention, is the set of claims that issue from this application, in the specific form in which such claims issue, including any subsequent correction. Any definitions expressly set forth herein for terms contained in such claims shall govern the meaning of such terms as used in the claims. Hence, no limitation, element, property, feature, advantage or attribute that is not expressly recited in a claim should limit the scope of such claim in any way. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense.

Claims
  • 1. A non-volatile, solid-state storage system, comprising: a plurality of flash memory cards, each flash memory card having flash memory devices mounted thereon, wherein the plurality of flash memory cards are arranged in a stack;a master card, configured to be mounted in a bus slot on a motherboard, wherein the master card enables the plurality of flash memory cards to each communicate over a single bus corresponding to the bus slot, and wherein the master card splits the single bus into a plurality of lanes to enable the plurality of flash memory cards to each communicate over a respective lane of the plurality of lanes; anda cable coupling the master card to the plurality of flash memory cards arranged in the stack;wherein the plurality of flash memory cards arranged in the stack includes:a first flash memory card electrically coupled to the master card via the cable to communicatively couple the first flash memory card to the single bus; anda second flash memory card, daisy chained to and distinct from the first flash memory card, wherein the second flash memory card is (a) directly electrically coupled to the first flash memory card, and (b) indirectly communicatively coupled to the master card via the first flash memory card.
  • 2. The system of claim 1, wherein the bus slot is a PCI Express bus slot.
  • 3. The system of claim 1, wherein the bus slot is a HyperTransport (HT) bus slot.
  • 4. The system of claim 1, wherein the plurality of flash memory cards arranged in the stack includes a third flash memory card that is (a) coupled to the first flash memory card and (b) not cabled to the master card, wherein the third flash memory card is indirectly communicatively coupled to the master card via the first flash memory card.
  • 5. The system of claim 1, further comprising: a third flash memory card that is (a) directly electrically coupled to the second flash memory card and (b) indirectly communicatively coupled to the master card via the first flash memory card and the second flash memory card.
  • 6. The system of claim 1, further comprising a battery back-up.
  • 7. The system of claim 6, wherein the battery back-up is coupled to the first and second flash memory cards.
  • 8. The system of claim 7, wherein: the system is included in a rack-mounted computer system; andthe battery back-up is on a back-up board mounted within a flash caddy installed in a disk bay of the rack-mounted computer system, the battery back-up providing back-up power to two or more flash memory cards of the plurality of flash memory cards mounted within the flash caddy, the flash caddy for receiving the two or more flash memory cards of the plurality of flash memory cards.
  • 9. The system of claim 1, wherein the system is included in a rack-mounted computer system and further comprises: a flash caddy, installed in a disk bay of the rack-mounted computer system, for receiving two or more flash memory cards of the plurality of flash memory cards in a stacked arrangement, the flash caddy enabled to separately receive at least the first flash memory card and the second flash memory card.
  • 10. The system of claim 9, wherein the flash caddy includes two or more sets of card guides to physically support two or more flash memory cards of the plurality of flash memory cards within the flash caddy, wherein a first set of card guides of the two or more sets of card guides is shaped to receive an edge of the first flash memory card and a second set of card guides of the two or more sets of card guides is shaped to receive an edge of the second flash memory card.
  • 11. The system of claim 9, further comprising: an inter-board interconnect on the first flash memory card for directly electrically coupling to the second flash memory card in the flash caddy.
  • 12. The system of claim 11, wherein the inter-board interconnect forms a daisy chain connection between the first flash memory card and the second flash memory card.
  • 13. The system of claim 1, wherein the master card is an active master card, wherein the active master card includes active circuitry for one or more of: processing, switching, routing, reformatting, and converting the single bus into the plurality of lanes to enable the plurality of flash memory cards to each communicate over a respective lane of the plurality of lanes.
  • 14. An apparatus comprising: a first flash memory card for storing information, wherein the first flash memory card has flash memory devices mounted thereon and includes: a first interface for electrically coupling the first flash memory card via a cable to a master card mounted in a bus slot on a motherboard so as to communicatively couple the first flash memory card to a single bus corresponding to the bus slot, and wherein the master card splits the single bus into a plurality of lanes to enable the plurality of flash memory cards to each communicate over a respective lane of the plurality of lanes; anda second interface for directly electrically coupling the first flash memory card to a second flash memory card that has flash memory devices mounted thereon, and is daisy chained to and distinct from the first flash memory card so as to indirectly communicatively couple the second flash memory card to the master card, wherein the first and second flash memory cards are two of a plurality of flash memory cards that are arranged in a stack.
  • 15. The apparatus of claim 14, wherein the master card enables a plurality of flash memory cards, at least including the first flash memory and the second flash memory card, to each communicate over the single bus.
  • 16. The apparatus of claim 14, wherein the bus slot is a PCI Express bus slot.
  • 17. The system of claim 1, wherein the plurality of flash memory cards are arranged in the stack in a disk bay, and the first and second flash memory cards are interconnected within the disk bay using one of a board-to-board interconnect and a backplane interconnect.
CLAIM OF PRIORITY AND RELATED APPLICATION DATA

The present application claims priority to U.S. provisional patent application 61/323,322, entitled “Non-volatile, solid-state storage system mounted within a processing node,” filed on Apr. 12, 2010, and is hereby incorporated by reference for all purposes as if fully set forth herein. This application is related to U.S. non-provisional patent application Ser. No. 12/983,754, entitled “Efficient Flash Memory-Based Object Store,” filed on Jan. 3, 2011, invented by John Busch et al., the entire contents of which are incorporated by reference for all purposes as if fully set forth herein. This application is related to U.S. non-provisional patent application Ser. No. 12/983,758, entitled “Flexible Way of Specifying Storage Attributes in a Flash-Memory Based Object Store,” filed on Jan. 3, 2011, invented by Darryl Ouye et al., the entire contents of which are incorporated by reference for all purposes as if fully set forth herein. This application is related to U.S. Non-provisional patent application Ser. No. 12/983,762, entitled “Minimizing Write Operations to a Flash Memory-Based Object Store,” filed on Jan. 3, 2011, invented by Darpan Dinker, the entire contents of which are incorporated by reference for all purposes as if fully set forth herein. This application is related to U.S. provisional patent application No. 61/359,237, entitled “Approaches for Replication in a Distributed Transaction System Employing Solid State Devices,” filed Jun. 28, 2010, invented by John Busch et al., the entire contents of which are incorporated by reference for all purposes as if fully set forth herein.

US Referenced Citations (212)
Number Name Date Kind
4916605 Beardsley et al. Apr 1990 A
5046002 Takashi et al. Sep 1991 A
5057996 Cutler et al. Oct 1991 A
5117350 Parrish et al. May 1992 A
5212789 Rago May 1993 A
5287496 Chen et al. Feb 1994 A
5297258 Hale et al. Mar 1994 A
5394555 Hunter et al. Feb 1995 A
5403639 Belsan et al. Apr 1995 A
5423037 Hvasshovd Jun 1995 A
5509134 Fandrich et al. Apr 1996 A
5537534 Voigt et al. Jul 1996 A
5603001 Sukegawa et al. Feb 1997 A
5611057 Pecone et al. Mar 1997 A
5613071 Rankin et al. Mar 1997 A
5680579 Young et al. Oct 1997 A
5692149 Lee Nov 1997 A
5701480 Raz Dec 1997 A
5742787 Talreja Apr 1998 A
5887138 Hagersten et al. Mar 1999 A
5897661 Baranovsky et al. Apr 1999 A
5897664 Nesheim et al. Apr 1999 A
5960436 Chang et al. Sep 1999 A
5963983 Sakakura et al. Oct 1999 A
6000006 Bruce et al. Dec 1999 A
6023745 Lu Feb 2000 A
6052815 Zook Apr 2000 A
6130759 Blair Oct 2000 A
6141692 Loewenstein et al. Oct 2000 A
6151688 Wipfel et al. Nov 2000 A
6216126 Ronstrom Apr 2001 B1
6298390 Matena et al. Oct 2001 B1
6308169 Ronstrom et al. Oct 2001 B1
6434144 Romanov Aug 2002 B1
6467060 Malakapalli et al. Oct 2002 B1
6615313 Kato et al. Sep 2003 B2
6658526 Nguyen et al. Dec 2003 B2
6704835 Garner Mar 2004 B1
6728826 Kaki et al. Apr 2004 B2
6745209 Holenstein et al. Jun 2004 B2
6804766 Noel et al. Oct 2004 B1
6874044 Chou et al. Mar 2005 B1
6938084 Gamache et al. Aug 2005 B2
6944699 Bugnion et al. Sep 2005 B1
6981070 Luk et al. Dec 2005 B1
7003586 Bailey et al. Feb 2006 B1
7010521 Hinshaw et al. Mar 2006 B2
7043621 Merchant et al. May 2006 B2
7082481 Lambrache et al. Jul 2006 B2
7162467 Eshleman et al. Jan 2007 B2
7200718 Duzett Apr 2007 B2
7203890 Normoyle Apr 2007 B1
7249280 Lamport et al. Jul 2007 B2
7251749 Fong et al. Jul 2007 B1
7269708 Ware Sep 2007 B2
7269755 Moshayedi et al. Sep 2007 B2
7272605 Hinshaw et al. Sep 2007 B1
7272654 Brendel Sep 2007 B1
7281160 Stewart Oct 2007 B2
7305386 Hinshaw et al. Dec 2007 B2
7334154 Lorch et al. Feb 2008 B2
7359927 Cardente Apr 2008 B1
7383290 Mehra et al. Jun 2008 B2
7406487 Gupta et al. Jul 2008 B1
7415488 Muth et al. Aug 2008 B1
7417992 Krishnan Aug 2008 B2
7436771 Roberts et al. Oct 2008 B2
7467265 Tawri et al. Dec 2008 B1
7529882 Wong May 2009 B2
7542968 Yokomizo et al. Jun 2009 B2
7562162 Kreiner et al. Jul 2009 B2
7584222 Georgiev Sep 2009 B1
7610445 Manus et al. Oct 2009 B1
7623494 Zhu et al. Nov 2009 B2
7627618 Honigfort Dec 2009 B2
7647449 Roy et al. Jan 2010 B1
7657710 Loewenstein Feb 2010 B2
7809691 Karmarkar et al. Oct 2010 B1
7822711 Ranade Oct 2010 B1
7885923 Tawri et al. Feb 2011 B1
7917472 Persson Mar 2011 B2
8015352 Zhang et al. Sep 2011 B2
8018729 Skinner Sep 2011 B2
8024515 Auerbach et al. Sep 2011 B2
8037349 Mandagere et al. Oct 2011 B2
8069328 Pyeon Nov 2011 B2
8099391 Monckton Jan 2012 B1
8103643 Danilov et al. Jan 2012 B2
8161248 Blumrich et al. Apr 2012 B2
8205206 Özer et al. Jun 2012 B2
8225053 McCorkendale et al. Jul 2012 B1
8239617 Linnell Aug 2012 B1
8261266 Pike et al. Sep 2012 B2
8261289 Kasravi et al. Sep 2012 B2
8321450 Thatte et al. Nov 2012 B2
8335776 Gokhale Dec 2012 B2
8356306 Herington Jan 2013 B2
8370853 Giampaolo et al. Feb 2013 B2
8401994 Hoang et al. Mar 2013 B2
8504526 Gokhale et al. Aug 2013 B2
8666939 O'Krafka et al. Mar 2014 B2
8671074 Wang et al. Mar 2014 B2
8683480 Bachar et al. Mar 2014 B2
20010032253 Duxbury Oct 2001 A1
20020089933 Giroux et al. Jul 2002 A1
20020129192 Spiegel et al. Sep 2002 A1
20020166031 Chen et al. Nov 2002 A1
20020184239 Mosher, Jr. et al. Dec 2002 A1
20030016596 Chiquoine et al. Jan 2003 A1
20030097610 Hofner May 2003 A1
20030177408 Fields et al. Sep 2003 A1
20030220985 Kawamoto et al. Nov 2003 A1
20040010502 Bomfim et al. Jan 2004 A1
20040078379 Hinshaw et al. Apr 2004 A1
20040143562 Chen et al. Jul 2004 A1
20040148283 Harris et al. Jul 2004 A1
20040172494 Pettey et al. Sep 2004 A1
20040172577 Tan et al. Sep 2004 A1
20040205151 Sprigg et al. Oct 2004 A1
20040230862 Merchant et al. Nov 2004 A1
20040267835 Zwilling et al. Dec 2004 A1
20050005074 Landin et al. Jan 2005 A1
20050021565 Kapoor et al. Jan 2005 A1
20050027701 Zane et al. Feb 2005 A1
20050028134 Zane et al. Feb 2005 A1
20050034048 Nemawarkar et al. Feb 2005 A1
20050081091 Bartfai et al. Apr 2005 A1
20050086413 Lee et al. Apr 2005 A1
20050120133 Slack-Smith Jun 2005 A1
20050131964 Saxena Jun 2005 A1
20050240635 Kapoor et al. Oct 2005 A1
20050246487 Ergan et al. Nov 2005 A1
20060059428 Humphries et al. Mar 2006 A1
20060064549 Wintergerst Mar 2006 A1
20060085594 Roberson et al. Apr 2006 A1
20060123200 Ito et al. Jun 2006 A1
20060130063 Kilian et al. Jun 2006 A1
20060161530 Biswal et al. Jul 2006 A1
20060174063 Soules et al. Aug 2006 A1
20060174069 Shaw et al. Aug 2006 A1
20060179083 Kulkarni et al. Aug 2006 A1
20060195648 Chandrasekaran et al. Aug 2006 A1
20060212795 Cottrille et al. Sep 2006 A1
20060218210 Sarma et al. Sep 2006 A1
20060242163 Miller et al. Oct 2006 A1
20060253724 Zhang Nov 2006 A1
20070038794 Purcell et al. Feb 2007 A1
20070043790 Kryger Feb 2007 A1
20070043860 Pabari Feb 2007 A1
20070073896 Rothman et al. Mar 2007 A1
20070143368 Lundsgaard et al. Jun 2007 A1
20070156842 Vermeulen et al. Jul 2007 A1
20070174541 Chandrasekaran et al. Jul 2007 A1
20070234182 Wickeraad et al. Oct 2007 A1
20070276784 Piedmonte Nov 2007 A1
20070283079 Iwamura et al. Dec 2007 A1
20070288692 Bruce et al. Dec 2007 A1
20070288792 Thorpe et al. Dec 2007 A1
20070294564 Reddin et al. Dec 2007 A1
20070299816 Arora et al. Dec 2007 A1
20080016300 Yim et al. Jan 2008 A1
20080034076 Ishikawa et al. Feb 2008 A1
20080034174 Traister et al. Feb 2008 A1
20080034249 Husain et al. Feb 2008 A1
20080046538 Susarla et al. Feb 2008 A1
20080046638 Maheshwari et al. Feb 2008 A1
20080104141 McMahon May 2008 A1
20080126706 Newport et al. May 2008 A1
20080172402 Birdwell et al. Jul 2008 A1
20080256103 Fachan et al. Oct 2008 A1
20080288713 Lee et al. Nov 2008 A1
20080288819 Heller, Jr. Nov 2008 A1
20080295105 Özer et al. Nov 2008 A1
20080301256 McWilliams Dec 2008 A1
20090006500 Shiozawa et al. Jan 2009 A1
20090006681 Hubert et al. Jan 2009 A1
20090006888 Bernhard et al. Jan 2009 A1
20090019456 Saxena et al. Jan 2009 A1
20090024871 Emaru et al. Jan 2009 A1
20090030943 Kall Jan 2009 A1
20090059539 Ryu et al. Mar 2009 A1
20090070530 Satoyama et al. Mar 2009 A1
20090150599 Bennett Jun 2009 A1
20090177666 Kaneda Jul 2009 A1
20090198791 Menghnani Aug 2009 A1
20090240664 Dinker et al. Sep 2009 A1
20090240869 O'Krafka et al. Sep 2009 A1
20090327751 Koifman et al. Dec 2009 A1
20100058021 Kawamura Mar 2010 A1
20100080057 Reuter et al. Apr 2010 A1
20100107017 Munjal et al. Apr 2010 A1
20100125695 Wu et al. May 2010 A1
20100241895 Li et al. Sep 2010 A1
20100262762 Borchers et al. Oct 2010 A1
20100299490 Attarde et al. Nov 2010 A1
20100306448 Chen et al. Dec 2010 A1
20100318821 Kwan et al. Dec 2010 A1
20100325498 Nagadomi Dec 2010 A1
20110022566 Beaverson et al. Jan 2011 A1
20110072206 Ross et al. Mar 2011 A1
20110082965 Koka et al. Apr 2011 A1
20110082985 Haines et al. Apr 2011 A1
20110099420 MacDonald McAlister et al. Apr 2011 A1
20110167038 Wang et al. Jul 2011 A1
20110179279 Greevenbosch et al. Jul 2011 A1
20110185147 Hatfield et al. Jul 2011 A1
20110191299 Huynh Huu et al. Aug 2011 A1
20110225214 Guo Sep 2011 A1
20120005154 George et al. Jan 2012 A1
20120072449 Patch et al. Mar 2012 A1
20130066948 Colrain et al. Mar 2013 A1
20130198478 Bitner Aug 2013 A1
Foreign Referenced Citations (2)
Number Date Country
1548600 Jan 2007 EP
1746510 Jan 2007 EP
Non-Patent Literature Citations (45)
Entry
Ajmani, Automatic Software Upgrades for Distributed Systems, MIT, Sep. 2004, 164 pgs.
Amza, Data Replication Strategies for Fault Tolerance and Availability on Commodity Clusters, 2000, 9 pgs.
Rice, Extension Versioning, Update and Compatibility, Aug. 9, 2011, 11 pgs.
Chockler, Active Disk Paxos with infinitely many processes, Springer-Verlag, Apr. 2005, 12 pgs.
Dwork, Concensus in the presence of partial synchrony, MIT, 1988, 6 pgs.
Guerraoui, A Leader Election Protocol for Eventually Synchronous Shared Memory Systems, IEEE, 2006, 6 pgs.
Lamport, Cheap Paxos, Microsoft, 2004, 9 pgs.
Lamport, Fast Paxos, Microsoft, Jul. 2005, 43 pgs.
Lamport, Generalized Consensus and Paxos, Microsoft, Mar. 2004, 25 pgs.
Lamport, Paxos Made Simple, Nov. 2001, 14 pgs.
Malkhi, Lecture notes in computer science [Section: Omega Meets Paxos, Leader election and stability without eventual timely links], 2005, pp. 199-213.
Pease, Reaching Agreement in the Presence of Faults, ACM, 1980, pp. 228-234.
Schneider, Implementing fault tolerant:services using the state machine, Cornell Univ., 1990, 21 pgs.
Mukherjee et al., “Verification of an Industrial CC-NUMA Server,” Proceeding of the 15th International Conference on VLSI Design, 2002, 6 pages.
Shacham et al., “Verificaiton of Chip Multiprocessor Memory Systems Using a Relaxed Scoreboard,” Microarchitecture, 2008, MICRO-41, 2008, 41st IEEE/ACM International Symposium, Nov. 8-12, 2008, 12 pages.
Unknown Author, Supermicro, “Intel Itanium Processor 9300 Series Based Server Systems,” Jul. 8, 2010, http://www.supermicro.com/products/nfo/itanium.cfm, 3 pages.
Walker, Hash Table Tutorial, Oct. 13, 2007, http://www.eternallyconfuzzled.com/tuts/datastructures/jsw—tut—hashtable.aspx, 14 pgs.
bsn-modulestore, Versioning Concept, Oct. 13, 2010, 2 pgs.
Btrfs, http://en.wikipedia.org, Oct. 3, 2011, 9 pgs.
Buchholz, The Structure of the Reiser File System, Jan. 26, 2006, 21 pgs.
Chacon, Git, The Fast Version Control System, Oct. 3, 2011, 3 pgs.
Email Communication from James Bodwin to Christopher Brokaw re prior art, Sep. 13, 2011, 4 pgs.
Git (Software), http://en.wikipedia.org, Oct. 3, 2011, 10 pgs.
Hitz, File System Design for an NFS File Server Appliance, Jan. 19, 1994, 23 pgs.
McDonald, Architectural Semantics for Practical Transactional Memory, Jun. 2006, 12 pgs.
McGonigle, A Short History of btrfs, Aug. 14, 2009, 11 pgs.
Mellor, ZFS—the future of file systems? Aug. 14, 2006, 5 pgs.
Mercurial, http://en.wikipedia.org, Oct. 2, 2011, 6 pages.
Module: Mongoid: Versioning, http://rdoc.info, Documentation by Yard 0.7.2, 6 pages Oct. 3, 2011.
Noach, Database Schema under Version Control, code.openarck.org, Apr. 22, 2010, 6 pages.
Reiser FS, http://enwikipedia.org, Sep. 17, 2011, 5 pgs.
Rice, Toolkit Version Format, Aug. 19, 2011, 4 pgs.
Russell, Track and Record Database Schema Versions, Jun. 28, 2005, 8 pgs.
Schooner Information Technology, IPAF, PCT/US2008/065167, Oct. 23, 2008, 7 pgs.
Schooner Information Technology, ISR/WO, PCT/US2008/065167, Jan 28, 2009, 16 pgs.
SQL Server Database Schema Versioning and Update, Dec. 2, 2009, 2 pgs.
Sufficiently Advanced Bug, File Versioning, Caching and Hashing, Oct. 3, 2011, 3 pgs.
The Z File System (ZFS), FreeBSD Handbook, Oct. 3, 2011, 8 pgs (Author not provided).
Tux3 Linux Filesystem Project, 2008, 1 pg.
Tux3 Versioning Filesystem, Jul. 2008, 67 pgs.
Tux3, http://en.wikipedia.org, Jun. 2, 2010, 3 pgs.
Vijaykumar, Speculative Versioning Cache, Dec. 1, 2001, 13 pgs.
WAFL—Write Anywhere File Layout, 1999, 1 pg.
Write Anywhere File Layout, Sep. 9, 2011, 2 pgs.
ZFS, http://en.wikipedia.org Sep. 30, 2011, 18 pgs.
Related Publications (1)
Number Date Country
20120011302 A1 Jan 2012 US
Provisional Applications (1)
Number Date Country
61323322 Apr 2010 US