All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sébastien CRAMATTE" <s.cramatte@wanadoo.fr>
To: lartc@vger.kernel.org
Subject: [LARTC] Ethernet bridge overflow ?
Date: Fri, 23 Feb 2007 16:04:12 +0000	[thread overview]
Message-ID: <45DF107C.8080403@wanadoo.fr> (raw)

Hello,

I've setuped  an ethernet bridge on a debian sarge 3.1 with  l7-filter +
ipp2 shapper rules
The server is a supermicro p4sci + celeron pentium 4 base 3ghz  + 512Mb
+ 2 ethernet e1000

One interface is connected to a cisco catalyst switch
The other interface is connected directly to a CMTS (a sort of router
for cable modem) configured as bridge too.

More than 20Mbps of bandwith cross this bridge. Most of this traffic is
p2p (~80%)
When traffic goes over 14Mbps the  bridge seems to saturate (overflow ?
) and start to make colision and loose packets

I've take a look to this  paper
http://facweb.cti.depaul.edu/jyu/Publications/Yu-Linux-TSM2004.pdf

And with a duron 1,3Ghz+512 mbps he obtain these values

Input Rate   28,444,444
(bps)
Latency    29
(us)
Throughput 28,000,000
(bps)
Linux CPU 77%
Occupancy

A duron 1,3 is less powered than a celeron p4 3 ...  So I don't
understand why I've got this problem :(


When I make a  "top" or "uptime" all seems that works well ...
I've got rrdtool graphs that check cpu and load and seems normal too ...

Does someone  have got somes ideas ?
Any clue or tips to isolate/resolve the problem are welcome


Regards

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

             reply	other threads:[~2007-02-23 16:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-23 16:04 Sébastien CRAMATTE [this message]
2007-02-23 17:31 ` [LARTC] Ethernet bridge overflow ? Larry Brigman
2007-02-23 18:30 ` Sébastien CRAMATTE
2007-02-26 10:39 ` Ivan Vladimirov

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=45DF107C.8080403@wanadoo.fr \
    --to=s.cramatte@wanadoo.fr \
    --cc=lartc@vger.kernel.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.