litmus-rt-tegra.git/include/linux/raid, branch wip-nested-locking

Added missing tegra files.

2013-01-22T15:38:37+00:00

Patched in Tegra support.

2013-01-17T21:15:55+00:00

UAPI: Remove empty Kbuild files

2013-01-03T01:36:10+00:00

Empty files can get deleted by the patch program, so remove empty Kbuild
files and their links from the parent Kbuilds.

Signed-off-by: David Howells 
Signed-off-by: Linus Torvalds

lib/raid6: Add AVX2 optimized gen_syndrome functions

2012-12-13T08:51:03+00:00

Add AVX2 optimized gen_syndrom functions, which is simply based on
sse2.c written by hpa.

Signed-off-by: Yuanhan Liu 
Reviewed-by: H. Peter Anvin 
Signed-off-by: Jim Kukunas 
Signed-off-by: NeilBrown

lib/raid6: Add AVX2 optimized recovery functions

2012-12-13T05:42:01+00:00

Optimize RAID6 recovery functions to take advantage of
the 256-bit YMM integer instructions introduced in AVX2.

The patch was tested and benchmarked before submission.
However hardware is not yet released so benchmark numbers
cannot be reported.

Acked-by: "H. Peter Anvin" 
Signed-off-by: Jim Kukunas 
Signed-off-by: NeilBrown

UAPI: (Scripted) Disintegrate include/linux/raid

2012-10-09T08:49:02+00:00

Signed-off-by: David Howells 
Acked-by: Arnd Bergmann 
Acked-by: Thomas Gleixner 
Acked-by: Michael Kerrisk 
Acked-by: Paul E. McKenney 
Acked-by: Dave Jones

lib/raid6: Add SSSE3 optimized recovery functions

2012-05-22T03:54:18+00:00

Add SSSE3 optimized recovery functions, as well as a system
for selecting the most appropriate recovery functions to use.

Originally-by: H. Peter Anvin 
Signed-off-by: Jim Kukunas 
Signed-off-by: NeilBrown

md: add possibility to change data-offset for devices.

2012-05-20T23:27:00+00:00

When reshaping we can avoid costly intermediate backup by
changing the 'start' address of the array on the device
(if there is enough room).

So as a first step, allow such a change to be requested
through sysfs, and recorded in v1.x metadata.

(As we didn't previous check that all 'pad' fields were zero,
 we need a new FEATURE flag for this.
 A (belatedly) check that all remaining 'pad' fields are
 zero to avoid a repeat of this)

The new data offset must be requested separately for each device.
This allows each to have a different change in the data offset.
This is not likely to be used often but as data_offset can be
set per-device, new_data_offset should be too.

This patch also removes the 'acknowledged' arg to rdev_set_badblocks as
it is never used and never will be.  At the same time we add a new
arg ('in_new') which is currently always zero but will be used more
soon.

When a reshape finishes we will need to update the data_offset
and rdev->sectors.  So provide an exported function to do that.

Signed-off-by: NeilBrown

md: allow a reshape operation to be reversed.

2012-05-20T23:27:00+00:00

Currently a reshape operation always progresses from the start
of the array to the end unless the number of devices is being
reduced, in which case it progressed in the opposite direction.

To reverse a partial reshape which changes the number of devices
you can stop the array and re-assemble with the raid-disks numbers
reversed and it will undo.

However for a reshape that does not change the number of devices
it is not possible to reverse the reshape in the middle - you have to
wait until it completes.

So add a 'reshape_direction' attribute with is either 'forwards' or
'backwards' and can be explicitly set when delta_disks is zero.

This will become more important when we allow the data_offset to
change in a reshape.  Then the explicit statement of what direction is
being used will be more useful.

This can be enabled in raid5 trivially as it already supports
reverse reshape and just needs to use a different trigger to request it.

Signed-off-by: NeilBrown

md: Use existed macros instead of numbers

2012-03-13T00:21:23+00:00

Signed-off-by: majianpeng 
Signed-off-by: NeilBrown