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

[doc/protocol.git] / mgs_disconnect.txt

diff --git a/mgs_disconnect.txt b/mgs_disconnect.txt
index 89e5174..5a5804e 100644 (file)
--- a/mgs_disconnect.txt
+++ b/mgs_disconnect.txt
@@ -2,15 +2,20 @@ RPC 251: MGS DISCONNECT - Disconnect client from an MGS
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 [[mgs-disconnect-rpc]]
 
-.MGS_DISCONNECT (251)
-[options="header"]
-|====
-| request | reply
-| empty   | empty
-|====
+.MGS_DISCONNECT Generic Packet Structure
+image::mgs-disconnect-generic.png["MGS_DISCONNECT Generic Packet Structure",height=100]
 
-N.B. The usual 'struct req_format' definition does not exist for
-MGS_DISCONNECT.
+//////////////////////////////////////////////////////////////////////
+The mgs-disconnect-generic.png diagram resembles this text art:
+
+       MGS_DISCONNECT:
+      --request------
+      | ptlrpc_body |
+      ---------------
+      --reply--------
+      | ptlrpc_body |
+      ---------------
+//////////////////////////////////////////////////////////////////////
 
 The information exchanged in a DISCONNECT message is only that normally
 conveyed in the RPC descriptor, as described in <<struct-ptlrpc-body>>.