| 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: Wed, 11 Apr 2007 17:23:00 -0700 From: "David Schwartz" <davids@...master.com> To: <linux-kernel@...r.kernel.org> Subject: RE: Help Understanding Linux memory management > 1) When physical memory runs low, the memory manager will try to use > memory currently allocated to the pagecache. Is this true? Yes. > 2) When vm.overcommit_memory = 2 (overcommit disabled), and memory runs > low, it appears that the memory manager does not try to use memory > currently allocated to pagecache. Is this true? It does try, that doesn't mean it will succeed. If overcommit is disabled, the OS must have enoug (RAM+swap) to handle the maximum memory consumption is has allowed to take place. Perhaps you are laboring under the incorrect assumption that the pagecache can always be shrunk to zero? Not all the data in the pagecache is discardable. For example, any page that has been modified from its disk copy cannot be discarded. > 3) Is it possible to disable the pagecache? No, because huge amounts of capability would become impossible. It is not even clear to me how you could execute self-modifying code without a pagecache. DS - 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