From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: linux-ide@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>,
Tejun Heo <htejun@gmail.com>
Subject: Re: libata and DMA quirks
Date: Fri, 27 Jun 2008 19:31:23 +1000 [thread overview]
Message-ID: <1214559083.8011.544.camel@pasglop> (raw)
In-Reply-To: <4864AE92.2090805@ru.mvista.com>
On Fri, 2008-06-27 at 13:10 +0400, Sergei Shtylyov wrote:
> > It doesn't use DMA to transfer the bulk of ATAPI ? I know it uses PIO
> > for the CDB but the rest of the transfer isn't done with DMA ?
> >
> Like I said, DMA is used only for the *block* transfer commands for
> which the transfer size would always be a multiple of 16 bytes.
Ok, I see. That might explain why I never saw a problem not doing
anything special with drivers/ide.
Cheers,
Ben.
next prev parent reply other threads:[~2008-06-27 9:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-27 6:41 libata and DMA quirks Benjamin Herrenschmidt
2008-06-27 8:37 ` Sergei Shtylyov
2008-06-27 8:51 ` Benjamin Herrenschmidt
2008-06-27 9:10 ` Sergei Shtylyov
2008-06-27 9:31 ` Benjamin Herrenschmidt [this message]
2008-06-27 8:54 ` Alan Cox
2008-06-27 9:29 ` Benjamin Herrenschmidt
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=1214559083.8011.544.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=sshtylyov@ru.mvista.com \
/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