lustre_rpcs.txt

   1 Lustre RPCs
   2 -----------
   3 [[lustre-rpcs]]
   4
   5 Lustre RPC operations are implemented as a pair of messages, a request
   6 and its reply.  The 'pb_type' field is set to PTLRPC_MSG_REQUEST for
   7 requests initiating the operation, and normally PTLRPC_MSG_REPLY for
   8 replies unless the message encountered a fatal error before it could
   9 be processed, in which case it will contain PTLRPC_MSG_ERR.
  10
  11 The type of operation requested is denoted by the 'pb_opc' op-code
  12 field of the RPC request. Note that as a general matter, the receipt
  13 by a client of the reply message only assures the client that the
  14 server has initiated the action, if any, but does not guarantee that
  15 any modification has been committed to persistent storage. See the
  16 discussion in <<transno>> and <<recovery>> for how the client is given
  17 confirmation that a request has been completed.
  18
  19 include::ost_setattr.txt[]
  20
  21 include::ost_connect.txt[]
  22
  23 include::ost_disconnect.txt[]
  24
  25 include::ost_punch.txt[]
  26
  27 include::ost_statfs.txt[]
  28
  29 include::mds_getattr.txt[]
  30
  31 include::mds_reint.txt[]
  32
  33 include::mds_connect.txt[]
  34
  35 include::mds_disconnect.txt[]
  36
  37 include::mds_getstatus.txt[]
  38
  39 include::mds_statfs.txt[]
  40
  41 include::mds_getxattr.txt[]
  42
  43 include::ldlm_enqueue.txt[]
  44
  45 include::ldlm_cancel.txt[]
  46
  47 include::ldlm_bl_callback.txt[]
  48
  49 include::ldlm_cp_callback.txt[]
  50
  51 include::ldlm_gl_callback.txt[]
  52
  53 include::mgs_connect.txt[]
  54
  55 include::mgs_disconnect.txt[]
  56
  57 include::mgs_config_read.txt[]
  58
  59 include::llog_origin_handle_create.txt[]
  60
  61 include::llog_origin_handle_next_block.txt[]
  62
  63 include::llog_origin_handle_read_header.txt[]
  64
  65 include::struct_lustre_msg.txt[]
  66