From: Eric Dumazet <dada1@cosmosbay.com>
To: Tobias Diedrich <ranma+kernel@tdiedrich.de>
Cc: linux-net@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: dst cache overflow
Date: Thu, 16 Aug 2007 18:45:01 +0200 [thread overview]
Message-ID: <20070816184501.cbbd28a2.dada1@cosmosbay.com> (raw)
In-Reply-To: <20070814180015.GB3024@yamamaya.is-a-geek.org>
On Tue, 14 Aug 2007 20:00:15 +0200
Tobias Diedrich <ranma+kernel@tdiedrich.de> wrote:
> Eric Dumazet wrote:
>
> > Tobias Diedrich <ranma+kernel@tdiedrich.de> wrote:
> >
> > > Hello,
> > >
> > > I suspect I'm seeing a slow dst cache leakage on one of my servers.
> > > The server in question (oni) regularly needs to be rebooted, because
> > > it loses network connectivity. However, netconsole and syslog shows that the
> > > machine is still running and the kernel complains about "dst cache
> > > overflow".
> > >
> > > I have since installed a monitoring script, which stores the output of
> > > both "ip route ls cache | fgrep cache | wc -l" and the 'entries' value
> > > of /proc/net/stat/rt_cache (as suggested in
> > > http://www.mail-archive.com/netdev@vger.kernel.org/msg02107.html)
> > > and produces a nice rrd graph:
> > >
> > > http://uguu.de/~ranma/route-month-oni.png
> > > So entries is growing more or less constantly, while the number of
> > > active routes (not visible on the graph due to being too small) is
> > > relatively constant.
> > >
> > > Comparing this to another host running the exact same kernel:
> > > http://uguu.de/~ranma/route-month-ari.png
> > > Here cached_routes and entries barely differ at all.
> > >
> > > The funny thing is, both hosts are running the exact same kernel
> > > and use more or less the same iptables rules.
> > >
> > > So I'm not sure what would cause the dst cache to leak only on host
> > > oni?
> > >
> >
> > Could you send the result of these commands on oni and ari ?
> >
> > ip route ls
> > grep . /proc/sys/net/ipv4/route/*
>
> Sure.
>
> AFAICS the only visible difference is gc_thresh, which is probably
> double the size on oni since oni has double the amount of memory
> (512MB for oni vs. 256MB for ari).
You might try to boot oni adding this to kernel commandline : rhash_entries=2047
so that oni has the same route cache hashtable, and see if it changes anything.
next prev parent reply other threads:[~2007-08-16 16:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-14 16:06 dst cache overflow Tobias Diedrich
2007-08-14 17:24 ` Eric Dumazet
2007-08-14 18:00 ` Tobias Diedrich
2007-08-16 16:45 ` Eric Dumazet [this message]
2007-12-14 17:29 ` Tobias Diedrich
2007-12-15 6:29 ` Herbert Xu
2007-12-15 10:08 ` Tobias Diedrich
2007-12-16 7:35 ` Herbert Xu
2007-12-16 8:38 ` Tobias Diedrich
2008-03-17 1:25 ` Tobias Diedrich
2008-03-18 18:59 ` Tobias Diedrich
2008-03-23 9:21 ` IPv6 slab leak (was: Re: dst cache overflow) Tobias Diedrich
2008-05-16 19:46 ` Tobias Diedrich
2008-05-18 16:49 ` Tobias Diedrich
-- strict thread matches above, loose matches on Subject: below --
2008-10-13 13:54 dst cache overflow Oleksandr Samoylyk
2005-03-20 20:51 buakaw
2005-03-22 3:40 ` dst cache overflow Andrew Morton
2005-03-22 8:39 ` buakaw
2005-03-22 16:16 ` Phil Oester
2005-03-22 17:07 ` buakaw
2005-03-22 21:12 ` Eric Dumazet
2005-03-22 22:14 ` buakaw
2005-03-23 6:21 ` Eric Dumazet
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=20070816184501.cbbd28a2.dada1@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=ranma+kernel@tdiedrich.de \
/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