| 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: <871velawrn.fsf@basil.nowhere.org> Date: Mon, 12 Apr 2010 10:41:00 +0200 From: Andi Kleen <andi@...stfloor.org> To: ebiederm@...ssion.com (Eric W. Biederman) Cc: tek-life <teklife.kernel@...il.com>, dhazelton@...er.net, oliver@...kum.org, linux-kernel@...r.kernel.org Subject: Re: Can we remove the Zone_DMA? ebiederm@...ssion.com (Eric W. Biederman) writes: Revisiting old posts. Sorry for digging up this old thread from its grave. > Ultimately I don't see much point in disabling ZONE_DMA. It is a lot of > work to track down if it is really needed, and it only costs 16MB. So > unless someone shows me that ZONE_DMA triggers the OOM killer unnecessarily > or otherwise impacts the system what does legacy code hurt? It has quite a lot of impact on slab for example. The main users today are mostly some users who need to have less tha 4GB on 64bit systems. The problem is for those often 16MB is not enough. So on many systems 16MB is too much and on others it isn't enough. A long time ago I had a patchkit to replace it with a range allocator, merge it with softiotlb and replace all the allocations with real masks. It never got quite merged and still needed some more work. ftp://firstfloor.org/pub/ak/dma/INTRO All the issues described in the INTRO are still there. -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