From: Stephen Hemminger <shemminger@osdl.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Oops in 2.6.17.7 running multiple eth bridges
Date: Thu, 10 Aug 2006 11:28:47 -0700 [thread overview]
Message-ID: <20060810112847.3d868ccc@localhost.localdomain> (raw)
In-Reply-To: 31296a430608101034v2ecfbf8an66510427da49af4d@mail.gmail.com
On Thu, 10 Aug 2006 19:34:22 +0200
"Peter M" <peter.mdk@gmail.com> wrote:
> I have built a multi bridge i386 machine with 8 eth devices which
> keeps crashing on me.
>
> Kernel 2.6.7.17
>
> I'm using a network card with 4 ports (tulip) and 4 r8169 based cards.
>
> br0: eth0 eth1
> br1: eth2 eth3
> br2: eth3 eth4
> br3: eth5 eth6
>
> Below crash came when I unplugged a cable on a running bridge. Today I
> have had two crashes without touching the cables but didn't get any
> usable syslog.
>
> I have attached a number of info files which might help.
>
> Regards
> Peter M.
Looks like you are running out of memory. You will need more memory
to be able to hold all the receive rings data, as well as data in flight.
Rough estimate:
R8169 := 4 * 256 (ringsize) * 2K
Tulip := 4 * 128 * 2K
That comes out to 3 Meg in use just being idle. Once you get going
it could easily be 3x that.
And that is for standard 1500 byte MTU. If you use large packets, you
will have problems with memory fragmentation and will probably have
to go to a bigger 64 bit machine and even more memory.
next prev parent reply other threads:[~2006-08-10 18:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 17:34 Oops in 2.6.17.7 running multiple eth bridges Peter M
2006-08-10 18:28 ` Stephen Hemminger [this message]
[not found] ` <31296a430608101459g237ee2c8u509f6a19507d9c6c@mail.gmail.com>
2006-08-10 23:09 ` Stephen Hemminger
2006-08-15 11:00 ` Oops in 2.6.17.7 running multiple eth bridges [r8169?] Daniel Drake
2006-08-15 18:07 ` Stephen Hemminger
2006-08-16 9:11 ` Francois Romieu
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=20060810112847.3d868ccc@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox