linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Timofey Titovets <nefelim4ag@gmail.com>
To: linux-raid@vger.kernel.org
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [RFC PATCH] raid6_pq: Add module options to prefer algorithm
Date: Wed, 2 Jan 2019 05:34:46 +0300	[thread overview]
Message-ID: <CAGqmi74gL=urkvKuSGpDF05f6BpTC0zdf1vDSVDZ-9qr+2q5Tw@mail.gmail.com> (raw)
In-Reply-To: <20180504001541.2068-1-nefelim4ag@gmail.com>

Gentle ping.

пт, 4 мая 2018 г. в 03:15, Timofey Titovets <nefelim4ag@gmail.com>:
>
> Skip testing unnecessary algorithms to speedup module initialization
>
> For my systems:
>   Before: 1.510s (initrd)
>   After:  977ms  (initrd) # I set prefer to fastest algorithm
>
> Dmesg after patch:
> [    1.190042] raid6: avx2x4   gen() 28153 MB/s
> [    1.246683] raid6: avx2x4   xor() 19440 MB/s
> [    1.246684] raid6: using algorithm avx2x4 gen() 28153 MB/s
> [    1.246684] raid6: .... xor() 19440 MB/s, rmw enabled
> [    1.246685] raid6: using avx2x2 recovery algorithm
>
> Signed-off-by: Timofey Titovets <nefelim4ag@gmail.com>
> CC: linux-btrfs@vger.kernel.org
> ---
>  lib/raid6/algos.c | 28 +++++++++++++++++++++++++---
>  1 file changed, 25 insertions(+), 3 deletions(-)
>
> diff --git a/lib/raid6/algos.c b/lib/raid6/algos.c
> index 5065b1e7e327..abfcb4107fc3 100644
> --- a/lib/raid6/algos.c
> +++ b/lib/raid6/algos.c
> @@ -30,6 +30,11 @@ EXPORT_SYMBOL(raid6_empty_zero_page);
>  #endif
>  #endif
>
> +static char *prefer_name;
> +
> +module_param(prefer_name, charp, 0);
> +MODULE_PARM_DESC(prefer_name, "Prefer gen/xor() algorithm");
> +
>  struct raid6_calls raid6_call;
>  EXPORT_SYMBOL_GPL(raid6_call);
>
> @@ -155,10 +160,27 @@ static inline const struct raid6_calls *raid6_choose_gen(
>  {
>         unsigned long perf, bestgenperf, bestxorperf, j0, j1;
>         int start = (disks>>1)-1, stop = disks-3;       /* work on the second half of the disks */
> -       const struct raid6_calls *const *algo;
> -       const struct raid6_calls *best;
> +       const struct raid6_calls *const *algo = NULL;
> +       const struct raid6_calls *best = NULL;
> +
> +       if (strlen(prefer_name)) {
> +               for (algo = raid6_algos; strlen(prefer_name) && *algo; algo++) {
> +                       if (!strncmp(prefer_name, (*algo)->name, 8)) {
> +                               best = *algo;
> +                               break;
> +                       }
> +               }
> +               if (!best)
> +                       pr_info("raid6: %-8s prefer not found\n", prefer_name);
> +       }
> +
> +
> +
> +       if (!algo) {
> +               algo = raid6_algos;
> +       }
>
> -       for (bestgenperf = 0, bestxorperf = 0, best = NULL, algo = raid6_algos; *algo; algo++) {
> +       for (bestgenperf = 0, bestxorperf = 0; *algo; algo++) {
>                 if (!best || (*algo)->prefer >= best->prefer) {
>                         if ((*algo)->valid && !(*algo)->valid())
>                                 continue;
> --
> 2.17.0



-- 
Have a nice day,
Timofey.

      reply	other threads:[~2019-01-02  2:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-04  0:15 [RFC PATCH] raid6_pq: Add module options to prefer algorithm Timofey Titovets
2019-01-02  2:34 ` Timofey Titovets [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAGqmi74gL=urkvKuSGpDF05f6BpTC0zdf1vDSVDZ-9qr+2q5Tw@mail.gmail.com' \
    --to=nefelim4ag@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).