From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: George Dunlap <dunlapg@umich.edu>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Zhigang Wang <zhigang.x.wang@oracle.com>,
Tim Deegan <Tim.Deegan@citrix.com>,
Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: Cpu pools discussion
Date: Tue, 28 Jul 2009 15:57:26 +0200 [thread overview]
Message-ID: <4A6F03C6.9060603@ts.fujitsu.com> (raw)
In-Reply-To: <de76405a0907280647g6c34e655md2bbe37a9caa61b7@mail.gmail.com>
George Dunlap wrote:
> On Tue, Jul 28, 2009 at 2:39 PM, Juergen
> Gross<juergen.gross@ts.fujitsu.com> wrote:
>> I think your first point is the most important one.
>> It might be possible to build a load balancing scheme to shift cpus between
>> pools dynamically, but this should be step 2, I think :-)
>> But it would be a nice project :-)
>
> If I recall your use case, Juergen, I thought the whole point was to
> keep some set of VMs limited to just a subset of CPUs? So the first
> point is a feature for you, not a bug. :-)
Indeed.
I just like to think about further enhancements, even if my company isn't
requiring them...
>
> If we ever do find someone who wants cpu pools, perhaps to use
> different schedulers, but wants to be able to dynamically adjust pool
> size, then they can work on such a project. Until then, no point
> spending time on something no one's going to use.
Absolutely true.
OTOH I see pools as an interesting way to support large NUMA systems in an
effective way. And for this usage you would need such a project :-)
I think it is very important to check the possible future enhancements, as
they might influence decisions today.
Juergen
--
Juergen Gross Principal Developer Operating Systems
TSP ES&S SWE OS6 Telephone: +49 (0) 89 636 47950
Fujitsu Technolgy Solutions e-mail: juergen.gross@ts.fujitsu.com
Otto-Hahn-Ring 6 Internet: ts.fujitsu.com
D-81739 Muenchen Company details: ts.fujitsu.com/imprint.html
next prev parent reply other threads:[~2009-07-28 13:57 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 15:20 Cpu pools discussion George Dunlap
2009-07-27 15:50 ` Keir Fraser
2009-07-28 0:41 ` Zhigang Wang
2009-07-28 9:19 ` Tim Deegan
2009-07-28 10:15 ` Juergen Gross
2009-07-28 12:50 ` George Dunlap
2009-07-28 13:07 ` Tim Deegan
2009-07-28 13:24 ` Juergen Gross
2009-07-28 13:31 ` Tim Deegan
2009-07-28 13:39 ` Juergen Gross
2009-07-28 13:47 ` George Dunlap
2009-07-28 13:57 ` Juergen Gross [this message]
2009-07-28 15:29 ` Dan Magenheimer
2009-07-28 15:49 ` Keir Fraser
2009-07-28 16:26 ` George Dunlap
2009-07-29 0:29 ` Zhigang Wang
2009-07-29 5:47 ` Juergen Gross
2009-07-28 13:41 ` George Dunlap
2009-07-28 13:55 ` Keir Fraser
2009-07-29 6:14 ` Juergen Gross
2009-07-29 7:39 ` Keir Fraser
2009-07-29 8:52 ` Juergen Gross
2009-07-29 9:35 ` Keir Fraser
2009-07-29 11:06 ` Juergen Gross
2009-07-29 12:28 ` Keir Fraser
2009-07-29 12:33 ` Juergen Gross
2009-07-29 13:00 ` Keir Fraser
2009-07-30 5:46 ` Juergen Gross
2009-07-30 8:30 ` Keir Fraser
2009-07-30 8:58 ` Juergen Gross
2009-07-30 12:51 ` Juergen Gross
2009-07-30 13:18 ` Keir Fraser
2009-07-31 5:25 ` Juergen Gross
2009-07-28 5:40 ` Juergen Gross
2009-07-28 9:09 ` Keir Fraser
2009-07-28 10:19 ` Juergen Gross
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=4A6F03C6.9060603@ts.fujitsu.com \
--to=juergen.gross@ts.fujitsu.com \
--cc=Keir.Fraser@eu.citrix.com \
--cc=Tim.Deegan@citrix.com \
--cc=dunlapg@umich.edu \
--cc=xen-devel@lists.xensource.com \
--cc=zhigang.x.wang@oracle.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.