Lines Matching refs:message

54  managed through three locks: "token", "message", and "ack", together
55  with the Lock Value Block (LVB) of one of the "message" lock.
66  other nodes to acknowledge the message before proceeding.  Only one
67  message can be processed at a time.
80    RESYNCING message identifies a range of the devices that the
90    array. The slot-number of the device is included in the message.
108   3.2.2 message: The lock resource which carries the data to
111   3.2.3 ack: The resource, acquiring which means the message has been
124     sender get EX on "message"
127     "message":EX
130     Sender checks that it still needs to send a message. Messages
132     "token" may have made this message inappropriate or redundant.
135     sender down-convert "message" from EX to CW
137     [ wait until all receivers have *processed* the "message" ]
140                                      receiver get CR on "message"
142                                      receiver processes the message
145                                      receiver tries to get PR on "message"
148    "token":EX                     "message":CR              "message":CR
149    "message":CW
153     have processed message)
155     sender releases "message"
157                                receiver upconvert to PR on "message"
159                                receiver release "message"
214     2. Node 1 sends a NEWDISK message with uuid and slot number
256  It does *not* send a RESYNCING message.
262  send a RESYNCING message.  resync_start reports the whole
265  resync_finish() also sends a BITMAP_NEEDS_SYNC message which
274  message to all other nodes, otherwise metadata_update_cancel()
305  the array.  It causes a REMOVE message to be send to other nodes.
309  This sends a RE_ADD message to all other nodes and then