From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jeff Garzik <jeff@garzik.org>,
IDE/ATA development list <linux-ide@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: libata git tree, mbox queue status and contents
Date: Sun, 05 Aug 2007 18:34:08 +0400 [thread overview]
Message-ID: <46B5DFE0.4060008@ru.mvista.com> (raw)
In-Reply-To: <20070803172040.52853316@the-village.bc.nu>
Alan Cox wrote:
>>* Alan: IORDY handling -- upstream whenever Alan is happy
> I'm happy with it from testing. Just a little worried about it going
> upstream mid -rc as it could have a weird side effect somewhere. I've
> verified an original pre ATA IDE drive with it too now 8)
>>* Alan: ACPI checks for 80wire cable -- upstream whenever Alan is happy
> Happy
>>* Albert: irq_on/off. Really need to give this some thought. Not sure
>>I like where this model is going. Polling and twiddling irq on/off
>>should be kept to a minimum, because it's sorta an admission that the
>>host state machine has broken down, and we need to bandaid. Its a
>>bandaid not a root-cause solution.
> I think of it more as an admission that the IDE design is lacking in a
> few areas. No suprise as its an emulation of a 15 year old interface that
> was normally used polled.
Hehe, note that even host polling has always been racy the way ATA spec.
described it: there was noting said about the period whithin which the device
should assert INTRQ after clearing BSY (and the interrupt-pending state wasn't
clearly specified also), so there's a possibility for the fast host to *not*
clear interrupt pending by reading the status reg. with BSY=0 but before the
devie enters interrupt-pending state, and thus possibly stalling the further
transfer.
MBR, Sergei
next prev parent reply other threads:[~2007-08-05 14:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 16:09 libata git tree, mbox queue status and contents Jeff Garzik
2007-08-03 16:20 ` Alan Cox
2007-08-04 8:14 ` Tejun Heo
2007-08-05 14:34 ` Sergei Shtylyov [this message]
2007-08-08 14:42 ` Mark Lord
2007-08-08 16:28 ` Jeff Garzik
2007-08-13 12:09 ` Jens Axboe
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=46B5DFE0.4060008@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--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 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.