All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <kernel@teksavvy.com>
To: IDE/ATA development list <linux-ide@vger.kernel.org>,
	Jeff Garzik <jgarzik@pobox.com>, Tejun Heo <htejun@gmail.com>
Subject: Re: Why so much PIO for r/w accesses ?
Date: Sun, 21 Nov 2010 18:39:51 -0500	[thread overview]
Message-ID: <4CE9ADC7.8040800@teksavvy.com> (raw)
In-Reply-To: <4CE9ACAA.9060203@teksavvy.com>

On 10-11-21 06:35 PM, Mark Lord wrote:
> While working on something unrelated today,
> I instrumented ata_sff_data_xfer32() to generate a printk() on each invocation.
>
> Imagine then my complete surprise to see that print() being invoked very frequently
> after rebooting with the modified kernel.
>
> ata_sff_data_xfer32() is for PIO read/writes.. something that I don't expect to
> see.
>
> This is an ata_piix system, with a pure SATA SSD.
> Why are we using PIO so much?
> Or am I simply misunderstanding something basic here.. ?
>
> Confused.

Definitely just me being confused.  :)

I changed the printk() into an ata_dev_printk(), and discovered that
all of those reads/writes are targeting the DVD-RW drive, not the SSD.

So this is simply hald or something similar polling for disc-insertion,
and PIO is used (as always) for the PACKET command transfer.

Duh.  :)

  reply	other threads:[~2010-11-21 23:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-21 23:35 Why so much PIO for r/w accesses ? Mark Lord
2010-11-21 23:39 ` Mark Lord [this message]
2010-11-22 11:35 ` Sergei Shtylyov

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=4CE9ADC7.8040800@teksavvy.com \
    --to=kernel@teksavvy.com \
    --cc=htejun@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@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.