From: Brad Campbell <lists2009@fnarfbargle.com>
To: Ole Tange <ole@tange.dk>
Cc: Igor M Podlesny <for.poige+lsr@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: Software RAID checksum performance on 24 disks not even close to kernel reported
Date: Wed, 06 Jun 2012 09:40:37 +0800 [thread overview]
Message-ID: <4FCEB515.5050209@fnarfbargle.com> (raw)
In-Reply-To: <CA+4vN7x0f3f3=htC4iaPmDPqdviv8+AqAqY3sxKbP1X+89gtuQ@mail.gmail.com>
On 06/06/12 02:44, Ole Tange wrote:
> On Tue, Jun 5, 2012 at 1:29 PM, Igor M Podlesny<for.poige+lsr@gmail.com> wrote:
>> On 5 June 2012 15:47, Ole Tange<ole@tange.dk> wrote:
>>> On Tue, Jun 5, 2012 at 5:39 AM, Igor M Podlesny<for.poige+lsr@gmail.com> wrote:
>>>> On 5 June 2012 07:14, Ole Tange<ole@tange.dk> wrote:
>>>> […]
>>>>> I tested this by creating 24 devices in RAM, used different chunk
>>>>> sizes, and then copied the linux kernel source. Test script can be
>>>>> found on http://oletange.blogspot.dk/2012/05/software-raid-performance-on-24-disks.html
> :
>> Wanna try CONFIG_MULTICORE_RAID456? :-)
>
> If the kernel can checksum 6196 MB/s why would I need
> CONFIG_MULTICORE_RAID456? Please elaborate on why you think that is
> needed.
I'd have thought there was a significant difference between the test
generating that figure (being a large, single block being checksummed)
and shunting around blocks from 20 odd block devices, arranging them and
checksumming them.
I'm not debating the validity of your tests at all, however I do
question your assertion than a single raid6 thread should even get close
to that theoretical figure when actually doing real work.
Why not do as the man suggested and enable CONFIG_MULTICORE_RAID456 and
see what happens?
Regards,
Brad
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-06-06 1:40 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 23:14 Software RAID checksum performance on 24 disks not even close to kernel reported Ole Tange
2012-06-05 1:26 ` Joe Landman
2012-06-05 3:36 ` Igor M Podlesny
2012-06-05 7:47 ` Ole Tange
2012-06-05 11:25 ` Peter Grandi
2012-06-05 20:57 ` Ole Tange
2012-06-06 17:37 ` Peter Grandi
2012-06-05 14:15 ` Stan Hoeppner
2012-06-05 20:45 ` Ole Tange
2012-06-05 3:39 ` Igor M Podlesny
2012-06-05 7:47 ` Ole Tange
2012-06-05 11:29 ` Igor M Podlesny
2012-06-05 13:09 ` Peter Grandi
2012-06-05 21:17 ` Ole Tange
2012-06-06 1:38 ` Stan Hoeppner
2012-06-05 18:44 ` Ole Tange
2012-06-06 1:40 ` Brad Campbell [this message]
2012-06-06 3:48 ` Marcus Sorensen
2012-06-06 11:21 ` Ole Tange
2012-06-06 11:17 ` Ole Tange
2012-06-06 12:58 ` Brad Campbell
2012-06-06 14:11 ` Ole Tange
2012-06-06 16:05 ` Igor M Podlesny
2012-06-06 19:51 ` Ole Tange
2012-06-06 22:21 ` Igor M Podlesny
2012-06-06 22:53 ` Peter Grandi
2012-06-07 3:41 ` Igor M Podlesny
2012-06-07 4:59 ` Stan Hoeppner
2012-06-07 5:22 ` Igor M Podlesny
2012-06-07 9:03 ` Stan Hoeppner
2012-06-07 9:22 ` Igor M Podlesny
2012-06-06 16:09 ` Dan Williams
2012-06-06 19:19 ` Ole Tange
2012-06-06 19:24 ` Dan Williams
2012-06-06 19:26 ` Ole Tange
2012-06-07 4:06 ` Stan Hoeppner
2012-06-07 14:40 ` Joe Landman
2012-06-08 1:23 ` Stan Hoeppner
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=4FCEB515.5050209@fnarfbargle.com \
--to=lists2009@fnarfbargle.com \
--cc=for.poige+lsr@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=ole@tange.dk \
/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).