linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: "Raz Ben-Jehuda(caro)" <raziebe@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: cpu consumption
Date: Thu, 01 Dec 2005 21:02:44 -0500	[thread overview]
Message-ID: <438FAB44.5030807@pobox.com> (raw)
In-Reply-To: <5d96567b0511260545j61970a01j3b5c435766a51a6d@mail.gmail.com>

Raz Ben-Jehuda(caro) wrote:
> Hello Jeff.
> Here is my problem.
> 
> When I issue a READ operation over a SATA disk in linux i have
> huge cpu consumption , about 90% cpu usage.
> 
> I am using MAXTOR disks in a supermicro machine.
> the cpu test was made when i "raw read" from the DISK using DIRECT_IO.

I dunno... do some profiling (in-kernel profiler, or oprofile) and see 
where the CPU is being consumed.

Are you also seeing a lot of interrupts?

	Jeff




  reply	other threads:[~2005-12-02  2:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-26 13:45 cpu consumption Raz Ben-Jehuda(caro)
2005-12-02  2:02 ` Jeff Garzik [this message]
2005-12-02  2:14   ` Tejun Heo

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=438FAB44.5030807@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=linux-ide@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).