linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: "Raz Ben-Jehuda(caro)" <raziebe@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: cpu
Date: Sun, 29 May 2005 23:52:35 +0400	[thread overview]
Message-ID: <429A1D83.6010901@tls.msk.ru> (raw)
In-Reply-To: <5d96567b05052815251f1cd297@mail.gmail.com>

Raz Ben-Jehuda(caro) wrote:
> I was testing linux raid for sometime, I created several test units
> which send read request to the raid using big buffers( 4MB).
> It seems to be that the software raid consumes to much cpu. I reach
> 100% cpu usage just by reading from the raid.
> I used 4 disks raid 0.

Now try to do the same test without raid - I bet it will use
as much CPU as your raid test.  Raid0 requires almost no CPU
resources, unlike improperly set up IDE disks (no DMA is the
first thing to check -- hdparm is your friend).

/mjt

      reply	other threads:[~2005-05-29 19:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-28 22:25 cpu Raz Ben-Jehuda(caro)
2005-05-29 19:52 ` Michael Tokarev [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=429A1D83.6010901@tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=linux-raid@vger.kernel.org \
    --cc=raziebe@gmail.com \
    /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).