From: Wolfgang Denk <wd@denx.de>
To: Benjamin ESTRABAUD <be@mpstor.com>
Cc: Pieter De Wit <pieter@insync.za.net>, linux-raid@vger.kernel.org
Subject: Re: Using Video cards (CUDA) for RAID parity
Date: Mon, 16 Dec 2013 17:07:43 +0100 [thread overview]
Message-ID: <20131216160743.73CE838465B@gemini.denx.de> (raw)
In-Reply-To: <52A9A1B3.5080706@mpstor.com>
Dear Benjamin,
In message <52A9A1B3.5080706@mpstor.com> you wrote:
> On several more RAID specific SoC (like the PowerPC 440x/460x) a XOR
> engine is included to speed up RAID calculations (effectively a hardware
> RAID engine).
>
> I think Intel Atom CPUs were planned/got a similar engine added, but
> with the advance in CPU efficiencies and frequencies, these XOR engines
> are practically obsolete: You will barely use 5% of your CPU (if a high
> end CPU) for the parity calculation on RAID5.
>
> These days it seems that the overhead from the parity calculations are
> so small that they become insignificant.
I fully agree here.
Even on a not so fresh desktop CPU (Intel Core2 Quad CPU Q9550 at
2.83GHz) I see this in the kernel logs:
...
[ 15.944466] xor: measuring software checksum speed
[ 15.983008] prefetch64-sse: 11592.000 MB/sec
[ 16.020008] generic_sse: 10232.000 MB/sec
[ 16.045623] xor: using function: prefetch64-sse (11592.000 MB/sec)
...
So for each percent of CPU bandwith I offer I get 115 MB/s bandwith
for parity calculations. None of the RAID arrays I have running would
ever need even close to 10 % of my CPU (in theory, at least).
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
I can't say I've ever been lost, but I was bewildered once for three
days. - Daniel Boone (Attributed)
next prev parent reply other threads:[~2013-12-16 16:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 10:27 Using Video cards (CUDA) for RAID parity Pieter De Wit
2013-12-12 11:44 ` Benjamin ESTRABAUD
2013-12-16 16:07 ` Wolfgang Denk [this message]
2013-12-12 11:52 ` David Brown
2013-12-12 16:57 ` Pieter De Wit
2013-12-12 17:13 ` Benjamin ESTRABAUD
[not found] ` <ff87dc745635b18a71b98ce36356eea7@insync.za.net>
2013-12-12 18:57 ` Benjamin ESTRABAUD
2013-12-12 17:30 ` Chris Green
2013-12-12 17:51 ` joystick
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=20131216160743.73CE838465B@gemini.denx.de \
--to=wd@denx.de \
--cc=be@mpstor.com \
--cc=linux-raid@vger.kernel.org \
--cc=pieter@insync.za.net \
/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).