All of lore.kernel.org
 help / color / mirror / Atom feed
From: Emmanuel Ackaouy <ackaouy@gmail.com>
To: pak333@comcast.net
Cc: ncmike@us.ibm.com, xen-devel@lists.xensource.com
Subject: Re: Re: Xen scheduler
Date: Tue, 24 Apr 2007 16:34:43 +0200	[thread overview]
Message-ID: <4f871bf437d5f30f1626777a8ba042c5@gmail.com> (raw)
In-Reply-To: <042320071933.18629.462D0A250001D375000048C52207021633CCCCCC050E9F@comcast.net>

On Apr 23, 2007, at 21:33, pak333@comcast.net wrote:
> Basically all my questions boil down to this: Does the Scheduler know 
> about the pcpu layout(same socket) and does it do any scheduling based 
> on that.

Yes but not how you suggested.

The scheduler actually tries to schedule VCPUs across multiple
sockets before it "co-schedules" a socket. The idea behind this is
to maximize the achievable memory bandwidth.

On hyperthreaded systems, the scheduler will also attempt to
schedule across cores before it co-schedules hyperthreads. This
is to maximize achievable cycles.

At this time, no attempt is made to schedule 2 VCPUs of the
same VM any differently than 2 VCPUs of distinct VMs.

If you feel two VCPUs would do better co-scheduled on a
core or socket, you'd currently have to use cpumasks -- as
mike suggested -- to restrict where they can run manually. I'd
be curious to know of real world cases where doing this
increases performance significantly.

Hope this helps.

Cheers,
Emmanuel.

  parent reply	other threads:[~2007-04-24 14:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-23 19:33 Re: Xen scheduler pak333
2007-04-24 11:07 ` Petersson, Mats
2007-04-24 14:47   ` Emmanuel Ackaouy
2007-04-24 14:53     ` Petersson, Mats
2007-04-24 14:34 ` Emmanuel Ackaouy [this message]
2007-04-24 14:42   ` Petersson, Mats
2007-04-24 14:55     ` Emmanuel Ackaouy

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=4f871bf437d5f30f1626777a8ba042c5@gmail.com \
    --to=ackaouy@gmail.com \
    --cc=ncmike@us.ibm.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 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.