# Patent

## Title
Method and system and apparatus for use in data storage

## Abstract

Systems, devices and methods for interfacing a single bus with multiple buses invisibly to devices using the single bus are presented. More specifically, in one embodiment an I/O bus may be interfaced with multiple other I/O buses of the same or different formats. Commands may be received on the first I/O bus and invisibly to a computing device or processor which issues the commands, translated into a set of commands configured to effectuate a received command in conjunction with storage media coupled to the other I/O buses. This set of commands may also be configured to implement additional functionality in conjunction with the storage media such as RAID or data encryption.

## Background
RELATED APPLICATIONS
This application claims a benefit of priority to the filing date of U.S. Provisional Patent Application Ser. No. 60/961,605 by Brian Bruce and Ahmad Chamseddine, entitled “Method and System for RAID Implementation” filed on Jul. 23, 2007, the entire contents of which are hereby expressly incorporated by reference for all purposes.


TECHNICAL FIELD
Embodiments of the invention relate generally to the use of storage devices. More particularly, embodiments of the invention relate to implementing the use of multiple storage devices in conjunction with one another to achieve one or more desired objectives in a particular context. In certain embodiments, these objectives may include increased capacity, increased speed, security or another objective altogether.
BACKGROUND
Data represents a significant asset for many entities. Consequently, data loss, whether accidental or caused by malicious activity, can be costly in terms of wasted manpower, loss of goodwill from customers, loss of time and potential legal liability. To ensure proper protection of data for business, legal or other purposes, many entities may desire to protect their data using a variety of techniques, including data storage, redundancy, security, etc. These techniques may, however, conflict with other competing constraints or demands imposed by the state or configuration of computing devices used to process or store this data.
These types of constraints may center around processing constraints particular to an environment or context in which data is being processed or utilized, space constraints within such an environment, cost constraints placed on the hardware or software used to process, manage or otherwise store data, or other constraints altogether may impede the ability to achieve desirable levels of protection with respect to important data. It would be desirable therefore, to be able to achieve a desired level of data protection utilizing solutions which may account for, or be less affected by, certain of these constraints.
SUMMARY
Systems, devices and methods for interfacing a single bus with multiple buses invisibly to devices using the single bus are presented. More specifically, in one embodiment an I/O bus may be interfaced with multiple other I/O buses of the same or different formats. Commands may be received on the first I/O bus and invisibly to a computing device or processor which issues the command, translated into a set of commands configured to effectuate the received command in conjunction with storage media coupled to the other I/O buses. This set of commands may also be configured to implement additional functionality in conjunction with the storage media such as RAID or data encryption.
Embodiments of the invention disclosed herein can be implemented all or in part by logic, including hardware or by programming one or more computer systems or devices with computer-executable instructions embodied in a computer-readable medium. When executed by a processor, these instructions operate to cause these computer systems and devices to perform one or more functions particular to embodiments of the invention disclosed herein. Programming techniques, computer languages, devices, and computer-readable media necessary to accomplish this are known in the art and thus will not be further described herein.
Certain technical advantages may be obtained through the use of embodiments of the present invention. More specifically, embodiments of the present invention may be operating system and bus agnostic, any bus can be utilized and RAID, security, extra capacity, etc. can be implemented or obtained regardless of a native bus format. Thus, this functionality provided by embodiments of the present invention may be obtained without modification to drivers or other software on native systems and without the addition of a separate RAID controller.
Furthermore, embodiments of the present invention may allow increased throughput by allowing multiple storage media to be utilized in conjunction with certain buses (where only one drive may have been utilized previously) to minimize latency on the bus and maximize throughput.
These, and other, aspects of the invention will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. The following description, while indicating various embodiments of the invention and numerous specific details thereof, is given by way of illustration and not of limitation. Many substitutions, modifications, additions or rearrangements may be made within the scope of the invention, and the invention includes all such substitutions, modifications, additions or rearrangements.



BRIEF DESCRIPTION OF THE DRAWINGS
The drawings accompanying and forming part of this specification are included to depict certain aspects of the invention. A clearer impression of the invention, and of the components and operation of systems provided with the invention, will become more readily apparent by referring to the exemplary, and therefore nonlimiting, embodiments illustrated in the drawings, wherein identical reference numerals designate the same components. Note that the features illustrated in the drawings are not necessarily drawn to scale.
FIG. 1 is a block diagram of one embodiment of a mobile computer.
FIG. 2 is a block diagram of one embodiment of a storage server.
FIG. 3 is a block diagram of one embodiment of a virtual translator storage device.
FIG. 4 is a block diagram of one embodiment of the use of a virtual translator storage device.
FIG. 5 is a block diagram of one embodiment of the use of a virtual translator storage device.
FIG. 6A is a block diagram of one embodiment of a virtual translator storage device.
FIG. 6B is a block diagram of one embodiment of a virtual translator storage device and its appearance to a user of a bus.
FIG. 7 is a block diagram of one embodiment of the use of a virtual translator storage device.
FIGS. 8A and 8B are block diagram of embodiments of the use of a virtual translator storage device.
FIG. 9 is a block diagram of one embodiment of a virtual translator storage device.
FIG. 10 is a block diagram of one embodiment of the use of a virtual translator storage device.
FIGS. 11A and 11B are block diagrams of the footprint of one embodiment of using a virtual translator storage device in conjunction with two storage devices.



