Virtualization in a storage system

• US 7,864,758 B1
• Filed: 01/18/2002
• Issued: 01/04/2011
• Est. Priority Date: 09/28/2001
• Status: Expired due to Term

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: EMC Corporation (Dell Technologies Inc.)
• Inventors: Lolayekar, Santosh C., Frey, Robert T., Lee, Wan-Hui, Maranon, Renato E., Cheng, Yu-Ping
• Primary Examiner(s): Moe; Aung S
• Assistant Examiner(s): Grey; Christopher P
• Application Number:
  US10/051,396
• Time in Patent Office: 3,273 Days
• Field of Search: 370/423, 370/389, 370229-2362, 370/242, 370/244, 370/252, 370/253, 370/400, 370/401, 711/6, 711/202, 711/203, 709/203, 709/213, 709/214, 709/219
• US Class Current: 370/389
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Abstract

A storage switch in accordance with an embodiment of the invention is a highly scalable switch that allows the creation of a SAN that is easy to deploy and that can be centrally managed. Moreover, such a storage switch also allows the deployment of a global infrastructure, allowing the resources of the SAN, such as storage devices, to essentially be positioned anywhere on the globe. Further, such a storage switch allows a multi-protocol SAN, e.g., one that includes both iSCSI or Fibre Channel, and processes data packets at “wire speed.” To further enable wire-speed processing, a switch in accordance with the invention has “intelligence” distributed to each of its linecards, through which it classifies packets into data and control packets, it performs virtualization functions, and it performs protocol translation functions. A switch in accordance with the invention further performs serverless storage services such as mirroring, snapshot, and replication.

Claims

1. A method for use in a switch in a storage network, comprising:

receiving a packet at an ingress port of an ingress linecard, said packet destined for a virtual target with a virtual target address, the packet associated with a request;

adding a local header to the packet;

retrieving a virtual target descriptor identifier, wherein the virtual target descriptor identifier identifies a virtual target descriptor, wherein the virtual target descriptor stores information about the virtual target;

allocating an ingress task control block identified by an ingress task control block index, wherein the ingress task control block index stores information about the request;

placing the ingress task control block index and the virtual target descriptor identifier into the local header;

retrieving a flowID from the virtual target descriptor and placing the flowID into the local header, wherein the flowID identifies an egress linecard;

forwarding the packet to the egress linecard through a fabric;

receiving the packet at the egress linecard;

using the virtual target descriptor identifier, retrieving a physical target descriptor identifier, wherein the physical target descriptor identifier identifies a physical target descriptor, wherein the physical target descriptor stores information about a physical target that is associated with the virtual target;

allocating an egress task control block with an egress task control block index, wherein the egress task control block index stores information about the request;

using information in the physical target descriptor to convert the virtual target address to a physical target address;

removing the local header and forwarding the packet to an egress port on the egress linecard; and

sending the packet from the egress port to a physical target device, using the egress task control block index as a source identifier.

2. The method of claim 1, wherein all of the steps occur at wire speed.

3. The method of claim 1, wherein all of the steps occur without buffering the packet.

4. The method of claim 1, wherein the virtual target descriptor, the virtual target descriptor identifier, the ingress task control block the egress task control block, the physical target descriptor, and the physical target descriptor identifier are each stored in memory on the respective linecards.

5. The method of claim 1, wherein the virtual target descriptor and the ingress task control block are stored in an SRAM on the ingress linecard, the virtual target descriptor identifier is stored in a CAM on the ingress linecard, the physical target descriptor and the egress task control block are stored in an SRAM on the egress linecard, and the physical target descriptor identifier is stored in a CAM on the egress linecard.