public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ford <david+cert@blue-labs.org>
To: Deepinder Singh <dsingh@somanetworks.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Memory leaks with GRE Tunnels
Date: Thu, 31 Jan 2002 14:35:02 -0500	[thread overview]
Message-ID: <3C599C66.30202@blue-labs.org> (raw)
In-Reply-To: <3C598DE3.8090405@somanetworks.com>

[-- Attachment #1: Type: text/plain, Size: 1587 bytes --]

I use GRE tunnels a lot.  I have run my rc.networking script several 
dozen times with no problems and everything is cranking along nicely. 
 You can view my scripts at http://blue-labs.org/.  I always use a 
single numbered interface, "gre1".

However the below really is a bug that should be fixed I would imagine.

David

Deepinder Singh wrote:

> Hi ,
>
> I have been doing some testing using GRE tunnels in Linux ( which btw 
> work great ). I found that creating and deleting a tunnel results in a 
> memory leak.
>
> To test it out I wrote a small script that basically loops around 
> creating and then deleting 8000 tunnel interfaces at a time. On the 
> eighth iteration  the system hangs a whole with no error messages. 
> There  was still enoungh virtual memory around even with the leaks so 
> I figured something else is wrong. It turns out that the interface 
> numbers ( as seen in ' ip link ls' )  do not seem to be reused when an 
> interface is deleted and as such the system hangs when the number 
> reaches 64K.
>
> I suspect the two issues are realted but am more of a cisco guy and 
> know kernel internals. The total mem leak for the 64 K tunnels is 
> about 200 megs.
>
> Please cc me if you reply to this post as I am not on the list.
>
> thanks,
> Deepinder Singh
> Sr. Network Eng.
> Soma Networks
>
> -
> To unsubscribe from this list: send the line "unsubscribe 
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/



[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3269 bytes --]

      parent reply	other threads:[~2002-01-31 19:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-31 18:33 Memory leaks with GRE Tunnels Deepinder Singh
2002-01-31 18:57 ` George Bonser
2002-01-31 19:40   ` Deepinder Singh
2002-02-02  4:29     ` andrew may
2002-01-31 20:49   ` Olaf Titz
2002-01-31 19:35 ` David Ford [this message]

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=3C599C66.30202@blue-labs.org \
    --to=david+cert@blue-labs.org \
    --cc=dsingh@somanetworks.com \
    --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