From: Anthony Liguori <aliguori@us.ibm.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Tony Breeds <tony@bakeyournoodle.com>
Subject: Re: [BUNDLE] Testing a simpler inter-domain transport
Date: Sun, 05 Feb 2006 10:56:09 -0600 [thread overview]
Message-ID: <43E62E29.4090209@us.ibm.com> (raw)
In-Reply-To: <1139110732.25090.41.camel@localhost.localdomain>
Rusty Russell wrote:
>It's unoptimized, but shows some promise. Here are the benchmarks for
>tcpblast and tbench, on a uniproc 3GHz Pentium 4. I'd appreciate SMP
>numbers if someone has hardware on hand:
>
> UDP blast: tcpblast -u -s50000 dom0 9999
> Current Xen = 254961 KB/s
> Simple share = 233952 KB/s
> TCP blast: tcpblast -t -s50000 dom0 9999
> Current Xen = 86566.4 KB/s
> Simple share = 135415 KB/s
> Bidir tcp load: tbench 10
> Current Xen = 31.9551 MB/sec
> Simple share = 64.2113 MB/sec
>
>
I imagine the numbers for the Simple share should be pretty similiar for
domU to domU right? I also imagine that domU to domU under Current xen
should be considerably worse right?
Any idea why there's UDP degradation?
This stuff looks awesome :-)
Regards,
Anthony Liguori
>It's not plumbed into xenbus, so creating LANs is a manual process,
>using the dmesg output from the initial creation:
>
> dom0# modprobe ohlan create
> ohlan: created lan eth1 at address 0x1b6000
> domU# modprobe ohlan address=0x1b6000
>
>Feedback welcome!
>Rusty.
>
>
next prev parent reply other threads:[~2006-02-05 16:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-05 3:38 [BUNDLE] Testing a simpler inter-domain transport Rusty Russell
2006-02-05 10:26 ` NAHieu
2006-02-05 11:13 ` Rusty Russell
2006-02-05 16:56 ` Anthony Liguori [this message]
2006-02-06 4:40 ` Rusty Russell
2006-02-08 10:12 ` Daniel Veillard
2006-02-08 10:23 ` Rusty Russell
2006-02-08 10:34 ` Muli Ben-Yehuda
2006-02-08 10:46 ` Daniel Veillard
2006-02-08 10:54 ` Muli Ben-Yehuda
2006-02-08 17:49 ` Matt Mackall
2006-02-08 11:04 ` Rusty Russell
-- strict thread matches above, loose matches on Subject: below --
2006-02-06 20:01 Magenheimer, Dan (HP Labs Fort Collins)
2006-02-07 0:10 ` Rusty Russell
2006-02-06 20:48 Yang, Fred
2006-02-06 21:38 Magenheimer, Dan (HP Labs Fort Collins)
2006-02-08 1:31 Magenheimer, Dan (HP Labs Fort Collins)
2006-02-08 2:55 ` Hollis Blanchard
2006-02-10 3:15 ` Rusty Russell
2006-02-10 17:54 Magenheimer, Dan (HP Labs Fort Collins)
2006-02-12 23:39 King, Steven R
2006-02-12 23:59 ` Ronald G Minnich
2006-02-13 2:32 ` Rusty Russell
2006-02-13 9:38 ` Daniel Veillard
2006-02-13 3:24 King, Steven R
2006-02-13 3:47 ` Rusty Russell
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=43E62E29.4090209@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=rusty@rustcorp.com.au \
--cc=tony@bakeyournoodle.com \
--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.