DETAILED DESCRIPTION
The invention and the various features and advantageous details thereof are explained more fully with reference to the nonlimiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well known starting materials, processing techniques, components and equipment are omitted so as not to unnecessarily obscure the invention in detail. It should be understood, however, that the detailed description and the specific examples, while indicating preferred embodiments of the invention, are given by way of illustration only and not by way of limitation. Various substitutions, modifications, additions and/or rearrangements within the spirit and/or scope of the underlying inventive concept will become apparent to those skilled in the art from this disclosure. Embodiments discussed herein can be implemented at least in part using suitable computer-executable instructions that may reside on a computer readable medium (e.g., a HD), hardware circuitry or the like, or any combination. Before proceeding with the remainder of the disclosure it may be helpful to review U.S. application Ser. No. 12/048,271, entitled “Method and System for A Storage Device”, Brian Bruce and Ahmad Chamseddine, filed Mar. 14, 2008, the entire contents of which are incorporated fully herein by reference.
As discussed above, data represents a significant asset for many entities. Consequently, data loss, whether accidental or caused by malicious activity, can be costly in terms of wasted manpower, loss of goodwill from customers, loss of time and potential legal liability. To ensure proper protection of data for business, legal or other purposes, many entities may desire to protect their data using a variety of techniques, including data storage, redundancy, security, etc. These techniques may, however, conflict with other competing constraints or demands imposed by the state or configuration of computing devices used to process or store this data.
This tension may be better understood with reference to FIG. 1 which depicts a high level overview of one embodiment of an architecture for a mobile computer (e.g. also sometimes referred to as a notebook or laptop computer). A mobile computer 100 comprises a mother board 110 with a Central Processing Unit (CPU) 120 where the mother board is coupled to a storage device 140 (e.g. a hard disk drive, solid state storage such as flash memory or the like, media library of tape drives, other type of storage media such as disk platters, etc., the terms storage device and storage media will be used interchangeably throughout) through an I/O bus 130 (e.g. an ATA bus, such as a SATA or PATA bus, a PCI bus, a SCSI bus or any other type of bus). Thus, data processed by, or otherwise utilized in conjunction with, mobile computer 100 may be stored in storage device 140.
However, storage device 140 may only be of a certain capacity. In other words current technical limitations of the storage device may only allow a particular type of storage device 140 to store a certain amount of data (referred to as the capacity of the storage device). For example, the largest capacity hard disk drive may be around 750 gigabytes. Part and parcel with this limitation, the capacity of storage device 140 may further be limited by the physical constraints imposed by the packaging of mobile computer 100. There may only be a limited amount of space in which to place storage device 140. In many cases, this additional limitation further constrains the capacity of storage device 140 which may be utilized in this physical package (as the physical size of a storage device may be related to its capacity). For example, the largest disk drive that is currently in use in mobile computers is around 160 gigabytes.
Consequently, the amount of data which may be stored in conjunction with mobile computer 100 is limited by the capacity of storage device 140. This limitation exists, in part, because in most cases I/O bus 130 may only allow (e.g. is configured or designed to operate with) one storage device to be coupled to the I/O bus 130. Thus, the capacity of storage device 140 (which itself may be constrained by technological limitations or the physical limitations imposed by the packaging of mobile computer 100) may be the biggest gating factor in the amount of data which may be stored by mobile computer 100.
Mobile computer 100 may, however, also comprise a second I/O Bus 150 coupled to mother board 110, where the second I/O Bus 150 interfaces with a modular bay 160. A variety of devices may be inserted into (e.g. interfaced with), or used in conjunction with, modular bay 160. For example, a CD or DVD drive may be utilized in conjunction with modular bay 160, a floppy disk drive or another type of storage device such as a hard disk or the like may also be utilized in conjunction with modular bay 160. Consequently, in order to expand the amount of data which may be stored in conjunction with mobile computer 100, in many cases modular bay 160 may be utilized in conjunction with a second storage device in addition to storage device 140. Utilizing the modular bay 160 of mobile computer 100 may, however, preclude the use of modular bay 160 for interfacing with another desired device (e.g. DVD or CD drive), may entail constant swapping between the second storage device and another desired device and may require a user to carry multiple additional devices.
Similar types of problems may present themselves in other computing devices or systems which utilize storage devices, such as enterprise servers, storage servers, storage area networks (SANs), network attached storage (NAS) systems, or the like. These types of problems may be better illustrated with reference to FIG. 2 which depicts a block diagram of one embodiment of a computer storage system. Storage system 200 comprises a storage server 230 which receives commands or instructions over I/O bus 210, which may be a type of serial bus such as fiber channel, SCSI or the like, but may also be any type of I/O bus known in the art. Based on the commands or instructions received over I/O bus 210, storage server 230 may communicate with one or more of storage devices 240 (e.g. hard disk drives, tape drives, optical drives, solid state storage devices, etc.) to write, read or otherwise operate on, data associated with those storage devices 240. These communications may take over an I/O bus 220 corresponding to the storage device 240, where each of these I/O buses 220, may in turn, be different, for example I/O bus 220a may be a SCSI bus, I/O Bus 220b may be a serial ATA bus, etc.
In most cases, however, no matter the type of I/O bus utilized, the I/O bus 220 may limited to being coupled only to one storage device 240 or type of storage device 230 (e.g. a storage device may comprise multiple physical tape drives or other storage mediums). As can be seen, this limitation may constrain the storage associated with storage server 230 to the number of I/O buses 220 associated with storage router 230 and the type and size of storage devices 240 associated with each of I/O buses 220.
To remedy the aforementioned deficiencies, problems and limitations, among others, attention is now directed to systems, methods and devices for interfacing a single bus with multiple buses invisibly to devices using the single bus. By allowing multiple buses to be interfaced to the single bus, a number of storage devices may be coupled to each of the buses, greatly increasing the maximum storage capacity, speed, etc. relative to the coupling of only a single storage device to single bus, without using any additional buses or slots. Advantageously, in one embodiment, this increased capacity or other capabilities may be obtained without alterations to any of the other hardware or software of systems with which it utilized, and to that hardware or software the multiple buses (and multiple attached storage devices) may appear as a single bus and a single storage device. For example, using an embodiment of the systems, methods and devices presented herein, multiple storage devices such as hard disk drives or the like may be utilized in a mobile computer without changing the BIOS of the mobile computer where the multiple disk drives appear as a single volume to the operating system of the mobile computer.
Moving now to FIG. 3, a block diagram for one embodiment of a system for interfacing multiple buses with a single bus is depicted. More specifically, virtual storage translator device 310 may allow a primary I/O bus 320 to be interfaced with multiple secondary I/O buses 330. I/O bus 320 may be almost any type of bus known in the art, such a SATA or PATA bus. Virtual storage translator device 310, may be a standalone ASIC, a field programmable gate array (FPGA), a circuit board comprising one or more ASICs operable to execute computer readable instructions, a set of computer readable instructions, some combination of hardware and software, etc. In one embodiment, virtual storage translator device 310 may use one or more ASICs such as the Silicon Image Si5723 Storage Processor.
This virtual storage translator device 310 is operable to receive commands or instructions (used interchangeably herein) on primary I/O bus 320 and translate or map these commands or instructions such that they are effectuated with respect to storage devices 340 on secondary I/O buses 330, where secondary I/O buses 350 may each be a different type of I/O bus (e.g. SATA, PATA, SCSI, FC, etc.) and secondary I/O buses 330 may be the same or different from primary I/O bus 320. This translator or mapping may for example, entail tracking where various files are stored or translating commands or instructions in one protocol to equivalent commands or instructions in another protocol.
Furthermore, this translator or mapping process may be accomplished seamlessly or invisibly with respect to a computing device or processor which issues the commands or instruction over I/O bus 320. In other words, in some embodiments, to a computing device interfacing with I/O bus 320 it appears as if a single storage device is present on I/O bus 320 where this single storage device may have the capacity of the combined capacity of the storage devices 340 coupled to each of I/O buses 330.
The functionality of an embodiment of a virtual storage translator device may be better depicted with reference to FIG. 4 which depicts a block diagram of the use of an embodiment of a virtual storage translator device in a mobile computing environment. Mobile computer 400 comprises a mother board 410 with a Central Processing Unit (CPU) 420 where the mother board is coupled to virtual storage translator device 470 through an primary I/O bus 430, such as a SATA, PATA or other type of bus. Virtual translator storage device 470 is, in turn, coupled to each of storage devices 460 using a corresponding secondary I/O bus 440, which may also be SATA or other type of bus.
Virtual translator storage device 470 may simulate a single drive which is the combined size of storage device 430 by performing or executing the commands received on primary I/O bus 420 utilizing storage device 430. In other words, in this embodiment, two storage device 430 may be utilized in conjunction with a I/O bus 420 designed to interface with only a single storage device without altering the BIOS or other software executing in conjunction with the mobile computer 400. In fact, to an operating system 400 executing on mobile computer (e.g. executing on CPU of mother board 410) it appears as if a single storage device (e.g. hard disk drive, etc.) is present on I/O bus 410. As can be seen then, storage capacity corresponding to I/O bus 410 may effectively be doubled without any alteration to the hardware or software of mobile computer 410 relative to coupling only a single storage device to I/O bus 410. In other words, no matter the size of a single storage device which can be coupled to I/O bus, this size can be effectively doubled (or tripled, quadrupled, etc.) by attaching multiple devices of this same capacity to virtual translator storage device 420.
In certain embodiments, in fact, the use of two drives may occupy the same, or close to the same, footprint as the use of a single storage device. This can be seen with brief reference to FIGS. 11A and 11B which depict two views of the use of two storage devices in a mobile environment. As can be seen with reference to these FIGURES, in one embodiment, the two storage devices are configured to fit within the physical parameters of a mobile computer which may have been designed to be utilized with a single storage media.
Returning now to FIG. 4, as discussed above, storage devices used with embodiments of a virtual translator storage device may be any type of storage devices known in the art, such as spinning media or disk drives, solid state hard drives, optical drives, etc. As may be realized each of these various types of storage devices may have different strengths or weaknesses. For example, spinning media drives may have a higher capacity than solid state hard drives while being susceptible to failure when subject to excessive shock or vibration while conversely solid state media drives may be of comparatively lesser capacity while being more resistant to shock or vibration.
When only a single storage device is utilized in a mobile environment the advantages and disadvantages of the particular type of storage device utilized must be dealt with: if a solid state drive is chosen more resistance to shock and vibration is achieved at the expense of capacity, while if a spinning media drive is chosen capacity is gained by sacrificing durability. Using virtual translator storage device 470, however, multiple storage devices may be utilized in conjunction with I/O bus 430 and by utilizing various or different types of storage devices a variety of objectives may be achieved. For example, if storage device 460a is a solid state storage device and storage device 460b is a spinning disk drive the benefits of a solid state drive (e.g. durability, shock resistance, etc.) may be obtained while simultaneously realizing the benefits of a spinning disk drive (e.g. capacity).
To accentuate the advantages of utilizing different types of storage device in conjunction with virtual translator storage device 470 it may be desired to designate where (e.g. on which storage device 460) certain data is stored. For example, it may be useful to store critical or important data on a solid state storage device to protect against loss of this data as these devices are more resistant to shock and vibration. By the same token it may be useful to store non-critical or less important data on a spinning media drive such that the relatively more limited capacity of a solid state storage device is not utilized to store such non-critical data. Thus, in one embodiment a utility or application may be provided in conjunction with mobile computer 400 (e.g. which may execute on, or utilized with other software such as an operating system or the like on, mobile computer 400) which allow data (e.g. files, directories, etc.) to be designated as critical (or non-critical). Based on a designation associated with data virtual storage translator device 470 may store the data on an appropriate storage device 460. For example, if a file is designated as critical it may be stored on solid state storage device while if the file is designated as non-critical (or is not designated as critical) the file may be stored on a spinning storage device. Again, the storage of data to an appropriate or designated storage device may be accomplished by virtual storage translator device 470 invisible to a user or the hardware or software of mobile computer 400.
Similar efficacy and advantages may be achieved by embodiments of a virtual translator storage device in other settings, including those which are not mobile in nature, such as other types of personal or other computing devices. To explain more clearly attention is now directed to FIG. 5 which depicts a block diagram of the use of an embodiment of a virtual storage translator device in a storage server setting. Storage system 500 comprises a storage server 530 (e.g. an enterprise server, a storage server, an NFS server, a storage router in a SAN or NAS, etc.) which receives commands or instructions from one or more hosts (not shown) over I/O bus 510, which may be a serial or other type of bus. Storage server 530 may, in turn, interface with one or more I/O buses 580 each operable to interface with a storage device. Each of these I/O buses 540 is coupled to an embodiment of a virtual translator storage device 570. Virtual translator storage device 570 is coupled to a set of corresponding storage devices 590 using a set of corresponding I/O bus 580 (e.g. each storage device 590 corresponding to a virtual translator storage device 570 is coupled to that virtual translator storage device 570 through a corresponding I/O bus 580).
Each of virtual translator storage devices 570 simulates a single storage device which is the combined size of storage devices 590 corresponding to that virtual translator storage device 570 by performing or executing the commands received on corresponding I/O bus 540 utilizing storage devices 590 (as discussed above). In other words, in this embodiment, multiple storage devices 590 may be utilized in conjunction with I/O buses 540 designed to interface with only a single storage device without altering the software or hardware executing in conjunction with storage server 530. In fact, to the hardware or software of storage sever 530 it appears as if a single storage device (e.g. hard disk drive, etc.) is present on each of I/O buses 540.
As can be seen then, storage capacity corresponding to I/O bus 540 may effectively be doubled without any alteration to the hardware or software of storage server 530 relative to coupling only a single storage device to each of I/O buses 540. Specifically, no matter the capacity of a single storage device which can be coupled to I/O bus 540, this capacity can be effectively doubled (or tripled, quadrupled, etc.) by attaching multiple storage devices of this same capacity to a virtual translator storage device 570 on a single I/O bus 540.
In addition to providing the advantages detailed above, such as increased capacity, speed, form factor etc. embodiments of the virtual translator storage device may provide additional functionality. Specifically, in one embodiment, a virtual translator storage device may provide one or more Redundant Array of Independent Drives (RAID) implementations. While a virtual translator storage device may be utilized to implement RAID in a variety of settings, a RAID implementation may be particularly useful in a mobile computing environment as previously it was only possible to implement software RAID on mobile computers, which imposed a significant impact on both the performance and reliability of the mobile computers on which it was implemented.
By utilizing a RAID controller in conjunction with an embodiment of a virtual translator storage device RAID functionality may be implemented invisibly with respect to the system with which it is utilized. In other words, other hardware or software (such as the BIOS or operating system) of the system on which RAID is implemented need not be altered to implement this RAID functionality.
Moving now to FIG. 6A, a block diagram for one embodiment of a system for interfacing multiple buses with a single bus is depicted, where RAID may be implemented with respect to storage devices on these multiple buses. More specifically, virtual storage translator device 610 may allow a primary I/O bus 620 to be interfaced with multiple secondary I/O buses 630. I/O bus 620 may be almost any type of bus known in the art, such a serial, SATA or PATA bus. Virtual storage translator device 610, includes RAID controller 660 which may be hardware (e.g. on an ASIC), a portion of the hardware or ASIC comprising virtual storage translator device 610, computer readable instructions on a computer readable media, or some combination. RAID controller 660 may be operable to implement one or more RAID levels (e.g. RAID levels 0, 1, 3, 4, 5, 6 or any nested RAID levels, etc.), multi-RAID modes (e.g. implementations which create virtual volumes and balance the benefits of capacity and protection) cascaded storage devices and the like. In other words, in one embodiment, RAID controller 660 handles the management of the storage devices coupled to secondary I/O buses 630, performing any parity calculations required by an implemented level RAID level or executing other processing utilized for the RAID implementation.
This management may, in one embodiment, include maintaining one or more first in first out (FIFO) queues 666 for buffering or holding received commands until they are processed and map 662 which is a map between the addressing utilizing in conjunction with commands issued over I/O bus 620 and the storage of data with respect to storage media 640. For example, if RAID controller is implementing RAID 0 with respect to storage media 640, all of storage media 640 may appear as one contiguous set of addresses to users of I/O bus 620 and thus commands over I/O bus 620 may attempt to store or otherwise access data according to these contiguous addresses. To implement RAID 0, however, this data may be stored in storage media according to a different addressing scheme or at different locations than those referred to by command received over I/O bus 620. Thus, map 662 may correlate or otherwise associate addresses or locations of the type or format received over I/O bus 620 with addresses or locations in one or more of storage media 640.
Thus, virtual storage translator device 610 may be operable to receive commands or instructions on primary I/O bus 620 and translate these commands or instructions such that they are effectuated with respect to storage device 640 on secondary I/O buses 630 or to receive responses or data on a secondary I/O bus 630 and translate the response or data such that it can be communicated to a recipient (e.g. issuer of a command) on primary I/O bus 620, where secondary I/O buses 630 may each be a different type of I/O bus (e.g. SATA, PATA, SCSI, FC, etc.) and secondary I/O buses 630 may be the same or different from primary I/O bus 620. The translation of these commands or responses from the protocol in which they are received on a bus (e.g. primary I/O bus 620 or a secondary I/O bus 630) to a suitable protocol may be accomplished by using native bus interfaces 670 (e.g. an interface corresponding to primary I/O bus 620 or one or more of secondary I/O buses 630) and protocol translator 664.
Additionally, virtual storage translator device 610 is operable to implement a RAID scheme with respect to these commands or instructions and the data stored on storage devices coupled to secondary I/O buses 630. Both this translator process and the implementation of a RAID scheme may be accomplished seamlessly or invisibly with respect to a computing device or processor which issues the commands or instruction over I/O bus 620. In other words, in some embodiments, to a computing device interfacing with I/O bus 620 it appears as if a single storage device or media is present on I/O bus 620 irrespective of the implementation of the RAID scheme implemented. Portions of the functionality utilized to implement RAID functionality, including RAID controller 660, map 662, FIFO queues 666, protocol translator 664 or native bus interfaces 670 may utilize a set of computer readable instructions of one or more ASICs such as the Silicon Image Si5723 Storage Processor.
From the above description, it will be noted that different RAID schemes may be implemented by RAID controller 660 to achieve different objectives. For example, RAID level 0 may be implemented to improve performance or improve storage capacity, RAID levels 1, 3, 4 5, or 6 may be implemented to provide some measure of fault tolerance or recovery (of course it will also be noted that the level of RAID implemented may depend at least partially on the number of secondary I/O buses 630 or storage devices 640 coupled to these Secondary I/O buses 630 are implemented with respect to the embodiment of the virtual translator storage device 610).
Advantageously, in one embodiment, to a device utilizing I/O bus 620, it appears that a single storage device is present on I/O bus 620. FIG. 6B is a block diagram of one embodiment of a virtual translator storage device and its appearance to a device coupled to a bus. Specifically, in one embodiment, it may appear to any device coupled to I/O bus 620 which may issue commands, receive responses or otherwise communicate over I/O bus 620 that a hard disk drive 685 is present on I/O bus 620. In other words, in one embodiment, virtual storage translator 610 and associated storage media 640 may function unbeknownst to, or without affecting, other devices coupled to or using I/O bus 620. Thus, the increased capacity or other capabilities offered by virtual storage translator device 610 may be obtained without alterations to any of the other hardware or software of systems with which it utilized, and to that hardware or software it appears only that a single hard disk drive 685 is present on the I/O bus 620.
The functionality of an embodiment of a virtual storage translator device may be better depicted with reference to FIG. 7 which depicts a block diagram of the use of an embodiment of a virtual storage translator device having a RAID controller in a mobile computing environment. Mobile computer 700 comprises a mother board 710 with a Central Processing Unit (CPU) 720 where the mother board is coupled to virtual storage translator device 770 through an I/O bus 730, such as a SATA or other type of bus. Virtual translator storage device 770 is, in turn, coupled to each of storage devices 760 using a corresponding I/O bus 740, which may also be SATA or other type of bus. Virtual translator storage device 770 comprises RAID controller 762 such that RAID may be implemented with respect to commands received on primary I/O bus 730 utilizing storage devices 760. In other words, in this embodiment, RAID may be implemented by RAID controller 762 with respect to two storage devices 760 in conjunction with an I/O bus 730 designed to interface with only a single storage device without altering the BIOS or other software executing in conjunction with the mobile computer 700. In fact, to an operating system or other software executing on mobile computer 700 (e.g. executing on CPU of mother board 710) it may appear as if a single storage device (e.g. hard disk drive, etc.) is present on I/O bus 730. As can be seen then, hardware RAID may be implemented to accomplish various objectives (increase speed or performance, redundancy, fault tolerance, etc.) without any alteration to the hardware or software of mobile computer 700 (e.g. alteration to the BIOS, operating system, drivers, etc.).
Though no alteration to the BIOS, operating system, or other software executing in conjunction with mobile computer 700 is necessary to implement RAID utilizing virtual storage translator device 770, it may however, be helpful in one embodiment to provide a utility to manage or control the implementation of RAID by virtual storage translator device 770. Consequently, in one embodiment just such a utility is provided on mobile computing device 700. More specifically, an application operable to communicate with virtual storage translator device 770 and view both storage devices 760, their configuration, the implementation (e.g. level) of RAID implemented etc. where the application allows configuration of these drives, the RAID configuration or level implemented in conjunction with storage devices 760, which of the storage device 760 are utilized, etc. may be included on mobile computer 700.
RAID may also be usefully implemented by embodiments of a virtual translator storage device in a variety of other settings in which embodiments of a virtual translator storage device may be utilized. To illustrate, FIG. 8A depicts a block diagram of the use of an embodiment of a virtual storage translator device comprising a RAID controller in a storage server setting. Storage system 800 comprises a storage server 830 which receives commands or instructions from one or more hosts (not shown) over I/O Bus 810, which may be a serial or other type of bus. Storage server 830 may, in turn, interface with one or I/O buses 840 each operable to interface with a storage device. Each of these I/O buses 840 is coupled to an embodiment of a virtual translator storage device 870 where the virtual translator storage device 870 comprises a RAID controller 860. Each of virtual translator storage devices 870 is coupled to a set of corresponding storage devices 890 using a set of corresponding I/O buses 880. Each of virtual translator storage devices 870 may or may not implement RAID in conjunction with its corresponding storage devices invisibly to storage server 830. In other words, to the software and hardware of storage sever it appears as if a single storage device (e.g. hard disk drive, etc.) is present on each of I/O buses 840 and no alteration to the hardware of storage server is necessary to accomplish the implementation of RAID.
It should be noted that a wide variety of objectives may be accomplished through the use of embodiments of virtual translator storage devices 870 in conjunction with a storage server 830 (e.g. increased speed, performance, redundancy, etc.) and that many permutations of various RAID implementations may be possible. For example, no RAID may be implemented with respect to virtual translator storage device 870a, RAID level 0 may be implemented with respect to another virtual translator storage device (not shown), RAID level 1 may be implemented with respect to virtual translator storage device 870n, etc.
Additionally, forms of “distributed RAID” (e.g. where RAID functionality may be implemented at multiple locations where the RAID functionality at each location may vary) may be implemented in embodiments where a storage server itself has RAID capability. For example, suppose storage server 830 is implementing RAID level 0, while each of virtual translator storage devices 870 is implementing RAID level 1. In this case, invisibly to storage server 830 (e.g. to hardware and software of storage server 830 it appears as if one storage devices is present on each of I/O buses 840) the speed benefits of a RAID level 0 implementation may be gleaned from storage server 830 while the fault tolerance and redundancy of RAID level 1 may also be obtained through the implementation of RAID level 1 at each of virtual translator storage devices 870 while simultaneously increasing the capacity which may be utilized by storage server 830 (relative to a RAID level 1 implementation by storage server 830 with a single storage device on each I/O bus 840). Moreover, as the processing associated with the RAID level 1 implementation is distributed amongst each of virtual translator storage devices 870 the implementation of RAID 1 may be significantly faster than a comparable centralized implementation (e.g. on a storage serve alone) of an equivalent RAID level.
It may be useful here to illustrate one example of a type of distributed RAID. FIG. 8B depicts a block diagram of the use of an embodiment of a virtual storage translator device comprising a RAID controller in a storage server setting. Storage system 802 comprises a storage server 832 which receives commands or instructions from one or more hosts (not shown) over I/O Bus 812, which may be a serial or other type of bus. Storage server 832 comprises RAID controller 822, which may be a hardware RAID controller of the type known in the art (such as a bus based controller card RAID controller or an external RAID controller like those made by Promise Technologies, Intel, Adaptec, etc.), a software RAID controller, or some combination of the two such that one or more levels of RAID can be implemented with respect to storage devices on one or more of I/O buses 842.
Thus, the RAID controller 822 may, in turn, interface with one or I/O buses 842 each operable to interface with a storage device where the RAID controller 822 is configured to implement RAID functionality with respect to storage devices on the I/O buses 842. Each of these I/O buses 842 may be additionally coupled to an embodiment of a virtual translator storage device 872 where the virtual translator storage device 872 itself comprises a RAID controller 862. Each of virtual translator storage devices 872 is coupled to a set of corresponding storage devices 892 using a set of corresponding I/O buses 882. Each of virtual translator storage devices 872 may or may not implement RAID in conjunction with its corresponding storage devices invisibly to storage server 832. In other words, to the RAID controller 822 of storage sever 832 it appears as if a single storage device (e.g. hard disk drive, etc.) is present on each of I/O buses 842 and no alteration to the hardware of storage server is necessary to accomplish the implementation of RAID.
It should be noted that a wide variety of objectives may be accomplished through the use of embodiments of virtual translator storage devices 872 in conjunction with a storage server 832 (e.g. increased speed, performance, redundancy, etc.) and that many permutations of various RAID implementations may be possible. For example, no RAID may be implemented with respect to virtual translator storage device 872a, RAID level 0 may be implemented with respect to another virtual translator storage device (not shown), RAID level 1 may be implemented with respect to virtual translator storage device 872n, etc.
By distributing RAID functionality as detailed above, a wide variety of objectives may be accomplished, including locating relatively more complex RAID functionality where faster processing may take place and locating other, less processing intense RAID functionality in other locales. For example, relatively complex RAID functionality (e.g. RAID 5 or RAID 10) may be implemented with respect to RAID controller 822 of storage server 832 while relatively less complex RAID functionality (e.g. RAID 0 or RAID 1) may be implemented with respect to virtual storage translator devices 872. Having the ability to distribute this RAID functionality may provide the ability to reduce costs associated with various RAID implementations by allowing complex (and thus expensive) RAID processing to be centralized (e.g. at the storage server) while still implementing less complex RAID functionality at other locales, freeing up processing power (e.g. at the storage server) to implement other functionality (e.g. complex RAID functionality).
In addition to RAID functionality, other forms of functionality may be implemented with respect to embodiments of a virtual translator storage device. In one embodiment, this functionality may include performing encryption on the data stored on one or more of the storage devices associated with the virtual translator storage device. Encrypting data in conjunction with an embodiment of the virtual translator storage device may increase performance of a system with which a virtual translator storage device is utilized (e.g. because no bandwidth is consumed by the operating system for encrypting and decrypting) while simultaneously eliminating a security risk (a compromised operating system or stored data). In a notebook computer setting encrypting at the device level is extremely important for removable storage devices as these devices may frequently be misplaced, stolen or otherwise accessed by unauthorized persons. In the same vein, embodiment of the virtual storage translation device may allow all data on a storage device to be fully encrypted (as opposed to the storage device containing a mix of encrypted and non-encrypted data). A fully encrypted drive provides a greater level of security than a drive that contains non-encrypted and encrypted data.
Turning to FIG. 9, a block diagram for one embodiment of a system for interfacing multiple buses with a single bus is depicted, where encryption may be implemented with respect to data stored on one or more of the storage devices on these multiple buses. More specifically, virtual storage translator device 910 may allow a primary I/O bus 920 to be interfaced with multiple secondary I/O buses 930. Virtual storage translator device 910, includes encryption logic 960 which may be hardware (e.g. on an ASIC), a portion of the hardware or ASIC comprising virtual storage translator device 910, computer readable instructions on a computer readable media, or some combination. Encryption logic 960 may be operable to implement apply one or more encryption algorithms to data being stored to, or retrieved from, storage devices 940 to encrypt according to established standards such as SSL, it could provide low-level whole or partial encryption of a storage device, or it some other function involving an encryption algorithm. These encryption algorithms may include, but are not limited to, all or a subset of the following:










