From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: ide-cs using 100% CPU
Date: Sun, 08 Aug 2004 13:32:10 -0600 [thread overview]
Message-ID: <000f01c47d7e$669727f0$6401a8c0@northbrook> (raw)
In-Reply-To: fa.ggacpdl.26on0d@ifi.uio.no
----- Original Message -----
From: "Hamie" <hamish@travellingkiwi.com>
> Robert Hancock wrote:
>
> >It isn't that the CPU is doing so much work, it's mostly waiting. However
> >
> >
>
> That was my point... While waiting, shouldn't the CPU be off doing
> something else? Like giving X some attention...
>
> >with this type of PIO access, the CPU must do all the reads/writes from
the
> >buffer and while doing this the CPU is blocked and cannot do anything
else.
> >
> >
> >
>
> Or is the CF requirements such that it's spending it's time doing the
> actual reads & writes from the buffer, and it's the hardware inserting
> wait-states when it's being accessed?
>
That's basically what's happening, when the CPU does a write or a read of
some data from the buffer, it has to wait for that to go all the way across
the bus and to/from the card, meanwhile no other useful work can be done
while it is waiting. As Alan Cox mentioned, having a hyperthreaded CPU helps
tremendously in such cases, since the other "half" of the CPU can be doing
useful work while the first half is blocked.
next parent reply other threads:[~2004-08-08 19:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.hhjr2f2.1ql2t80@ifi.uio.no>
[not found] ` <fa.ggacpdl.26on0d@ifi.uio.no>
2004-08-08 19:32 ` Robert Hancock [this message]
[not found] <fa.j0leddb.okcbor@ifi.uio.no>
[not found] ` <fa.goasld9.1q1kb05@ifi.uio.no>
2004-08-07 19:21 ` ide-cs using 100% CPU Robert Hancock
2004-08-08 15:24 ` Hamie
2004-07-18 9:30 Hamie
2004-08-06 19:27 ` Russell King
2004-08-06 19:33 ` Hamie
2004-08-06 19:38 ` Russell King
2004-08-07 17:55 ` Hamie
2004-08-07 22:26 ` Alan Cox
2004-08-08 9:03 ` Hamie
2004-08-08 15:24 ` Alan Cox
2004-08-09 9:57 ` Paulo Marques
2004-08-09 12:32 ` P
2004-08-09 20:11 ` Bill Davidsen
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='000f01c47d7e$669727f0$6401a8c0@northbrook' \
--to=hancockr@shaw.ca \
--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