Searched hist:be85f93ae2df32dea0b20908316f1d894c3e0f64 (Results 1 – 3 of 3) sorted by relevance
| /linux/lib/raid6/ |
| H A D | algos.c | diff be85f93ae2df32dea0b20908316f1d894c3e0f64 Tue Nov 13 00:26:52 CET 2018 Daniel Verkamp <dverkamp@chromium.org> lib/raid6: add option to skip algo benchmarking
This is helpful for systems where fast startup time is important.
It is especially nice to avoid benchmarking RAID functions that are
never used (for example, BTRFS selects RAID6_PQ even if the parity RAID
mode is not in use).
This saves 250+ milliseconds of boot time on modern x86 and ARM systems
with a dozen or more available implementations.
The new option is defaulted to 'y' to match the previous behavior of
always benchmarking on init.
Signed-off-by: Daniel Verkamp <dverkamp@chromium.org>
Signed-off-by: Shaohua Li <shli@fb.com>
|
| /linux/include/linux/raid/ |
| H A D | pq.h | diff be85f93ae2df32dea0b20908316f1d894c3e0f64 Tue Nov 13 00:26:52 CET 2018 Daniel Verkamp <dverkamp@chromium.org> lib/raid6: add option to skip algo benchmarking
This is helpful for systems where fast startup time is important.
It is especially nice to avoid benchmarking RAID functions that are
never used (for example, BTRFS selects RAID6_PQ even if the parity RAID
mode is not in use).
This saves 250+ milliseconds of boot time on modern x86 and ARM systems
with a dozen or more available implementations.
The new option is defaulted to 'y' to match the previous behavior of
always benchmarking on init.
Signed-off-by: Daniel Verkamp <dverkamp@chromium.org>
Signed-off-by: Shaohua Li <shli@fb.com>
|
| /linux/lib/ |
| H A D | Kconfig | diff be85f93ae2df32dea0b20908316f1d894c3e0f64 Tue Nov 13 00:26:52 CET 2018 Daniel Verkamp <dverkamp@chromium.org> lib/raid6: add option to skip algo benchmarking
This is helpful for systems where fast startup time is important.
It is especially nice to avoid benchmarking RAID functions that are
never used (for example, BTRFS selects RAID6_PQ even if the parity RAID
mode is not in use).
This saves 250+ milliseconds of boot time on modern x86 and ARM systems
with a dozen or more available implementations.
The new option is defaulted to 'y' to match the previous behavior of
always benchmarking on init.
Signed-off-by: Daniel Verkamp <dverkamp@chromium.org>
Signed-off-by: Shaohua Li <shli@fb.com>
|