SSL v3.0 cipher suites















Key




SSL v3.0 Cipher Suite/OpenSSL Name
Auth
Cipher
Length
Mode
Hash















SSL_RSA_EXPORT_WITH_RC4_40_MD5
RSA
RC4
40
—
MD5


EXP-RC4-MD5







SSL_RSA_WITH_RC4_128_MD5
RSA
RC4
128
—
MD5


RC4-MD5







SSL_RSA_WITH_RC4_128_SHA
RSA
RC4
128
—
SHA-1


RC4-SHA







SSL_RSA_EXPORT_WITH_RC2_CBC_40_MD5
RSA
RC2
40
CBC
MD5


EXP-RC2-CBC-MD5







SSL_RSA_EXPORT_WITH_DES40_CBC_SHA
RSA
DES
40
CBC
SHA-1


EXP-DES-CBC-SHA







SSL_RSA_WITH_DES_CBC_SHA
RSA
DES
56
CBC
SHA-1


DES-CBC-SHA







SSL_RSA_WITH_3DES_EDE_CBC_SHA
RSA
3DES
168
CBC
SHA-1


DES-CBC3-SHA







SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA
DSA
DES
40
CBC
SHA-1


EXP-EDH-DSS-DES-CBC-SHA







SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA
DSA
3DES
168
CBC
SHA-1


