All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
	Tony Breeds <tony@bakeyournoodle.com>
Subject: Re: [BUNDLE] Testing a simpler inter-domain transport
Date: Mon, 06 Feb 2006 15:40:48 +1100	[thread overview]
Message-ID: <1139200849.18753.23.camel@localhost.localdomain> (raw)
In-Reply-To: <43E62E29.4090209@us.ibm.com>

On Sun, 2006-02-05 at 10:56 -0600, Anthony Liguori wrote:
> 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:

> 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?

Yes.  The current driver is a hack, which creates the shared page when
invoked (in dom0) with "create" as a module param.  However, you can
attach as many domUs as you want to that same LAN.

> Any idea why there's UDP degradation?

No 8(.  I'm going to write a block driver and see what that's like.

I was surprised at how aggressively Xen is switching between domains
when an event channel was activated: so much so that we rarely got 32
packets off before the switch.   Less aggressive scheduling will
definitely help us, and possibly help the existing drivers.

> This stuff looks awesome :-)

Thanks, just fiddling.  It'll be interesting to see what changes the PPC
guys will need for this.

Cheers!
Rusty.
-- 
 ccontrol: http://ozlabs.org/~rusty/ccontrol

  reply	other threads:[~2006-02-06  4:40 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 [this message]
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=1139200849.18753.23.camel@localhost.localdomain \
    --to=rusty@rustcorp.com.au \
    --cc=aliguori@us.ibm.com \
    --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.