linux-kernel - Re: [openib-general] Suggestions for how to remove bus_to

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20060714.153503.123972494.davem@davemloft.net>
Date:	Fri, 14 Jul 2006 15:35:03 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	ralphc@...hscale.com
Cc:	muli@...ibm.com, rdreier@...co.com, linux-kernel@...r.kernel.org,
	openib-general@...nib.org
Subject: Re: [openib-general] Suggestions for how to remove bus_to_virt()

From: Ralph Campbell <ralphc@...hscale.com>
Date: Fri, 14 Jul 2006 15:27:07 -0700

> Note that the current design only supports one IOMMU type in a system.
> This could support multiple IOMMU types at the same time.

This is not true, the framework allows multiply such types
and in fact Sparc64 takes advantage of this.  We have about
4 or 5 different PCI controllers, and the IOMMUs are slightly
different in each.

Even with the standard PCI DMA mapping calls, we can gather the
platform private information necessary to program the IOMMU
appropriately for a given chipset.

The dma_mapping_ops idea will never get accepted by folks like Linus,
for reasons I've outlined in previous emails in this thread.  So, it's
best to look elsewhere for solutions to your problem, such as the
ideas used by the USB and IEE1394 device layers.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/