From: Daniel Veillard <veillard@redhat.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: Wed, 8 Feb 2006 05:12:42 -0500 [thread overview]
Message-ID: <20060208101241.GD30975@redhat.com> (raw)
In-Reply-To: <1139110732.25090.41.camel@localhost.localdomain>
On Sun, Feb 05, 2006 at 02:38:51PM +1100, Rusty Russell wrote:
> Hi all,
>
> I've finally found time to resurrect my "share" code, update it for Xen
> 3.0 and (with Tony Breeds' help) created a simple LAN driver. You can
> find the bundle here:
>
> http://ozlabs.org/~rusty/xen/xen-share-2006-02-05.hg
Hum, I tried
hg clone http://ozlabs.org/~rusty/xen/xen-share-2006-02-05.hg
and my version fails with a zlib compression error raising an incorrect header
check,
> 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
>
> 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!
point to point performances looks good, but I'm starting to worry about
thing like group communication in a large Xen machine, assuming you can run
a few dozens domains consurrently, it may be useful to get some efficient
muticast based communication mechanism, the shared pages should help in some
ways (usuall memory/speed tradeoff though). Did you look at this ?
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
next prev parent reply other threads:[~2006-02-08 10:12 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
2006-02-06 4:40 ` Rusty Russell
2006-02-08 10:12 ` Daniel Veillard [this message]
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=20060208101241.GD30975@redhat.com \
--to=veillard@redhat.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.