From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ian Pratt <Ian.Pratt@eu.citrix.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
"Tian, Kevin" <kevin.tian@intel.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [RFC] Scheduler work, part 1: High-level goals and interface.
Date: Fri, 10 Apr 2009 10:34:45 -0700 [thread overview]
Message-ID: <49DF8335.7030501@goop.org> (raw)
In-Reply-To: <4FA716B1526C7C4DB0375C6DADBC4EA34172EC1C9C@LONPMAILBOX01.citrite.net>
Ian Pratt wrote:
> 1. explicitly present HT to guests and gang schedule threads
>
> 2. normal free-for-all with HT aware accounting.
>
> Of course, #1 isn't optimal if guests may migrate between HT and non-HT systems.
>
Well, we could extend vcpu hotplug to deal with those kinds of cpu
topology changes, but I guess that doesn't help most Windows/hvm
guests. But I think if those vcpus stop being siblings, I don't think
it would hurt if we stopped gang scheduling them, so long as they're
kept close (same package, I guess).
J
next prev parent reply other threads:[~2009-04-10 17:34 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 15:58 [RFC] Scheduler work, part 1: High-level goals and interface George Dunlap
2009-04-09 18:41 ` Jeremy Fitzhardinge
2009-04-10 0:33 ` Tian, Kevin
2009-04-10 16:15 ` Jeremy Fitzhardinge
2009-04-10 17:16 ` Ian Pratt
2009-04-10 17:19 ` Jeremy Fitzhardinge
2009-04-11 10:00 ` Tian, Kevin
2009-04-15 15:47 ` George Dunlap
2009-04-15 13:54 ` George Dunlap
2009-04-15 16:23 ` Jeremy Fitzhardinge
2009-04-10 17:34 ` Jeremy Fitzhardinge [this message]
2009-04-11 9:57 ` Tian, Kevin
2009-04-11 17:11 ` Ian Pratt
2009-04-12 6:27 ` Tian, Kevin
2009-04-11 9:52 ` Tian, Kevin
2009-04-15 15:56 ` George Dunlap
2009-04-16 5:11 ` Tian, Kevin
2009-04-16 10:27 ` George Dunlap
2009-04-16 14:10 ` Dan Magenheimer
2009-04-16 16:32 ` Jeremy Fitzhardinge
2009-04-16 18:20 ` Andrew Lyon
2009-04-16 18:28 ` Jeremy Fitzhardinge
2009-04-17 10:17 ` George Dunlap
2009-04-17 14:13 ` Dan Magenheimer
2009-04-17 14:55 ` Jeremy Fitzhardinge
2009-04-17 15:55 ` Dan Magenheimer
2009-04-17 16:17 ` Jeremy Fitzhardinge
2009-04-17 16:46 ` Dan Magenheimer
2009-04-17 17:05 ` George Dunlap
2009-04-17 10:02 ` Tian, Kevin
2009-04-15 14:29 ` George Dunlap
2009-04-10 0:15 ` Tian, Kevin
2009-04-15 15:07 ` George Dunlap
2009-04-16 4:58 ` Tian, Kevin
2009-04-10 2:28 ` Zhiyuan Shao
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=49DF8335.7030501@goop.org \
--to=jeremy@goop.org \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Pratt@eu.citrix.com \
--cc=kevin.tian@intel.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.