From: Jeff Garzik <jgarzik@pobox.com>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: Tejun Heo <htejun@gmail.com>, linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata: always use polling IDENTIFY
Date: Sun, 03 Dec 2006 08:02:40 -0500 [thread overview]
Message-ID: <4572CAF0.2040806@pobox.com> (raw)
In-Reply-To: <20061203125603.493ebde6@localhost.localdomain>
Alan wrote:
> On Sun, 3 Dec 2006 19:30:32 +0900
> Tejun Heo <htejun@gmail.com> wrote:
>
>> libata switched to IRQ-driven IDENTIFY when IRQ-driven PIO was
>> introduced. This has caused a lot of problems including device
>> misdetection and phantom device.
>>
>> ATA_FLAG_DETECT_POLLING was added recently to selectively use polling
>> IDENTIFY on problemetic drivers but many controllers and devices are
>> affected by this problem and trying to adding ATA_FLAG_DETECT_POLLING
>> for each such case is diffcult and not very rewarding.
>>
>> This patch makes libata always use polling IDENTIFY. This is
>> consistent with libata's original behavior and drivers/ide's behavior.
>>
>> Signed-off-by: Tejun Heo <htejun@gmail.com>
>
> Acked-by: Alan Cox <alan@redhat.com>
>
> One possibility however would be to invert the flag we have now so we can
> try turning -on- IRQ polling on some devices in future and maybe figure
> it out that way around ?
Agreed, though it is low priority.
You'll note that Tejun's change only applies to the [large] set of
drivers using libata-sff, rather than all drivers. Modern, unbridged
SATA controllers (ahci, sata_sil24) continue to do their own interrupts
based on received packets (FIS's) through the use of the higher level
libata hooks.
Jeff
prev parent reply other threads:[~2006-12-03 13:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-03 10:30 [PATCH] libata: always use polling IDENTIFY Tejun Heo
2006-12-03 11:14 ` Jeff Garzik
2006-12-03 12:34 ` [PATCH RESEND] " Tejun Heo
2006-12-03 12:58 ` Jeff Garzik
2006-12-03 12:56 ` [PATCH] " Alan
2006-12-03 13:02 ` Jeff Garzik [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=4572CAF0.2040806@pobox.com \
--to=jgarzik@pobox.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=htejun@gmail.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 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).