EDH-DSS-DES-CBC3-SHA







SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA
RSA
DES
40
CBC
SHA-1


EXP-EDH-RSA-DES-CBC-SHA







SSL_DHE_RSA_WITH_DES_CDC_SHA
RSA
DES
56
CBC
SHA-1


EDH-RSA-DES-CBC-SHA







SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA
RSA
3DES
168
CBC
SHA-1


EDH-RSA-DES-CBC3-SHA



















TLS v1.0 cipher suites















Key




TLS v1.0 CipherSuite/□OpenSSL Name
Auth
Cipher
Length
Mode
Hash















TLS_RSA_EXPORT_WITH_RC4_40_MD5
RSA
RC4
40
—
MD5


EXP-RC4-MD5







TLS_RSA_WITH_RC4_128_MD5
RSA
RC4
128
—
MD5


RC4-MD5







TLS_RSA_WITH_RC4_128_SHA
RSA
RC4
128
—
SHA-1


RC4-SHA







TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5
RSA
RC2
40
CBC
MD5


EXP-RC2-CBC-MD5







TLS_RSA_EXPORT_WITH_DES40_CBC_SHA
RSA
DES
40
CBC
SHA-1


EXP-DES-CBC-SHA







TLS_RSA_WITH_DES_CBC_SHA
RSA
DES
56
CBC
SHA-1


