LUDOC-276 protocol: Document RPCs for setattr

[doc/protocol.git] / lustre_messages.txt

diff --git a/lustre_messages.txt b/lustre_messages.txt
index ad3b858..5c38651 100644 (file)
--- a/lustre_messages.txt
+++ b/lustre_messages.txt
@@ -20,119 +20,11 @@ while the combination of 'pb_opc' and 'pb_type' uniquely determines a
 message's format, the reverse is not true. A given format may be used
 in many different messages.
 
-The "Empty" Message
-~~~~~~~~~~~~~~~~~~~
-
-'empty'
-^^^^^^^
-
-.example
-[options="header"]
-|====
-| pb_opc     | pb_type
-| MDS_STATFS | PTL_RPC_MSG_REQUEST
-|====
-
-
-An 'empty' message is one that consists only of the Lustre message
-preamble 'ptlrpc_body'. It occurs as either the request of the reply
-(or both) in a variety of Lustre operations.
-
-.format
-[options="header"]
-|====
-| structure        | meaning
-| ptlrpc_body      | message preamble
-|====
-
-The LDLM Enqueue Client Message
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-'ldlm_enqueue_client'
-^^^^^^^^^^^^^^^^^^^^^
-
-.example
-[options="header"]
-|====
-| pb_opc       | pb_type
-| LDLM_ENQUEUE | PTL_RPC_MSG_REQUEST
-|====
-
-
-An 'ldlm_enqueue_client' message format is used to acquire a lock.
-
-.format
-[options="header"]
-|====
-| structure        | meaning
-| ptlrpc_body      | message preamble
-| ldlm_request     | details of the lock request
-|====
-
-An 'ldlm_enqueue_client' message concatenates two data elements into a
-single byte-stream. The two elements correspond to structures
-detailed in the <<data-structs,Data Structures and Defines Section>>.
-
-The LDLM Enqueue Server Message
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-'ldlm_enqueue_server'
-^^^^^^^^^^^^^^^^^^^^^
-
-.example
-[options="header"]
-|====
-| pb_opc       | pb_type
-| LDLM_ENQUEUE | PTL_RPC_MSG_REPLY
-|====
-
-
-An 'ldlm_enqueue_server' message format is used to inform a client
-about the status of its request for a lock.
-
-.format
-[options="header"]
-|====
-| structure        | meaning
-| ptlrpc_body      | message preamble
-| ldlm_reply       | details of the lock request
-|====
-
-An 'ldlm_enqueue_server' message concatenates two data elements
-into a single byte-stream. The three elements correspond to structures
-detailed in the <<data-structs,Data Structures and Defines Section>>.
-
-The LDLM Enqueue Server Message with LVB
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-'ldlm_enqueue_lvb_server'
-^^^^^^^^^^^^^^^^^^^^^^^^^
-
-.example
-[options="header"]
-|====
-| pb_opc       | pb_type
-| LDLM_ENQUEUE | PTL_RPC_MSG_REPLY
-|====
-
-
-An 'ldlm_enqueue_lvb_server' message format is used to inform a client
-about the status of its request for a lock.
-
-.format
-[options="header"]
-|====
-| structure        | meaning
-| ptlrpc_body      | message preamble
-| ldlm_reply       | details of the lock request
-| ost_lvb          | lock value block
-|====
-
-An 'ldlm_enqueue_lvb_server' message concatenates three data elements
-into a single byte-stream. It closely resembles the
-'ldlm_enqueue_server' message with the addition of a lock value
-block. The three elements correspond to structures detailed in the
-<<data-structs,Data Structures and Defines Section>>.
+N.B. As each of the following "message formats" is introduced in the
+context of describing "Lustre commands", the corresponding section
+here will be deleted. These brief entries just state the name of the
+format and its structures. That information is better included in the
+section on the command itself. -ACU
 
 The LLog Origin Handle Create Client
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~