From: Andi Kleen <ak@suse.de>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-arch@vger.kernel.org, ide <linux-ide@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-scsi@vger.kernel.org
Subject: Re: DMA mapping on SCSI device?
Date: Tue, 29 Jan 2008 05:28:00 +0100 [thread overview]
Message-ID: <200801290528.00934.ak@suse.de> (raw)
In-Reply-To: <479E6E8C.2090501@shaw.ca>
> 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.
I cannot imagine why it should be that difficult. The PCI subsystem
could over a pci_clone_device() or similar function. For all complicated
purposes (sysfs etc) the original device could be used, so it would
be hopefully not that difficult.
The alternative would be to add a new family of PCI mapping
functions that take an explicit mask. Disadvantage would be changing
all architectures, but on the other hand the interface could be phase
in one by one (and nF4 primarily only works on x86 anyways)
I suspect the later would be a little cleaner, although they don't
make much difference.
-Andi
next prev parent reply other threads:[~2008-01-29 4:28 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 [this message]
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
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=200801290528.00934.ak@suse.de \
--to=ak@suse.de \
--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 \
/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).