From: Eric Dumazet <eric.dumazet@gmail.com>
To: Kumar S <ps2kumar@yahoo.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: Memory leak in ip_dst_cache
Date: Sat, 10 Sep 2011 00:08:45 +0200 [thread overview]
Message-ID: <1315606125.2606.19.camel@edumazet-laptop> (raw)
In-Reply-To: <1315605497.25052.YahooMailNeo@web113916.mail.gq1.yahoo.com>
Le vendredi 09 septembre 2011 à 14:58 -0700, Kumar S a écrit :
> I agree, 3 MB is not a concern. But actually this is exceeding, we are
> seeing more than 1200000 objects in a span of 24 hours, which is close
> to 300 MB.
Hmm, please include netdev in your mails.
Then there is something else.
Maybe a timer bug preventing dst_gc_task() to make its duty.
> Other tasks require somewhere around 200 MB+. When it reaches this
> number, the board reboots. In lab we could simulate this. That is how
> I'm trying to understand the problem. I'm injecting around 10k routes,
> and waiting for them to ageout.
>
I dont know, you could try disable IP route cache.
On recent (2.6.29+) kernels, thats very easy
# Disable Ip route cache (negative value in rebuild_count)
echo 3000000000 >/proc/sys/net/ipv4/rt_cache_rebuild_count
On an old kernel, you probably need to patch your kernel, or backport
commit 1080d709fb9d8cd43 (net: implement emergency route cache rebulds
when gc_elasticity is exceeded)
next prev parent reply other threads:[~2011-09-09 22:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-09 5:04 Memory leak in ip_dst_cache Kumar S
2011-09-09 5:30 ` Eric Dumazet
[not found] ` <1315593553.98279.YahooMailNeo@web113904.mail.gq1.yahoo.com>
[not found] ` <1315596786.2606.3.camel@edumazet-laptop>
2011-09-09 20:48 ` Kumar S
2011-09-09 21:47 ` Eric Dumazet
[not found] ` <1315605497.25052.YahooMailNeo@web113916.mail.gq1.yahoo.com>
2011-09-09 22:08 ` Eric Dumazet [this message]
2011-09-09 22:53 ` Kumar S
2011-09-10 13:04 ` Neil Horman
2011-09-12 3:38 ` Kumar S
2011-09-12 5:40 ` Eric Dumazet
2011-09-12 6:07 ` Kumar S
2011-09-12 6:28 ` Eric Dumazet
2011-09-12 17:16 ` Kumar S
2011-09-12 17:57 ` Eric Dumazet
2011-09-12 22:20 ` Kumar S
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=1315606125.2606.19.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=ps2kumar@yahoo.com \
/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