From: Andres Lagar Cavilla <andreslc@cs.toronto.edu>
To: xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Subject: Network freezing for paravirt linux, 3.0.3
Date: Tue, 28 Nov 2006 10:08:11 -0500 [thread overview]
Message-ID: <456C50DB.4090809@cs.toronto.edu> (raw)
Hi,
as part of My Xen-GL work I've been experiencing some temporary domU
network outages.
At a very basic level I'm using the TCP/IP stack to transport OpenGL
command from the domU to dom0, where they can be directly executed on
some nice piece of graphics hardware. Now, beasts like Enemy Territory
or Unreal Tournament 2004 seem to exceed a gigabit of bandwidth
utilization. All those bots and rich textures don't help much :)
At points in the game domU networking completely freezes, becoming
unresponsive to ssh, ping, the openGL transport, and other services I
tried. Other simptoms:
- Tcpdump reveals that the only traffic on the vifX.Y are inbound
broadcasts.
- There are no dropped packets (as shown by ifconfig and
/proc/net/dev).
- Happens with both transmit checksumming offload enabled and disabled.
- Measured from both dom0 and domU.
- Both with network bridging and routing.
- Did not happen for an hvm doing network emulation (did happen for
PV-on-HVM network driver).
- For whatever it's worth, doesn't happen with vmware network
emulation either.
It thus looks like the culprit is netfront, or possibly a
netback/netfront interaction (Q: is netback employed in the qemu-dm
emulation path, or packets are simply relayed from the tap to vifX.Y?).
I would love to provide more information, but I'm unsure where to get it.
Andres
next reply other threads:[~2006-11-28 15:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 15:08 Andres Lagar Cavilla [this message]
2006-11-28 15:19 ` [Xen-devel] Network freezing for paravirt linux, 3.0.3 Ian Pratt
2006-11-28 15:25 ` Keir Fraser
2006-11-28 17:34 ` [Xen-devel] " Andres Lagar Cavilla
2006-11-28 20:53 ` Andres Lagar Cavilla
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=456C50DB.4090809@cs.toronto.edu \
--to=andreslc@cs.toronto.edu \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@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.