From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@TU-Ilmenau.DE>
To: linux-kernel@vger.kernel.org
Subject: Re: Hardware vs. Software Raid Speed
Date: Wed, 23 Aug 2006 21:42:10 +0200 [thread overview]
Message-ID: <ecib2i$1ip$2@sea.gmane.org> (raw)
In-Reply-To: 44EC94A9.4010903@gmail.com
Tejun Heo <htejun@gmail.com> wrote:
> And, yeah, they're all software RAID. Also, there isn't much to be
> gained from making RAID0/1 hardware. The software overhead isn't that
The CPU cycles in fact don't usually matter. The I/O overhead (on the
PCI bus) due to multiple transfers of the (more or less) same data is
typically more interesting.
regards
Mario
--
The secret that the NSA could read the Iranian secrets was more
important than any specific Iranian secrets that the NSA could
read. -- Bruce Schneier
prev parent reply other threads:[~2006-08-23 19:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 6:52 Hardware vs. Software Raid Speed Marc Perkel
2006-08-23 7:25 ` Andre Tomt
2006-08-23 8:39 ` Alistair John Strachan
2006-08-23 17:47 ` Tejun Heo
2006-08-23 17:55 ` Marc Perkel
2006-08-24 5:13 ` Joel Jaeggli
2006-08-23 19:42 ` Mario 'BitKoenig' Holbe [this message]
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='ecib2i$1ip$2@sea.gmane.org' \
--to=mario.holbe@tu-ilmenau.de \
--cc=linux-kernel@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