From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: planned csched improvements?
Date: Tue, 20 Oct 2009 11:54:52 +0200 [thread overview]
Message-ID: <4ADD88EC.2090005@ts.fujitsu.com> (raw)
In-Reply-To: <de76405a0910200237q399f8175r3b67c4607f4d743a@mail.gmail.com>
George Dunlap wrote:
> On Tue, Oct 20, 2009 at 1:01 AM, Mukesh Rathor <mukesh.rathor@oracle.com> wrote:
>> Moreover, my focus is large, 32 to 128 logical processors, with 1/2
>> to 1TB memory. As such, I also want to address VCPUs being confined
>> to logical block of physical CPUs, taking into consideration that
>> licenses are per physical cpu core.
>
> This sounds like it would benefit from the "CPU pools" patch submitted
> by Juergen Gross.
Indeed.
Same problem, so same solution should be fine :-)
Mukesh, if you need more infos about cpu pools, I would be glad to help.
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-10-20 9:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 14:53 planned csched improvements? Jan Beulich
2009-10-09 15:59 ` George Dunlap
2009-10-12 7:31 ` Jan Beulich
2009-10-17 0:16 ` Mukesh Rathor
2009-10-19 9:34 ` George Dunlap
2009-10-20 0:01 ` Mukesh Rathor
2009-10-20 9:37 ` George Dunlap
2009-10-20 9:54 ` Juergen Gross [this message]
2009-10-21 2:26 ` Mukesh Rathor
2009-10-10 8:03 ` Tian, Kevin
2009-10-12 7:27 ` Jan Beulich
2009-10-12 7:32 ` Tian, Kevin
2009-10-12 7:34 ` Keir Fraser
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=4ADD88EC.2090005@ts.fujitsu.com \
--to=juergen.gross@ts.fujitsu.com \
--cc=George.Dunlap@eu.citrix.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.