All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Kevin Radloff <radsaq@gmail.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: PATCH: Fix broken PIO with libata
Date: Wed, 17 May 2006 02:39:02 +0900	[thread overview]
Message-ID: <446A0E36.5060505@gmail.com> (raw)
In-Reply-To: <446A0B6C.8050901@garzik.org>

Jeff Garzik wrote:
> Kevin Radloff wrote:
>> On 5/16/06, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>>> On Maw, 2006-05-16 at 11:33 -0400, Kevin Radloff wrote:
>>> > However, I still have a problem with pata_pcmcia (that I actually
>>> > experienced also with the ide-cs driver) where sustained reading or
>>> > writing to the CF card spikes the CPU with nearly 100% system time.
>>>
>>> That is normal. The PCMCIA devices don't support DMA. As a result of
>>> this the processor has to fetch each byte itself over the ISA speed
>>> PCMCIA bus link.
>>
>> Hrm, as I recall that only started happening with ide-cs sometime in
>> the single digits of 2.6.x.. And note that it's only maxing out at
>> about 1.5MB/s. Should that saturate my laptop's 1.1GHz Pentium M
>> processor?
> 
> Doing data xfer using PIO rather than DMA definitely eats tons of CPU 
> cycles.

Yeap, in addition, if doing real PIO (unbuffered by the HBA), the time 
it takes is soley determined by what PIO mode is in use.  It doesn't 
matter how fast the CPU is.  Faster CPUs only end up wasting more 
cycles.  :-(

-- 
tejun

  reply	other threads:[~2006-05-16 17:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-16 14:39 PATCH: Fix broken PIO with libata Alan Cox
2006-05-16 15:33 ` Kevin Radloff
2006-05-16 15:53   ` Alan Cox
2006-05-16 17:19     ` Kevin Radloff
2006-05-16 17:27       ` Jeff Garzik
2006-05-16 17:39         ` Tejun Heo [this message]
2006-05-16 18:13           ` Kevin Radloff
2006-05-16 22:51       ` Alan Cox
2006-05-16 15:36 ` Tejun Heo
2006-05-16 15:48   ` Jeff Garzik
2006-05-16 15:57     ` Tejun Heo
2006-05-16 23:00     ` Paul Mackerras
2006-05-16 17:10   ` Jeff Garzik

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=446A0E36.5060505@gmail.com \
    --to=htejun@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=radsaq@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 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.