LUDOC-297 protocol: Update protocol document

[doc/protocol.git] / ldlm_cp_callback.txt

diff --git a/ldlm_cp_callback.txt b/ldlm_cp_callback.txt
index 071db0f..52c16c5 100644 (file)
--- a/ldlm_cp_callback.txt
+++ b/ldlm_cp_callback.txt
@@ -4,27 +4,23 @@ RPC 105: LDLM_CP_CALLBACK
 
 An RPC that notifies an entity that a requested lock is now available.
 
-.LDLM_CP_CALLBACK Generic Packet Structure
-image::ldlm-cp-callback-generic.png["LDLM_CP_CALLBACK Generic Packet Structure",height=100]
+.LDLM_CP_CALLBACK Request Packet Structure
+image::ldlm-cp-callback-request.png["LDLM_CP_CALLBACK Request Packet Structure",height=50]
 
 //////////////////////////////////////////////////////////////////////
-The ldlm-cp-callback-generic.png diagram resembles this text
+The ldlm-cp-callback-request.png diagram resembles this text
 art:
 
        LDLM_CP_CALLBACK:
       --request-------------------------------
       | ptlrpc_body | ldlm_request | ost_lvb |
       ----------------------------------------
-      --reply--------
-      | ptlrpc_body |
-      ---------------
 //////////////////////////////////////////////////////////////////////
 
 The request RPC identifies the relevant resource that already had a
 request pending. It notifies the original requester that it now has
 the stated lock, along with attribute information the about the
-resource. The reply is just an acknowledgment of receipt, and doesn't
-carry any further information about the lock or the resource.
+resource.
 
 'ptlrpc_body'::
 RPC descriptor <<struct-ptlrpc-body>>.
@@ -36,3 +32,22 @@ what lock is current, and what lock desired. <<struct-ldlm-request>>
 'ost_lvb'::
 Attribute data associated with a resource on an OST. <<struct-ost-lvb>>
 
+.LDLM_CP_CALLBACK Reply Packet Structure
+image::ldlm-cp-callback-reply.png["LDLM_CP_CALLBACK Reply Packet Structure",height=50]
+
+//////////////////////////////////////////////////////////////////////
+The ldlm-cp-callback-reply.png diagram resembles this text
+art:
+
+       LDLM_CP_CALLBACK:
+      --reply--------
+      | ptlrpc_body |
+      ---------------
+//////////////////////////////////////////////////////////////////////
+
+The reply is just an acknowledgment of receipt, and doesn't
+carry any further information about the lock or the resource.
+
+'ptlrpc_body'::
+RPC descriptor <<struct-ptlrpc-body>>.
+