All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: george.dunlap@citrix.com, xen-devel@lists.xensource.com
Cc: kurt.hackel@oracle.com, andrew.thomas@oracle.com
Subject: credit1 scheduler question.
Date: Tue, 7 Feb 2012 15:12:31 -0500	[thread overview]
Message-ID: <20120207201231.GA23813@phenom.dumpdata.com> (raw)

Hey George,

I was wondering if you could explain in simple terms how the scheduler would
handle per-physical CPU when there are say 16 guests (each guest is using
one VCPU), 32 physical CPUs and dom0 is not restricted to any CPUs. Would
the scheduler per physical CPU schedule: guest, dom0, guest, dom0, and so
on; or would it be more random? (I assume that both guest and dom0 would do
a hypercall yield too).

Thanks!

             reply	other threads:[~2012-02-07 20:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-07 20:12 Konrad Rzeszutek Wilk [this message]
2012-02-08 12:18 ` credit1 scheduler question George Dunlap
2012-02-08 14:22   ` Pasi Kärkkäinen
2012-02-08 16:14     ` George Dunlap
2012-02-08 16:36       ` Dario Faggioli
2012-02-09 13:37         ` George Dunlap

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=20120207201231.GA23813@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=andrew.thomas@oracle.com \
    --cc=george.dunlap@citrix.com \
    --cc=kurt.hackel@oracle.com \
    --cc=xen-devel@lists.xensource.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.