DES-CBC-SHA







TLS_RSA_WITH_3DES_EDE_CBC_SHA
RSA
3DES
168
CBC
SHA-1


DES-CBC3-SHA







TLS_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA
DSA
DES
40
CBC
SHA-1


EXP-EDH-DSS-DES-CBC-SHA







TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA
DSA
3DES
168
CBC
SHA-1


EDH-DSS-DES-CBC3-SHA







TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA
RSA
DES
40
CBC
SHA-1


EXP-EDH-RSA-DES-CBC-SHA







TLS_DHE_RSA_WITH_DES_CBC_SHA
RSA
DES
56
CBC
SHA-1


EDH-RSA-DES-CBC-SHA







TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA
RSA
3DES
168
CBC
SHA-1


EDH-RSA-DES-CBC3-SHA



















AES cipher suites from RFC3268, extending TLS v1.0















Key




TLS v1.0 Cipher Suite/□OpenSSL Name
Auth
Cipher
Length
Mode
Hash





TLS_RSA_WITH_AES_128_CBC_SHA
RSA
AES
128
CBC
SHA-1


AES128 -SHA







TLS_RSA_WITH_AES_256_CBC_SHA
RSA
AES
256
CBC
SHA-1


AES256-SHA







TLS_DHE_DSS_WITH_AES_128_CBC_SHA
DSA
AES
128
CBC
SHA-1


