Linux ATA/IDE development
 help / color / mirror / Atom feed
From: Pat LaVarre <p.lavarre@ieee.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: when limited to a single DRQ block per disk transaction
Date: 14 May 2004 14:12:18 -0600	[thread overview]
Message-ID: <1084565538.3084.27.camel@patibmrh9> (raw)
In-Reply-To: <40A522F8.2080904@pobox.com>

Jeff G:

> This limit does not apply to DMA.
> Only to PIO, PIO multi, and ATAPI PIO.

Understood.

> > Do we mean to be discussing a limit of one PATA DRQ INTRQ per CDB?
> 
> Correct.
> 
> If DRQ block size is 16 sectors, then each CDB is limited to a maximum 
> of 16 sectors.

To me, the limit looks worse than that.  [If I still don't get this in
your next reply, I'll now volunteer to wait a day before I reply again
in this thread.]

In PATA ATA PIO, distinct from ATAPI PIO, to guarantee at most one PATA
DRQ INTRQ per CDB when reading or writing more than one LBA/CDB, we have
to resort to ops x C4 C5 C6 = "READ MULTIPLE", "WRITE MULTIPLE", "SET
MULTIPLE MODE".  linux-2.6.6-bk1/include/linux/* gives these ops the
names WIN_SETMULT WIN_MULTREAD WIN_MULTWRITE.

In PATA ATAPI PIO, distinct from ATA PIO, we cannot guarantee at most
one PATA DRQ INTRQ per CDB, unless we limit the host to reading at most
one LBA/CDB, because the ATAPI device may issue more than the minimum
number of INTRQ that a chosen byte count limit guarantees.

Therefore the AHCI limit of at most one PATA DRQ INTRQ per CDB is in
effect an abolition of ATAPI PIO block i/o, except for the mostly
theoretical possibility of hosts and devices that together tolerate the
overhead of shattering a stream into single blocks.

Else I've misunderstood something vital.

Pat LaVarre



  reply	other threads:[~2004-05-14 20:12 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           ` when limited to a single DRQ block per disk transaction Pat LaVarre
2004-05-14 19:50             ` Jeff Garzik
2004-05-14 20:12               ` Pat LaVarre [this message]
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=1084565538.3084.27.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