# Patent

## Title
Method and system for remote cache direct data placement

## Abstract

Method and system for processing a read request are provided. The first adapter receives the read request from a client to read data using a logical object managed by a second adapter. The first adapter is configured to generate a vendor unique command descriptor block for the second adapter to obtain the data and write the data at a location specified by the read request. The second adapter is configured to retrieve the data from a storage location specified by the logical object and writing the data at the location specified by the read request; and notifies the first adapter after writing the data.

## Background
TECHNICAL FIELD
The present disclosure relates to network communications and devices.
BACKGROUND
A computer network, often simply referred to as a network, is a group of interconnected computers and devices that facilitates communication among users and allows users to share resources. Adapters, switches and other devices are typically used during network communication for reading and writing data at mass storage devices.
Computing devices (or systems) use the mass storage devices to store data. Data centers are commonly used to store large amount of data for computing devices. Different storage options are available for computing devices to store data and retrieve data. For example, direct-attached storage (DAS), network attached storage (NAS) and storage area networks (SANs).
A DAS system typically includes a plurality of storage drives that are directly attached to a computing device (for example, a server) and is accessible via a host bus adapter (HBA). Common protocols used for DAS storage devices are SCSI (Small Computer Systems Interface), ATA (AT attachment), SATA (Serial ATA), SAS (Serial Attached SCSI) and others.
NAS is a file level storage that provides access to a plurality of computing devices. NAS typically uses network file sharing protocols, for example, NFS (Networked File System), CIFS (Common Internet File System) and others for storing and managing data at storage devices.
SAN is a dedicated network that provides access to consolidated, block level data storage. SANs are primarily used to make storage devices, such as disk arrays, tape libraries, and others, accessible to servers so that the devices appear like locally attached devices to an operating system of a computing device. A SAN typically has its own network of storage devices that are generally not accessible through the local area network by other devices. SANs often utilize a Fibre Channel fabric topology, an infrastructure specially designed to handle storage communications. SANs may also use iSCSI (i.e. mapping SCSI over TCP/IP (Transmission Control Protocol/Internet Protocol), Fibre Channel over Ethernet (FCoE), FCP (Fibre Channel over SCSI), Hyper SCSI (i.e. SCSI over Ethernet) and other protocols for storing data at storage devices.
Continuous efforts are being made to better provide access to storage systems and improve how data is stored and retrieved in a network environment having a plurality of computing devices.



BRIEF DESCRIPTION OF THE DRAWINGS
The various present embodiments relating to the management of network elements now will be discussed in detail with an emphasis on highlighting the advantageous features. These novel and non-obvious embodiments are depicted in the accompanying drawings, which are for illustrative purposes only. These drawings include the following figures, in which like numerals indicate like parts:
FIG. 1A is a functional block diagram of a system, used according to one embodiment;
FIG. 1B shows an example of an intelligent storage adapter (ISA);
FIG. 1C shows an example of a configuration for using the ISAs, according to one embodiment;
FIG. 2A shows an arrangement of using more than one ISA in a server chassis; and
FIG. 2B shows a process flow according to one embodiment of the present disclosure.



DETAILED DESCRIPTION
The following detailed description describes the present embodiments with reference to the drawings. In the drawings, reference numbers label elements of the present embodiments. These reference numbers are reproduced below in connection with the discussion of the corresponding drawing features.
As a preliminary note, any of the embodiments described with reference to the figures may be implemented using software, firmware, hardware (e.g., fixed logic circuitry), manual processing, or a combination of these implementations. The terms “logic,” “module,” “component,” “system,” and “functionality,” as used herein, generally represent software, firmware, hardware, or a combination of these elements. For instance, in the case of a software implementation, the terms “logic,” “module,” “component,” “layer” “system,” and “functionality” represent executable instructions that perform specified tasks when executed on a hardware based processing device or devices (e.g., CPU or CPUs). The program code can be stored in one or more non-transitory, computer readable memory devices.
More generally, the illustrated separation of logic, modules, components, systems, and functionality into distinct units may reflect an actual physical grouping and allocation of software, firmware, and/or hardware, or can correspond to a conceptual allocation of different tasks performed by a single software program, firmware program, and/or hardware unit. The illustrated logic, modules, components, systems, and functionality may be located at a single site (e.g., as implemented by a processing device), or may be distributed over a plurality of locations. The term “machine-readable media” and the like refers to any kind of medium for retaining information in any form, including various kinds of storage devices (magnetic, optical, static, etc.).
The embodiments disclosed herein may be implemented as a computer process (method), a computing system, or as an article of manufacture, such as a computer program product or computer-readable media. The computer program product may be non-transitory, computer storage media, readable by a computer device, and encoding a computer program of instructions for executing a computer process. The computer program product may also be readable by a computing system, and encoding a computer program of instructions for executing a computer process.
In one embodiment, an adapter, for example, a network device is provided. The adapter includes a storage protocol controller having a port for interfacing with a storage area network (SAN) based storage device and another adapter operating within a cluster is provided. The adapter includes a processor executing instructions for managing a local storage device that is configured to operate as a caching device for a computing device. The adapter operates as a host bus adapter and a storage controller for managing storage space at the local storage device and the SAN-based storage device.
System 100:
FIG. 1A is a block diagram of a system 100 configured for use with the present embodiments. System 100 may include a plurality of computing systems 102A-102N (may also be referred to as server (s) 102 or host system 102), each coupled to an adapter 114 (also referred to as an intelligent storage adapter (ISA) 114) that interfaces with other devices and ISAs, as described below in more detail.
The computing system 102A may include one or more processors 104, also known as central processing units (CPUs). Processor 104 may be, or may include, one or more programmable general-purpose or special-purpose microprocessors, digital signal processors (DSPs), programmable controllers, application specific integrated circuits (ASICs), programmable logic devices (PLDs), or the like, or a combination of such hardware devices.
Processor 104 executes machine implemented instructions (or process steps/blocks) out of a memory 106 and interfaces with an interconnect 107 that may be referred to as a computer bus 107. The computer bus 107 may be, for example, a system bus, a Peripheral Component Interconnect (PCI) bus, PCI-Express (PCIe) bus, a HyperTransport or industry standard architecture (ISA) bus, a SCSI bus, a universal serial bus (USB), an Institute of Electrical and Electronics Engineers (IEEE) standard 1394 bus (sometimes referred to as “Firewire”), or any other type of bus.
The computing system 102A may further include a storage device 108, which may be for example a hard disk, a CD-ROM, a non-volatile memory device (flash or memory stick) or any other storage device for storing structured or unstructured data. Storage 108 may store operating system program files (or data containers), application program files, for example, email applications, database applications, management applications, and other application files. Some of these files are stored on storage 108 using an installation program. For example, the processor 104 may execute computer-executable process steps of an installation program so that the processor 14 can properly execute the application program.
In one embodiment, storage device 108 may be a solid state storage device (may also be referred to herein as SSD 108). SSDs are becoming popular for servers that may need to store large amounts of data. ISA 114 described below in more detail may be used to manage and/or access storage device 108, according to one embodiment.
Memory 106 also interfaces with the computer bus 107 to provide the processor 104 with access to memory storage. Memory 106 may include random access main memory (RAM). When executing stored computer-executable process steps from storage 108, the processor 104 may store and execute the process steps out of memory 106. Read only memory (ROM, not shown) may also be used to store invariant instruction sequences, such as start-up instruction sequences or basic input/output system (BIOS) sequences for operation of a keyboard (not shown).
In one embodiment, processor 104 may execute an application 105 for performing certain functions. For example, application 105 may be a database application, a virtual machine executed in a virtual environment (provided by VMW are Corporation, Microsoft Corporation or any other entity) electronic email application (for example, Microsoft Exchange) or any other application type. Application 105 may issue read and write requests that are processed by ISA 114, as described below in more detail. Application 105 may also be referred to as a “client”.
The computing system 102A also includes other devices and interfaces 109, which may include a display device interface, a keyboard interface, a pointing device interface and others. The details of these components are not germane to the inventive embodiments.
ISA 114 may be configured to handle both network and storage traffic while interfacing with other elements. In one embodiment, as described below in detail, ISA 114 may be configured to provide the functionality of a host bus adapter (HBA) by providing connectivity to SAN (storage area network) based storage arrays as well as present logical storage from a local storage device connected to the ISA. Various network and storage protocols may be used to handle network and storage traffic, for example, Ethernet, Fibre Channel, Fibre Channel over Ethernet (FCoE), Internet over Small Computer System Interface (iSCSI), and others. Some of the common protocols are described below.
Ethernet is a common network protocol used for network communication. The original Ethernet bus or star topology was developed for local area networks (LAN) to transfer data at 10 Mbps (mega bits per second). Newer Ethernet standards (for example, Fast Ethernet (100 Base-T) and Gigabit Ethernet) support data transfer rates that are greater than 1 gigabit (Gb). The various embodiments described herein may use Ethernet (which includes 100 Base-T and/or Gigabit Ethernet) as the network protocol. However, the adaptive embodiments disclosed herein are not limited to any particular protocol, as long as the functional goals are met by an existing or new network protocol.
Fibre Channel (may also be referred to as “FC”) is a common storage protocol used in SANs. Fibre Channel is a set of American National Standards Institute (ANSI) standards that provide a serial transmission protocol for storage and network protocols such as HIPPI, SCSI, IP, ATM and others. Fibre Channel supports three different topologies: point-to-point, arbitrated loop and fabric. The point-to-point topology attaches two devices directly. The arbitrated loop topology attaches devices in a loop. The fabric topology attaches host systems directly (via HBAs) to a fabric, which are then connected to multiple devices. The Fibre Channel fabric topology allows several media types to be interconnected. Fibre Channel fabric devices include a node port or “N_Port” that manages Fabric connections. The N_port establishes a connection to a Fabric element (e.g., a switch) having a fabric port or F_port.
A new and upcoming standard, called Fibre Channel over Ethernet (FCOE) has been developed to handle both Ethernet and Fibre Channel traffic in a storage area network (SAN). This functionality would allow Fibre Channel to leverage high speed, for example, 10 Gigabit Ethernet networks while preserving the Fibre Channel protocol. In one embodiment, ISA 114 can be configured to operate as a FCOE adapter. Those of ordinary skill in the art will appreciate, however, that the present embodiments are not limited to any particular protocol.
iSCSI is an IP based storage networking standard for linking data storage facilities. By carrying SCSI commands over IP networks, iSCSI is used to facilitate data transfers over intranets and to manage storage over long distances. iSCSI can be used to transmit data over local area networks (LANs), wide area networks (WANs), or the Internet and can enable location-independent data storage and retrieval. The protocol allows clients to send SCSI commands (referred to as command or (control) data blocks (CDBs) to SCSI storage devices (may be referred to as targets) on remote servers. iSCSI is a SAN-based protocol, allowing organizations to consolidate storage into data center storage arrays while providing hosts (such as database and web servers) with the illusion of locally attached disks. Unlike traditional Fibre Channel, which uses special-purpose cabling, iSCSI can be run over long distances using existing network infrastructure. In one embodiment, ISA 114 may operate as an initiator as well as a target for responding to input/output (referred to as 110 or “10”) requests for reading and writing information at storage devices.
Storage space at a storage device (local or SAN-based) is typically presented to application 105 as a logical entity referred to as a logical unit number (LUN). Each LUN is uniquely identified by an identifier (LUN ID) and is associated with physical storage space. A LUN has a size associated with it that may indicate the amount of storage space that is made available to a computing system and a drive letter that may be used to access the LUN.
A LUN is typically divided into logical block addresses (LBAs) that are used by application 105 to read and write data to storage locations. The LBAs are mapped with actual physical storage to read and write data. A LUN used by an application may be referred to as a data LUN. A LUN that is accessible via a SAN connection may be referred to as a SAN LUN. A LUN at a local storage device managed by ISA 114 may be referred to as “cache” LUN. A cache LUN may be used to cache data stored at a SAN LUN or another data LUN. The cache LUN is managed by ISA 114 and may not be visible to application 105.
Referring back to FIG. 1A, computing system 102 uses an adapter interface 110 to communicate with ISA 114 via a link 112. In one embodiment, link 112 may be a PCI-Express link or any other interconnect type. The adaptive embodiments disclosed herein are not limited to any particular link type.
ISA 114 may communicate and interface with a mass storage system 120 via a SAN 116 that may include one or more switch (may be referred to as fabric switch). The mass storage system 120 may include a plurality of storage devices 124A-124N. Storage space at storage devices 124A-124N may be presented as SAN LUNs to application 105 via SAN 116. Controller 122 of mass storage system 120 may be used to manage storage devices 124A-124N. In one embodiment, controller 122 may include a processor, an ISA 114 and other similar components.
System 100 may also include a management console 118, used according to one embodiment. Management console 118 may be a computer system similar to computing system 102A described above in detail. Management console 118 executes a management application 117 that may be used to configure storage space as logical structures (for example, as LUNs) that are presented to computing systems 102A-102N for storing information or as cache LUNs at local storage for caching information stored at SAN LUNs. Permissions associated with a LUN may also be configured using management application 117. The permissions indicate which entities may be allowed to access a LUN to read and/or write information. Management application 117 may store LUN attributes and permissions in a configuration data structure 117A at a storage location.
In one embodiment, ISA 114 is provided that can provide transparent data caching at SSDs while efficiently synchronizing the SSD data with SAN-based storage devices. The ISA enables management of data stored at the SSDs. The ISA also enables the SSDs to be shared as SAN storage allowing other servers 102B-102N to access data residing at SSDs in server 102A. ISA 114 may configure a LUN from the local storage 108 and present the LUN to servers 102A-102N, allowing the local storage 108 to be shared by other Servers 102B-102N.
In another embodiment, ISA 114 provides traditional SAN connectivity to computing systems 102A and to the SSDs at each computing system. The SSDs may be managed as a storage pool that may be configured to operate as a cache pool to cache read/write data for SAN LUNs presented to the computing systems. SAN LUNs when configured may be tagged with an attribute that allows caching at the local SSDs for read and/or write caching.
FIG. 1B shows an example of ISA 114A that includes a storage protocol controller 128 (shown as “external storage protocol controller”) with ports 126A and 126B. The storage protocol controller may be a Fibre Channel controller (or application specific integrated circuit (ASIC)) that is available from QLogic Corporation for interfacing with Fibre Channel based storage devices via ports 126A/126B. Ports 126A/126B include logic and circuitry for sending and receiving Fibre Channel frames. Fibre Channel is simply shown as an example and the various embodiments disclosed herein are not limited to any particular storage/network protocol. Thus ports 126A-126B are not limited to just Fibre Channel ports. Furthermore, although only two ports 126A and 126B are shown as an example, the adaptive embodiments disclosed herein are not limited to any particular number of ports.
Storage protocol controller 128 may operate as a host bus adapter for managing I/O requests for SAN-based storage. Storage protocol controller 128 is configured to process I/O requests for reading data from SAN-based storage (124A-124N) and writing data to SAN-based storage. Thus storage protocol controller 128 is used to take advantage of existing SAN infrastructure, while providing access to SSDs for computing systems 102A-102N.
In one embodiment, storage protocol controller 128 includes a processor (not shown) for executing the Fibre Channel stack having layers, FC0-FC3. FC0 is defined by the Fibre Channel specification as the physical layer, which includes cables (fiber optics, twisted-pair), connectors and others. FC1 layer is defined as the data link layer. This layer implements the 8B/10B encoding and decoding of signals. FC2 layer 49C is defined as the network layer. This layer defines the main Fibre Channel framing, addressing, and control protocols. FC3 layer is an auxiliary layer that provides common services like encryption or RAID related. FC4 layer is the protocol mapping layer where other protocols, such as SCSI are encapsulated into an information unit for delivery to FC2 and transmission across a Fibre Channel network. This layer provides flexibility to Fibre Channel as a networking technology compatible with other technologies.
ISA 114A also includes a host interface 150 that interfaces with processor 104 via link 112. The structure of host interface 150 will depend on the type of connection/interconnect used to communicate with processor 104. For example, if a PCI-Express link is used to communicate with processor 104, then host interface 150 includes logic and circuitry for receiving and sending PCI-Express packets/information.
ISA 114A includes a system on chip (SOC) 131 that includes a micro-processor 130 having access to an adapter memory (may also be referred to as local memory) 132. Processor 130 may be one or more programmable general-purpose or special-purpose microprocessors, digital signal processors (DSPs), programmable controllers, application specific integrated circuits (ASICs), reduced instruction set computer (RISC), programmable logic devices (PLDs), or the like, or a combination of such hardware devices. Memory 132 may be used to store firmware instructions and various data structures for ISA 114A for controlling overall ISA 114A operations. Memory 132 may also store instructions for implementing the various embodiments described herein.
SOC 131 may also include a receive module 134 and a transmit module 136. The receive module 134 may be used to store packets that are received via ports 126A/126B, while transmit module 136 may be used to store information that is transmitted via ports 126A/126B or to local SSDs that are described below. Receive module 134 and/or transmit module 136 may be separate modules and may include more than one component for processing received information or information that is transmitted.
ISA 114A may also include a non-volatile memory 138 (shown as flash memory) for storing parameters/instructions that may be used by micro-processor 130 for executing the instructions described below in detail. ISA 114A also includes a storage connector 140 that interfaces with another card 141 (may also be referred to as a daughter card 141), according to one embodiment. In one embodiment, the storage connector may be a PCI-Express connector, PCI connector or any other connector type based on the interconnect used by SOC 131 to interface with the SSDs. The daughter card 141 includes a memory controller 142 that interfaces with a plurality of connectors' 144A-144N. The plurality of connectors' 144A-144N are used to plug in SSDs 148A-148N (similar to storage 108). In this embodiment, SSDs 148A-148N are included within a server chassis 146. In one embodiment, connectors' 144A-144N may be SATA connectors for receiving SSDs 148A-148N. In another embodiment, connectors' 144A-144N may be SAS connectors.
ISA 114A has SAN connectivity because of ports 126A-126B, similar to a host bus adapter, as mentioned above. The storage protocol controller 128 allows SAN storage based processing. Unlike conventional HBAs, ISA 114A also includes a storage connector 140 that provides local storage solutions via SSDs 148A-148N.
In another embodiment of ISA 114A is configured such that a daughter card has the SSDs 148A-148N on the card itself, rather than on the server chassis 146. In another embodiment of ISA 114A is configured such that the memory controller 142 is on the same card as the other components of ISA 114A. The SSDs 148A-148N are also on the same card connected via one or more storage connectors.
FIG. 1C shows a system 100A where each ISA 114B-114D (similar to ISA 114A described above) in servers 102A-102N are coupled to a fabric switch 160, according to one embodiment. Fabric switch 160 includes a plurality of ports 160A-160E. Ports 160A-160C are coupled to ISA 114B-114D ports, respectively, while port 160D is coupled to controller 122 of the mass storage system 120. Management console 118 may be coupled to port 160E for configuring various components of system 100A.
Management console 118 may also be used to configure LUNs 156A-156N that are presented to servers 102A-102N for storing information. The LUNs may be based on storage located at SAN-based storage 120 or at a local SSD148A-148N.
The LUNs 156A-156N may be configured to operate as a local LUN. In this configuration, the LUN may be used as a “boot” LUN. The LUN may be used by the host computing system to which it is presented. One or more ISAs may present the boot LUN to any of the servers that are served by a cluster of ISAs. LUNs 156A-156N may also be configured as a SAN mirror LUN. In such configuration, the LUN is a mirror of a LUN that is associated with a SAN-based storage device. LUNs 156A-156N may also be configured as Peer Mirror LUN. In such a configuration, the LUN is mirrored across at least two ISAs and hence can be made accessible to at least two servers.
The LUNs 156A-156C may also be accessible by one or more servers via SAN 116. In this example, a DAS (direct attached storage) based SSD becomes accessible as SAN storage, while the DAS based storage is still managed by an application 105 (for example, a database application).
In FIG. 1C, in one embodiment ISA 114B in server 102A acts as a storage protocol controller for LUN 156A, serving up LUN 156A to initiators ISA 114C in server 102B and ISA 114D in server 102C. At the same time, ISA 114B also acts as a traditional HBA (initiator) for SAN LUNs at SAN storage devices 124A-124N.
FIG. 2A shows a configuration where a host system may 200 have more than one ISA, shown as cache client adapter 204 and a cache owner adapter 206. More than one ISA may be provided for redundancy and failover. The cache client adapter 204 interfaces with client 202A from among clients' 202A-202N. Clients' 202A-202N may be applications, VMs or computing devices.
Cache owner adapter 206 owns a cache LUN at SSD 208 for one or more clients. In conventional systems, when a request to read data for client 202A is received by cache client adapter 204, it passes the request to cache owner adapter 206. The cache owner adapter 206 obtains the requested data from SSD 208 or from a SAN LUN (not shown in FIG. 2A. The data is first stored at cache owner 206 and then provided to cache client adapter 210. The cache client adapter 204 then sends the data via a direct memory access (DMA) operation to host memory 203. This process is cumbersome because the requested data has to be buffered numerous times, for example, at 206 and then at 204. The embodiments described herein provide a better solution, as described below with respect to FIG. 2B.
FIG. 2B shows a process 212 for performing a read operation, according to one embodiment. The process starts in block b214, when a client 202A is operational and the cache owner adapter 208 and cache client adapter 204 are initialized and operational to service I/O requests on behalf of client 202A and other clients.
In block B216, client 202A sends a read request for cache client adapter 204 with a scatter gather table. The scatter gather table (or any other instruction) allows the cache client 204 to place data directly at host memory 203. As an example, the request in block B216 is for reading data from a LUN that is managed (or owned) by cache owner adapter 206. The LUN may be based on local SSD 208 or a SAN LUN.
Cache client adapter 204 receives or obtains the client request and determines that the data requested by the client is from a LUN managed by cache owner adapter 206. This may be determined by the cache client adapter 204 by examining request that includes a LUN identifier and then using a data structure (not shown) to find the cache owner. In one embodiment, cache client adapter 204 generates a vendor unique command descriptor block (VUCDB) for cache owner adapter 206 to write data to host memory 203. The VUCDB includes a SCSI command descriptor block (CDB) and the scatter gather table. An example of a VUCDB format is provided below with respect to Table I. The first column provides a byte offset, the second provides the field for byte offset, and the third column describes the field. The various bytes/format for the VUCDB are provided below.









TABLE I





Byte




Offset (h)
Field
Description







0
OpCode
Operation Code


1-4
Vendor Tag
Identifies the CDB as a VUCDB


5
Version
Identifies the version of CDB format


6-7
Service Action
Service Action Code to be performed



Code
embedded in the CDB


8-B
Data Length
Amount of data to be transferred (in bytes)


C-F
Handle
Uniquely identifies the CDB









Byte 0 of the VUCDB may have an OpCode. OpCode 0xC9 may be interpreted as a read request.
Byte 1 through 4 may be used to provide a vendor signature, for example, a signature to identify the vendor providing the ISA or the ISA itself. Byte 1 may include the most significant bit (MSB) of the signature and Byte 3 may be used to include the least significant bit (LSB) of the signature. Hexadecimal value of each character is stored in the CDB.
Byte 5 of the VU CDB indicates a version level. The version level is used to interpret the payload.
Bytes 6-7 include a Service Action Code that are used to interpret the type of action that needs to be performed for a CDB payload specified in bytes 8-11 of the CDB.
An example of the VUCDB and the data placement header using the Table I format are provided below:
typedef struct_RC_VU_CDB—
{
UCHAR OpCode;//1 Byte—0xC9
UCHAR VendorTag[ISA_VU_CMND_SIGN_LEN];//4 Bytes—0x514C4743—TQLGCT

    
    
        UCHAR Version;//1 Byte
    
    


UCHAR Reserved0;//1 Byte
UCHAR Reserved1;//1 Byte
UCHAR HeaderLength[4];//4 Byte—Header Length (original SCSI CDB and SG table length)
UCHAR DataLength[4];//4 Bytes—Total Length of Remote Data Placement command
} RC_VU_CDB;//16 bytes
typedef struct_RC_DATA_PLACEM ENT_HDR— {

    
    
        UCHAR CDB[32];SCSI Command Descriptor Block
    
    


UCHAR CDBLength;//Length of CDB
UCHAR Reserved0[3];
UCHAR SGDataLength[4];//Data Transfer Length
UCHAR Reserved1[24];

    
    
        } RC_DATA_PLACEMENT_HDR;//64 Bytes
    
    


As shown above, the VUCDB identifies the vendor “QLGC” in the vendor tag. The header length includes the original CDB and the scatter gather (SG) table length.
The RC_Data_Placement_Hdr structure provided above describes the original SCSI command that was sent by a host application includes various fields that are self-explanatory. For example, the header provides the CDB and the CDB length. The SGD at a length array is placed after the RC_Data_Placement_Hdr structure to indicate where the data should be placed in host memory.
Referring back to FIG. 2B, in block B218, the VUCDB with the scatter gather table generated by cache client adapter 204 is sent to the cache owner adapter 206.
In block B222, the cache owner adapter 206 decodes the VUCDB using the header and obtains the requested data. Thereafter, cache owner adapter 206 places the data directly at host memory 203. In one embodiment, when the data is at SSD 208, then the SOC 131 or a module of SOC 131 places the data via a DMA operation. When data is obtained from a SAN LUN, then the external storage protocol controller 128 places the data directly at host memory 203 via a DMA operation.
In block B224, the cache owner adapter 206 sends a status to the cache client adapter 204 indicating that the write operation has been completed. In block B226, the cache client adapter 204 notifies the client 202A.
The process described above is efficient and has very advantages. For example, a read operation is converted into a write operation by a VUCDB. The VUCDB is used by the cache owner to directly write the data instead of first buffering the data at the cache owner adapter, providing it to the cache client adapter and then the client cache adapter sending the data by a DMA operation. The process thus reduces the need for a plurality of buffering operations and efficiently provides data.
Although the present disclosure has been described with reference to specific embodiments, these embodiments are illustrative only and not limiting. For example, although the description above has been described with respect to an ISA, any other device may be configured to perform the foregoing function. Thus the term adapter and device are interchangeable. Many other applications and embodiments of the present disclosure will be apparent in light of this disclosure and the following claims. References throughout this specification to “one embodiment” or “an embodiment” means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Therefore, it is emphasized and should be appreciated that two or more references to “an embodiment” or “one embodiment” or “an alternative embodiment” in various portions of this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures or characteristics being referred to may be combined as suitable in one or more embodiments of the disclosure, as will be recognized by those of ordinary skill in the art.

## Claims

1. A machine implemented method, comprising;
receiving a read request at a first adapter to read data using a logical object managed by a second adapter;
the first adapter generating a command descriptor block for the second adapter to obtain the data and write the data at a location specified by the read request;
the second adapter retrieving the data from a storage location specified by the logical object and writing the data at the location specified by the read request;
the second adapter notifying the first adapter after writing the data; and
the first adapter notifying a client that send the read request.

2. The method of claim 1, wherein the logical object is a logical unit number (LUN).

3. The method of claim 2, wherein the LUN is based on storage space a local storage device managed by the second adapter.

4. The method of claim 2, wherein the LUN is based on a storage space at a storage device accessible via a storage area network.

5. The method of claim 4, wherein a storage controller at the second adapter obtains the data and writes the data at the location specified by the read request using a direct memory access (DMA) operation.

6. The method of claim 5, wherein the storage controller is a Fibre Channel controller configured to interface with Fibre Channel storage devices.

7. The method of claim 1, wherein the read request includes a scatter gather table identifying the storage location where the data is to be written.

8. A machine implemented method, comprising;
a first adapter generating a command descriptor block for a second adapter to obtain data in response to a read request from a client and write the data at a location specified by the read request;
the second adapter retrieving the data and writing the data at the location specified by the read request; and
the second adapter notifying the first adapter after writing the data.

9. The method of claim 8, wherein the read request specifies a logical unit number (LUN) associated with a storage space where the data is stored.

10. The method of claim 9, wherein the LUN is based on storage space at a local storage device managed by the second adapter.

11. The method of claim 9, wherein the LUN is based on a storage space at a storage device accessible via a storage area network.

12. The method of claim 11, wherein a storage controller at the second adapter obtains the data and writes the data at the location specified by the read request using a direct memory access (DMA) operation.

13. The method of claim 8, wherein the read request includes a scatter gather table identifying the storage location where the data is to be written.

14. A system, comprising;
a first adapter receiving a read request from a client to read data using a logical object managed by a second adapter;
wherein the first adapter is configured to generate a vendor unique command descriptor block for the second adapter to obtain the data and write the data at a location specified by the read request; and
wherein the second adapter is configured to retrieve the data from a storage location specified by the logical object and writing the data at the location specified by the read request; and notify the first adapter after writing the data.

15. The system of claim 14, wherein the logical object is a logical unit number (LUN).

16. The system of claim 15, wherein the LUN is based on storage space a local storage device managed by the second adapter.

17. The system of claim 15, wherein the LUN is based on a storage space at a storage device accessible via a storage area network.

18. The system of claim 17, wherein a storage controller at the second adapter obtains the data and writes the data at the location specified by the read request using a direct memory access (DMA) operation.

19. The system of claim 17, wherein the storage controller is a Fibre Channel controller configured to interface with Fibre Channel storage devices.

20. The system of claim 14, wherein the read request includes a scatter gather table identifying the storage location where the data is to be written.