From: Boian Bonev <boian@bonev.com>
To: Andrew Morton <akpm@osdl.org>, netdev@oss.sgi.com
Cc: buakaw@buakaw.homelinux.net
Subject: Re: dst cache overflow messages
Date: Mon, 21 Mar 2005 04:05:26 +0200 [thread overview]
Message-ID: <20050321020526.20420.qmail@orange.bonev.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1341 bytes --]
hi,
this happens very rare. it is mostly seen on systems with full bgp table combined with a massive scan on diverse networks caused by worms/troyans/etc.
you can tuneup your systems' max route cache size by
echo sane-big-value > /proc/sys/net/ipv4/route/max_size
if you happen to get a permanent attack, you may also need to twiddle with garbage collection values in /proc/sys/net/ipv4/route/gc_* to ensure that the route cache will not grow more than the max value for the period of gc.
b.
> ----- Original Message ----
> From: Andrew Morton <akpm@osdl.org>
> To: netdev@oss.sgi.com
> Sent: Sun, 20 Mar 2005 16:37:25 -0800
> Subject: Fw: dst cache overflow messages
>
>
>
> Begin forwarded message:
>
> Date: Sun, 20 Mar 2005 22:51:08 +0200 (EET)
> From: buakaw@buakaw.homelinux.net
> To: linux-kernel@vger.kernel.org
> Subject:
>
>
> the system become very laggy.
> i use kernel 2.6.10/2.6.11.3 on p4 2.8, msi915p, 3 x 3com905 boomerang.
> and the cpu usage normally be about 12% and after something happens it
> boost to 100% and it is used mostly by ksoftirqd/0, and a little bit by
> migration/0 and event/0. and in syslog i found thies lines
>
> Mar 20 22:21:09 buakaw kernel: printk: 5543 messages suppressed.
> Mar 20 22:21:09 buakaw kernel: dst cache overflow
>
> what can cause this?
reply other threads:[~2005-03-21 2:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050321020526.20420.qmail@orange.bonev.com \
--to=boian@bonev.com \
--cc=akpm@osdl.org \
--cc=buakaw@buakaw.homelinux.net \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).