From: Tejun Heo <htejun@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Mikael Pettersson <mikpe@it.uu.se>,
Jeff Norden <jeff@math.tntech.edu>,
alan@redhat.com, linux-kernel@vger.kernel.org,
Albert CC Lee <albertcc@tw.ibm.com>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: [PATCH 1/1] pata_it821x: fix lost interrupt with atapi devices
Date: Mon, 17 Sep 2007 07:00:03 +0200 [thread overview]
Message-ID: <46EE09D3.9010201@gmail.com> (raw)
In-Reply-To: <20070906013929.1621849d@the-village.bc.nu>
[cc'ing Albert and linux-ide]
Alan Cox wrote:
> /from the media. */
>> > + if (qc->nbytes < 2048)
>> > + return -EOPNOTSUPP;
>> > +
>> > /* No ATAPI DMA in smart mode */
>> > if (itdev->smart)
>> > return -EOPNOTSUPP;
>> >
>>
>> This looks like a gross hack. Aren't you supposed to inspect
>> the command instead and whitelist the ones you know are OK,
>> like pata_pdc2027x.c and sata_promise.c do?
>
> It does seem to be about transfer size in the IT821x case not commands.
> It may be to do with how we issue ATAPI command transfer sizes from high
> up (patch went to Jeff) but for now this is definitely the right approach
>
> Reviewed-by: Alan Cox <alan@redhat.com>
I wonder whether we should be using similar check in generic path too.
We have quite a few cases where MWDMA ATAPI devices choking on commands
with small transfer sizes. I don't think we'll experience significant
performance regression with this applied and even if there is some, it's
far better to have slightly slower working device.
What do you guys think?
--
tejun
next parent reply other threads:[~2007-09-17 8:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200709041607.l84G7KsT032647@norden.math.tntech.edu>
[not found] ` <18141.42848.537873.349518@alkaid.it.uu.se>
[not found] ` <20070906013929.1621849d@the-village.bc.nu>
2007-09-17 5:00 ` Tejun Heo [this message]
2007-09-17 10:00 ` [PATCH 1/1] pata_it821x: fix lost interrupt with atapi devices Jeff Garzik
2007-09-17 11:46 ` Tejun Heo
2007-09-18 9:14 ` Alan Cox
2007-09-18 9:07 ` Alan Cox
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=46EE09D3.9010201@gmail.com \
--to=htejun@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alan@redhat.com \
--cc=albertcc@tw.ibm.com \
--cc=jeff@math.tntech.edu \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
/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).