| 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
| ||
|
Message-ID: <8739v3kgl6.fsf@basil.nowhere.org> Date: Wed, 28 Jul 2010 13:09:57 +0200 From: Andi Kleen <andi@...stfloor.org> To: FUJITA Tomonori <fujita.tomonori@....ntt.co.jp> Cc: ak@...ux.intel.com, konrad.wilk@...cle.com, akataria@...are.com, lenb@...nel.org, x86@...nel.org, linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org, petr@...are.com Subject: Re: swiotlb detection should be memory hotplug aware ? FUJITA Tomonori <fujita.tomonori@....ntt.co.jp> writes: > >> The other problem is that using only two bits for the needed address >> space is also extremly >> inefficient (4GB and 16MB on x86). Really want masks everywhere and >> optimize for the >> actual requirements. > > swiotlb doesn't allocate GFP_DMA memory. It handles only GFP_DMA32. I was lumping GFP_DMA and swiotlb together here. The pci_alloc_consistent() function uses both interchangedly. They really effectively are the same thing these days and just separated by historical accident. > I have a half-baked patch for it. I'll send it later. The problem are still the *_map users which usually cannot sleep, and then it's difficult to grow. For *_alloc it's relatively easy and to some extend already implemented. -Andi -- ak@...ux.intel.com -- Speaking for myself only. -- 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/
Powered by blists - more mailing lists