The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.

The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.

Date of Patent:
May. 09, 2023

Filed:

Oct. 25, 2021
Applicant:

Netapp, Inc., San Jose, CA (US);

Inventors:

Randolph Sterns, Boulder, CO (US);

Charles Binford, Wichita, KS (US);

Joseph Blount, Wichita, KS (US);

Joseph Moore, Wichita, KS (US);

William P. Delaney, Wichita, KS (US);

Assignee:

NETAPP, INC., San Jose, CA (US);

Attorneys:
Primary Examiner:
Int. Cl.
CPC ...
G06F 3/06 (2006.01); G06F 12/0868 (2016.01);
U.S. Cl.
CPC ...
G06F 3/0617 (2013.01); G06F 3/061 (2013.01); G06F 3/0665 (2013.01); G06F 3/0689 (2013.01); G06F 12/0868 (2013.01); G06F 2212/1024 (2013.01); G06F 2212/1032 (2013.01); G06F 2212/263 (2013.01); G06F 2212/282 (2013.01); G06F 2212/286 (2013.01); G06F 2212/312 (2013.01);
Abstract

A system shares I/O load between controllers in a high availability system. For writes, a controller determines based on one or more factors which controller will flush batches of data from write-back cache to better distribute the I/O burden. The determination occurs after the local storage controller caches the data, mirrors it, and confirms write complete to the host. Once it is determined which storage controller will flush the cache, the flush occurs and the corresponding metadata at a second layer of indirection is updated by that determined storage controller (whether or not it is identified as the owner of the corresponding volume to the host, while the volume owner updates metadata at a first layer of indirection). For a host read, the controller that owns the volume accesses the metadata from whichever controller(s) flushed the data previously and reads the data, regardless of which controller had performed the flush.


Find Patent Forward Citations

Loading…