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:56:21 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805605@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805568@msgid-missing>
>>>>> On Tue, 4 Dec 2001 17:29:32 +0100, Christoph Hellwig <hch@caldera.de> said:
Christoph> The problem is that we need a uniform API on all Linux
Christoph> plattforms. Linus has decided on this one, may it be
Christoph> nice or not. (And I don't really like the pci_dac_* part
Christoph> as it is to implementation-specific).
>> 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.
Christoph> On IA64 yes, on i386 or other 32bit plattforms not.
Then fix those implementations. There is nothing difficult in first
checking the DMA mask.
Look, this is precisely why I'm reluctant to add the pci_dac*()
support now: people will use it in the wrong way and eventually we'll have
to add yet another layer of mapping underneath pci_dac_*().
pci_dac_*() is not intended for all DAC-capable devices. It is
intended for DAC capable devices that generate tons of mappings. If
you don't believe me, check with Dave Miller.
--david
next prev parent reply other threads:[~2001-12-04 19:56 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
2001-12-04 19:56 ` David Mosberger [this message]
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-105590698805605@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox