From: Mark Lord <liml@rtr.ca>
To: Tejun Heo <htejun@gmail.com>, Jeff Garzik <jgarzik@pobox.com>,
IDE/ATA development list <linux-ide@vger.kernel.org>,
Alan Cox <alan@redhat.com>
Subject: ata_std_qc_defer not good enough for FIS-based switching ?
Date: Mon, 28 Apr 2008 17:06:37 -0400 [thread overview]
Message-ID: <48163C5D.9050605@rtr.ca> (raw)
Tejun,
I've been trying to track down interrupt timeouts here with sata_mv,
and I think I've found the problem
With a Marvell 7042 chip and a port-multiplier, the driver selects
.qc_defer = ata_std_qc_defer, which is supposed to be correct for FIS-based switching.
But.. There is a mix of NCQ and non-NCQ drives plugged into that PM,
and ata_std_qc_defer() seems happy to mix things up by issuing NCQ commands
to some ports while simultaneously sending non-NCQ commands to other ports.
Needless to say, this confuses the heck out of the hardware,
which cannot tolerate non-NCQ commands in FIS-based switching mode,
or NCQ commands in non FIS-based switching mode.
Are there controllers which *can* handle such a mix (ahci, sil24 ?)
So it looks like a I need a .qc_defer() function which examines all links
from the common host port for activity, and then asks for command deferral
when the new command has a different protocol than those that are outstanding.
Weird that none of the other LLDs need this. Or do they?
Cheers
next reply other threads:[~2008-04-28 21:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 21:06 Mark Lord [this message]
2008-04-28 22:08 ` ata_std_qc_defer not good enough for FIS-based switching ? Mark Lord
2008-04-28 23:11 ` Tejun Heo
2008-04-28 23:42 ` Mark Lord
2008-04-29 1:18 ` Tejun Heo
2008-04-29 2:26 ` Mark Lord
2008-05-14 14:11 ` Tejun Heo
2008-05-14 14:45 ` Mark Lord
2008-05-14 14:53 ` Mark Lord
2008-05-14 15:50 ` Mark Lord
2008-05-14 15:59 ` Mark Lord
2008-05-15 7:12 ` Tejun Heo
2008-05-15 6:51 ` Tejun Heo
2008-04-29 17:09 ` Mark Lord
2008-04-29 17:17 ` Mark Lord
2008-04-30 9:38 ` Tejun Heo
2008-04-30 14:02 ` Mark Lord
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=48163C5D.9050605@rtr.ca \
--to=liml@rtr.ca \
--cc=alan@redhat.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.