Lines Matching defs:read
23 * A read request is being submitted for this block
31 * Empty -> Want - on read or write to get old data for parity calc
34 * Want -> Empty - on failed read
35 * Want -> Clean - on successful completion of read request
62 * One list (bh_read) for read requests, one (bh_write) for write.
66 * If a buffer is on the read list when the associated cache buffer is
67 * Uptodate, the data is copied into the read buffer and it's b_end_io
69 * if the buffer has just successfully been read. end_request should
73 * take buffers off the read queue.
81 * The write list and read list both act as fifos. The read list,
134 * read-modify-write)
149 * not re-read from disk.
151 * blocks, and mark them as not up to date. This causes new read requests
266 struct bio *toread, *read, *towrite, *written;
278 /* 'syncing' means that we need to read all devices, either
282 * read all devices, just the replacement targets.
307 R5_Wantread, /* want to schedule a read */
312 R5_ReadError, /* seen a read error here recently */
327 R5_ReadRepl, /* Will/did read from replacement rather than orig */
332 R5_WantReplace, /* We need to update the replacement, we have read
342 R5_OrigPageUPTDODATE, /* with write back cache, we read old data into
447 * in a pre-read phase. Further, if the "delayed" queue is empty when