From: "pradeep singh rautela" <rautelap@gmail.com>
To: "pak333@comcast.net" <pak333@comcast.net>
Cc: xen-devel@lists.xensource.com
Subject: Re: Xen scheduler
Date: Sat, 21 Apr 2007 14:51:52 +0530 [thread overview]
Message-ID: <6bc632150704210221n66cc0cabpd32f366d127662af@mail.gmail.com> (raw)
In-Reply-To: <042120070603.1707.4629A924000D2BC9000006AB2200735446CCCCCC050E9F@comcast.net>
[-- Attachment #1.1: Type: text/plain, Size: 811 bytes --]
On 4/21/07, pak333@comcast.net <pak333@comcast.net> wrote:
>
> Hi,
>
> On running on a dual/quad core does the Xen scheduler take into account
> the physical layout of the cores.
> For example if a VM has two vcpus, and there are 4 physical cpus free,
> will it take care to assign the 2vcpus (from a VM) to 2 pcpus on the same
> socket.
>
Shouldn't this is be concealed.You may never know which physical CPU is
actualyl running a vcpu. It may get scheduled on to a different physical CPU
depending on the load on the other CPUs.
CMIIW
~psr
Thanks
> - Prabha
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
--
---
pradeep singh rautela
"Genius is 1% inspiration, and 99% perspiration" - not me :)
[-- Attachment #1.2: Type: text/html, Size: 1681 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2007-04-21 9:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-21 6:03 Xen scheduler pak333
2007-04-21 9:21 ` pradeep singh rautela [this message]
2007-04-22 13:09 ` Mike D. Day
-- strict thread matches above, loose matches on Subject: below --
2007-10-24 19:55 xen scheduler Agarwal, Lomesh
2007-10-25 23:29 ` Atsushi SAKAI
2011-04-19 20:51 Xen scheduler David Xu
2011-04-20 8:47 ` George Dunlap
2015-05-18 7:54 xen scheduler Rajendra Bele
2015-05-18 14:53 ` Dario Faggioli
2015-05-19 1:50 ` Rajendra Bele
2015-05-19 8:43 ` Dario Faggioli
2015-05-21 7:55 ` Rajendra Bele
2015-05-21 9:57 ` Dario Faggioli
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=6bc632150704210221n66cc0cabpd32f366d127662af@mail.gmail.com \
--to=rautelap@gmail.com \
--cc=pak333@comcast.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).