DHE-DSS-AES128-SHA







TLS_DHE_DSS_WITH_AES_256_CBC_SHA
DSA
AES
256
CBC
SHA-1


DHE -DSS-AES256-SHA







TLS_DHE_RSA_WITH_AES_128_CBC_SHA
RSA
AES
128
CBC
SHA-1


DHE-RSA-AES128-SHA







TLS_DHE_RSA_WITH_AES_256_CBC_SHA
RSA
AES
256
CBC
SHA-1


DHE-RSA-AES256-SHA



















Additional Export 1024 and other cipher suites















Key




TLS v1.0 Cipher Suite/□OpenSSL Name
Auth
Cipher
Length
Mode
Hash















TLS_RSA_EXPORT1024_WITH_DES_CBC_SHA
RSA
DES
56
CBC
SHA-1


EXP1024-DES-CBC-SHA







TLS_RSA_EXPORT1024_WITH_RC4_56_SHA
RSA
RC4
56
—
SHA-1


EXP1024-RC4-SHA







TLS_DHE_DSS_EXPORT1024_WITH_DES_CBC_SHA
DSA
DES
56
CBC
SHA-1


EXP1024-DHE-DSS-DES-CBC-SHA







TLS_DHE_DSS_EXPORT1024_WITH_RC4_56_SHA
DSA
RC4
56
—
SHA-1


