linux-toradex.git/drivers/md/raid5.h, branch v3.2.46

md/raid5: typedef removal: raid5_conf_t -> struct r5conf

2011-10-11T05:49:52+00:00

Signed-off-by: NeilBrown

md: remove typedefs: mdk_thread_t -> struct md_thread

2011-10-11T05:48:23+00:00

Signed-off-by: NeilBrown

md: remove typedefs: mddev_t -> struct mddev

2011-10-11T05:47:53+00:00

Having mddev_t and 'struct mddev_s' is ugly and not preferred

Signed-off-by: NeilBrown

md: removing typedefs: mdk_rdev_t -> struct md_rdev

2011-10-11T05:45:26+00:00

The typedefs are just annoying. 'mdk' probably refers to 'md_k.h'
which used to be an include file that defined this thing.

Signed-off-by: NeilBrown

md/raid5: Clear bad blocks on successful write.

2011-07-28T01:39:23+00:00

On a successful write to a known bad block, flag the sh
so that raid5d can remove the known bad block from the list.

Signed-off-by: NeilBrown

md/raid5: write errors should be recorded as bad blocks if possible.

2011-07-28T01:39:22+00:00

When a write error is detected, don't mark the device as failed
immediately but rather record the fact for handle_stripe to deal with.

Handle_stripe then attempts to record a bad block.  Only if that fails
does the device get marked as faulty.

Signed-off-by: NeilBrown

md/raid5: use bad-block log to improve handling of uncorrectable read errors.

2011-07-28T01:39:22+00:00

If we get an uncorrectable read error - record a bad block rather than
failing the device.
And if these errors (which may be due to known bad blocks) cause
recovery to be impossible, record a bad block on the recovering
devices, or abort the recovery.

As we might abort a recovery without failing a device we need to teach
RAID5 about recovery_disabled handling.

Signed-off-by: NeilBrown

md/raid5: add some more fields to stripe_head_state

2011-07-26T01:35:20+00:00

Adding these three fields will allow more common code to be moved
to handle_stripe()

struct field rearrangement by Namhyung Kim.

Signed-off-by: NeilBrown 
Reviewed-by: Namhyung Kim

md/raid5: unify stripe_head_state and r6_state

2011-07-26T01:35:19+00:00

'struct stripe_head_state' stores state about the 'current' stripe
that is passed around while handling the stripe.
For RAID6 there is an extension structure: r6_state, which is also
passed around.
There is no value in keeping these separate, so move the fields from
the latter into the former.

This means that all code now needs to treat s->failed_num as an small
array, but this is a small cost.

Signed-off-by: NeilBrown 
Reviewed-by: Namhyung Kim

md/raid5: replace sh->lock with an 'active' flag.

2011-07-26T01:34:20+00:00

sh->lock is now mainly used to ensure that two threads aren't running
in the locked part of handle_stripe[56] at the same time.

That can more neatly be achieved with an 'active' flag which we set
while running handle_stripe.  If we find the flag is set, we simply
requeue the stripe for later by setting STRIPE_HANDLE.

For safety we take ->device_lock while examining the state of the
stripe and creating a summary in 'stripe_head_state / r6_state'.
This possibly isn't needed but as shared fields like ->toread,
->towrite are checked it is safer for now at least.

We leave the label after the old 'unlock' called "unlock" because it
will disappear in a few patches, so renaming seems pointless.

This leaves the stripe 'locked' for longer as we clear STRIPE_ACTIVE
later, but that is not a problem.

Signed-off-by: NeilBrown 
Reviewed-by: Namhyung Kim