xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Simon Martin <furryfuttock@gmail.com>
To: xen-devel@lists.xen.org
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	Dario Faggioli <dario.faggioli@citrix.com>,
	Nate Studer <nate.studer@dornerworks.com>,
	Don Slutz <dslutz@verizon.com>,
	Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: Strange interdependace between domains
Date: Fri, 14 Feb 2014 12:02:38 +0000	[thread overview]
Message-ID: <6010385428.20140214120238@gmail.com> (raw)
In-Reply-To: <295276356.20140213222507@gmail.com>

Hello Simon,

Thanks everyone and especially Ian! It was the hyperthreading that was
causing the problem.

Here's my current configuration:

# xl cpupool-list -c
Name               CPU list
Pool-0             0,1
pv499              2,3
# xl vcpu-list
Name                                ID  VCPU   CPU State   Time(s) CPU Affinity
Domain-0                             0     0    0   r--      16.6  0
Domain-0                             0     1    1   -b-       7.3  1
win7x64                              1     0    1   -b-      82.5  all
win7x64                              1     1    0   -b-      18.6  all
pv499                                2     0    3   r--     226.1  3

I  have  pinned  dom0 as I wasn't sure whether it belongs to Pool-0 (I
assume it does, can you confirm please).

Dario, if you are going to look at the

Looking at my timings with this configuration I am seeing a 1%
variation (945 milliseconds +/- 5). I think this can be attributable
to  RAM  contention, at the end of the day all cores are competing for
the same bus.

-- 
Best regards,
 Simon                            mailto:furryfuttock@gmail.com

  parent reply	other threads:[~2014-02-14 12:02 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-13 16:56 Strange interdependace between domains Simon Martin
2014-02-13 17:07 ` Ian Campbell
2014-02-13 17:28   ` Simon Martin
2014-02-13 17:39     ` Dario Faggioli
2014-02-13 17:36 ` Dario Faggioli
2014-02-13 20:47   ` Nate Studer
2014-02-13 22:25   ` Simon Martin
2014-02-13 23:13     ` Dario Faggioli
2014-02-14 10:26       ` Don Slutz
2014-02-14 12:02     ` Simon Martin [this message]
2014-02-14 13:26       ` Andrew Cooper
2014-02-14 17:21       ` Dario Faggioli
2014-02-17 12:46         ` Simon Martin
2014-02-18 16:55           ` Dario Faggioli
2014-02-18 17:58             ` Don Slutz
2014-02-18 18:06               ` Dario Faggioli
2014-02-20  6:07                 ` Juergen Gross
2014-02-20 18:22                   ` Dario Faggioli
2014-02-21  6:31                     ` Juergen Gross
2014-02-21 17:24                       ` Dario Faggioli
2014-02-24  9:25                         ` Juergen Gross
2014-02-17 13:19         ` Juergen Gross
2014-02-17 15:08           ` Dario Faggioli
2014-02-18  5:31             ` Juergen Gross
2014-02-17 14:13         ` Nate Studer
2014-02-18 16:47           ` 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=6010385428.20140214120238@gmail.com \
    --to=furryfuttock@gmail.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=dario.faggioli@citrix.com \
    --cc=dslutz@verizon.com \
    --cc=nate.studer@dornerworks.com \
    --cc=xen-devel@lists.xen.org \
    /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).