linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: John Robinson <john.robinson@anonymous.org.uk>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID5 XOR speed vs RAID6 Q speed (was Re: AVX RAID5 xor checksumming)
Date: Sun, 01 Apr 2012 17:01:05 -0700	[thread overview]
Message-ID: <4F78EC41.6040108@zytor.com> (raw)
In-Reply-To: <4F76ECD0.1060608@anonymous.org.uk>

On 03/31/2012 04:38 AM, John Robinson wrote:
> On 29/03/2012 22:44, Jim Kukunas wrote:
>> Based on xor_speed, the AVX implementation appears to be ~32% faster
>> than the
>> SSE implementation on my i7 2600:
>>
>>     generic_sse: 15088.000 MB/sec
>>     avx: 19936.000 MB/sec
> 
> I just noticed in my logs the other day (recent el5 kernel on a Core 2):
> 
> raid5: automatically using best checksumming function: generic_sse
>    generic_sse:  7805.000 MB/sec
> raid5: using function: generic_sse (7805.000 MB/sec)
> raid6: int64x1   2635 MB/s
> raid6: int64x2   3208 MB/s
> raid6: int64x4   3020 MB/s
> raid6: int64x8   2519 MB/s
> raid6: sse2x1    5099 MB/s
> raid6: sse2x2    5742 MB/s
> raid6: sse2x4    8237 MB/s
> raid6: using algorithm sse2x4 (8237 MB/s)
> 
> I was just wondering how it's possible to do the RAID6 Q calculation
> faster than the RAID5 XOR calculation - or am I reading this log excerpt
> wrongly?
> 
> It's probably academic, since the machine this is running on only has a
> maximum of about 4500 MB/s of memory throughput, and a lot of that would
> be consumed sending data to disc in amongst the calculations being done.
> 

It *might* be a result of how these different algorithms are
benchmarked, but yes, that really looks a bit odd, especially since the
RAID6 code *also* computes the XOR checksum (it does P and Q in parallel
since it has to read the data anyway).

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


  reply	other threads:[~2012-04-02  0:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-29 21:44 AVX RAID5 xor checksumming Jim Kukunas
2012-03-29 21:44 ` [PATCH] raid5: add AVX optimized RAID5 checksumming Jim Kukunas
2012-03-31 11:38 ` RAID5 XOR speed vs RAID6 Q speed (was Re: AVX RAID5 xor checksumming) John Robinson
2012-04-02  0:01   ` H. Peter Anvin [this message]
2012-04-02 22:48   ` Jim Kukunas
2012-04-03 10:23     ` John Robinson
2012-04-03 23:56       ` Jim Kukunas
2012-04-03 23:56         ` [PATCH 1/2] crypto: wait for a full jiffy in do_xor_speed Jim Kukunas
2012-04-03 23:56         ` [PATCH 2/2] crypto: disable preemption while benchmarking RAID5 xor checksumming Jim Kukunas
2012-04-06 20:43         ` RAID5 XOR speed vs RAID6 Q speed (was Re: AVX RAID5 xor checksumming) Dan Williams
2012-04-17 15:32           ` Boaz Harrosh

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=4F78EC41.6040108@zytor.com \
    --to=hpa@zytor.com \
    --cc=john.robinson@anonymous.org.uk \
    --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).