1 RPC 104: LDLM_BL_CALLBACK
2 ~~~~~~~~~~~~~~~~~~~~~~~~~
3 [[ldlm-bl-callback-rpc]]
5 An RPC that assists with getting a lock back from an entity that has
8 .LDLM_BL_CALLBACK Request Packet Structure
9 image::ldlm-bl-callback-request.png["LDLM_BL_CALLBACK Request Packet Structure",height=50]
11 //////////////////////////////////////////////////////////////////////
12 The ldlm-bl-callback-request.png diagram resembles this text
16 --request---------------------
17 | ptlrpc_body | ldlm_request |
18 ------------------------------
19 //////////////////////////////////////////////////////////////////////
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.
27 RPC descriptor. <<struct-ptlrpc-body>>
30 Description of the lock being requested. Which resource is the target,
31 what lock is current, and what lock desired. <<struct-ldlm-request>>
33 .LDLM_BL_CALLBACK Reply Packet Structure
34 image::ldlm-bl-callback-reply.png["LDLM_BL_CALLBACK Reply Packet Structure",height=50]
36 //////////////////////////////////////////////////////////////////////
37 The ldlm-bl-callback-reply.png diagram resembles this text
44 //////////////////////////////////////////////////////////////////////
46 The Reply is just an acknowledgment of receipt, and doesn't carry any
47 further information about the lock or the resource.
50 RPC descriptor. <<struct-ptlrpc-body>>