From: Avi Kivity <avi@redhat.com>
To: Matty <matty91@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: slow guest performance with build load, looking for ideas
Date: Sun, 05 Jul 2009 11:07:24 +0300 [thread overview]
Message-ID: <4A505F3C.2090202@redhat.com> (raw)
In-Reply-To: <8bfce36e0907030341x32629f4er4bffc972a65c2e38@mail.gmail.com>
On 07/03/2009 01:41 PM, Matty wrote:
>> What is the host cpu type? On pre-Nehalem/Barcelona processors kvm has poor
>> scalability in mmu intensive workloads like kernel builds.
>>
>
> Hey Avi,
>
> Are there plans to address these scalability issues for
> pre-Nehalem/Barcelona processors? I poked around the KVM website, and
> I don't see anything related to this.
>
Not really. While it is possible to scale the kvm mmu for these older
processors, I don't think it's really worthwhile in terms of effort and
complexity vs. return.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2009-07-05 8:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 21:04 slow guest performance with build load, looking for ideas Erik Jacobson
2009-06-14 9:33 ` Avi Kivity
2009-06-15 14:15 ` Erik Jacobson
2009-06-15 14:24 ` Avi Kivity
2009-06-15 15:25 ` Michael Tokarev
2009-06-15 15:27 ` Avi Kivity
2009-06-16 7:03 ` Michael Tokarev
2009-06-16 8:07 ` Avi Kivity
2009-06-18 23:07 ` Erik Jacobson
2009-06-28 14:17 ` Avi Kivity
2009-06-28 19:05 ` Erik Jacobson
2009-06-28 21:28 ` Avi Kivity
2009-07-01 21:41 ` Erik Jacobson
2009-07-02 5:48 ` Avi Kivity
2009-07-02 9:41 ` Avi Kivity
2009-07-03 15:43 ` Mark McLoughlin
2009-07-03 16:28 ` Erik Jacobson
2009-07-09 2:36 ` Erik Jacobson
2009-07-09 7:48 ` Avi Kivity
2009-07-09 18:01 ` Erik Jacobson
2009-07-12 8:38 ` Avi Kivity
2009-07-16 12:20 ` Jes Sorensen
2009-07-25 14:33 ` Avi Kivity
2009-07-03 10:41 ` Matty
2009-07-05 8:07 ` Avi Kivity [this message]
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=4A505F3C.2090202@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=matty91@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.