From: Anthony Liguori <anthony@codemonkey.ws>
To: alex <tomorrowanewday@gmail.com>
Cc: avi@redhat.com, kvm@vger.kernel.org
Subject: Re: Is guest OS oriented scheduling welcome?
Date: Fri, 24 Apr 2009 08:16:54 -0500 [thread overview]
Message-ID: <49F1BBC6.4010906@codemonkey.ws> (raw)
In-Reply-To: <820ac2e90904232310g48a978f0wb482deae064aed97@mail.gmail.com>
alex wrote:
> just now, I tried cgroup. I admit that as far as only CPU share is
> concerned, cgroup is enough.
>
> However, AFAIK Linux schedules each thread independently, ignoring the
> upper level logic.
>
> for example, suppose VM1 is an SMP one, and it is used to receive
> network packets, which causes it run the TCP/IP stack code frequently.
> The use of spin-lock implies that the lock holder will release it
> fast. However, when vcpu threads are scheduled independently, when one
> vcpu is spinning, the lock holder might be off the CPU! This would
> make the VM's SMP scalability bad.
>
Sure, but credit doesn't do gang scheduling either.
Instead of gang scheduling, I think the best solution to this problem is
spin lock paravirtualization.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-04-24 13:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 6:10 Re:Re: Is guest OS oriented scheduling welcome? alex
2009-04-24 13:16 ` Anthony Liguori [this message]
[not found] <1060494.867561240402736300.JavaMail.coremail@app167.163.com>
2009-04-22 12:22 ` Avi Kivity
2009-04-22 12:34 ` Daniel P. Berrange
2009-04-24 0:19 ` Anthony Liguori
2009-04-24 2:55 ` Andrew de Andrade
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=49F1BBC6.4010906@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=tomorrowanewday@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox