| 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
| ||
|
Date: Tue, 25 Mar 2008 16:49:23 -0700 From: "Luck, Tony" <tony.luck@...el.com> To: "David Miller" <davem@...emloft.net>, <paulus@...ba.org> Cc: <clameter@....com>, <linux-mm@...ck.org>, <linux-kernel@...r.kernel.org>, <linux-ia64@...r.kernel.org>, <torvalds@...ux-foundation.org> Subject: RE: larger default page sizes... > > How do I get gcc to use hugepages, for instance? > > Implementing transparent automatic usage of hugepages has been > discussed many times, it's definitely doable and other OSs have > implemented this for years. > > This is what I was implying. "large" pages, or "super" pages perhaps ... but Linux "huge" pages seem pretty hard to adapt for generic use by applications. They are generally a somewhere between a bit too big (2MB on X86) to way too big (64MB, 256MB, 1GB or 4GB on ia64) for general use. Right now they also suffer from making the sysadmin pick at boot time how much memory to allocate as huge pages (while it is possible to break huge pages into normal pages, going in the reverse direction requires a memory defragmenter that doesn't exist). Making an application use huge pages as heap may be simple (just link with a different library to provide with a different version of malloc()) ... code, stack, mmap'd files are all a lot harder to do transparently. -Tony -- 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