From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] 2.4.16-ia64-011128 is missing dma64_addr_t
Date: Tue, 04 Dec 2001 19:55:02 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805607@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805568@msgid-missing>
>>>>> On Tue, 4 Dec 2001 17:18:23 +0100, Christoph Hellwig <hch@caldera.de> said:
Chris> On Tue, Dec 04, 2001 at 08:12:47AM -0800, David Mosberger
Chris> wrote:
>> No, of course not. You that said ia64 should use pci_dac_*()
>> instead of an I/O TLB emulation and I'm saying that this doesn't
>> work because pci_dac_*() is a non-solution.
>>
>> The suggestion is to always use the normal pci_*() mapping
>> routines, independent of whether the platform is 32 or 64 bit.
Chris> Yes and no. Drivers that can and want to use DAC can do that
Chris> on 32bit plattforms now, using the pci_dac_* stuff without
Chris> _any_ IOMMU. This should work on ia64 aswell, even if it's
Chris> native dma_addr_t already is a 64 bit type.
The reason I don't like this very much is that you're assuming that
all DAC-capable devices will be able to address the full 64-bit
address space. That just doesn't seem to be the case. And as soon as
we have machines with larger memories than some of the DAC-capable
devices can address, we're back to pci_dac_*() having to have some
smarts as to whether a direct mapping is possible.
The only extra overhead of going through normal pci mapping routines
is a function call. If that's noticable, you have a very fast device
indeed.
--david
next prev parent reply other threads:[~2001-12-04 19:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-02 3:56 [Linux-ia64] 2.4.16-ia64-011128 is missing dma64_addr_t Keith Owens
2001-12-03 18:23 ` Gérard Roudier
2001-12-03 19:34 ` David Mosberger
2001-12-03 21:29 ` David Mosberger
2001-12-04 17:01 ` Gérard Roudier
2001-12-04 18:15 ` Gérard Roudier
2001-12-04 19:38 ` Gérard Roudier
2001-12-04 19:54 ` David Mosberger
2001-12-04 19:54 ` David Mosberger
2001-12-04 19:54 ` David Mosberger
2001-12-04 19:55 ` David Mosberger [this message]
2001-12-04 19:56 ` David Mosberger
2001-12-04 21:42 ` David Mosberger
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=marc-linux-ia64-105590698805607@msgid-missing \
--to=davidm@hpl.hp.com \
--cc=linux-ia64@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.