From: Grant Grundler <grundler@cup.hp.com>
To: davem@redhat.com
Cc: linux-mm@kvack.org
Subject: IOMMU setup vs DAC (PCI)
Date: Fri, 9 Feb 2001 11:39:56 -0800 (PST) [thread overview]
Message-ID: <200102091939.LAA08207@milano.cup.hp.com> (raw)
Dave (Miller),
Matthew Wilcox and I had the following conversation:
<ggg> willy: how do systems which support dual address cycle PCI (ie 64-bit
addressing) access hi-mem (>4GB)? bounce-buffers?
* ggg is wondering if any recent changes define a 64-bit type for dma_addr_t
<willy> ggg: the IOMMU is used to map a 32-bit PCI address to a 64-bit
address-bus address
<ggg> willy: what if I design a board that doesn't *have* an IOMMU?
<willy> except on x86 where bounce buffers get used.
<ggg> IOMMU has a performance cost.
<willy> so does DAC.
<ggg> DAC is cheap compared to IOMMU overhead.
<willy> i'll have to take your word for that.
<ggg> DAC doesn't cost the CPU anything and IOMMU mgt does.
<willy> but how much mgt needs to be done? if you're doing a 4k read from
disc, it's surely cheaper?
<ggg> IOMMU also has to R/W TLB and get flushed in certain circumstances - ie
extra PIO to the IOMMU
<ggg> willy: no way.
<ggg> willy: setup time on IOMMU kills you.
<ggg> try bigger reads and we can argue. I don't know where the tradeoff is for
parisc IOMMU's.
<willy> i'm the wrong person to be arguing with. davem/rth/linus/sct/mingo
are the people.
<ggg> willy: ok.
* ggg sends mail to davem
<willy> linux-mm might be the right list to argue this on.
<ggg> ok. what's the full email addr?
<ggg> vger.kernel.org?
<willy> @kvack.org
<ggg> ok tnx.
My original quest was for an architecturally neutral way to pass
64-bit physical memory addresses back to a 64-bit capable card.
pci_dma_supported() interface provides the right hook for the
driver to advertise device capabilities. dma_addr_t is defined
in most arches (read x86) to be 32-bit. But IA64 (u64) and mips*
(unsigned long) have broken ground here already. I'll explore
further to see if parisc*-linux can in fact use "unsigned long".
But I'm still interested in any comments or insights.
(ie am I out to lunch? ;^)
thanks,
grant
Grant Grundler
parisc-linux {PCI|IOMMU|SMP} hacker
+1.408.447.7253
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next reply other threads:[~2001-02-09 19:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-09 19:39 Grant Grundler [this message]
2001-02-09 19:42 ` David S. Miller
2001-02-09 20:04 ` Grant Grundler
2001-02-09 19:47 ` Kanoj Sarcar
2001-02-09 19:52 ` David S. Miller
2001-02-09 20:07 ` Kanoj Sarcar
2001-02-09 20:23 ` David S. Miller
2001-02-09 21:11 ` Kanoj Sarcar
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=200102091939.LAA08207@milano.cup.hp.com \
--to=grundler@cup.hp.com \
--cc=davem@redhat.com \
--cc=linux-mm@kvack.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