From: John Robinson <john.robinson@anonymous.org.uk>
To: linux-raid@vger.kernel.org
Subject: Re: RAID5 XOR speed vs RAID6 Q speed (was Re: AVX RAID5 xor checksumming)
Date: Tue, 03 Apr 2012 11:23:16 +0100 [thread overview]
Message-ID: <4F7ACF94.5080505@anonymous.org.uk> (raw)
In-Reply-To: <20120402224818.GA2248@jtkukuna_gentoo_sb>
On 02/04/2012 23:48, Jim Kukunas wrote:
> On Sat, Mar 31, 2012 at 12:38:56PM +0100, John Robinson wrote:
[...]
>> 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: 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?
>
> Out of curiosity, are you running with CONFIG_PREEMPT=y?
No. Here's an excerpt from my .config:
# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not set
CONFIG_PREEMPT_BKL=y
CONFIG_PREEMPT_NOTIFIERS=y
But this is a Xen dom0 kernel, 2.6.18-308.1.1.el5.centos.plusxen. Now, a
non-Xen kernel (2.6.18-308.1.1.el5) says:
raid5: automatically using best checksumming function: generic_sse
generic_sse: 11892.000 MB/sec
raid5: using function: generic_sse (11892.000 MB/sec)
raid6: int64x1 2644 MB/s
raid6: int64x2 3238 MB/s
raid6: int64x4 3011 MB/s
raid6: int64x8 2503 MB/s
raid6: sse2x1 5375 MB/s
raid6: sse2x2 5851 MB/s
raid6: sse2x4 9136 MB/s
raid6: using algorithm sse2x4 (9136 MB/s)
Looks like it loses a chunk of performance running as a Xen dom0.
Even still, 11892 MB/s for XOR vs 9136 MB/s for XOR+Q - it still seems
remarkable that the XOR can't be done several times faster than the Q.
Cheers,
John.
next prev parent reply other threads:[~2012-04-03 10:23 UTC|newest]
Thread overview: 12+ 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
2012-04-02 22:48 ` Jim Kukunas
2012-04-03 10:23 ` John Robinson [this message]
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
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=4F7ACF94.5080505@anonymous.org.uk \
--to=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 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.