EXP1024-DHE-DSS-RC4-SHA







TLS_DHE_DSS_WITH_RC4_128_SHA
DSA
RC4
128
—
SHA-1


DHE-DSS-RC4-SHA





Note: these ciphers can also be used in SSL v3 among others.
















SSL v2.0 cipher suites















Key




TLS v1.0 Cipher Suite/□OpenSSL Name
Auth
Cipher
Length
Mode
Hash















SSL_CK_RC4_128_WITH_MD5
—
RC4
128
—
MD5


RC4-MD5







SSL_CK_RC4_128_EXPORT40_WITH_MD5
—
RC4
128
—
MD5


EXP-RC4-MD5







SSL_CK_DES_64_CBC_WITH_MD5
—
DES
64
CBC
MD5


DES-CBC-MD5







SSL_CK_DES_192_EDE3_CBC_WITH_MD5
—
3DES
192
CBC
MD5


DES-CBC3-MD5









Encryption

In one embodiment, the following algorithms for encryption may be supported:















Algorithm
Key Length
Encryption Mode









AES
128
CBC



3DES
168
CBC



Blowfish
128
CBC



Cast
128
CBC



Arcfour (RC4)
128
—



AES
192
CBC



AES
256
CBC










Authentication

In one embodiment, the following algorithms for authentication may be supported:












Algorithm
Key Length
Encryption Mode







DSA
Any, defaults to 1024
n/a - only used for authentication


RSA
Any, defaults to 1024
n/a - only used for authentication









