One-sided reliable remote direct memory operations

Patent metadata

Field	Value
Publication number	US-11526462-B2
Application number	US-202017071164-A
Country	US
Kind code	B2
Filing date	Oct 15, 2020
Priority date	Aug 6, 2018
Publication date	Dec 13, 2022
Grant date	Dec 13, 2022

Abstract

Techniques are provided to allow more sophisticated operations to be performed remotely by machines that are not fully functional. Operations that can be performed reliably by a machine that has experienced a hardware and/or software error are referred to herein as Remote Direct Memory Operations or “RDMOs”. Unlike RDMAs, which typically involve trivially simple operations such as the retrieval of a single value from the memory of a remote machine, RDMOs may be arbitrarily complex. The techniques described herein can help applications run without interruption when there are software faults or glitches on a remote system with which they interact.

First claim

What is claimed is:

1. A method of attempting performance of an operation on a particular computing device, comprising:
concurrently executing, on the particular computing device that contains local volatile memory:
a first execution candidate, implemented in a first reliability domain on the particular computing device, capable of performing the operation,
a second execution candidate, implemented in a second reliability domain on the particular computing device, capable of performing the operation, and
a third execution candidate, implemented in a third reliability domain on the particular computing device, capable of performing the operation;

wherein the first, second and third reliability domains are distinct from each other;
wherein the operation requires access to data in the local volatile memory associated with the particular computing device;
based on one or more factors, selecting a target execution candidate, from among the first, second and third execution candidates; and
attempting performance of the operation using the target execution candidate.

2. The method of claim 1 , further comprising:
receiving a request to perform the operation, from a requesting entity executing on a second computing device that is remote relative to the particular computing device;
wherein said attempting performance of the operation using the target execution candidate is performed in response to receiving the request to perform the operation from the requesting entity.

3. The method of claim 1 , wherein said selecting the target execution candidate is performed by a requesting entity executing on a second computing device that is remote relative to the particular computing device.

4. The method of claim 1 , wherein said selecting the target execution candidate is performed at the particular computing device.

5. The method of claim 1 , wherein the target execution candidate is one of:
an application running on one or more processors of the particular computing device;
implemented in a network interface controller of the particular computing device;
implemented within an operating system executing on the particular computing device;
implemented within a privileged domain on the particular computing device;
executed on a first set of one or more cores of a processor in the particular computing device;
executed on a second set of one or more cores of the processor, wherein membership of the second set of one or more cores is different than membership of the first set of one or more cores; or
an interpreter that interprets instructions that, when interpreted, cause performance of the operation.

6. The method of claim 5 , wherein:
the target execution candidate is an interpreter that interprets instructions that, when interpreted, cause performance of the operation;
the interpreter is implemented on a network interface controller through which the particular computing device communicates over a network;
wherein the target execution candidate performs the operation by interpreting instructions specified in data provided to the network interface controller.

7. A method of attempting performance of an operation on a particular computing device, comprising:
concurrently executing, on the particular computing device that contains local volatile memory:
a first execution candidate, implemented in a first reliability domain on the particular computing device, capable of performing the operation, and
a second execution candidate, implemented in a second reliability domain on the particular computing device, capable of performing the operation;

wherein the first reliability domain includes a first set of one or more cores of a processor of the particular computing device;
wherein the second reliability domain includes a second set of one or more cores of the processor of the particular computing device;
wherein the first set of one or more cores is different than the second set of one or more cores;
wherein the operation requires access to data in the local volatile memory of the particular computing device;
selecting a target execution candidate, from among the first and second execution candidates; and
causing the target execution candidate to perform the operation.

8. The method of claim 7 wherein:
the first execution candidate supports a first set of operations;
the second execution candidate supports a second set of operations; and
the second set of operations is a proper subset of the first set of operations.

9. The method of claim 7 , further comprising:
receiving a request to perform the operation, from a requesting entity executing on a second computing device that is remote relative to the particular computing device;
wherein said attempting performance of the operation using the target execution candidate is performed in response to receiving the request to perform the operation from the requesting entity.

10. One or more non-transitory computer-readable media storing one or more sequences of instructions for attempting performance of an operation on a particular computing device, the one or more sequences of instructions comprising instructions that, when executed by one or more processors, cause:
concurrently executing, on the particular computing device that contains local volatile memory:
a first execution candidate, implemented in a first reliability domain on the particular computing device, capable of performing the operation,
a second execution candidate, implemented in a second reliability domain on the particular computing device, capable of performing the operation, and
a third execution candidate, implemented in a third reliability domain on the particular computing device, capable of performing the operation;

wherein the first, second and third reliability domains are distinct from each other;
wherein the operation requires access to data in the local volatile memory associated with the particular computing device;
based on one or more factors, selecting a target execution candidate, from among the first, second and third execution candidates; and
attempting performance of the operation using the target execution candidate.

11. The one or more non-transitory computer-readable media of claim 10 , wherein the one or more sequences of instructions further comprise instructions that, when executed by one or more processors, cause:
receiving a request to perform the operation, from a requesting entity executing on a second computing device that is remote relative to the particular computing device;
wherein said attempting performance of the operation using the target execution candidate is performed in response to receiving the request to perform the operation from the requesting entity.

12. The one or more non-transitory computer-readable media of claim 10 , wherein said selecting the target execution candidate is performed by a requesting entity executing on a second computing device that is remote relative to the particular computing device.

13. The one or more non-transitory computer-readable media of claim 10 , wherein said selecting the target execution candidate is performed at the particular computing device.

14. The one or more non-transitory computer-readable media of claim 10 , wherein the target execution candidate is one of:
an application running on one or more processors of the particular computing device;
implemented in a network interface controller of the particular computing device;
implemented within an operating system executing on the particular computing device;
implemented within a privileged domain on the particular computing device;
execu

Assignees

• Oracle Int Corp

Inventors

• Lahiri Tirthankar
• Loaiza Juan R
• Swart Garret F
• Kamp Jesse
• Pant Avneesh
• Kimura Hideaki

Classifications

• G06F11/2046

  where the redundant components share persistent storage (G06F11/2043 takes precedence) · CPC title

• G06F9/544

  Buffers; Shared memory; Pipes · CPC title

• G06F11/2023 Primary

  Failover techniques · CPC title

• G06F11/2025

  using centralised failover control functionality · CPC title

• G06F15/167 Primary

  using a common memory, e.g. mailbox · CPC title