From: "Josh Burke" <kernelbridgeissue@iokui.com>
To: bridge@osdl.org
Subject: [Bridge] slow network performance when using bridged interfaces in 2.6.13 compared to 2.6.12.
Date: Fri, 28 Oct 2005 21:33:39 +0000 [thread overview]
Message-ID: <W3514615840246961130535219@webmail4> (raw)
(originally filed as a bug in Fedora's bugzilla, see https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=171933)
Greetings,
Using Fedora Core 4 on a Dell PE 420sc. Malfunctioning kernel is smp-2.6.13-1.1532_FC4. Properly functioning kernels included smp-2.6.12-1.1456_FC4.
Network performance is extremely poor when using bridged network interfaces. When not using brctl, the interface gives ~800kbps. When using brctl to bridge two interfaces, the speed drops to ~1.0kbps.
Reverting to kernel-smp-2.6.12-1.1456_FC4 returns the speed to normal.
The two interfaces have IP addresses when not bridged. They do not have IP addresses when they are bridged. (As expected.)
No unusual output in dmesg.
Traffic is not slowed that originates on a bridge interfaces and goes out a bridge interface, only traffic from the host that the bridge is on, is slowed.
Making these connections unbridged returns normal traffic performance. Reverting to 2.6.12 also returns normal performance.
Tcpdump indicates increasing pauses returning packets. (From bridge host to the outside. Bridge host is a web server, though even SSH connections are slow.)
For example:
14:25:53.387001 IP 192.168.0.1.https > 10.0.0.1.32752: tcp 1260
14:25:53.648768 IP 10.0.0.1.32752 > 192.168.0.1.https: tcp 0
14:25:53.648817 IP 192.168.0.1.https > 10.0.0.1.32752: tcp 1260
14:25:53.648859 IP 192.168.0.1.https > 10.0.0.1.32752: tcp 1260
14:25:53.770239 IP 10.0.0.1.32752 > 192.168.0.1.https: tcp 0
14:26:03.242674 IP 192.168.0.1.https > 10.0.0.1.32752: tcp 1260
14:26:03.462594 IP 10.0.0.1.32752 > 192.168.0.1.https: tcp 0
14:26:03.462675 IP 192.168.0.1.https > 10.0.0.1.32752: tcp 1260
14:26:03.462714 IP 192.168.0.1.https > 10.0.0.1.32752: tcp 1260
14:26:03.581169 IP 10.0.0.1.32752 > 192.168.0.1.https: tcp 0
14:26:22.526025 IP 192.168.0.1.https > 10.0.0.1.32752: tcp 1260
14:26:22.784218 IP 10.0.0.1.32752 > 192.168.0.1.https: tcp 0
14:26:22.784325 IP 192.168.0.1.https > 10.0.0.1.32752: tcp 1260
14:26:22.784379 IP 192.168.0.1.https > 10.0.0.1.32752: tcp 1260
14:26:22.895638 IP 10.0.0.1.32752 > 192.168.0.1.https: tcp 0
14:27:00.780762 IP 192.168.0.1.https > 10.0.0.1.32752: tcp 1260
14:27:01.045112 IP 10.0.0.1.32752 > 192.168.0.1.https: tcp 0
14:27:01.045209 IP 192.168.0.1.https > 10.0.0.1.32752: tcp 1260
14:27:01.045263 IP 192.168.0.1.https > 10.0.0.1.32752: tcp 1260
14:27:01.160083 IP 10.0.0.1.32752 > 192.168.0.1.https: tcp 0
(192.168.0.1 = bridge host, 10.0.0.1 = external host. This happened while trying to download a text file.)
Any suggestions, or places to look for information, is appreciated.
- Josh
next reply other threads:[~2005-10-28 21:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-28 21:33 Josh Burke [this message]
2005-10-28 22:36 ` [Bridge] slow network performance when using bridged interfaces in 2.6.13 compared to 2.6.12 Stephen Hemminger
2005-10-29 5:39 ` Stephen Hemminger
-- strict thread matches above, loose matches on Subject: below --
2005-10-28 23:07 Josh Burke
2005-10-31 16:18 Josh Burke
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=W3514615840246961130535219@webmail4 \
--to=kernelbridgeissue@iokui.com \
--cc=bridge@osdl.org \
/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.