LUDOC-296 protocol: Rearrange presentation to be more top-down

[doc/protocol.git] / struct_mdt_body.txt

diff --git a/mdt_body.txt b/struct_mdt_body.txt
similarity index 97%
rename from mdt_body.txt
rename to struct_mdt_body.txt
index ecce92d..78d9741 100644 (file)
--- a/mdt_body.txt
+++ b/struct_mdt_body.txt
@@ -5,6 +5,7 @@ MDT Body
 An 'mdt_body' structure conveys information about the metadata for a
 single resource, typically an MDT inode.
 
+[source,c]
 ----
 struct mdt_body {
        struct lu_fid mbo_fid1; /* OBD_MD_FLID */
@@ -47,8 +48,9 @@ struct mdt_body {
 For an operation that involves two resources both the 'mbo_fid1' and
 'mbo_fid2' fields will be filled in. If the 'mdt_body' is part of an
 RPC affecting or involving only a single resource then 'mbo_fid1' will
-designate that resource and 'mbo_fid2' will be cleared (see
-<<struct-lu-fid>>).
+designate that resource and 'mbo_fid2' will be cleared.
+
+include::struct_lu_fid.txt[]
 
 The 'mbo_handle' field indicates the identity of an open file related
 to the operation, if any. If there is no lock then it is just 0.
@@ -56,6 +58,7 @@ to the operation, if any. If there is no lock then it is just 0.
 The 'mbo_valid' field identifies which of the remaining fields are
 actually in force. The flags in 'mbo_valid' are:
 
+[source,c]
 ----
 #define OBD_MD_FLID        (0x00000001ULL)
 #define OBD_MD_FLATIME     (0x00000002ULL)