LUDOC-298 protocl: Editorial pass through the document.

[doc/protocol.git] / ldlm_cancel.txt

diff --git a/ldlm_cancel.txt b/ldlm_cancel.txt
index 80b186f..6830bb7 100644 (file)
--- a/ldlm_cancel.txt
+++ b/ldlm_cancel.txt
@@ -4,20 +4,17 @@ RPC 103: LDLM_CANCEL
 
 An RPC that notifies an entity that a requested lock is no longer needed.
 
-.LDLM_CANCEL Generic Packet Structure
-image::ldlm-cancel-generic.png["LDLM_CANCEL Generic Packet Structure",height=100]
+.LDLM_CANCEL Request Packet Structure
+image::ldlm-cancel-request.png["LDLM_CANCEL Request Packet Structure",height=50]
 
 //////////////////////////////////////////////////////////////////////
-The ldlm-cancel-generic.png diagram resembles this text
+The ldlm-cancel-request.png diagram resembles this text
 art:
 
        LDLM_CANCEL:
       --request---------------------
       | ptlrpc_body | ldlm_request |
       ------------------------------
-      --reply--------
-      | ptlrpc_body |
-      ---------------
 //////////////////////////////////////////////////////////////////////
 
 'ptlrpc_body'::
@@ -28,3 +25,18 @@ The request RPC identifies the lock being canceled. Only the first
 'lock_handle' field is used. The rest of the 'ldlm_request' sturcture
 is not used. <<struct-ldlm-request>>
 
+.LDLM_CANCEL Reply Packet Structure
+image::ldlm-cancel-reply.png["LDLM_CANCEL Reply Packet Structure",height=50]
+
+//////////////////////////////////////////////////////////////////////
+The ldlm-cancel-reply.png diagram resembles this text
+art:
+
+       LDLM_CANCEL:
+      --reply--------
+      | ptlrpc_body |
+      ---------------
+//////////////////////////////////////////////////////////////////////
+
+'ptlrpc_body'::
+RPC descriptor. <<struct-ptlrpc-body>>