linux-kernel - Re: RFC: Removal of pci_dma

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <20061124.135115.26533586.davem@davemloft.net>
Date:	Fri, 24 Nov 2006 13:51:15 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	ralf@...ux-mips.org
Cc:	linux-kernel@...r.kernel.org
Subject: Re: RFC: Removal of pci_dma_* functions

From: Ralf Baechle <ralf@...ux-mips.org>
Date: Fri, 24 Nov 2006 17:03:59 +0000

> A grep for
> 
>   pci_dac_dma_supported()
>   pci_dac_page_to_dma()
>   pci_dac_dma_to_page()
>   pci_dac_dma_to_offset()
>   pci_dac_dma_sync_single_for_cpu()
>   pci_dac_dma_sync_single_for_device()
> 
> reveals that only a some platforms implement these functions and there seems
> to be no single user.  Any objections against removing?  Or why did we ever
> add them anyay ...

They were meant for things like those Dolphin clustering cards that
can map arbitrary amounts of remote memory on the local system.

Unfortunately, none of the drivers for these things are upstream, but
I can nearly guarentee you that those drivers use these interfaces
because they map so much memory that they cannot tolerate the
limitations imposed by IOMMUs, even the ones with 2GB mapping windows
like on sparc64.
-
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/