| 1 |
|
| 2 | #ifndef _RAID5_H
|
| 3 | #define _RAID5_H
|
| 4 |
|
| 5 | #include <linux/raid/xor.h>
|
| 6 | #include <linux/dmaengine.h>
|
| 7 | #include <linux/local_lock.h>
|
| 8 |
|
| 9 | |
| 10 | *
|
| 11 | * Each stripe contains one buffer per device. Each buffer can be in
|
| 12 | * one of a number of states stored in "flags". Changes between
|
| 13 | * these states happen *almost* exclusively under the protection of the
|
| 14 | * STRIPE_ACTIVE flag. Some very specific changes can happen in bi_end_io, and
|
| 15 | * these are not protected by STRIPE_ACTIVE.
|
| 16 | *
|
| 17 | * The flag bits that are used to represent these states are:
|
| 18 | * R5_UPTODATE and R5_LOCKED
|
| 19 | *
|
| 20 | * State Empty == !UPTODATE, !LOCK
|
| 21 | * We have no data, and there is no active request
|
| 22 | * State Want == !UPTODATE, LOCK
|
| 23 | * A read request is being submitted for this block
|
| 24 | * State Dirty == UPTODATE, LOCK
|
| 25 | * Some new data is in this buffer, and it is being written out
|
| 26 | * State Clean == UPTODATE, !LOCK
|
| 27 | * We have valid data which is the same as on disc
|
| 28 | *
|
| 29 | * The possible state transitions are:
|
| 30 | *
|
| 31 | * Empty -> Want - on read or write to get old data for parity calc
|
| 32 | * Empty -> Dirty - on compute_parity to satisfy write/sync request.
|
| 33 | * Empty -> Clean - on compute_block when computing a block for failed drive
|
| 34 | * Want -> Empty - on failed read
|
| 35 | * Want -> Clean - on successful completion of read request
|
| 36 | * Dirty -> Clean - on successful completion of write request
|
| 37 | * Dirty -> Clean - on failed write
|
| 38 | * Clean -> Dirty - on compute_parity to satisfy write/sync (RECONSTRUCT or RMW)
|
| 39 | *
|
| 40 | * The Want->Empty, Want->Clean, Dirty->Clean, transitions
|
| 41 | * all happen in end_io at interrupt time.
|
| 42 | * Each sets the Uptodate bit before releasing the Lock bit.
|
| 43 | * This leaves one multi-stage transition:
|
| 44 | * Want->Dirty->Clean
|
| 45 | * This is safe because thinking that a Clean buffer is actually dirty
|
| 46 | * will at worst delay some action, and the stripe will be scheduled
|
| 47 | * for attention after the transition is complete.
|
| 48 | *
|
| 49 | * There is one possibility that is not covered by these states. That
|
| 50 | * is if one drive has failed and there is a spare being rebuilt. We
|
| 51 | * can't distinguish between a clean block that has been generated
|
| 52 | * from parity calculations, and a clean block that has been
|
| 53 | * successfully written to the spare ( or to parity when resyncing).
|
| 54 | * To distinguish these states we have a stripe bit STRIPE_INSYNC that
|
| 55 | * is set whenever a write is scheduled to the spare, or to the parity
|
| 56 | * disc if there is no spare. A sync request clears this bit, and
|
| 57 | * when we find it set with no buffers locked, we know the sync is
|
| 58 | * complete.
|
| 59 | *
|
| 60 | * Buffers for the md device that arrive via make_request are attached
|
| 61 | * to the appropriate stripe in one of two lists linked on b_reqnext.
|
| 62 | * One list (bh_read) for read requests, one (bh_write) for write.
|
| 63 | * There should never be more than one buffer on the two lists
|
| 64 | * together, but we are not guaranteed of that so we allow for more.
|
| 65 | *
|
| 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 end_io
|
| 68 | * routine is called. This may happen in the end_request routine only
|
| 69 | * if the buffer has just successfully been read. end_request should
|
| 70 | * remove the buffers from the list and then set the Uptodate bit on
|
| 71 | * the buffer. Other threads may do this only if they first check
|
| 72 | * that the Uptodate bit is set. Once they have checked that they may
|
| 73 | * take buffers off the read queue.
|
| 74 | *
|
| 75 | * When a buffer on the write list is committed for write it is copied
|
| 76 | * into the cache buffer, which is then marked dirty, and moved onto a
|
| 77 | * third list, the written list (bh_written). Once both the parity
|
| 78 | * block and the cached buffer are successfully written, any buffer on
|
| 79 | * a written list can be returned with end_io.
|
| 80 | *
|
| 81 | * The write list and read list both act as fifos. The read list,
|
| 82 | * write list and written list are protected by the device_lock.
|
| 83 | * The device_lock is only for list manipulations and will only be
|
| 84 | * held for a very short time. It can be claimed from interrupts.
|
| 85 | *
|
| 86 | *
|
| 87 | * Stripes in the stripe cache can be on one of two lists (or on
|
| 88 | * neither). The "inactive_list" contains stripes which are not
|
| 89 | * currently being used for any request. They can freely be reused
|
| 90 | * for another stripe. The "handle_list" contains stripes that need
|
| 91 | * to be handled in some way. Both of these are fifo queues. Each
|
| 92 | * stripe is also (potentially) linked to a hash bucket in the hash
|
| 93 | * table so that it can be found by sector number. Stripes that are
|
| 94 | * not hashed must be on the inactive_list, and will normally be at
|
| 95 | * the front. All stripes start life this way.
|
| 96 | *
|
| 97 | * The inactive_list, handle_list and hash bucket lists are all protected by the
|
| 98 | * device_lock.
|
| 99 | * - stripes have a reference counter. If count==0, they are on a list.
|
| 100 | * - If a stripe might need handling, STRIPE_HANDLE is set.
|
| 101 | * - When refcount reaches zero, then if STRIPE_HANDLE it is put on
|
| 102 | * handle_list else inactive_list
|
| 103 | *
|
| 104 | * This, combined with the fact that STRIPE_HANDLE is only ever
|
| 105 | * cleared while a stripe has a non-zero count means that if the
|
| 106 | * refcount is 0 and STRIPE_HANDLE is set, then it is on the
|
| 107 | * handle_list and if recount is 0 and STRIPE_HANDLE is not set, then
|
| 108 | * the stripe is on inactive_list.
|
| 109 | *
|
| 110 | * The possible transitions are:
|
| 111 | * activate an unhashed/inactive stripe (get_active_stripe())
|
| 112 | * lockdev check-hash unlink-stripe cnt++ clean-stripe hash-stripe unlockdev
|
| 113 | * activate a hashed, possibly active stripe (get_active_stripe())
|
| 114 | * lockdev check-hash if(!cnt++)unlink-stripe unlockdev
|
| 115 | * attach a request to an active stripe (add_stripe_bh())
|
| 116 | * lockdev attach-buffer unlockdev
|
| 117 | * handle a stripe (handle_stripe())
|
| 118 | * setSTRIPE_ACTIVE, clrSTRIPE_HANDLE ...
|
| 119 | * (lockdev check-buffers unlockdev) ..
|
| 120 | * change-state ..
|
| 121 | * record io/ops needed clearSTRIPE_ACTIVE schedule io/ops
|
| 122 | * release an active stripe (release_stripe())
|
| 123 | * lockdev if (!--cnt) { if STRIPE_HANDLE, add to handle_list else add to inactive-list } unlockdev
|
| 124 | *
|
| 125 | * The refcount counts each thread that have activated the stripe,
|
| 126 | * plus raid5d if it is handling it, plus one for each active request
|
| 127 | * on a cached buffer, and plus one if the stripe is undergoing stripe
|
| 128 | * operations.
|
| 129 | *
|
| 130 | * The stripe operations are:
|
| 131 | * -copying data between the stripe cache and user application buffers
|
| 132 | * -computing blocks to save a disk access, or to recover a missing block
|
| 133 | * -updating the parity on a write operation (reconstruct write and
|
| 134 | * read-modify-write)
|
| 135 | * -checking parity correctness
|
| 136 | * -running i/o to disk
|
| 137 | * These operations are carried out by raid5_run_ops which uses the async_tx
|
| 138 | * api to (optionally) offload operations to dedicated hardware engines.
|
| 139 | * When requesting an operation handle_stripe sets the pending bit for the
|
| 140 | * operation and increments the count. raid5_run_ops is then run whenever
|
| 141 | * the count is non-zero.
|
| 142 | * There are some critical dependencies between the operations that prevent some
|
| 143 | * from being requested while another is in flight.
|
| 144 | * 1/ Parity check operations destroy the in cache version of the parity block,
|
| 145 | * so we prevent parity dependent operations like writes and compute_blocks
|
| 146 | * from starting while a check is in progress. Some dma engines can perform
|
| 147 | * the check without damaging the parity block, in these cases the parity
|
| 148 | * block is re-marked up to date (assuming the check was successful) and is
|
| 149 | * not re-read from disk.
|
| 150 | * 2/ When a write operation is requested we immediately lock the affected
|
| 151 | * blocks, and mark them as not up to date. This causes new read requests
|
| 152 | * to be held off, as well as parity checks and compute block operations.
|
| 153 | * 3/ Once a compute block operation has been requested handle_stripe treats
|
| 154 | * that block as if it is up to date. raid5_run_ops guaruntees that any
|
| 155 | * operation that is dependent on the compute block result is initiated after
|
| 156 | * the compute block completes.
|
| 157 |
|
| 158 |
|
| 159 | |
| 160 | * Operations state - intermediate states that are visible outside of
|
| 161 | * STRIPE_ACTIVE.
|
| 162 | * In general _idle indicates nothing is running, _run indicates a data
|
| 163 | * processing operation is active, and _result means the data processing result
|
| 164 | * is stable and can be acted upon. For simple operations like biofill and
|
| 165 | * compute that only have an _idle and _run state they are indicated with
|
| 166 | * sh->state flags (STRIPE_BIOFILL_RUN and STRIPE_COMPUTE_RUN)
|
| 167 |
|
| 168 | |
| 169 | * enum check_states - handles syncing / repairing a stripe
|
| 170 | * @check_state_idle - check operations are quiesced
|
| 171 | * @check_state_run - check operation is running
|
| 172 | * @check_state_result - set outside lock when check result is valid
|
| 173 | * @check_state_compute_run - check failed and we are repairing
|
| 174 | * @check_state_compute_result - set outside lock when compute result is valid
|
| 175 |
|
| 176 | enum check_states {
|
| 177 | check_state_idle = 0,
|
| 178 | check_state_run,
|
| 179 | check_state_run_q,
|
| 180 | check_state_run_pq,
|
| 181 | check_state_check_result,
|
| 182 | check_state_compute_run,
|
| 183 | check_state_compute_result,
|
| 184 | };
|
| 185 |
|
| 186 | |
| 187 | * enum reconstruct_states - handles writing or expanding a stripe
|
| 188 |
|
| 189 | enum reconstruct_states {
|
| 190 | reconstruct_state_idle = 0,
|
| 191 | reconstruct_state_prexor_drain_run,
|
| 192 | reconstruct_state_drain_run,
|
| 193 | reconstruct_state_run,
|
| 194 | reconstruct_state_prexor_drain_result,
|
| 195 | reconstruct_state_drain_result,
|
| 196 | reconstruct_state_result,
|
| 197 | };
|
| 198 |
|
| 199 | #define DEFAULT_STRIPE_SIZE 4096
|
| 200 | struct stripe_head {
|
| 201 | struct hlist_node hash;
|
| 202 | struct list_head lru;
|
| 203 | struct llist_node release_list;
|
| 204 | struct r5conf *raid_conf;
|
| 205 | short generation; |
| 206 | * reshape
|
| 207 | sector_t sector;
|
| 208 | short pd_idx;
|
| 209 | short qd_idx;
|
| 210 | short ddf_layout;
|
| 211 | short hash_lock_index;
|
| 212 | unsigned long state;
|
| 213 | atomic_t count;
|
| 214 | int bm_seq;
|
| 215 | int disks;
|
| 216 | int overwrite_disks; |
| 217 | * this is only checked when stripe
|
| 218 | * has STRIPE_BATCH_READY
|
| 219 |
|
| 220 | enum check_states check_state;
|
| 221 | enum reconstruct_states reconstruct_state;
|
| 222 | spinlock_t stripe_lock;
|
| 223 | int cpu;
|
| 224 | struct r5worker_group *group;
|
| 225 |
|
| 226 | struct stripe_head *batch_head;
|
| 227 | spinlock_t batch_lock;
|
| 228 | struct list_head batch_list;
|
| 229 |
|
| 230 | union {
|
| 231 | struct r5l_io_unit *log_io;
|
| 232 | struct ppl_io_unit *ppl_io;
|
| 233 | };
|
| 234 |
|
| 235 | struct list_head log_list;
|
| 236 | sector_t log_start;
|
| 237 | struct list_head r5c;
|
| 238 |
|
| 239 | struct page *ppl_page;
|
| 240 | |
| 241 | * struct stripe_operations
|
| 242 | * @target - STRIPE_OP_COMPUTE_BLK target
|
| 243 | * @target2 - 2nd compute target in the raid6 case
|
| 244 | * @zero_sum_result - P and Q verification flags
|
| 245 | * @request - async service request flags for raid_run_ops
|
| 246 |
|
| 247 | struct stripe_operations {
|
| 248 | int target, target2;
|
| 249 | enum sum_check_flags zero_sum_result;
|
| 250 | } ops;
|
| 251 |
|
| 252 | #if PAGE_SIZE != DEFAULT_STRIPE_SIZE
|
| 253 |
|
| 254 | struct page **pages;
|
| 255 | int nr_pages;
|
| 256 | int stripes_per_page;
|
| 257 | #endif
|
| 258 | struct r5dev {
|
| 259 | |
| 260 | * writing data to both devices.
|
| 261 |
|
| 262 | struct bio req, rreq;
|
| 263 | struct bio_vec vec, rvec;
|
| 264 | struct page *page, *orig_page;
|
| 265 | unsigned int offset;
|
| 266 | struct bio *toread, *read, *towrite, *written;
|
| 267 | sector_t sector;
|
| 268 | unsigned long flags;
|
| 269 | u32 log_checksum;
|
| 270 | unsigned short write_hint;
|
| 271 | } dev[];
|
| 272 | };
|
| 273 |
|
| 274 | |
| 275 | * for handle_stripe.
|
| 276 |
|
| 277 | struct stripe_head_state {
|
| 278 | |
| 279 | * to check/correct parity, or to reconstruct a missing device.
|
| 280 | * 'replacing' means we are replacing one or more drives and
|
| 281 | * the source is valid at this point so we don't need to
|
| 282 | * read all devices, just the replacement targets.
|
| 283 |
|
| 284 | int syncing, expanding, expanded, replacing;
|
| 285 | int locked, uptodate, to_read, to_write, failed, written;
|
| 286 | int to_fill, compute, req_compute, non_overwrite;
|
| 287 | int injournal, just_cached;
|
| 288 | int failed_num[2];
|
| 289 | int p_failed, q_failed;
|
| 290 | int dec_preread_active;
|
| 291 | unsigned long ops_request;
|
| 292 |
|
| 293 | struct md_rdev *blocked_rdev;
|
| 294 | int handle_bad_blocks;
|
| 295 | int log_failed;
|
| 296 | int waiting_extra_page;
|
| 297 | };
|
| 298 |
|
| 299 |
|
| 300 | enum r5dev_flags {
|
| 301 | R5_UPTODATE,
|
| 302 | R5_LOCKED,
|
| 303 | R5_DOUBLE_LOCKED,
|
| 304 | R5_OVERWRITE,
|
| 305 |
|
| 306 | R5_Insync,
|
| 307 | R5_Wantread,
|
| 308 | R5_Wantwrite,
|
| 309 | R5_Overlap, |
| 310 | * on this block
|
| 311 | R5_ReadNoMerge,
|
| 312 | R5_ReadError,
|
| 313 | R5_ReWrite,
|
| 314 |
|
| 315 | R5_Expanded,
|
| 316 | R5_Wantcompute, |
| 317 | * uptodate
|
| 318 |
|
| 319 | R5_Wantfill, |
| 320 | * filling
|
| 321 |
|
| 322 | R5_Wantdrain,
|
| 323 | R5_WantFUA,
|
| 324 | R5_SyncIO,
|
| 325 | R5_WriteError,
|
| 326 | R5_MadeGood,
|
| 327 | R5_ReadRepl,
|
| 328 | R5_MadeGoodRepl, |
| 329 | * fixed by writing to it
|
| 330 | R5_NeedReplace, |
| 331 | * up-to-date at this stripe.
|
| 332 | R5_WantReplace, |
| 333 | * data in, and now is a good time to write it out.
|
| 334 |
|
| 335 | R5_Discard,
|
| 336 | R5_SkipCopy,
|
| 337 | R5_InJournal, |
| 338 | * if R5_InJournal is set for parity pd_idx, all the
|
| 339 | * data and parity being written are in the journal
|
| 340 | * device
|
| 341 |
|
| 342 | R5_OrigPageUPTDODATE, |
| 343 | * dev->orig_page for prexor. When this flag is
|
| 344 | * set, orig_page contains latest data in the
|
| 345 | * raid disk.
|
| 346 |
|
| 347 | };
|
| 348 |
|
| 349 | |
| 350 | * Stripe state
|
| 351 |
|
| 352 | enum {
|
| 353 | STRIPE_ACTIVE,
|
| 354 | STRIPE_HANDLE,
|
| 355 | STRIPE_SYNC_REQUESTED,
|
| 356 | STRIPE_SYNCING,
|
| 357 | STRIPE_INSYNC,
|
| 358 | STRIPE_REPLACED,
|
| 359 | STRIPE_PREREAD_ACTIVE,
|
| 360 | STRIPE_DELAYED,
|
| 361 | STRIPE_BIT_DELAY,
|
| 362 | STRIPE_EXPANDING,
|
| 363 | STRIPE_EXPAND_SOURCE,
|
| 364 | STRIPE_EXPAND_READY,
|
| 365 | STRIPE_IO_STARTED,
|
| 366 | STRIPE_FULL_WRITE,
|
| 367 | STRIPE_BIOFILL_RUN,
|
| 368 | STRIPE_COMPUTE_RUN,
|
| 369 | STRIPE_ON_UNPLUG_LIST,
|
| 370 | STRIPE_DISCARD,
|
| 371 | STRIPE_ON_RELEASE_LIST,
|
| 372 | STRIPE_BATCH_READY,
|
| 373 | STRIPE_BATCH_ERR,
|
| 374 | STRIPE_LOG_TRAPPED, |
| 375 | * this bit is used in two scenarios:
|
| 376 | *
|
| 377 | * 1. write-out phase
|
| 378 | * set in first entry of r5l_write_stripe
|
| 379 | * clear in second entry of r5l_write_stripe
|
| 380 | * used to bypass logic in handle_stripe
|
| 381 | *
|
| 382 | * 2. caching phase
|
| 383 | * set in r5c_try_caching_write()
|
| 384 | * clear when journal write is done
|
| 385 | * used to initiate r5c_cache_data()
|
| 386 | * also used to bypass logic in handle_stripe
|
| 387 |
|
| 388 | STRIPE_R5C_CACHING, |
| 389 | * see more detail in the raid5-cache.c
|
| 390 |
|
| 391 | STRIPE_R5C_PARTIAL_STRIPE, |
| 392 | * in conf->r5c_partial_stripe_list)
|
| 393 |
|
| 394 | STRIPE_R5C_FULL_STRIPE, |
| 395 | * in conf->r5c_full_stripe_list)
|
| 396 |
|
| 397 | STRIPE_R5C_PREFLUSH,
|
| 398 | };
|
| 399 |
|
| 400 | #define STRIPE_EXPAND_SYNC_FLAGS \
|
| 401 | ((1 << STRIPE_EXPAND_SOURCE) |\
|
| 402 | (1 << STRIPE_EXPAND_READY) |\
|
| 403 | (1 << STRIPE_EXPANDING) |\
|
| 404 | (1 << STRIPE_SYNC_REQUESTED))
|
| 405 | |
| 406 | * Operation request flags
|
| 407 |
|
| 408 | enum {
|
| 409 | STRIPE_OP_BIOFILL,
|
| 410 | STRIPE_OP_COMPUTE_BLK,
|
| 411 | STRIPE_OP_PREXOR,
|
| 412 | STRIPE_OP_BIODRAIN,
|
| 413 | STRIPE_OP_RECONSTRUCT,
|
| 414 | STRIPE_OP_CHECK,
|
| 415 | STRIPE_OP_PARTIAL_PARITY,
|
| 416 | };
|
| 417 |
|
| 418 | |
| 419 | * RAID parity calculation preferences
|
| 420 |
|
| 421 | enum {
|
| 422 | PARITY_DISABLE_RMW = 0,
|
| 423 | PARITY_ENABLE_RMW,
|
| 424 | PARITY_PREFER_RMW,
|
| 425 | };
|
| 426 |
|
| 427 | |
| 428 | * Pages requested from set_syndrome_sources()
|
| 429 |
|
| 430 | enum {
|
| 431 | SYNDROME_SRC_ALL,
|
| 432 | SYNDROME_SRC_WANT_DRAIN,
|
| 433 | SYNDROME_SRC_WRITTEN,
|
| 434 | };
|
| 435 | |
| 436 | * Plugging:
|
| 437 | *
|
| 438 | * To improve write throughput, we need to delay the handling of some
|
| 439 | * stripes until there has been a chance that several write requests
|
| 440 | * for the one stripe have all been collected.
|
| 441 | * In particular, any write request that would require pre-reading
|
| 442 | * is put on a "delayed" queue until there are no stripes currently
|
| 443 | * in a pre-read phase. Further, if the "delayed" queue is empty when
|
| 444 | * a stripe is put on it then we "plug" the queue and do not process it
|
| 445 | * until an unplug call is made. (the unplug_io_fn() is called).
|
| 446 | *
|
| 447 | * When preread is initiated on a stripe, we set PREREAD_ACTIVE and add
|
| 448 | * it to the count of prereading stripes.
|
| 449 | * When write is initiated, or the stripe refcnt == 0 (just in case) we
|
| 450 | * clear the PREREAD_ACTIVE flag and decrement the count
|
| 451 | * Whenever the 'handle' queue is empty and the device is not plugged, we
|
| 452 | * move any strips from delayed to handle and clear the DELAYED flag and set
|
| 453 | * PREREAD_ACTIVE.
|
| 454 | * In stripe_handle, if we find pre-reading is necessary, we do it if
|
| 455 | * PREREAD_ACTIVE is set, else we set DELAYED which will send it to the delayed queue.
|
| 456 | * HANDLE gets cleared if stripe_handle leaves nothing locked.
|
| 457 |
|
| 458 |
|
| 459 | |
| 460 | * There are three safe ways to access disk_info.rdev.
|
| 461 | * 1/ when holding mddev->reconfig_mutex
|
| 462 | * 2/ when resync/recovery/reshape is known to be happening - i.e. in code that
|
| 463 | * is called as part of performing resync/recovery/reshape.
|
| 464 | * 3/ while holding rcu_read_lock(), use rcu_dereference to get the pointer
|
| 465 | * and if it is non-NULL, increment rdev->nr_pending before dropping the RCU
|
| 466 | * lock.
|
| 467 | * When .rdev is set to NULL, the nr_pending count checked again and if
|
| 468 | * it has been incremented, the pointer is put back in .rdev.
|
| 469 |
|
| 470 |
|
| 471 | struct disk_info {
|
| 472 | struct md_rdev *rdev;
|
| 473 | struct md_rdev *replacement;
|
| 474 | struct page *extra_page;
|
| 475 | };
|
| 476 |
|
| 477 | |
| 478 | * Stripe cache
|
| 479 |
|
| 480 |
|
| 481 | #define NR_STRIPES 256
|
| 482 |
|
| 483 | #if PAGE_SIZE == DEFAULT_STRIPE_SIZE
|
| 484 | #define STRIPE_SIZE PAGE_SIZE
|
| 485 | #define STRIPE_SHIFT (PAGE_SHIFT - 9)
|
| 486 | #define STRIPE_SECTORS (STRIPE_SIZE>>9)
|
| 487 | #endif
|
| 488 |
|
| 489 | #define IO_THRESHOLD 1
|
| 490 | #define BYPASS_THRESHOLD 1
|
| 491 | #define NR_HASH (PAGE_SIZE / sizeof(struct hlist_head))
|
| 492 | #define HASH_MASK (NR_HASH - 1)
|
| 493 | #define MAX_STRIPE_BATCH 8
|
| 494 |
|
| 495 | |
| 496 | * This is because we sometimes take all the spinlocks
|
| 497 | * and creating that much locking depth can cause
|
| 498 | * problems.
|
| 499 |
|
| 500 | #define NR_STRIPE_HASH_LOCKS 8
|
| 501 | #define STRIPE_HASH_LOCKS_MASK (NR_STRIPE_HASH_LOCKS - 1)
|
| 502 |
|
| 503 | struct r5worker {
|
| 504 | struct work_struct work;
|
| 505 | struct r5worker_group *group;
|
| 506 | struct list_head temp_inactive_list[NR_STRIPE_HASH_LOCKS];
|
| 507 | bool working;
|
| 508 | };
|
| 509 |
|
| 510 | struct r5worker_group {
|
| 511 | struct list_head handle_list;
|
| 512 | struct list_head loprio_list;
|
| 513 | struct r5conf *conf;
|
| 514 | struct r5worker *workers;
|
| 515 | int stripes_cnt;
|
| 516 | };
|
| 517 |
|
| 518 | |
| 519 | * r5c journal modes of the array: write-back or write-through.
|
| 520 | * write-through mode has identical behavior as existing log only
|
| 521 | * implementation.
|
| 522 |
|
| 523 | enum r5c_journal_mode {
|
| 524 | R5C_JOURNAL_MODE_WRITE_THROUGH = 0,
|
| 525 | R5C_JOURNAL_MODE_WRITE_BACK = 1,
|
| 526 | };
|
| 527 |
|
| 528 | enum r5_cache_state {
|
| 529 | R5_INACTIVE_BLOCKED, |
| 530 | * waiting for 25% to be free
|
| 531 |
|
| 532 | R5_ALLOC_MORE, |
| 533 | * stripe.
|
| 534 |
|
| 535 | R5_DID_ALLOC, |
| 536 | * more until at least one has been
|
| 537 | * released. This avoids flooding
|
| 538 | * the cache.
|
| 539 |
|
| 540 | R5C_LOG_TIGHT, |
| 541 | * prioritize stripes at last_checkpoint
|
| 542 |
|
| 543 | R5C_LOG_CRITICAL, |
| 544 | * only process stripes that are already
|
| 545 | * occupying the log
|
| 546 |
|
| 547 | R5C_EXTRA_PAGE_IN_USE, |
| 548 | * for prexor
|
| 549 |
|
| 550 | };
|
| 551 |
|
| 552 | #define PENDING_IO_MAX 512
|
| 553 | #define PENDING_IO_ONE_FLUSH 128
|
| 554 | struct r5pending_data {
|
| 555 | struct list_head sibling;
|
| 556 | sector_t sector;
|
| 557 | struct bio_list bios;
|
| 558 | };
|
| 559 |
|
| 560 | struct raid5_percpu {
|
| 561 | struct page *spare_page;
|
| 562 | void *scribble; |
| 563 | * lists and performing address
|
| 564 | * conversions
|
| 565 |
|
| 566 | int scribble_obj_size;
|
| 567 | local_lock_t lock;
|
| 568 | };
|
| 569 |
|
| 570 | struct r5conf {
|
| 571 | struct hlist_head *stripe_hashtbl;
|
| 572 |
|
| 573 | spinlock_t hash_locks[NR_STRIPE_HASH_LOCKS];
|
| 574 | struct mddev *mddev;
|
| 575 | int chunk_sectors;
|
| 576 | int level, algorithm, rmw_level;
|
| 577 | int max_degraded;
|
| 578 | int raid_disks;
|
| 579 | int max_nr_stripes;
|
| 580 | int min_nr_stripes;
|
| 581 | #if PAGE_SIZE != DEFAULT_STRIPE_SIZE
|
| 582 | unsigned long stripe_size;
|
| 583 | unsigned int stripe_shift;
|
| 584 | unsigned long stripe_sectors;
|
| 585 | #endif
|
| 586 |
|
| 587 | |
| 588 | * It has value MaxSector when no reshape is happening
|
| 589 | * If delta_disks < 0, it is the last sector we started work on,
|
| 590 | * else is it the next sector to work on.
|
| 591 |
|
| 592 | sector_t reshape_progress;
|
| 593 | |
| 594 | * before (or after) this address, all reshape has completed.
|
| 595 |
|
| 596 | sector_t reshape_safe;
|
| 597 | int previous_raid_disks;
|
| 598 | int prev_chunk_sectors;
|
| 599 | int prev_algo;
|
| 600 | short generation;
|
| 601 | seqcount_spinlock_t gen_lock;
|
| 602 | unsigned long reshape_checkpoint; |
| 603 | * metadata
|
| 604 | long long min_offset_diff; |
| 605 | * data_offset and
|
| 606 | * new_data_offset across all
|
| 607 | * devices. May be negative,
|
| 608 | * but is closest to zero.
|
| 609 |
|
| 610 |
|
| 611 | struct list_head handle_list;
|
| 612 | struct list_head loprio_list;
|
| 613 | struct list_head hold_list;
|
| 614 | struct list_head delayed_list;
|
| 615 | struct list_head bitmap_list;
|
| 616 | struct bio *retry_read_aligned;
|
| 617 | unsigned int retry_read_offset;
|
| 618 | struct bio *retry_read_aligned_list;
|
| 619 | atomic_t preread_active_stripes;
|
| 620 | atomic_t active_aligned_reads;
|
| 621 | atomic_t pending_full_writes;
|
| 622 | int bypass_count;
|
| 623 | int bypass_threshold;
|
| 624 | int skip_copy;
|
| 625 | struct list_head *last_hold;
|
| 626 |
|
| 627 | atomic_t reshape_stripes;
|
| 628 | |
| 629 | * two caches.
|
| 630 |
|
| 631 | int active_name;
|
| 632 | char cache_name[2][48];
|
| 633 | struct kmem_cache *slab_cache;
|
| 634 | struct mutex cache_size_mutex;
|
| 635 |
|
| 636 | int seq_flush, seq_write;
|
| 637 | int quiesce;
|
| 638 |
|
| 639 | int fullsync; |
| 640 | * (fresh device added).
|
| 641 | * Cleared when a sync completes.
|
| 642 |
|
| 643 |
|
| 644 | struct raid5_percpu __percpu *percpu;
|
| 645 | int scribble_disks;
|
| 646 | int scribble_sectors;
|
| 647 | struct hlist_node node;
|
| 648 |
|
| 649 | |
| 650 | * Free stripes pool
|
| 651 |
|
| 652 | atomic_t active_stripes;
|
| 653 | struct list_head inactive_list[NR_STRIPE_HASH_LOCKS];
|
| 654 |
|
| 655 | atomic_t r5c_cached_full_stripes;
|
| 656 | struct list_head r5c_full_stripe_list;
|
| 657 | atomic_t r5c_cached_partial_stripes;
|
| 658 | struct list_head r5c_partial_stripe_list;
|
| 659 | atomic_t r5c_flushing_full_stripes;
|
| 660 | atomic_t r5c_flushing_partial_stripes;
|
| 661 |
|
| 662 | atomic_t empty_inactive_list_nr;
|
| 663 | struct llist_head released_stripes;
|
| 664 | wait_queue_head_t wait_for_quiescent;
|
| 665 | wait_queue_head_t wait_for_stripe;
|
| 666 | wait_queue_head_t wait_for_reshape;
|
| 667 | unsigned long cache_state;
|
| 668 | struct shrinker *shrinker;
|
| 669 | int pool_size;
|
| 670 | spinlock_t device_lock;
|
| 671 | struct disk_info *disks;
|
| 672 | struct bio_set bio_split;
|
| 673 |
|
| 674 | |
| 675 | * the new thread here until we fully activate the array.
|
| 676 |
|
| 677 | struct md_thread __rcu *thread;
|
| 678 | struct list_head temp_inactive_list[NR_STRIPE_HASH_LOCKS];
|
| 679 | struct r5worker_group *worker_groups;
|
| 680 | int group_cnt;
|
| 681 | int worker_cnt_per_group;
|
| 682 | struct r5l_log *log;
|
| 683 | void *log_private;
|
| 684 |
|
| 685 | spinlock_t pending_bios_lock;
|
| 686 | bool batch_bio_dispatch;
|
| 687 | struct r5pending_data *pending_data;
|
| 688 | struct list_head free_list;
|
| 689 | struct list_head pending_list;
|
| 690 | int pending_data_cnt;
|
| 691 | struct r5pending_data *next_pending_data;
|
| 692 | bool raid5_discard_unsupported;
|
| 693 |
|
| 694 | mempool_t *ctx_pool;
|
| 695 | int ctx_size;
|
| 696 | };
|
| 697 |
|
| 698 | #if PAGE_SIZE == DEFAULT_STRIPE_SIZE
|
| 699 | #define RAID5_STRIPE_SIZE(conf) STRIPE_SIZE
|
| 700 | #define RAID5_STRIPE_SHIFT(conf) STRIPE_SHIFT
|
| 701 | #define RAID5_STRIPE_SECTORS(conf) STRIPE_SECTORS
|
| 702 | #else
|
| 703 | #define RAID5_STRIPE_SIZE(conf) ((conf)->stripe_size)
|
| 704 | #define RAID5_STRIPE_SHIFT(conf) ((conf)->stripe_shift)
|
| 705 | #define RAID5_STRIPE_SECTORS(conf) ((conf)->stripe_sectors)
|
| 706 | #endif
|
| 707 |
|
| 708 | |
| 709 | * order without overlap. There may be several bio's per stripe+device, and
|
| 710 | * a bio could span several devices.
|
| 711 | * When walking this list for a particular stripe+device, we must never proceed
|
| 712 | * beyond a bio that extends past this device, as the next bio might no longer
|
| 713 | * be valid.
|
| 714 | * This function is used to determine the 'next' bio in the list, given the
|
| 715 | * sector of the current stripe+device
|
| 716 |
|
| 717 | static inline struct bio *r5_next_bio(struct r5conf *conf, struct bio *bio, sector_t sector)
|
| 718 | {
|
| 719 | if (bio_end_sector(bio) < sector + RAID5_STRIPE_SECTORS(conf))
|
| 720 | return bio->bi_next;
|
| 721 | else
|
| 722 | return NULL;
|
| 723 | }
|
| 724 |
|
| 725 | |
| 726 | * Our supported algorithms
|
| 727 |
|
| 728 | #define ALGORITHM_LEFT_ASYMMETRIC 0
|
| 729 | #define ALGORITHM_RIGHT_ASYMMETRIC 1
|
| 730 | #define ALGORITHM_LEFT_SYMMETRIC 2
|
| 731 | #define ALGORITHM_RIGHT_SYMMETRIC 3
|
| 732 |
|
| 733 | |
| 734 | * conversion of raid4 to raid5.
|
| 735 |
|
| 736 | #define ALGORITHM_PARITY_0 4
|
| 737 | #define ALGORITHM_PARITY_N 5
|
| 738 |
|
| 739 | |
| 740 | * Firstly, the exact positioning of the parity block is slightly
|
| 741 | * different between the 'LEFT_*' modes of md and the "_N_*" modes
|
| 742 | * of DDF.
|
| 743 | * Secondly, or order of datablocks over which the Q syndrome is computed
|
| 744 | * is different.
|
| 745 | * Consequently we have different layouts for DDF/raid6 than md/raid6.
|
| 746 | * These layouts are from the DDFv1.2 spec.
|
| 747 | * Interestingly DDFv1.2-Errata-A does not specify N_CONTINUE but
|
| 748 | * leaves RLQ=3 as 'Vendor Specific'
|
| 749 |
|
| 750 |
|
| 751 | #define ALGORITHM_ROTATING_ZERO_RESTART 8
|
| 752 | #define ALGORITHM_ROTATING_N_RESTART 9
|
| 753 | #define ALGORITHM_ROTATING_N_CONTINUE 10
|
| 754 |
|
| 755 | |
| 756 | * with exactly the same layout for data and parity, and
|
| 757 | * with the Q block always on the last device (N-1).
|
| 758 | * This allows trivial conversion from RAID5 to RAID6
|
| 759 |
|
| 760 | #define ALGORITHM_LEFT_ASYMMETRIC_6 16
|
| 761 | #define ALGORITHM_RIGHT_ASYMMETRIC_6 17
|
| 762 | #define ALGORITHM_LEFT_SYMMETRIC_6 18
|
| 763 | #define ALGORITHM_RIGHT_SYMMETRIC_6 19
|
| 764 | #define ALGORITHM_PARITY_0_6 20
|
| 765 | #define ALGORITHM_PARITY_N_6 ALGORITHM_PARITY_N
|
| 766 |
|
| 767 | static inline int algorithm_valid_raid5(int layout)
|
| 768 | {
|
| 769 | return (layout >= 0) &&
|
| 770 | (layout <= 5);
|
| 771 | }
|
| 772 | static inline int algorithm_valid_raid6(int layout)
|
| 773 | {
|
| 774 | return (layout >= 0 && layout <= 5)
|
| 775 | ||
|
| 776 | (layout >= 8 && layout <= 10)
|
| 777 | ||
|
| 778 | (layout >= 16 && layout <= 20);
|
| 779 | }
|
| 780 |
|
| 781 | static inline int algorithm_is_DDF(int layout)
|
| 782 | {
|
| 783 | return layout >= 8 && layout <= 10;
|
| 784 | }
|
| 785 |
|
| 786 | #if PAGE_SIZE != DEFAULT_STRIPE_SIZE
|
| 787 | |
| 788 | * Return offset of the corresponding page for r5dev.
|
| 789 |
|
| 790 | static inline int raid5_get_page_offset(struct stripe_head *sh, int disk_idx)
|
| 791 | {
|
| 792 | return (disk_idx % sh->stripes_per_page) * RAID5_STRIPE_SIZE(sh->raid_conf);
|
| 793 | }
|
| 794 |
|
| 795 | |
| 796 | * Return corresponding page address for r5dev.
|
| 797 |
|
| 798 | static inline struct page *
|
| 799 | raid5_get_dev_page(struct stripe_head *sh, int disk_idx)
|
| 800 | {
|
| 801 | return sh->pages[disk_idx / sh->stripes_per_page];
|
| 802 | }
|
| 803 | #endif
|
| 804 |
|
| 805 | int raid5_set_cache_size(struct mddev *mddev, int size);
|
| 806 | sector_t raid5_compute_blocknr(struct stripe_head *sh, int i, int previous);
|
| 807 | void raid5_release_stripe(struct stripe_head *sh);
|
| 808 | sector_t raid5_compute_sector(struct r5conf *conf, sector_t r_sector,
|
| 809 | int previous, int *dd_idx, struct stripe_head *sh);
|
| 810 |
|
| 811 | struct stripe_request_ctx;
|
| 812 |
|
| 813 | #define R5_GAS_PREVIOUS (1 << 0)
|
| 814 |
|
| 815 | #define R5_GAS_NOBLOCK (1 << 1)
|
| 816 |
|
| 817 | #define R5_GAS_NOQUIESCE (1 << 2)
|
| 818 | struct stripe_head *raid5_get_active_stripe(struct r5conf *conf,
|
| 819 | struct stripe_request_ctx *ctx, sector_t sector,
|
| 820 | unsigned int flags);
|
| 821 |
|
| 822 | int raid5_calc_degraded(struct r5conf *conf);
|
| 823 | int r5c_journal_mode_set(struct mddev *mddev, int journal_mode);
|
| 824 | #endif
|