From: Dave Hansen <dave@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: kvm@vger.kernel.org, Dave Hansen <dave@linux.vnet.ibm.com>
Subject: [RFC][PATCH 8/9] reduce kvm_lock hold times in mmu_skrink()
Date: Tue, 15 Jun 2010 06:55:29 -0700 [thread overview]
Message-ID: <20100615135528.01AC8966@kernel.beaverton.ibm.com> (raw)
In-Reply-To: <20100615135518.BC244431@kernel.beaverton.ibm.com>
mmu_shrink() is effectively single-threaded since the global
kvm_lock is held over the entire function.
I beleive its only use here is for synchronization of the
vm_list. Instead of using the kvm_lock to ensure
consistency of the list, we instead obtain a kvm_get_kvm()
reference. This keeps the kvm object on the vm_list while
we shrink it.
Since we don't need the lock to maintain the list any more,
we can drop it. We'll reacquire it if we need to get another
object off.
This leads to a larger number of atomic ops, but reduces
lock hold times: the typical latency vs. throughput debate.
Signed-off-by: Dave Hansen <dave@linux.vnet.ibm.com>
---
linux-2.6.git-dave/arch/x86/kvm/mmu.c | 48 ++++++++++++++++++++++++++--------
linux-2.6.git-dave/kernel/profile.c | 2 +
2 files changed, 40 insertions(+), 10 deletions(-)
diff -puN arch/x86/kvm/mmu.c~optimize_shrinker-3 arch/x86/kvm/mmu.c
--- linux-2.6.git/arch/x86/kvm/mmu.c~optimize_shrinker-3 2010-06-11 08:39:17.000000000 -0700
+++ linux-2.6.git-dave/arch/x86/kvm/mmu.c 2010-06-11 08:39:17.000000000 -0700
@@ -2930,7 +2930,8 @@ static int kvm_mmu_remove_some_alloc_mmu
static int shrink_kvm_mmu(struct kvm *kvm, int nr_to_scan)
{
- int idx, freed_pages;
+ int idx;
+ int freed_pages = 0;
idx = srcu_read_lock(&kvm->srcu);
spin_lock(&kvm->mmu_lock);
@@ -2950,23 +2951,50 @@ static int shrink_kvm_mmu(struct kvm *kv
static int mmu_shrink(int nr_to_scan, gfp_t gfp_mask)
{
+ int err;
+ int freed;
struct kvm *kvm;
if (nr_to_scan == 0)
goto out;
+retry:
+ nr_to_scan--;
spin_lock(&kvm_lock);
-
- list_for_each_entry(kvm, &vm_list, vm_list) {
- int freed = shrink_kvm_mmu(kvm, nr_to_scan);
- if (!freed)
- continue;
-
- list_move_tail(&kvm->vm_list, &vm_list);
- break;
+ if (list_empty(&vm_list)) {
+ spin_unlock(&kvm_lock);
+ goto out;
}
-
+ kvm = list_first_entry(&vm_list, struct kvm, vm_list);
+ /*
+ * With a reference to the kvm object, it can not go away
+ * nor get removed from the vm_list.
+ */
+ err = kvm_get_kvm(kvm);
+ /* Did someone race and start destroying the kvm object? */
+ if (err) {
+ spin_unlock(&kvm_lock);
+ goto retry;
+ }
+ /*
+ * Stick this kvm on the end of the list so the next
+ * interation will shrink a different one. Do this here
+ * so that we normally don't have to reacquire the lock.
+ */
+ list_move_tail(&kvm->vm_list, &vm_list);
+ /*
+ * Which lets us release the global lock, holding it for
+ * the minimal amount of time possible, and ensuring that
+ * we don't hold it during the (presumably slow) shrink
+ * operation itself.
+ */
spin_unlock(&kvm_lock);
+ freed = shrink_kvm_mmu(kvm, nr_to_scan);
+
+ kvm_put_kvm(kvm);
+
+ if (!freed && nr_to_scan > 0)
+ goto retry;
out:
return kvm_total_used_mmu_pages;
diff -puN virt/kvm/kvm_main.c~optimize_shrinker-3 virt/kvm/kvm_main.c
diff -puN kernel/profile.c~optimize_shrinker-3 kernel/profile.c
--- linux-2.6.git/kernel/profile.c~optimize_shrinker-3 2010-06-11 09:09:43.000000000 -0700
+++ linux-2.6.git-dave/kernel/profile.c 2010-06-11 09:12:24.000000000 -0700
@@ -314,6 +314,8 @@ void profile_hits(int type, void *__pc,
if (prof_on != type || !prof_buffer)
return;
pc = min((pc - (unsigned long)_stext) >> prof_shift, prof_len - 1);
+ if ((pc == prof_len - 1) && printk_ratelimit())
+ printk("profile_hits(%d, %p, %d)\n", type, __pc, nr_hits);
i = primary = (pc & (NR_PROFILE_GRP - 1)) << PROFILE_GRPSHIFT;
secondary = (~(pc << 1) & (NR_PROFILE_GRP - 1)) << PROFILE_GRPSHIFT;
cpu = get_cpu();
_
next prev parent reply other threads:[~2010-06-15 13:55 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
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 ` Dave Hansen [this message]
2010-06-16 8:54 ` [RFC][PATCH 8/9] reduce kvm_lock hold times in mmu_skrink() 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=20100615135528.01AC8966@kernel.beaverton.ibm.com \
--to=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