From: Jeff Garzik <jeff@garzik.org>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] libsas, aic94xx: fix dma mapping cockups with ATA
Date: Mon, 16 Jul 2007 16:19:14 -0400 [thread overview]
Message-ID: <469BD2C2.4040002@garzik.org> (raw)
In-Reply-To: <1184611264.3447.28.camel@localhost.localdomain>
James Bottomley wrote:
> This one was noticed by Gilbert Wu of Adaptec:
>
> The libata core actually does the DMA mapping for you, so there has to
> be an exception in the device drivers that *don't* do dma mapping for
> ATA commands. However, since we've already done this, libsas must now
> dma map any ATA commands that it wishes to issue ... and yes, this is a
> horrible mess.
Can you help me understand this logic?
libsas must DMA map an ATA command... because libata also DMA maps an
ATA command? That does not make sense to me.
Jeff
next prev parent reply other threads:[~2007-07-16 20:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 18:41 [PATCH] libsas, aic94xx: fix dma mapping cockups with ATA James Bottomley
2007-07-16 20:19 ` Jeff Garzik [this message]
2007-07-16 20:21 ` James Bottomley
2007-07-16 21:42 ` 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=469BD2C2.4040002@garzik.org \
--to=jeff@garzik.org \
--cc=James.Bottomley@SteelEye.com \
--cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).