Re: [PATCH RESEND v3 2/3] lib/raid6: Optimizing the raid6_select_algo time through asynchronous processing

Paul Menzel <[email protected]>
Newsgroups gmane.linux.raid,gmane.linux.kernel
Message-ID <[email protected]>
Dear sunliming,


Thank you for your patch. Two formal things, and one “real” question.


Am 20.03.26 um 07:07 schrieb [email protected]:
> From: sunliming <[email protected]>

It’d be great if you could spell your name with spaces. Sun Li Ming or 
Sunli Ming? (`git config --global user.name "Sun Li Ming"` would 
configure it.)

> Optimizing the raid6_select_algo time. In raid6_select_algo(), an raid6 gen
> algorithm is first selected quickly through synchronous processing, while
> the time-consuming process of selecting the optimal algorithm via benchmarking

Please adhere to the text width of 75 characters. 
(`scripts/checkpatch.pl` should have found this.)

> is handled asynchronously. This approach speeds up the overall startup time
> and ultimately ensures the selection of an optimal algorithm.

It’d be great if you shared the test system and exact numbers, and new 
log messages.

Is there any problem with the benchmark, if it is run asynchronously, 
because other things are run on the CPU?

If you are working on this, I was wondering if the current approach of 
selecting the algorithm during each boot is the best choice, and if it 
shouldn’t be dynamically configurable like schedulers and other things 
over sysfs and the Linux kernel command line, and also if the chosen 
algorithm can’t be cached as long as – I guess – the processor/CPU stays 
the same.

> Signed-off-by: sunliming <[email protected]>

(Ditto regarding the name.)


Kind regards,

Paul


> ---
>   lib/raid6/algos.c | 30 ++++++++++++++++++++----------
>   1 file changed, 20 insertions(+), 10 deletions(-)
> 
> diff --git a/lib/raid6/algos.c b/lib/raid6/algos.c
> index c21e3ad99d97..b8b5515ac7a6 100644
> --- a/lib/raid6/algos.c
> +++ b/lib/raid6/algos.c
> @@ -12,6 +12,7 @@
>    */
>   
>   #include <linux/raid/pq.h>
> +#include <linux/workqueue.h>
>   #ifndef __KERNEL__
>   #include <sys/mman.h>
>   #include <stdio.h>
> @@ -166,7 +167,7 @@ static inline int raid6_choose_gen_fast(void)
>   
>   	if (best) {
>   		raid6_call = *best;
> -		pr_info("raid6: skipped pq benchmark and selected %s\n",
> +		pr_info("raid6: raid6: fast selected %s, async benchmark pending\n",
>   				best->name);
>   	} else {
>   		pr_err("raid6: No valid algorithm found even for fast selection!\n");
> @@ -213,7 +214,7 @@ static inline const struct raid6_calls *raid6_gen_benchmark(
>   	}
>   
>   	if (!best) {
> -		pr_err("raid6: Yikes! No algorithm found!\n");
> +		pr_warn("raid6: async benchmark failed to find any algorithm\n");
>   		goto out;
>   	}
>   
> @@ -289,24 +290,33 @@ static int raid6_choose_gen_benmark(void)
>   	return ret;
>   }
>   
> +static struct work_struct raid6_benchmark_work;
> +
> +static void benchmark_work_func(struct work_struct *work)
> +{
> +	raid6_choose_gen_benmark();
> +}
> +
>   int __init raid6_select_algo(void)
>   {
>   	int ret = 0;
>   	const struct raid6_recov_calls *rec_best = NULL;
>   
> -	/* select raid gen_syndrome functions */
> -	if (!IS_ENABLED(CONFIG_RAID6_PQ_BENCHMARK))
> -		ret = raid6_choose_gen_fast();
> -	else
> -		ret = raid6_choose_gen_benmark();
> -
> +	/* phase 1: synchronous fast selection generation algorithm */
> +	ret = raid6_choose_gen_fast();
>   	if (ret < 0)
>   		goto out;
>   
>   	/* select raid recover functions */
>   	rec_best = raid6_choose_recov();
> -	if (!rec_best)
> +	if (!rec_best) {
>   		ret = -EINVAL;
> +		goto out;
> +	}
> +
> +	/* phase 2: asynchronous performance benchmarking */
> +	INIT_WORK(&raid6_benchmark_work, benchmark_work_func);
> +	schedule_work(&raid6_benchmark_work);
>   
>   out:
>   	return ret;
> @@ -314,7 +324,7 @@ int __init raid6_select_algo(void)
>   
>   static void raid6_exit(void)
>   {
> -	do { } while (0);
> +	cancel_work_sync(&raid6_benchmark_work);
>   }
>   
>   subsys_initcall(raid6_select_algo);
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.