| 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: <20060802153316.7813.qmail@web25813.mail.ukl.yahoo.com> Date: Wed, 2 Aug 2006 15:33:16 +0000 (GMT) From: moreau francis <francis_moreau2000@...oo.fr> To: Alan Cox <alan@...rguk.ukuu.org.uk> Cc: linux-kernel@...r.kernel.org, apw@...dowen.org Subject: Re : sparsemem usage Hi Alan ! Alan Cox wrote: > The kernel allocates memory out using groups of blocks in a buddy > system. 128K is smaller than one of the blocks so the kernel cannot > handle this. As I wrote to Andy Whitcroft, I would think that the kernel forbid allocation of blocks whose size is greater than the current memorysize. But I know nothing about the buddy allocator so I trust you ;) > You need 2MB (if I remember right) granularity for your MAX_ORDER is by default 11. Without changing this, I would say that I need 4MB granularity. > sections but nothing stops you marking most of the 2Mb section except > the 128K that exists as "in use" ok. But it will make pfn_valid() return "valid" for page beyond the first 128 KB. Won't that result in bad impacts later ? thanks Francis - 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