'ptlrpc_body'::
RPC descriptor <<struct-ptlrpc-body>>.
-'ldlm_request'::
-Description of the lock being requested. Which resource is the target,
-what lock is current, and what lock desired. <<struct-ldlm-request>>
+include::struct_ldlm_request.txt[]
-'ldlm_intent'::
-Description of the intent being included with the lock request.
-<<struct-ldlm-intent>>
+include::struct_ldlm_intent.txt[]
-'layout_intent'::
-Description of the layout information that is the subject of a layout
-intent.
+include::struct_layout_intent.txt[]
'mdt_body'::
In a request, an indication (in the 'mbo_valid' field) of what
'name'::
A text field supplying the name of the desired resource.
-'ldlm_reply'::
-Resembling the 'ldlm_request', but in this case indicating what the
-LDLM actually granted as well as relevant policy data. <<struct-ldlm-reply>>
-
-'mdt_body'::
-Metadata about a given resource. <<struct-mdt-body>>
+include::struct_ldlm_reply.txt[]
'ACL data'::
Access Control List data associated with a resource.
to quotas (and not yet incorporated into this document). LDLM_ENQUEUE
reply RPCs may include a zero length instance of an LVB.
-'ost_lvb'::
-An LVB to communicate attribute data for an extent associated with a
-resource on a lock. It is returned from an OST to a client requesting
-an extent lock. <<struct-ost-lvb>>
-
-'lov_mds_md'::
-Layout data associated with a resource. It is
-returned from an MDT to a client requesting a lock a lock with a
-layout intent. In an intent request (as opposed to a reply and as yet
-unimplemanted) it will modify the layout. It will not be included
-(zero length) in requests in current releases. <<struct-lov-mds-md>>
+include::struct_ost_lvb.txt[]
+
+include::struct_lov_mds_md.txt[]
+