summaryrefslogtreecommitdiff
path: root/ANDROID_3.4.5/drivers/md/raid10.h
diff options
context:
space:
mode:
authorSrikant Patnaik2015-01-11 12:28:04 +0530
committerSrikant Patnaik2015-01-11 12:28:04 +0530
commit871480933a1c28f8a9fed4c4d34d06c439a7a422 (patch)
tree8718f573808810c2a1e8cb8fb6ac469093ca2784 /ANDROID_3.4.5/drivers/md/raid10.h
parent9d40ac5867b9aefe0722bc1f110b965ff294d30d (diff)
downloadFOSSEE-netbook-kernel-source-871480933a1c28f8a9fed4c4d34d06c439a7a422.tar.gz
FOSSEE-netbook-kernel-source-871480933a1c28f8a9fed4c4d34d06c439a7a422.tar.bz2
FOSSEE-netbook-kernel-source-871480933a1c28f8a9fed4c4d34d06c439a7a422.zip
Moved, renamed, and deleted files
The original directory structure was scattered and unorganized. Changes are basically to make it look like kernel structure.
Diffstat (limited to 'ANDROID_3.4.5/drivers/md/raid10.h')
-rw-r--r--ANDROID_3.4.5/drivers/md/raid10.h150
1 files changed, 0 insertions, 150 deletions
diff --git a/ANDROID_3.4.5/drivers/md/raid10.h b/ANDROID_3.4.5/drivers/md/raid10.h
deleted file mode 100644
index 7c615613..00000000
--- a/ANDROID_3.4.5/drivers/md/raid10.h
+++ /dev/null
@@ -1,150 +0,0 @@
-#ifndef _RAID10_H
-#define _RAID10_H
-
-struct mirror_info {
- struct md_rdev *rdev, *replacement;
- sector_t head_position;
- int recovery_disabled; /* matches
- * mddev->recovery_disabled
- * when we shouldn't try
- * recovering this device.
- */
-};
-
-struct r10conf {
- struct mddev *mddev;
- struct mirror_info *mirrors;
- int raid_disks;
- spinlock_t device_lock;
-
- /* geometry */
- int near_copies; /* number of copies laid out
- * raid0 style */
- int far_copies; /* number of copies laid out
- * at large strides across drives
- */
- int far_offset; /* far_copies are offset by 1
- * stripe instead of many
- */
- int copies; /* near_copies * far_copies.
- * must be <= raid_disks
- */
- sector_t stride; /* distance between far copies.
- * This is size / far_copies unless
- * far_offset, in which case it is
- * 1 stripe.
- */
-
- sector_t dev_sectors; /* temp copy of
- * mddev->dev_sectors */
-
- int chunk_shift; /* shift from chunks to sectors */
- sector_t chunk_mask;
-
- struct list_head retry_list;
- /* queue pending writes and submit them on unplug */
- struct bio_list pending_bio_list;
- int pending_count;
-
- spinlock_t resync_lock;
- int nr_pending;
- int nr_waiting;
- int nr_queued;
- int barrier;
- sector_t next_resync;
- int fullsync; /* set to 1 if a full sync is needed,
- * (fresh device added).
- * Cleared when a sync completes.
- */
- int have_replacement; /* There is at least one
- * replacement device.
- */
- wait_queue_head_t wait_barrier;
-
- mempool_t *r10bio_pool;
- mempool_t *r10buf_pool;
- struct page *tmppage;
-
- /* When taking over an array from a different personality, we store
- * the new thread here until we fully activate the array.
- */
- struct md_thread *thread;
-};
-
-/*
- * this is our 'private' RAID10 bio.
- *
- * it contains information about what kind of IO operations were started
- * for this RAID10 operation, and about their status:
- */
-
-struct r10bio {
- atomic_t remaining; /* 'have we finished' count,
- * used from IRQ handlers
- */
- sector_t sector; /* virtual sector number */
- int sectors;
- unsigned long state;
- struct mddev *mddev;
- /*
- * original bio going to /dev/mdx
- */
- struct bio *master_bio;
- /*
- * if the IO is in READ direction, then this is where we read
- */
- int read_slot;
-
- struct list_head retry_list;
- /*
- * if the IO is in WRITE direction, then multiple bios are used,
- * one for each copy.
- * When resyncing we also use one for each copy.
- * When reconstructing, we use 2 bios, one for read, one for write.
- * We choose the number when they are allocated.
- * We sometimes need an extra bio to write to the replacement.
- */
- struct {
- struct bio *bio;
- union {
- struct bio *repl_bio; /* used for resync and
- * writes */
- struct md_rdev *rdev; /* used for reads
- * (read_slot >= 0) */
- };
- sector_t addr;
- int devnum;
- } devs[0];
-};
-
-/* when we get a read error on a read-only array, we redirect to another
- * device without failing the first device, or trying to over-write to
- * correct the read error. To keep track of bad blocks on a per-bio
- * level, we store IO_BLOCKED in the appropriate 'bios' pointer
- */
-#define IO_BLOCKED ((struct bio*)1)
-/* When we successfully write to a known bad-block, we need to remove the
- * bad-block marking which must be done from process context. So we record
- * the success by setting devs[n].bio to IO_MADE_GOOD
- */
-#define IO_MADE_GOOD ((struct bio *)2)
-
-#define BIO_SPECIAL(bio) ((unsigned long)bio <= 2)
-
-/* bits for r10bio.state */
-enum r10bio_state {
- R10BIO_Uptodate,
- R10BIO_IsSync,
- R10BIO_IsRecover,
- R10BIO_Degraded,
-/* Set ReadError on bios that experience a read error
- * so that raid10d knows what to do with them.
- */
- R10BIO_ReadError,
-/* If a write for this request means we can clear some
- * known-bad-block records, we set this flag.
- */
- R10BIO_MadeGood,
- R10BIO_WriteError,
-};
-#endif