From: Diwaker Gupta <diwakergupta@gmail.com>
To: Keir Fraser <keir.fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: Xen cluster n/w performance (again!)
Date: Tue, 23 Nov 2004 13:32:59 -0800 [thread overview]
Message-ID: <1b0b4557041123133226ff88@mail.gmail.com> (raw)
In-Reply-To: <E1CVy2F-0005du-00@mta1.cl.cam.ac.uk>
> One thing you might want to try is to change a line in the file
> linux-2.6.9-xenU/drivers/xen/netfront/netfront.c.
> From:
> #define RX_MIN_TARGET 8
> To:
> #define RX_MIN_TARGET NETIF_RX_RING_SIZE
>
> One possibility is that dynamic buffer sizing is dropping some packets
> and causing TCP to crap itself.
>
> If this improves things then I'll have to be much more careful about
> shrinking the buffers, and/or add a config option to disable the
> resizing completely.
>
> -- Keir
>
My bad.
Sorry about the false alarm everyone, it was a routing issue. With the
correct routing setup, I can see upto 930 Mbps between VMs running on
2 distinct physical machines in the cluster.
Cheers!
--
Diwaker Gupta
http://resolute.ucsd.edu/diwaker
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next prev parent reply other threads:[~2004-11-23 21:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-21 6:37 Xen cluster n/w performance (again!) Diwaker Gupta
2004-11-21 10:52 ` Ian Pratt
2004-11-21 20:10 ` Keir Fraser
2004-11-23 21:32 ` Diwaker Gupta [this message]
2004-11-23 22:14 ` Ian Pratt
2004-11-30 21:09 ` David Becker
2004-11-30 21:42 ` Ian Pratt
2004-11-30 23:42 ` David Becker
2004-12-01 9:09 ` Keir Fraser
2004-12-03 21:23 ` David Becker
2004-11-22 15:28 ` Xen cluster n/w performance David Becker
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=1b0b4557041123133226ff88@mail.gmail.com \
--to=diwakergupta@gmail.com \
--cc=keir.fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/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.