From: Matthew Wilcox <matthew@wil.cx>
To: Luben Tuikov <ltuikov@yahoo.com>
Cc: linux-arch@vger.kernel.org, ide <linux-ide@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-scsi@vger.kernel.org, Robert Hancock <hancockr@shaw.ca>
Subject: Re: DMA mapping on SCSI device?
Date: Wed, 30 Jan 2008 22:01:32 -0700 [thread overview]
Message-ID: <20080131050132.GA3836@parisc-linux.org> (raw)
In-Reply-To: <896139.88121.qm@web31812.mail.mud.yahoo.com>
On Tue, Jan 29, 2008 at 02:09:52PM -0800, Luben Tuikov wrote:
> > The ideal solution would be to do mapping against a
> > different struct
> > device for each port, so that we could maintain the proper
> > DMA mask for
> > each of them at all times. However I'm not sure if
> > that's possible. The
> > thought of using the SCSI struct device for DMA mapping was
> > brought up
> > at one point.. any thoughts on that?
>
> The reason for this is that the object that a struct scsi_dev
> represents has nothing to do with HW DMA engines.
It really would work, once the few remaining architectures move away
from asserting that the 'struct device' passed in is a pci device.
It seems like the best way forward to me.
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
prev parent reply other threads:[~2008-01-31 5:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-29 0:08 DMA mapping on SCSI device? Robert Hancock
2008-01-29 3:21 ` Grant Grundler
2008-01-29 3:37 ` Matthew Wilcox
2008-01-29 4:28 ` Andi Kleen
2008-01-29 15:33 ` James Bottomley
2008-01-29 22:23 ` Luben Tuikov
2008-01-29 22:09 ` Luben Tuikov
2008-01-30 2:00 ` Robert Hancock
2008-01-30 16:56 ` Mark Lord
2008-01-30 17:00 ` Mark Lord
2008-01-31 0:09 ` Robert Hancock
2008-01-31 5:01 ` Matthew Wilcox [this message]
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=20080131050132.GA3836@parisc-linux.org \
--to=matthew@wil.cx \
--cc=hancockr@shaw.ca \
--cc=linux-arch@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=ltuikov@yahoo.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;
as well as URLs for NNTP newsgroup(s).