From: George Dunlap <george.dunlap@eu.citrix.com>
To: Sisu Xi <xisisu@gmail.com>, Dario Faggioli <dario.faggioli@citrix.com>
Cc: Meng Xu <xumengpanda@gmail.com>, xen-devel <xen-devel@lists.xen.org>
Subject: Re: memory performance 20% degradation in DomU -- Sisu
Date: Thu, 13 Mar 2014 10:25:45 +0000 [thread overview]
Message-ID: <532187A9.1010608@eu.citrix.com> (raw)
In-Reply-To: <CAPqOm-pBW9XvW0kD3DhLPGWxEZFBtQVvD6xVQa-LEknyDa3QTg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 507 bytes --]
On 03/12/2014 04:50 PM, Sisu Xi wrote:
> Hi, Dario:
>
> Thanks for the reply.
>
> The CPU i am using is i7 X 980 @ 3.33 GHz,
> each core has dedicated L1(32K data, 32K inst) and L2 (256K unified)
> cache, all 6 cores share a 12MB L3 cache.
> I pinned Dom-0 to core 0, and Dom-U to core 1.
It might be worth switching those around -- e.g., try pinning domU to
core 4 / 5, or try pinning domU to core 0 and dom0 to core1, just to
rule out some kind of strange NUMA / microarchitecture effect.
-George
[-- Attachment #1.2: Type: text/html, Size: 2084 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-03-13 10:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 22:49 memory performance 20% degradation in DomU -- Sisu Sisu Xi
2014-03-04 23:00 ` Sisu Xi
2014-03-05 17:33 ` Konrad Rzeszutek Wilk
2014-03-05 20:09 ` Sisu Xi
2014-03-05 21:29 ` Gordan Bobic
2014-03-05 22:28 ` Konrad Rzeszutek Wilk
2014-03-06 10:31 ` Gordan Bobic
2014-03-05 22:09 ` Konrad Rzeszutek Wilk
2014-03-11 12:03 ` George Dunlap
2014-03-11 15:46 ` Sisu Xi
2014-03-11 20:21 ` Sisu Xi
2014-03-12 8:55 ` Dario Faggioli
2014-03-12 16:50 ` Sisu Xi
2014-03-13 10:25 ` George Dunlap [this message]
2014-03-12 8:59 ` 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=532187A9.1010608@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=xisisu@gmail.com \
--cc=xumengpanda@gmail.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).