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

[doc/protocol.git] / mds_getstatus.txt

diff --git a/mds_getstatus.txt b/mds_getstatus.txt
index 82f6fd5..43a31d7 100644 (file)
--- a/mds_getstatus.txt
+++ b/mds_getstatus.txt
@@ -2,20 +2,32 @@ RPC 40: MDS GETSTATUS - get the status from a target
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 [[mds-getstatus-rpc]]
 
-The MDS_GETSTATUS request is used to determine the filesystem ROOT FID
-during initial mount.  It is always sent to MDT0000 initially.
+.MDS_GETSTATUS Generic Packet Structure
+image::mds-getstatus-generic.png["MDS_GETSTATUS Generic Packet Structure",height=100]
 
-.MDS_GETSTATUS (40)
-[options="header"]
-|====
-| request  | reply
-| mdt_body | mdt_body
-|====
+//////////////////////////////////////////////////////////////////////
+The mds-getstatus-generic.png diagram resembles this text art:
 
-The request message 'mdt_body' is normally empty.
+       MDS_GETSTATUS:
+      --request-----------------
+      | ptlrpc_body | mdt_body |
+      --------------------------
+      --reply-------------------
+      | ptlrpc_body | mdt_body |
+      --------------------------
+//////////////////////////////////////////////////////////////////////
 
-The reply message 'mdt_body' contains only the FID of the filesystem
-ROOT in 'mbo_fid1'.  The client can then use the returned FID to
-fetch inode attributes for the root inode of the local mountpoint.
+'ptlrpc_body'::
+RPC descriptor. See <<struct-ptlrpc_body>>.
+
+'mdt_body'::
+See <<struct-mdt-body>>.
+
+In the request message, the 'mdt_body' is normally empty.
+
+In the reply message, the 'mdt_body' contains only the FID of the
+filesystem ROOT in 'mbo_fid1'.  The client can then use the returned
+FID to fetch inode attributes for the root inode of the local
+mountpoint.