linux-kernel - Re: [Intel IOMMU][patch 8/8] Preserve some Virtual Address when devices cannot address entire range.

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: <200704250855.49242.ak@suse.de>
Date:	Wed, 25 Apr 2007 08:55:48 +0200
From:	Andi Kleen <ak@...e.de>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	David Miller <davem@...emloft.net>, ashok.raj@...el.com,
	linux-kernel@...r.kernel.org, akpm@...l.org, gregkh@...e.de,
	muli@...ibm.com, asit.k.mallick@...el.com,
	suresh.b.siddha@...el.com, anil.s.keshavamurthy@...el.com,
	arjan@...ux.intel.com, shaohua.li@...el.com
Subject: Re: [Intel IOMMU][patch 8/8] Preserve some Virtual Address when devices cannot address entire range.

On Wednesday 25 April 2007 03:12:51 H. Peter Anvin wrote:

> You can probably find almost any possible bitmask if you look long 
> enough.  Hardware vendors are notorious for this kind of "optimizations".

The nice thing is if this was solved in the IOMMU code then we could drop
(or not initialize) GFP_DMA on systems with that hardware. I guess GFP_DMA32 
would still need to stay for the graphics devices though.

Not sure how much difference it would make though, but at least Christoph Lameter
seems to think it would.

-Andi
-
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/