Method and system for fast ordered writes with atomic multicast

• US 10,466,930 B2
• Filed: 04/28/2017
• Issued: 11/05/2019
• Est. Priority Date: 04/28/2017
• Status: Active Grant

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Inventors: Nishimoto, Michael, Rajadnya, Samir
• Primary Examiner(s): Vo, Tim T
• Assistant Examiner(s): Wang, Harry Z
• Application Number:
  US15/581,580
• Publication Number:
  US 20180314461A1
• Time in Patent Office: 921 Days
• CPC Class Codes: G06F 13/1668 Details of memory controller
• CPC Class Codes: G06F 13/4022 using switching circuits, e.g. switching matrix, connection or expansion network G06F13/4009 takes precedence
• CPC Class Codes: G06F 13/4068 Electrical coupling
• CPC Class Codes: G06F 13/4282 on a serial bus, e.g. I2C bus, SPI bus on daisy chain buses G06F13/4247
• CPC Class Codes: G06F 3/061 Improving I/O performance
• CPC Class Codes: G06F 3/0659 Command handling arrangements, e.g. command buffers, queues, command scheduling
• CPC Class Codes: G06F 3/0683 Plurality of storage devices

Abstract

In general, embodiments of the technology relate to a method and system for performing fast ordered writes in a storage appliance that includes multiple separate storage modules. More specifically, embodiments of the technology enable multicasting of data to multiple storage modules in a storage appliance, where the order in which the write requests are processed is the same across all storage modules in the storage appliance.

Claims

1. A method for processing write requests comprising:

receiving, by a hub tier switch in a fabric from a first client, a first write request comprising a first data and a multicast address, wherein the hub tier switch is associated with the multicast address;

transmitting, by the hub tier switch and in response to the first write request, a second write request to a first storage module and a third write request to a second storage module;

receiving, by the hub tier switch from a second client, a fourth write request comprising a second data and the multicast address;

transmitting, by the hub tier switch and in response to the fourth write request, a fifth write request to the first storage module and a sixth write request to the second storage module;

receiving, by the hub tier switch, a first commit request originating from the first client and a second commit request originating from the second client, wherein the first commit request and the second commit request each comprise the multicast address, wherein the first commit request is associated with the first write request and the second commit request is associated with the fourth write request;

transmitting, by the hub tier switch to the first storage module, a third commit request associated with the first commit request and a fourth commit request associated with the second commit request;

transmitting, by the hub tier switch to the second storage module, a fifth commit request associated with the first commit request and a sixth commit request associated with the second commit request;

processing, by the first storage module, the third commit request and the fourth commit request, wherein the third commit request is processed before the fourth commit request based on a first global submission queue, wherein the first global submission queue organizes each commit request into a first chronological sequence based on when each commit request was received by the first storage module; and

processing, by the second storage module, the fifth commit request and the sixth commit request, wherein the fifth commit request is processed before the sixth commit request based on a second global submission queue, where the second global submission queue organizes each commit request into a second chronological sequence based on when each commit request was received by the second storage module.

2. The method of claim 1, further comprising:

receiving, after transmitting the third commit request, a first commit reply from the first storage module;

receiving, after transmitting fifth commit request, a second commit reply from the second storage module;

transmitting the first commit reply to the first client; and

transmitting the second commit reply to the first client.

3. The method of claim 1, wherein the fabric is a Peripheral Component Interconnect Express (PCIe) fabric.

4. The method of claim 1, wherein the first write request is received by a leaf tier switch in the fabric and transmitted, based on the multicast address, to the hub tier switch.

5. The method of claim 1, wherein the first storage module comprises phase change storage media.

6. The method of claim 1, wherein the third commit request is associated with a first client identifier specifying the first client and the fourth commit request is associated with a second client identifier specifying the second client.

7. The method of claim 1, wherein processing the third commit request and the fourth commit request comprises:

storing the third commit request in a first client submission queue associated with first client and storing the fourth commit request in a second client submission queue associated with the second client,

wherein the third commit request is associated with a first global sequencing tag and the fourth commit request is associated with a second global sequencing tag, and

wherein the first global sequencing tag and the second global sequencing tag are based on the first chronological sequence.

8. The method of claim 7,

wherein the third commit request and the fourth commit request are processed based on the first global sequencing tag and the second global sequencing tag,

wherein processing the third commit request comprises storing a copy of the first data in persistent storage in the first storage module.

9. A storage appliance, comprising:

a fabric;

a storage array operatively connected to the fabric and comprising a first storage module and a second storage module,

wherein the fabric is programmed to;

receive, by a hub tier switch in the fabric from a first client, a first write request comprising a first data and a multicast address, wherein the hub tier switch is associated with the multicast address;

transmit, by the hub tier switch and in response to the first write request, a second write request to the first storage module and a third write request to the second storage module;

receive, by the hub tier switch from a second client, a fourth write request comprising a second data and the multicast address;

transmit, by the hub tier switch and in response to the fourth write request, a fifth write request to the first storage module and a sixth write request to the second storage module;

receive, by the hub tier switch, a first commit request originating from the first client and a second commit request originating from the second client, wherein the first commit request and the second commit request each comprise the multicast address, wherein the first commit request is associated with the first write request and the second commit request is associated with the fourth write request;

transmit, by the hub tier switch to the first storage module, a third commit request associated with the first commit request and a fourth commit request associated with the second commit request;

transmit, by the hub tier switch to the second storage module, a fifth commit request associated with the first commit request and a sixth commit request associated with the second commit request;

wherein the first storage module is configured to process the third commit request and the fourth commit request, wherein the third commit request is processed before the fourth commit request based on a first global submission queue, wherein the first global submission queue that organizes each commit request into a first chronological sequence based on when each commit request was received by the first storage module; and

wherein the second storage module is configured to process the fifth commit request and the sixth commit request, wherein the fifth commit request is processed before the sixth commit request based on a second global submission queue, wherein the second global submission queue that organizes each commit request into a second chronological sequence based on when each commit request was received by the second storage module.

10. The storage appliance of claim 9,

wherein the first write request is received by a leaf tier switch in the fabric,

wherein the leaf tier switch transmits, based on the multicast address, the first write request to the hub tier switch.

11. The storage appliance of claim 9, wherein processing the third commit request and the fourth commit request comprises:

storing the third commit request in a first client submission queue associated with first client and storing the fourth commit request in a second client submission queue associated with the second client,

wherein the third commit request is associated with a first global sequencing tag and the fourth commit request is associated with a second global sequencing tag,

wherein the first global sequencing tag and the second global sequencing tag are based on the first chronological sequence,

wherein the third commit request and the fourth commit request are processed based on the first global sequencing tag and the second global sequencing tag,

wherein processing the third commit request comprises storing a copy of the first data in persistent storage in the first storage module.

12. The storage appliance of claim 9, wherein the fabric is a Peripheral Component Interconnect Express (PCIe) fabric.