From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Matt Brown <matthew.brown.dev@gmail.com>, linuxppc-dev@lists.ozlabs.org
Cc: dja@axtens.net
Subject: Re: [v6, 1/2] raid6/altivec: Add vpermxor implementation for raid6 Q syndrome
Date: Tue, 20 Mar 2018 09:22:46 +1100 (AEDT) [thread overview]
Message-ID: <404rD729Rpz9sVr@ozlabs.org> (raw)
In-Reply-To: <20170804034233.13628-1-matthew.brown.dev@gmail.com>
On Fri, 2017-08-04 at 03:42:32 UTC, Matt Brown wrote:
> This patch uses the vpermxor instruction to optimise the raid6 Q syndrome.
> This instruction was made available with POWER8, ISA version 2.07.
> It allows for both vperm and vxor instructions to be done in a single
> instruction. This has been tested for correctness on a ppc64le vm with a
> basic RAID6 setup containing 5 drives.
>
> The performance benchmarks are from the raid6test in the /lib/raid6/test
> directory. These results are from an IBM Firestone machine with ppc64le
> architecture. The benchmark results show a 35% speed increase over the best
> existing algorithm for powerpc (altivec). The raid6test has also been run
> on a big-endian ppc64 vm to ensure it also works for big-endian
> architectures.
>
> Performance benchmarks:
> raid6: altivecx4 gen() 18773 MB/s
> raid6: altivecx8 gen() 19438 MB/s
>
> raid6: vpermxor4 gen() 25112 MB/s
> raid6: vpermxor8 gen() 26279 MB/s
>
> Signed-off-by: Matt Brown <matthew.brown.dev@gmail.com>
> Reviewed-by: Daniel Axtens <dja@axtens.net>
Series applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/2de95953c4e6ad54c9bee5e6a5518d
cheers
next prev parent reply other threads:[~2018-03-19 22:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 3:42 [v6 1/2] raid6/altivec: Add vpermxor implementation for raid6 Q syndrome Matt Brown
2017-08-04 3:42 ` [v6 2/2] lib/raid6: Build proper raid6test files on powerpc Matt Brown
2017-08-09 13:26 ` [v6 1/2] raid6/altivec: Add vpermxor implementation for raid6 Q syndrome Michael Ellerman
2017-08-09 23:41 ` Matt Brown
2017-08-09 23:41 ` Matt Brown
2018-03-19 22:22 ` Michael Ellerman [this message]
2018-03-20 10:15 ` [v6, " Michael Ellerman
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=404rD729Rpz9sVr@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=dja@axtens.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=matthew.brown.dev@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.