From: "Paul P. Pongco" <paulp@mozcom.com>
To: bridge@osdl.org
Subject: [Bridge] maximum throughput for linux bridge
Date: Fri, 13 Feb 2004 15:37:05 +0800 [thread overview]
Message-ID: <1076657825.735.72.camel@amidala.mozcom.com> (raw)
Hi,
Apologies if I am not suscribed to this list.
I have setup a linux bridge using 3c905C-TX/TX-M [Tornado] cards. Im
running it on RH 7.3 2.4.19 kernel.
Lately, I have seen the following errors on the bridge
Feb 10 07:40:24 safe kernel: eth2: Too much work in interrupt, status e401.
Feb 10 07:40:52 safe last message repeated 3 times
Feb 10 08:12:16 safe kernel: br0: received tcn bpdu on port 1(eth2)
Feb 10 08:12:16 safe kernel: br0: topology change detected, sending tcn bpdu
Feb 10 08:13:09 safe kernel: br0: received tcn bpdu on port 1(eth2)
Feb 10 08:13:09 safe kernel: br0: topology change detected, sending tcn bpdu
Im currently pushing around 45Mbs/20Mbs (down/up) of traffic on the
bridge (doing some bandwidth management) and Im concerned about its
performance and how it would scale.
Thanks in advance for your advice.
--
Cheers,
Paul P. Pongco
Mosaic Communications Inc.
next reply other threads:[~2004-02-13 7:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 7:37 Paul P. Pongco [this message]
2004-02-13 18:01 ` [Bridge] maximum throughput for linux bridge Stephen Hemminger
2004-02-15 12:02 ` Steffen Klassert
2004-02-16 14:36 ` Paul P. Pongco
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=1076657825.735.72.camel@amidala.mozcom.com \
--to=paulp@mozcom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox