X-Git-Url: https://git.whamcloud.com/?a=blobdiff_plain;f=lustre_messages.txt;h=89188f65ed612a1bdc0f1bbee5b7a58859673d75;hb=98909ef668eddd5a1c9742f1ff1facab0e1fc2b7;hp=5c386518da530ca2ca6164e1af5e38ec290003f2;hpb=6dd994a279ba773b290b4efac52b5d91b8252248;p=doc%2Fprotocol.git

diff --git a/lustre_messages.txt b/lustre_messages.txt
index 5c38651..89188f6 100644
--- a/lustre_messages.txt
+++ b/lustre_messages.txt
@@ -4,14 +4,14 @@ Lustre Messages
 
 A Lustre message is a sequence of bytes. The message begins with a
 <<lustre-message-header,Lustre Message Header>> and has between one
-and nine subsequences called "buffers". Each buffer has a structure
+and nine sub-sequences called "buffers". Each buffer has a structure
 (the size and meaning of the bytes) that corresponds to the 'struct'
 entities in the <<data-structs,Data Structures and Defines Section>>
 Section. The header gives the number of buffers in its 'lm_buffcount'
 field. The first buffer in any message is always the
-<<lustre-message-preamble,Lustre Message Preamble>>. The operation
+<<struct-ptlrpc-body,Lustre RPC Descriptor>>. The operation
 code ('pb_opc' field) and the message type ('pb_type' field: request
-or reply?) in the preamble together specify the "format" of the
+or reply?) in the descriptor together specify the "format" of the
 message, where the format is the number and content of the remaining
 buffers. As a shorthand, it is useful to name each of these formats,
 and the following list gives all of the formats along with the number
@@ -47,7 +47,7 @@ ask for the creation of a log entry object.
 [options="header"]
 |====
 | structure    | meaning
-| ptlrpc_body  | message preamble
+| ptlrpc_body  | RPC descriptor
 | llogd_body   | LLog description
 | string       | The name of the desired log
 |====
@@ -74,7 +74,7 @@ An 'llogd_body_only' message replies with information about the log.
 [options="header"]
 |====
 | structure    | meaning
-| ptlrpc_body  | message preamble
+| ptlrpc_body  | RPC descriptor
 | llogd_body   | LLog description
 |====
 
@@ -100,7 +100,7 @@ the log.
 [options="header"]
 |====
 | structure     | meaning
-| ptlrpc_body   | message preamble
+| ptlrpc_body   | RPC descriptor
 | llog_log_hdr  | LLog log header info
 |====
 
@@ -126,7 +126,7 @@ next block of data from the log.
 [options="header"]
 |====
 | structure     | meaning
-| ptlrpc_body   | message preamble
+| ptlrpc_body   | RPC descriptor
 | llogd_body    | LLog description
 | eadata	| variable length field for extended attributes
 |====
@@ -152,7 +152,7 @@ with information about the Lustre capabilities of that MDT.
 [options="header"]
 |====
 | structure        | meaning
-| ptlrpc_body      | message preamble
+| ptlrpc_body      | RPC descriptor
 | mdt_body	   | Information about the MDT
 | MDT_MD	   | OST stripe and index info
 | ACL		   | ACLs for the fid
@@ -185,7 +185,7 @@ with information about the Lustre capabilities of that MDT.
 [options="header"]
 |====
 | structure        | meaning
-| ptlrpc_body      | message preamble
+| ptlrpc_body      | RPC descriptor
 | mdt_body	   | Information about the MDT
 | lustre_capa	   | security capa info
 |====
@@ -214,7 +214,7 @@ An 'mdt_body_only' message format is used to convey MDT data.
 [options="header"]
 |====
 | structure        | meaning
-| ptlrpc_body      | message preamble
+| ptlrpc_body      | RPC descriptor
 | mdt_body	   | Information about the MDT
 |====
 
@@ -242,7 +242,7 @@ the MGS.
 [options="header"]
 |====
 | structure        | meaning
-| ptlrpc_body      | message preamble
+| ptlrpc_body      | RPC descriptor
 | mgs_config_body  | Information about the MGS supporting the request
 |====
 
@@ -267,7 +267,7 @@ the MGS.
 [options="header"]
 |====
 | structure        | meaning
-| ptlrpc_body      | message preamble
+| ptlrpc_body      | RPC descriptor
 | mgs_config_body  | Information about the MGS supporting the request
 |====
 
@@ -298,7 +298,7 @@ the obd_connect_server message.
 [options="header"]
 |====
 | structure        | meaning
-| ptlrpc_body      | message preamble
+| ptlrpc_body      | RPC descriptor
 | obd_uuid         | UUID of the target
 | obd_uuid         | UUID of the client
 | lustre_handle    | connection handle
@@ -336,7 +336,7 @@ that server. MGSs, MDSs, and OSSs send these replies.
 [options="header"]
 |====
 | structure        | meaning
-| ptlrpc_body      | message preamble
+| ptlrpc_body      | RPC descriptor
 | obd_connect_data | connection data
 |====
 
@@ -363,7 +363,7 @@ information to the client.
 [options="header"]
 |====
 | structure        | meaning
-| ptlrpc_body      | message preamble
+| ptlrpc_body      | RPC descriptor
 | obd_statfs	   | statfs system call info
 |====