All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nauman Rafique" <naumanr@gmail.com>
To: xen-devel@lists.xensource.com
Subject: CPU scheduling of domains and vcpus
Date: Mon, 21 Apr 2008 13:52:21 -0400	[thread overview]
Message-ID: <1301abeb0804211052i2c498568ue1a761ae8a618029@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 821 bytes --]

My question is related to an earlier discussion on the list (
http://lists.xensource.com/archives/html/xen-devel/2007-03/msg01395.html).
Is there any plan for implementing gang scheduling (of all vcpus of a
domain) in xen? I see that gang scheduling is mentioned in almost all the
latest talks about xen (posted on xen.org).
It seems to me that gang scheduling would be desirable, specially if there
are synchronization points (lock and semaphores) in guest OS and
applications. I understand that gang scheduling can lead to wasted cycles,
but that might be acceptable in certain situations. In fact, wasted cycles
can probably be avoided by doing opportunisitic gang scheduling (i.e. gang
schedule, unless there would be wasted cycles) and by carefully choosing the
number of vcpus.

--
Nauman Rafique
Purdue University

[-- Attachment #1.2: Type: text/html, Size: 962 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

             reply	other threads:[~2008-04-21 17:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-21 17:52 Nauman Rafique [this message]
2008-04-21 17:56 ` CPU scheduling of domains and vcpus Samuel Thibault
2008-04-21 20:32   ` Mike D. Day
2008-04-21 21:34     ` Samuel Thibault
2008-04-22 18:34       ` Nauman Rafique

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=1301abeb0804211052i2c498568ue1a761ae8a618029@mail.gmail.com \
    --to=naumanr@gmail.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.