From: Piotr Kowalczyk <poe@koba.pl>
To: linux-kernel@vger.kernel.org
Subject: dst cache overflow, again
Date: Mon, 21 Feb 2005 14:21:50 +0100 [thread overview]
Message-ID: <4219E06E.6030700@koba.pl> (raw)
Hi all,
I'm suffering from destination cache overflow on router running kernel
2.6.10. This wouldn't be anything special if not different numbers
reported by slabinfo and the real state. It's worth to mention that
there was no problems with old 2.4.x here.
user@somemachine:~$ cat /proc/slabinfo | grep ip_dst_cache; \
> cat /proc/net/rt_cache | wc -l; \
> /sbin/ip ro sh cache | grep cache | wc -l;
ip_dst_cache 153870 154530 256 15 1 : tunables 120 60
8 : slabdata 10302 10302 0
2159
2247
I'm increasing /proc/sys/net/ipv4/route/max_size, but the value reported
by slabinfo also slowly but steady is going up.
There is similar issue here (maybe even more),
http://www.uwsg.iu.edu/hypermail/linux/net/0312.3/0000.html, but
unfortunatelly stayed without answer.
Please give some hints about that, or if I'm wrong (meaning that is not
a bug), tell me what to do - I don't want to reboot this router every
week and CC: me (I'm not subscribed to the list).
I'm also wondering if tuning of rhash_entries= boot parameter could help?
Thank you,
Piotr Kowalczyk
ps.
Output of rtstat, in case it would help:
user@somemachine:~$ ./rtstat
size IN: hit tot mc no_rt bcast madst masrc OUT: hit tot
mc GC: tot ignored goal_miss ovrf HASH: in_search out_search
152294 5094 5563 0 98 0 0 0 153 26
0 5687 5685 2 0 3199 27
152377 4902 5851 0 108 0 0 0 153 20
0 5980 5978 2 0 3284 39
152416 4932 5526 0 76 0 0 0 128 26
0 5629 5627 2 0 3080 22
next reply other threads:[~2005-02-21 13:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-21 13:21 Piotr Kowalczyk [this message]
2005-02-21 16:20 ` dst cache overflow, again Phil Oester
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=4219E06E.6030700@koba.pl \
--to=poe@koba.pl \
--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