From: Pat LaVarre <p.lavarre@ieee.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-ide@vger.kernel.org
Subject: when limited to a single DRQ block per disk transaction
Date: 14 May 2004 13:37:35 -0600 [thread overview]
Message-ID: <1084563455.8752.49.camel@patibmrh9> (raw)
In-Reply-To: <40A51604.8070208@pobox.com>
Jeff G:
> > > Re: SATA ATAPI work in progress
> > > ...
> > > some AHCI SATA controllers can only transfer a _single_ DRQ block
> > > per disk transaction. In anticipation of the demise
> > > of PIO, no doubt :)
> ...
> for controllers that are limited to a single DRQ block per
> disk transaction,
Please can you say which controllers exhibit this limitation?
> the OS driver _must_ limit each ATA taskfile to no
> more than a DRQ block's worth of sector. If the ATAPI byte count limit
> is 8K, then the OS driver must guarantee that a single ATA taskfile does
> not transfer more than 8K.
Please can you give an example of a disk transaction that doesn't work
on some controllers?
I ask because I think somehow even this late in our thread I do not yet
understand what the limitation under discussion is.
Do we mean to be discussing a limit of one PATA DRQ INTRQ per CDB?
Pat LaVarre
next prev parent reply other threads:[~2004-05-14 19:37 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 20:20 SATA ATAPI work in progress Pat LaVarre
2004-05-12 20:40 ` Jeff Garzik
2004-05-12 23:14 ` Pat LaVarre
2004-05-13 15:07 ` Pat LaVarre
2004-05-13 20:56 ` Jeff Garzik
2004-05-13 21:16 ` Jeff Garzik
2004-05-13 21:25 ` Jeff Garzik
2004-05-13 21:36 ` Pat LaVarre
2004-05-13 21:44 ` Jeff Garzik
2004-05-13 21:49 ` Jeff Garzik
2004-05-14 18:23 ` Pat LaVarre
2004-05-14 18:55 ` Jeff Garzik
2004-05-14 19:37 ` Pat LaVarre [this message]
2004-05-14 19:50 ` when limited to a single DRQ block per disk transaction Jeff Garzik
2004-05-14 20:12 ` Pat LaVarre
2004-05-14 23:47 ` SATA ATAPI work in progress Pat LaVarre
2004-05-15 0:02 ` Pat LaVarre
2004-05-15 0:38 ` Jeff Garzik
2004-05-15 13:06 ` Pat LaVarre
2004-05-15 13:49 ` Pat LaVarre
2004-05-15 15:27 ` Jeff Garzik
2004-05-15 15:49 ` Pat LaVarre
2004-05-15 15:56 ` Pat LaVarre
2004-05-15 16:04 ` Pat LaVarre
2004-05-15 16:32 ` Jeff Garzik
2004-05-15 16:43 ` Pat LaVarre
2004-05-15 16:50 ` Pat LaVarre
2004-05-15 16:30 ` Jeff Garzik
2004-05-15 0:46 ` [PATCH] " Jeff Garzik
2004-05-15 13:08 ` Pat LaVarre
2004-05-15 13:10 ` Pat LaVarre
2004-05-15 14:13 ` Pat LaVarre
2004-05-14 18:28 ` Pat LaVarre
2004-05-14 18:38 ` Jeff Garzik
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=1084563455.8752.49.camel@patibmrh9 \
--to=p.lavarre@ieee.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox