RDMA Extensions for Enhanced Memory Placement
draft-talpey-rdma-commit-01

Document Type Active Internet-Draft (individual)
Last updated 2020-03-09
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
NFSv4 (provisionally)                                          T. Talpey
Internet-Draft                                                 Microsoft
Updates: 5040 7306 (if approved)                               T. Hurson
Intended status: Standards Track                                   Intel
Expires: September 10, 2020                                   G. Agarwal
                                                                 Marvell
                                                                  T. Reu
                                                                 Chelsio
                                                           March 9, 2020

             RDMA Extensions for Enhanced Memory Placement
                      draft-talpey-rdma-commit-01

Abstract

   This document specifies extensions to RDMA (Remote Direct Memory
   Access) protocols to provide capabilities in support of enhanced
   remotely-directed data placement on persistent memory-addressable
   devices.  The extensions include new operations supporting remote
   commitment to persistence of remotely-managed buffers, which can
   provide enhanced guarantees and improve performance for low-latency
   storage applications.  In addition to, and in support of these,
   extensions to local behaviors are described, which may be used to
   guide implementation, and to ease adoption.  This document updates
   RFC5040 (Remote Direct Memory Access Protocol (RDMAP)) and updates
   RFC7306 (RDMA Protocol Extensions).

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

Talpey, et al.         Expires September 10, 2020               [Page 1]
Internet-Draft               RDMA Push Mode                   March 2020

   This Internet-Draft will expire on September 10, 2020.

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Glossary  . . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Problem Statement . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Requirements for RDMA Flush . . . . . . . . . . . . . . .  10
       2.1.1.  Non-Requirements  . . . . . . . . . . . . . . . . . .  12
     2.2.  Requirements for Atomic Write . . . . . . . . . . . . . .  14
     2.3.  Requirements for RDMA Verify  . . . . . . . . . . . . . .  15
     2.4.  Local Semantics . . . . . . . . . . . . . . . . . . . . .  16
   3.  RDMA Protocol Extensions  . . . . . . . . . . . . . . . . . .  17
     3.1.  RDMAP Extensions  . . . . . . . . . . . . . . . . . . . .  17
       3.1.1.  RDMA Flush  . . . . . . . . . . . . . . . . . . . . .  20
       3.1.2.  RDMA Verify . . . . . . . . . . . . . . . . . . . . .  23
       3.1.3.  Atomic Write  . . . . . . . . . . . . . . . . . . . .  25
       3.1.4.  Discovery of RDMAP Extensions . . . . . . . . . . . .  27
     3.2.  Local Extensions  . . . . . . . . . . . . . . . . . . . .  28
       3.2.1.  Registration Semantics  . . . . . . . . . . . . . . .  28
       3.2.2.  Completion Semantics  . . . . . . . . . . . . . . . .  28
       3.2.3.  Platform Semantics  . . . . . . . . . . . . . . . . .  29
   4.  Ordering and Completions Table  . . . . . . . . . . . . . . .  29
   5.  Error Processing  . . . . . . . . . . . . . . . . . . . . . .  30
     5.1.  Errors Detected at the Local Peer . . . . . . . . . . . .  30
     5.2.  Errors Detected at the Remote Peer  . . . . . . . . . . .  31
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  31
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  31
   8.  To Be Added or Considered . . . . . . . . . . . . . . . . . .  32
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  33
Show full document text