mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@osdl.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Ethernet bridge leaking memory
Date: Thu, 10 Nov 2005 13:06:13 -0800	[thread overview]
Message-ID: <20051110130613.2bb0c9be@dxpl.pdx.osdl.net> (raw)
In-Reply-To: <200511102113.28334.kostja@siefen.de>

On Thu, 10 Nov 2005 21:13:27 +0100
Kostja Siefen <kostja@siefen.de> wrote:

> Hi,
> 
> I have a strange problem with ethernet bridging in 2.6.13 which leads to heavy 
> slab allocation until memory is completely filled up.
> 
> My setup:
> 
> HP nx7000 Laptop running Kernel 2.6.13
> - RTL 8139 network interface on board (module 8139too)
> - PC Card Wired LAN Network Interface (module pcnet_cs)
> 
> After modprobing bridge and calling
> 
> brctl addbr br0
> brctl addif br0 eth0 (RTL 8139)
> brctl addif br0 eth2 (PC Card Wired LAN)
> 
> the bridge is up and running and works like a charm. Sending some traffic (1 
> MB/s is enough) through that bridge leads to massive kernel memory 
> allocation. slabtop reports, that "skbuff_head_cache" and "size-2048" eat up 
> all the memory (256 MB). This looks like a memory leak to me.
> 
> Even unloading the network modules does not free any memory, a reboot is 
> required.
> 
> Any ideas? 
> 


Could you try identifying which flow or driver is leaking?

	eth0 ---> eth2
	eth0 ---> br0
	eth2 ---> br0
	eth2 ---> eth0
	br0  ---> eth0
	br0  ---> eth2

Also try without bridge, it may just be a driver leak



-- 
Stephen Hemminger <shemminger@osdl.org>
OSDL http://developer.osdl.org/~shemminger

  reply	other threads:[~2005-11-10 21:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-10 20:13 Kostja Siefen
2005-11-10 21:06 ` Stephen Hemminger [this message]
2005-12-10 16:32   ` Ferrari (sent by Nabble.com)

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=20051110130613.2bb0c9be@dxpl.pdx.osdl.net \
    --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

Powered by JetHome