From: "Paweł Staszewski" <pstaszewski@artcom.pl>
To: Bridge List <bridge@lists.osdl.org>
Subject: [Bridge] Performance problem with linux bridge ... compare kernel 2.6.13.4 to 2.6.15.1
Date: Sun, 29 Jan 2006 23:48:23 +0100 [thread overview]
Message-ID: <43DD4637.7090101@artcom.pl> (raw)
With kernel 2.6.13.4 linux bridge with traffic management for 4000users
and 20.4 MB/s(tx)/22.4 MB/s(rx) data load of CPU is max 50%
With kernel 2.6.15.1 the same linux bridge with the same traffic has
100% CPU load and in top I have ksoftirqd proccess.
The machine is P4 3.2 GHz with 1GB of ram and 4 NetGear 620 cards
The config is:
/sbin/modprobe acenic link=0x0100,0x0100,0x0100,0x0100
tx_coal_tick=256,256,256,256 rx_coal_tick=256,256,256,256
max_rx_desc=512,512,512,512 max_tx_desc=512,512,512,512
/sbin/ifconfig eth0 0.0.0.0 txqueuelen 10000 mtu 1500 up
/sbin/ifconfig eth1 0.0.0.0 txqueuelen 10000 mtu 1500 up
/sbin/ifconfig eth2 0.0.0.0 txqueuelen 10000 mtu 1500 up
/sbin/ifconfig eth3 0.0.0.0 txqueuelen 10000 mtu 1500 up
#To bond0
/sbin/ifconfig eth0 down
/sbin/ifconfig eth2 down
#To bond1
/sbin/ifconfig eth1 down
/sbin/ifconfig eth3 down
modprobe bonding max_bonds=2
ifconfig bond0 0.0.0.0 up
ifenslave-2.6 bond0 eth0 eth2
ifconfig bond1 0.0.0.0 up
ifenslave-2.6 bond1 eth1 eth3
/usr/local/sbin/brctl addbr br999
/sbin/vconfig add bond0 999
/sbin/vconfig add bond1 999
/sbin/ifconfig bond0.999 up
/sbin/ifconfig bond1.999 up
/usr/local/sbin/brctl addif br999 bond0.999
/usr/local/sbin/brctl addif br999 bond1.999
/sbin/ifconfig br999 up
Host has 102 vlans (bridges)
On each vlan interface is traffic management (iproute2 with hashing filters)
next reply other threads:[~2006-01-29 22:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-29 22:48 Paweł Staszewski [this message]
2006-01-30 17:12 ` [Bridge] Performance problem with linux bridge ... compare kernel 2.6.13.4 to 2.6.15.1 Stephen Hemminger
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=43DD4637.7090101@artcom.pl \
--to=pstaszewski@artcom.pl \
--cc=bridge@lists.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