From: "Reese Faucette" <reese@myri.com>
To: xen-devel@lists.xensource.com
Subject: vif interface dropping 80% packets
Date: Mon, 5 Feb 2007 16:30:51 -0800 [thread overview]
Message-ID: <086c01c74986$0e8fd120$58c31fac@bart> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1438 bytes --]
I'm trying to characterize the performance of 10G ethernet to a user domain.
The machine has 2 configured ethernet cards, eth0 is a 1G card, and eth2 is a 10G card. (eth1 is another 1G card and eth3 is another 10G, but these are not configured)
I have network bridge set up on eth2 with defaults, nothing special, just:
/etc/xen/scripts/network-bridge start vifnum=2
I have a user domain that attaches eth1 to this vif, and when I try netperf tests, I get tons of packet loss in the vif interface.
vif3.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:165602 errors:0 dropped:0 overruns:0 frame:0
TX packets:12982847 errors:0 dropped:48987465 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:8679444 (8.2 MiB) TX bytes:20888548648 (19.4 GiB)
As can be seen above, vif3.1 drops about 80% of the packets it should transmit. Is this expected due to something in the dom0 -> domU interface just not being able to keep up, or is there something I can do about it? It almost looks like the dom0->domU link is throttled at about 1Gb/s. I say this because the 10G link is running about 50-60% capacity when the drop rate is 80%.
Everything has MTU 1500, btw - I noticed that Xen is pretty unhappy with an MTU of 9000.
thanks,
-reese
[-- Attachment #1.2: Type: text/html, Size: 2783 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2007-02-06 0:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-06 0:30 Reese Faucette [this message]
2007-02-06 2:33 ` vif interface dropping 80% packets Reese Faucette
2007-02-06 13:43 ` Ian Pratt
2007-02-06 18:12 ` Santos, Jose Renato G
2007-02-06 18:58 ` Reese Faucette
2007-02-06 19:40 ` Santos, Jose Renato G
2007-02-06 22:52 ` Reese Faucette
2007-02-06 23:06 ` Ian Pratt
2007-02-06 23:35 ` Reese Faucette
2007-02-06 23:59 ` Ian Pratt
2007-02-07 20:52 ` Reese Faucette
2007-02-07 22:28 ` Ian Pratt
2007-02-07 0:16 ` Santos, Jose Renato G
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='086c01c74986$0e8fd120$58c31fac@bart' \
--to=reese@myri.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.