From: Eric Dumazet <dada1@cosmosbay.com>
To: Jesper Dangaard Brouer <hawk@diku.dk>
Cc: "David S. Miller" <davem@davemloft.net>,
dipankar@in.ibm.com, Robert Olsson <Robert.Olsson@data.slu.se>,
jens.laas@data.slu.se, hans.liss@its.uu.se,
linux-net@vger.kernel.org, linux-kernel@vger.kernel.org,
mike.stroyan@hp.com, Suresh Bhogavilli <sbhogavilli@verisign.com>
Subject: Re: Kernel panic: Route cache, RCU, possibly FIB trie.
Date: Thu, 23 Mar 2006 17:15:56 +0100 [thread overview]
Message-ID: <4422C9BC.3090400@cosmosbay.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0603231637360.29788@ask.diku.dk>
Jesper Dangaard Brouer a écrit :
>> grep . /proc/sys/net/ipv4/route/*
>> /proc/sys/net/ipv4/route/error_burst:5000
>> /proc/sys/net/ipv4/route/error_cost:1000
>> grep: /proc/sys/net/ipv4/route/flush: Operation not permitted
>> /proc/sys/net/ipv4/route/gc_elasticity:8
>> /proc/sys/net/ipv4/route/gc_interval:60
>> /proc/sys/net/ipv4/route/gc_min_interval:0
>> /proc/sys/net/ipv4/route/gc_min_interval_ms:500
>> /proc/sys/net/ipv4/route/gc_thresh:65536
>> /proc/sys/net/ipv4/route/gc_timeout:300
>> /proc/sys/net/ipv4/route/max_delay:10
>> /proc/sys/net/ipv4/route/max_size:1048576
>> /proc/sys/net/ipv4/route/min_adv_mss:256
>> /proc/sys/net/ipv4/route/min_delay:2
>> /proc/sys/net/ipv4/route/min_pmtu:552
>> /proc/sys/net/ipv4/route/mtu_expires:600
>> /proc/sys/net/ipv4/route/redirect_load:20
>> /proc/sys/net/ipv4/route/redirect_number:9
>> /proc/sys/net/ipv4/route/redirect_silence:20480
>> /proc/sys/net/ipv4/route/secret_interval:600
I would say : Change the settings :)
echo 2 > /proc/sys/net/ipv4/route/gc_elasticity
echo 1 > /proc/sys/net/ipv4/route/gc_interval
echo 131072 > /proc/sys/net/ipv4/route/gc_thresh
and watch the output of :
rtstat -c 100 -i 1
(you might have to recompile lnstat/rtstat from iproute2 package from
http://developer.osdl.org/dev/iproute2/download/
Eric
next prev parent reply other threads:[~2006-03-23 16:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 21:44 Kernel panic: Route cache, RCU, possibly FIB trie Jesper Dangaard Brouer
2006-03-20 22:09 ` Dipankar Sarma
2006-03-21 10:29 ` Jesper Dangaard Brouer
2006-03-21 10:37 ` David S. Miller
2006-03-21 14:51 ` Jesper Dangaard Brouer
2006-03-21 21:25 ` David S. Miller
2006-03-23 15:35 ` Jesper Dangaard Brouer
2006-03-23 15:44 ` Jesper Dangaard Brouer
2006-03-23 16:15 ` Eric Dumazet [this message]
2006-03-23 21:37 ` Jesper Dangaard Brouer
2006-03-24 6:11 ` Eric Dumazet
2006-03-24 10:34 ` Jesper Dangaard Brouer
2006-03-23 21:32 ` Robert Olsson
2006-03-21 13:28 ` Robert Olsson
2006-03-21 15:27 ` Jesper Dangaard Brouer
2006-03-21 15:37 ` Eric Dumazet
2006-03-21 15:43 ` Dipankar Sarma
2006-03-21 16:30 ` 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=4422C9BC.3090400@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=Robert.Olsson@data.slu.se \
--cc=davem@davemloft.net \
--cc=dipankar@in.ibm.com \
--cc=hans.liss@its.uu.se \
--cc=hawk@diku.dk \
--cc=jens.laas@data.slu.se \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=mike.stroyan@hp.com \
--cc=sbhogavilli@verisign.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