From: "David S. Miller" <davem@redhat.com>
To: Grant Grundler <grundler@cup.hp.com>
Cc: linux-mm@kvack.org
Subject: Re: IOMMU setup vs DAC (PCI)
Date: Fri, 9 Feb 2001 11:42:56 -0800 (PST) [thread overview]
Message-ID: <14980.18496.329382.393791@pizda.ninka.net> (raw)
In-Reply-To: <200102091939.LAA08207@milano.cup.hp.com>
Grant Grundler writes:
> 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? ;^)
You are going into unchartered territory. IA64 supports 64-bit
DMA as a HACK at best (see qla20xx driver) and uses a software
iommu implementation to handle all normal drivers using the
supported 32-bit pci_*() interfaces.
The 64-bit support API will appear in 2.5.x, no sooner.
And all that talk of IOMMU overhead assumes a shit implementation of
TLB flushing. With a sane setup you only flush once per circle walk
of the page tables, see the tricks in sparc64/kernel/pci_iommu.c to
see what I'm talking about. I can push 2 gigabytes to a disk over
SCSI and only take 18 PIOs to the IOMMU. Also, many IOMMU based PCI
implementations do not offer the software managed
prefetching/write-behind facilities when 64-bit DAC is used.
I say stay at 32-bit IOMMU based stuff for now.
Later,
David S. Miller
davem@redhat.com
--
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 prev parent reply other threads:[~2001-02-09 19:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-09 19:39 Grant Grundler
2001-02-09 19:42 ` David S. Miller [this message]
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=14980.18496.329382.393791@pizda.ninka.net \
--to=davem@redhat.com \
--cc=grundler@cup.hp.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