LUDOC-297 protocol: Update protocol document

[doc/protocol.git] / struct_mdt_rec_reint.txt

diff --git a/struct_mdt_rec_reint.txt b/struct_mdt_rec_reint.txt
index c9780f8..09c691a 100644 (file)
--- a/struct_mdt_rec_reint.txt
+++ b/struct_mdt_rec_reint.txt
@@ -42,6 +42,8 @@ struct mdt_rec_reint {
 The 'rr_opcode' field defines one among the several sub-commands for
 MDS REINT RPCs. Those opcodes are:
 
+.MDS Reint Type
+****
 [source,c]
 ----
 typedef enum {
@@ -54,6 +56,7 @@ typedef enum {
   REINT_SETXATTR = 7,
 } mds_reint_t;
 ----
+****
 
 Based on that opcode one of the variants of the structure will
 actually be used. See <<mds-reint-setattr-rpc>> for one example.
@@ -75,9 +78,9 @@ is for the REINT_SETATTR sub-operation.
 The 'rr_suppgid1' and 'rr_suppgid2' fields are supplementary GID
 information for kernels that have it.
 
-The 'rr_fid1' and 'rr_fid2' fields specify the file IDs for the
-resources being operated upon. If only one resource is being acted
-upon then 'rr_fid2' is not used.
+The 'rr_fid1' and 'rr_fid2' fields specify the FIDs (See
+<<struct-lu-fid>>) for the resources being operated upon. If only one
+resource is being acted upon then 'rr_fid2' is not used.
 
 The 'rr_mtime' 'rr_atime' and 'rr_ctime' fields give the object
 timestamps in seconds for the last modification time, the last
@@ -91,6 +94,8 @@ attribute.
 The 'rr_bias' field adds additional optional information to the
 REINT. The possible values are:
 
+.MDS Operation Bias
+****
 [source,c]
 ----
 enum mds_op_bias {
@@ -108,6 +113,7 @@ enum mds_op_bias {
        MDS_HSM_RELEASE         = 1 << 12,
 };
 ----
+****
 
 For example, MDS_DATA_MODIFIED signals to the HSM system that the MDT
 should set the corresponding HSM extended attribute. We'll return to