Thus, virtual storage translator device 910 may be operable to receive commands or instructions on primary I/O bus 920 and translate these commands or instructions such that they are effectuated with respect to storage device 940 on secondary I/O buses 930. Additionally, virtual storage translator device 910 is operable to apply encryption logic 960 to any data being stored or retrieved from one or more of these storage devices 940, such that data may be stored on one or more storage device 940 in an encrypted format. As this encryption may take place in virtual storage translator device 910, the encryption process may be more secure than a similar encryption process which is accomplished at the operating system or application level.
As a large degree of functionality has been discussed herein in conjunction with embodiments of a virtual translator storage device it should be pointed out that almost any permutation of embodiments of functionalities discussed herein may be implemented. For example, multiple virtual translator storage devices may be cascaded to achieve varying effects, RAID may be implemented with respect to none or all of the virtual translator storage devices in a particular system, different types of storage devices may be utilized in conjunction with virtual translator storage devices, RAID may be implemented with varying types of storage devices and hardware encryption may be utilized on one or more of these storage devices, etc.
Examples of such permutations may be better explained with reference to FIG. 10 which depicts one example of an implementation of the use of virtual translator storage devices. As discussed above virtual storage translator device 1030 may allow a primary I/O bus 1010 to be interfaced with multiple secondary I/O buses 1040. Here, secondary I/O bus 1040a may be coupled to a solid state storage device 1020 while secondary I/O bus 1040b is coupled to another virtual translator storage device 1050 which is, in turn, coupled to tertiary I/O buses 1080, each tertiary I/O bus 1080 coupled to a respective storage device 1090 which may be, for example, a spinning storage device or the like.
During operation of system 1000 virtual translator storage device 1030 may store data which has been designated as critical on solid state storage device 1020. Additionally, virtual translator storage device 1030 may use encryption circuitry or software 1032 to encrypt this critical data. Thus, all data designated as critical may be stored on solid state storage device 1020 in an encrypted form by virtual translator storage device 1030.
Similarly, virtual translator storage device 1030 may send commands or instructions to store non-critical data over I/O bus 1040b (without applying any encryption to the non-critical data). These commands or instructions may be received at virtual translator storage device 1050 which may utilize RAID controller 1060 to implement RAID with respect to storage devices 1090, for example RAID level 1 or another level. In this manner, critical data may be protected by storing it in an encrypted format on solid state storage device 1020, while greater capacity may be provided for storing non-critical data on storage device 1090 or non-critical data may be protected using the redundancy or fault tolerance provided by RAID implemented by virtual translator storage device 1050.
In the foregoing specification, the invention has been described with reference to specific embodiments. However, one of ordinary skill in the art appreciates that various modifications and changes can be made without departing from the scope of the invention as set forth in the claims below. Accordingly, the specification and figures are to be regarded in an illustrative rather than a restrictive sense, and all such modifications are intended to be included within the scope of invention. For example, it will be noted that many other permutations of use of embodiments of a virtual translator storage device may be implemented.
Benefits, other advantages, and solutions to problems have been described above with regard to specific embodiments. However, the benefits, advantages, solutions to problems, and any component(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential feature or component of any or all the claims.

## Claims

1. A device, comprising:
a processor;
a first interface operable to interface with a first I/O bus and receive a command for storing data utilizing a first protocol, wherein the device appears as a single storage device on the first I/O bus;
a second interface operable to interface with a plurality of second I/O buses to store the data corresponding to the command, a first I/O bus of the plurality of second I/O buses utilizing a second protocol associated with a first type of storage device selected for non-critical data storage and a second I/O bus of the plurality of second I/O buses utilizing a third protocol associated with a second type of storage device selected for critical data storage and different from the second protocol, wherein each I/O bus of the plurality of second I/O buses is operable to couple to one or more storage devices;
a controller comprising a memory for storing:
a set of instructions executable by the processor to determine a type of storage device into which the data is to be stored;
a plurality of queues operable to buffer the command received on the first I/O bus, wherein a first set of queues is configured to buffer commands associated with the first type of storage device and a second set of queues is configured to buffer commands associated with the second type of storage device;
a map operable to map an address for the command received on the first I/O bus to one or more physical addresses corresponding to the one or more storage devices coupled to the second I/O buses associated with the type of storage device into which the data is to be stored; and
a translator operable to configure a communication in the first protocol, the second protocol or the third protocol,

wherein the controller is operable to store data on the one or more storage devices coupled to the plurality of second I/O buses and to implement a level of RAID in conjunction with two or more storage devices coupled to the plurality of second I/O buses by buffering the command received through the first interface in one queue of the first set of queues or the second set of queues based on the determination that the data is non-critical or critical and translating the command received on the first I/O bus to one or more second commands according to the second protocol or the third protocol to implement the command in conjunction with the level of RAID.

2. The device of claim 1, wherein the RAID level is level 1, 3, 4, 5, 6 or 10.

3. The device of claim 1, wherein the storage device is further operable to implement multi-RAID modes and cascaded storage devices.

4. The device of claim 1, wherein the protocol associated with the first I/O bus of the plurality of second I/O buses is a SATA, PATA, SCSI, or FC.

5. The device of claim 4, wherein the protocol associated with the second I/O bus of the plurality of second I/O buses is SATA, PATA, SCSI, or FC.

6. The device of claim 1, wherein a first storage device coupled to the first I/O bus of the plurality of second I/O buses is a disk drive and a second storage device coupled to the second I/O bus of the plurality of second I/O buses is a solid state storage device.

7. The device of claim 6, wherein the set of instructions is operable to allow a user to specify on which of the one or more storage device data is stored.

8. The device of claim 1, further comprising encryption logic operable to implement one or more encryption algorithms to data being stored in, or retrieved from one or more of the one or more storage device.

9. A method of interfacing buses using a device having a processor and a non-transitory computer-readable medium storing a set of instructions executable for:
receiving a first command on a first I/O bus utilizing a first protocol;
determining a type of storage device into which data is to be stored, wherein the device comprises a plurality of second I/O buses including a first bus of the plurality of second I/O buses utilizing a second protocol associated with a first type of storage device selected for non-critical data storage and a second bus of the plurality of second I/O buses utilizing a third protocol associated with a second type of storage device selected for critical data storage and different from the second protocol, wherein each I/O bus of the plurality of second I/O buses is operable to couple to one or more storage devices;
buffering the first command in one or more of a plurality of queues, wherein a first set of the plurality of queues is configured to buffer commands associated with the first type of storage device and a second set of the plurality of queues is configured to buffer commands associated with the second type of storage device;
mapping an address for the first command received on the first I/O bus to one or more addresses corresponding to the one or more storage devices coupled to the plurality of second I/O buses;
translating the first command to one or more second commands according to the second protocol or the third protocol;
storing the data in the one or more storage devices, wherein the device is operable to map an address for the first command received on the first I/O bus to one or more addresses corresponding to the first type of storage devices coupled to the first bus of the plurality of second I/O buses or the second type of storage devices coupled to the second bus of the plurality of second I/O buses such that the device appears as a single storage device on the first I/O bus; and
implementing a level of RAID in conjunction with two or more storage devices coupled to the plurality of second I/O buses by buffering the first command in one queue of the first set of queues or the second set of queues based on the determination that the data is non-critical or critical and translating the first command received on the first I/O bus to one or more second commands according to the second protocol or the third protocol to implement the first command in conjunction with the level of RAID.

10. The method of claim 9, wherein the RAID level is level 1, 3, 4, 5, 6 or 10.

11. The method of claim 9, further comprising implementing multi-RAID modes and cascaded storage devices.

12. The method of claim 9, wherein the first I/O bus is a SATA, PATA, SCSI, or FC bus.

13. The method of claim 12, wherein each of the plurality of second I/O buses is a SATA, PATA, SCSI, or FC bus.

14. The method of claim 9, wherein the first storage device coupled to the first bus of the plurality of second I/O buses is a disk drive and the second storage device coupled to the second bus of the plurality of second I/O buses is a solid state storage device.

15. The method of claim 14, further comprising allowing a user to specify on which of the one or more storage device data is to be stored.

16. The method of claim 9, further comprising encrypting data being stored in, or retrieved from one or more of the one or more storage device.