From: Avi Kivity <avi@redhat.com>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [RFC][PATCH 4/9] create aggregate kvm_total_used_mmu_pages value
Date: Thu, 17 Jun 2010 11:23:25 +0300 [thread overview]
Message-ID: <4C19DB7D.5020508@redhat.com> (raw)
In-Reply-To: <1276707300.6437.17429.camel@nimitz>
On 06/16/2010 07:55 PM, Dave Hansen wrote:
> On Wed, 2010-06-16 at 11:48 +0300, Avi Kivity wrote:
>
>>> +static inline void kvm_mod_used_mmu_pages(struct kvm *kvm, int nr)
>>> +{
>>> + kvm->arch.n_used_mmu_pages += nr;
>>> + kvm_total_used_mmu_pages += nr;
>>>
>>>
>> Needs an atomic operation, since there's no global lock here. To avoid
>> bouncing this cacheline around, make the variable percpu and make
>> readers take a sum across all cpus. Side benefit is that you no longer
>> need an atomic but a local_t, which is considerably cheaper.
>>
> We do have the stuff in:
>
> include/linux/percpu_counter.h
>
> the downside being that they're not precise and they're *HUGE* according
> to the comment. :)
>
> It's actually fairly difficult to do a counter which is precise,
> scalable, and works well for small CPU counts when NR_CPUS is large. Do
> you mind if we just stick with a plain atomic_t for now?
>
Do we really need something precise?
I'm not excited by adding a global atomic. So far nothing in the kvm
hot paths depends on global shared memory (though we have lots of per-vm
shared memory).
Can we perhaps query the kmem_cache for a representation of the amount
of objects?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-06-17 8:23 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-15 13:55 [RFC][PATCH 0/9] rework KVM mmu_shrink() code Dave Hansen
2010-06-15 13:55 ` [RFC][PATCH 1/9] abstract kvm x86 mmu->n_free_mmu_pages Dave Hansen
2010-06-16 8:40 ` Avi Kivity
2010-06-15 13:55 ` [RFC][PATCH 2/9] rename x86 kvm->arch.n_alloc_mmu_pages Dave Hansen
2010-06-15 13:55 ` [RFC][PATCH 3/9] replace x86 kvm n_free_mmu_pages with n_used_mmu_pages Dave Hansen
2010-06-16 14:25 ` Marcelo Tosatti
2010-06-16 15:42 ` Dave Hansen
2010-06-15 13:55 ` [RFC][PATCH 4/9] create aggregate kvm_total_used_mmu_pages value Dave Hansen
2010-06-16 8:48 ` Avi Kivity
2010-06-16 15:06 ` Dave Hansen
2010-06-17 8:43 ` Avi Kivity
2010-06-16 16:55 ` Dave Hansen
2010-06-17 8:23 ` Avi Kivity [this message]
2010-06-15 13:55 ` [RFC][PATCH 5/9] break out some mmu_skrink() code Dave Hansen
2010-06-15 13:55 ` [RFC][PATCH 6/9] remove kvm_freed variable Dave Hansen
2010-06-15 13:55 ` [RFC][PATCH 7/9] make kvm_get_kvm() more robust Dave Hansen
2010-06-15 13:55 ` [RFC][PATCH 8/9] reduce kvm_lock hold times in mmu_skrink() Dave Hansen
2010-06-16 8:54 ` Avi Kivity
2010-06-15 13:55 ` [RFC][PATCH 9/9] make kvm mmu shrinker more aggressive Dave Hansen
2010-06-16 9:24 ` Avi Kivity
2010-06-16 15:25 ` Dave Hansen
2010-06-17 8:37 ` Avi Kivity
2010-06-18 15:49 ` Dave Hansen
2010-06-20 8:11 ` Avi Kivity
2010-06-22 16:32 ` Dave Hansen
2010-07-22 4:36 ` Avi Kivity
2010-07-22 5:36 ` Dave Hansen
2010-07-22 5:42 ` Avi Kivity
2010-06-16 8:38 ` [RFC][PATCH 0/9] rework KVM mmu_shrink() code Avi Kivity
2010-06-16 15:03 ` Dave Hansen
2010-06-17 8:40 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C19DB7D.5020508@redhat.com \
--to=avi@redhat.com \
--cc=dave@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).