-----------
[[lustre-rpcs]]
-Lustre RPC operations are implemented as a pair of messages, a request
-and its reply. The 'pb_type' field is set to PTLRPC_MSG_REQUEST for
-requests initiating the operation, and normally PTLRPC_MSG_REPLY for
-replies unless the message encountered a fatal error before it could
-be processed, in which case it will contain PTLRPC_MSG_ERR.
-
-The type of operation requested is denoted by the 'pb_opc' op-code field
-of the RPC request. Note that as a general matter, the receipt by a
-client of the reply message only assures the client that the server
-has initiated the action, if any, but does not guarantee that any
-modification has been committed to persistent storage. See the
-discussion on <<transno,transaction numbers>> and <<recovery>> for
-how the client is given confirmation that a request has been completed.
+The Lustre protocol consists of a collection of remote procedure calls
+(RPCs) collectively known as PtlRPCs. Each Lustre RPC is an operation
+that consists of a pair of messages, a request and its reply. The
+'pb_type' field is set to PTLRPC_MSG_REQUEST for requests initiating
+the operation, and normally PTLRPC_MSG_REPLY for replies unless the
+message encountered a fatal error before it could be processed, in
+which case it will contain PTLRPC_MSG_ERR.
+
+The type of operation requested is denoted by the 'pb_opc' op-code
+field of the RPC request. Note that as a general matter, the receipt
+by a client of the reply message only assures the client that the
+server has initiated the action, if any, but does not guarantee that
+any modification has been committed to persistent storage. See the
+discussion in <<transno>> and <<recovery>> for how the client is given
+confirmation that a request has been completed.
include::ost_setattr.txt[]
git://git.whamcloud.com / doc / protocol.git / blobdiff