| 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: Mon, 14 Jun 2010 23:10:08 +0530 From: Balbir Singh <balbir@...ux.vnet.ibm.com> To: Avi Kivity <avi@...hat.com> Cc: Dave Hansen <dave@...ux.vnet.ibm.com>, kvm <kvm@...r.kernel.org>, linux-mm@...ck.org, linux-kernel@...r.kernel.org Subject: Re: [RFC/T/D][PATCH 2/2] Linux/Guest cooperative unmapped page cache control * Avi Kivity <avi@...hat.com> [2010-06-14 18:34:58]: > On 06/14/2010 06:12 PM, Dave Hansen wrote: > >On Mon, 2010-06-14 at 14:18 +0530, Balbir Singh wrote: > >>1. A slab page will not be freed until the entire page is free (all > >>slabs have been kfree'd so to speak). Normal reclaim will definitely > >>free this page, but a lot of it depends on how frequently we are > >>scanning the LRU list and when this page got added. > >You don't have to be freeing entire slab pages for the reclaim to have > >been useful. You could just be making space so that _future_ > >allocations fill in the slab holes you just created. You may not be > >freeing pages, but you're reducing future system pressure. > > Depends. If you've evicted something that will be referenced soon, > you're increasing system pressure. > I don't think slab pages care about being referenced soon, they are either allocated or freed. A page is just a storage unit for the data structure. A new one can be allocated on demand. -- Three Cheers, Balbir -- 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