All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	xen-devel@lists.xenproject.org
Subject: Re: Perf regression of netperf compared Xen 4.4 to origin/master
Date: Wed, 2 Jul 2014 17:55:05 +0100	[thread overview]
Message-ID: <53B43969.1030507@citrix.com> (raw)
In-Reply-To: <20140702165200.GA3044@laptop.dumpdata.com>

On 02/07/14 17:52, Konrad Rzeszutek Wilk wrote:
> The test is pretty silly.
>
> I've 14 guests, and I make each guest run netperf against the other.
> I start with 1 pair, then 2 pairs, then up to 7. Each guest
> is 768 MB, runs in a RAMdisk and just has one vif. The box is
> a SuperMicro X8DB8+ with two E5520 and 12GB of RAM.
> The netperf runs for a minute. The guests are PVHVM and I am
> using qemu-upstream.  The guest configs are:
>
> builder='hvm'
> disk = [ 'file:/mnt/lab/bootstrap-x86_64/root_image.iso,hdc:cdrom,r']
> memory=768
> boot='d'
> vcpus=1
> serial='file:/var/log/xen/console-g-vm0.log'
> vnclisten='0.0.0.0'
> name='g-vm0'
> on_crash='preserve'
> # IP is 192.168.102.90
> vif = [ 'mac=00:0f:4b:01:01:00, bridge=switch' ]
> .. and naturally the ip, name and MAC change for each guest.
>
> The kernel for both the guest and domain 0 is the same - no
> configuration change. The Xen is built without debug=y.

What do you mean by this?  master has debugging enabled by default so
unless you build with debug=n, you will have a debug build.

~Andrew

  reply	other threads:[~2014-07-02 16:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-02 16:52 Perf regression of netperf compared Xen 4.4 to origin/master Konrad Rzeszutek Wilk
2014-07-02 16:55 ` Andrew Cooper [this message]
2014-07-03 10:46   ` George Dunlap
2014-07-03 18:00     ` Konrad Rzeszutek Wilk

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=53B43969.1030507@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=xen-devel@lists.xenproject.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 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.