Lines Matching full:may
31 * There are quite a few things that may happen to a drbd request
42 * It may be identified as a concurrent (write) request
45 * It may me handed over to the local disk subsystem.
46 * It may be completed by the local disk subsystem,
49 * it may be retried remotely.
51 * It may be queued for sending.
52 * It may be handed over to the network stack,
53 * which may fail.
54 * It may be acknowledged by the "peer" according to the wire_protocol in use.
55 * this may be a negative ack.
56 * It may receive a faked ack when the network connection is lost and the
58 * Sending may be canceled due to network connection loss.
60 * corresponding dirty bits in the resync-bitmap may be cleared or set,
143 * master_bio may already be completed and invalidated.
159 * when cleared, the master_bio may be completed.
160 * in (B,A) the request object may still linger on the transaction log
180 /* when set, the request may be freed (if RQ_NET_QUEUED is clear).
206 * We may use it as hint to send a P_UNPLUG_REMOTE */
298 * We still may or may not be inside some irqs disabled section