Lines Matching full:message
57 2.2 Message passing locks
62 managed through three locks: "token", "message", and "ack", together
63 with the Lock Value Block (LVB) of one of the "message" lock.
76 other nodes to acknowledge the message before proceeding. Only one
77 message can be processed at a time.
79 3.1 Message Types
96 RESYNCING message identifies a range of the devices that the
105 the array. Message contains an identifier for that device. See
112 array. The slot-number of the device is included in the message.
137 3.2.2 message
144 The resource, acquiring which means the message has been
157 sender get EX on "message"::
161 "message":EX
164 Sender checks that it still needs to send a message. Messages
166 "token" may have made this message inappropriate or redundant.
170 sender down-convert "message" from EX to CW
176 [ wait until all receivers have *processed* the "message" ]
179 receiver get CR on "message"
181 receiver processes the message
184 receiver tries to get PR on "message"
187 "token":EX "message":CR "message":CR
188 "message":CW
192 have processed message)
196 sender releases "message"
202 receiver upconvert to PR on "message"
204 receiver release "message"
263 2. Node 1 sends a NEWDISK message with uuid and slot number
309 It does *not* send a RESYNCING message.
316 send a RESYNCING message. resync_start reports the whole
319 resync_finish() also sends a BITMAP_NEEDS_SYNC message which
328 message to all other nodes, otherwise metadata_update_cancel()
362 the array. It causes a REMOVE message to be send to other nodes.
367 This sends a RE_ADD message to all other nodes and then