ldlm_bl_callback.txt

   1 RPC 104: LDLM_BL_CALLBACK
   2 ~~~~~~~~~~~~~~~~~~~~~~~~~
   3 [[ldlm-bl-callback-rpc]]
   4
   5 An RPC that assists with getting a lock back from an entity that has
   6 it.
   7
   8 .LDLM_BL_CALLBACK Request Packet Structure
   9 image::ldlm-bl-callback-request.png["LDLM_BL_CALLBACK Request Packet Structure",height=50]
  10
  11 //////////////////////////////////////////////////////////////////////
  12 The ldlm-bl-callback-request.png diagram resembles this text
  13 art:
  14
  15        LDLM_BL_CALLBACK:
  16       --request---------------------
  17       | ptlrpc_body | ldlm_request |
  18       ------------------------------
  19 //////////////////////////////////////////////////////////////////////
  20
  21 The request RPC resembles the simplest LDLM_ENQUEUE RPC, but only
  22 identifies the relevant resource that the destination entity already
  23 had a lock on. It notifies the recipient that the lock should be
  24 returned once and dirty write data has been flushed.
  25
  26 'ptlrpc_body'::
  27 RPC descriptor. <<struct-ptlrpc-body>>
  28
  29 'ldlm_request'::
  30 Description of the lock being requested. Which resource is the target,
  31 what lock is current, and what lock desired. <<struct-ldlm-request>>
  32
  33 .LDLM_BL_CALLBACK Reply Packet Structure
  34 image::ldlm-bl-callback-reply.png["LDLM_BL_CALLBACK Reply Packet Structure",height=50]
  35
  36 //////////////////////////////////////////////////////////////////////
  37 The ldlm-bl-callback-reply.png diagram resembles this text
  38 art:
  39
  40        LDLM_BL_CALLBACK:
  41       --reply--------
  42       | ptlrpc_body |
  43       ---------------
  44 //////////////////////////////////////////////////////////////////////
  45
  46 The Reply is just an acknowledgment of receipt, and doesn't carry any
  47 further information about the lock or the resource.
  48
  49 'ptlrpc_body'::
  50 RPC descriptor. <<struct-ptlrpc-body>>
  51