| 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: <45BBCFE9.5010600@redhat.com> Date: Sat, 27 Jan 2007 17:19:21 -0500 From: Rik van Riel <riel@...hat.com> To: Andrew Morton <akpm@...l.org> CC: Christoph Lameter <clameter@....com>, Nick Piggin <nickpiggin@...oo.com.au>, linux-mm@...ck.org, linux-kernel@...r.kernel.org Subject: Re: [RFC] Track mlock()ed pages Andrew Morton wrote: > Of course it would. But how do you know it is "too expensive"? We "scan > all the vmas mapping a page" as a matter of course in the page scanner - > millions of times a minute. If that's "too expensive" then ouch. We can do it lazily. At mlock time, move pages onto the mlocked list, unless they are there already. On munlock, move pages to the active list. For mlock-only memory (shared memory segments?) we could add a simple check to see if the next process on the list has the page mlocked, checking only that one. While scanning the active list, move mlocked pages that are found back onto the mlocked list. This lazy movement of pages will impact shared libraries, but probably not shared memory segments. Does this sound workable? -- Politics is the struggle between those who want to make their country the best in the world, and those who believe it already is. Each group calls the other unpatriotic. - 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