linux-kernel - Re: [RFC][PATCH 1/9] abstract kvm x86 mmu->n_free_mmu

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4C188E08.3060806@redhat.com>
Date:	Wed, 16 Jun 2010 11:40:40 +0300
From:	Avi Kivity <avi@...hat.com>
To:	Dave Hansen <dave@...ux.vnet.ibm.com>
CC:	linux-kernel@...r.kernel.org, kvm@...r.kernel.org
Subject: Re: [RFC][PATCH 1/9] abstract kvm x86 mmu->n_free_mmu_pages

On 06/15/2010 04:55 PM, Dave Hansen wrote:
> First of all, I think "free" is a poor name for this value.  In
> this context, it means, "the number of mmu pages which this kvm
> instance should be able to allocate."  To me, "free" implies
> much more that the objects are there and ready for use.  I think
> "available" is a much better description, especially when you
> see how it is calculated.
>
>    

Agreed.  Note that if reclaim is improved, we can drop it completely and 
let the kernel trim the cache when it grows too large.

-- 
error compiling committee.c: too many arguments to function

--
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/