From: Gregory Leblanc <gleblanc@linuxweasel.com>
To: linux-raid@vger.kernel.org
Subject: Re: EIO AP-1680 ATA133 RAID PCI Controller
Date: 12 Feb 2003 15:00:26 -0800 [thread overview]
Message-ID: <1045090825.12695.34.camel@gregdell> (raw)
In-Reply-To: <5.1.1.6.2.20030212083307.039a1dd0@mail.harddata.com>
[-- Attachment #1: Type: text/plain, Size: 1079 bytes --]
It's really impolite to send encrypted mail to the list. Anyone to whom
the message is encrypted won't be able to read it
On Wed, 2003-02-12 at 07:36, Maurice Hilarius wrote:
> -----BEGIN PGP MESSAGE-----
[snip]
> With regards to your message at 02:16 PM 2/11/03, Gregory Leblanc.
> Where you stated:
> While the performance of RAID 5 using software RAID is generally far
> superior to that provided by hardware RAID, host CPU usage can be
> -quite- high in high-load situations. The benchmarks recently posted
> had cpu usage numbers at over 90% on most sequeential writes and
> reads.
> Greg
>
> Naturally. There is no such thing as a free lunch.
> Look at it this way:
> If you have X amount of data to write, and it takes half as long, but
> uses 30% more CPU, you are ahead of the game..
The formatting of this message is all wonky, sorry about it being
confusing. Anyway, I agree, except that I have no numbers to back up
the CPU use differences, or the MB/sec differences. Without them, any
claims are pretty silly to try to make.
Greg
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-02-12 23:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-07 3:36 EIO AP-1680 ATA133 RAID PCI Controller tk Voice
2003-02-10 17:32 ` Steven Dake
2003-02-11 5:16 ` tk Voice
2003-02-11 17:16 ` Steven Dake
2003-02-11 21:16 ` Gregory Leblanc
2003-02-11 18:55 ` Trent Piepho
2003-02-12 15:36 ` Maurice Hilarius
2003-02-12 23:00 ` Gregory Leblanc [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=1045090825.12695.34.camel@gregdell \
--to=gleblanc@linuxweasel.com \
--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.