From: "Daniel P. Berrange" <berrange@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: ????????? <aleck_liu@163.com>,
kvm@vger.kernel.org, anthony@codemonkey.ws
Subject: Re: Is guest OS oriented scheduling welcome?
Date: Wed, 22 Apr 2009 13:34:20 +0100 [thread overview]
Message-ID: <20090422123420.GB14705@redhat.com> (raw)
In-Reply-To: <49EF0C1E.2060203@redhat.com>
On Wed, Apr 22, 2009 at 03:22:54PM +0300, Avi Kivity wrote:
> ????????? wrote:
> >Hello folks,
> >In the past, it was said KVM would like to treat the guest OS threads
> >differently in scheduling. However, till now, the qemu thread is regarded
> >as a conventional user thread. Therefore, it is hard to control how much
> >CPU slices one guest OS can utilize. I don't think a computing cloud
> >provider likes this idea.
Although the standard scheduler tunables are per thread, it is possible
to put each QEMU process into a separate CGroup, and use the cpu_shares
tunable to control scheduling priority of the guest as a whole, instead
of individual threads. Not sure it this is sufficient for what you
want, but it is one possible option for guest scheduling..
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
next prev parent reply other threads:[~2009-04-22 12:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1060494.867561240402736300.JavaMail.coremail@app167.163.com>
2009-04-22 12:22 ` Is guest OS oriented scheduling welcome? Avi Kivity
2009-04-22 12:34 ` Daniel P. Berrange [this message]
2009-04-24 0:19 ` Anthony Liguori
2009-04-24 2:55 ` Andrew de Andrade
2009-04-24 6:10 alex
2009-04-24 13:16 ` Anthony Liguori
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=20090422123420.GB14705@redhat.com \
--to=berrange@redhat.com \
--cc=aleck_liu@163.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=kvm@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