From: Eric Dumazet <eric.dumazet@gmail.com>
To: "Paweł Staszewski" <pstaszewski@itcare.pl>
Cc: Linux Network Development list <netdev@vger.kernel.org>
Subject: Re: Problem wit route cache
Date: Mon, 08 Feb 2010 14:51:07 +0100 [thread overview]
Message-ID: <1265637067.3048.14.camel@edumazet-laptop> (raw)
In-Reply-To: <4B7012BC.9000702@itcare.pl>
Le lundi 08 février 2010 à 14:33 +0100, Paweł Staszewski a écrit :
> >
> Yes this is x86_64 kernel
> i kernels 2.6.32.2 / 2.6.32.7 and now 2.6.33-rc6-git5 and on all
> kernels the same thing happens.
> grep . /proc/sys/net/ipv4/route/*
> /proc/sys/net/ipv4/route/error_burst:1250
> /proc/sys/net/ipv4/route/error_cost:250
> grep: /proc/sys/net/ipv4/route/flush: Permission denied
> /proc/sys/net/ipv4/route/gc_elasticity:2
> /proc/sys/net/ipv4/route/gc_interval:2
> /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:65535
> /proc/sys/net/ipv4/route/gc_timeout:300
> /proc/sys/net/ipv4/route/max_size:524288
> /proc/sys/net/ipv4/route/min_adv_mss:256
> /proc/sys/net/ipv4/route/min_pmtu:552
> /proc/sys/net/ipv4/route/mtu_expires:600
> /proc/sys/net/ipv4/route/redirect_load:5
> /proc/sys/net/ipv4/route/redirect_number:9
> /proc/sys/net/ipv4/route/redirect_silence:5120
> /proc/sys/net/ipv4/route/secret_interval:2
>
> This happens not all the time.
> I have this info only when there are "internet rush hours" - thn there
> is about 700Mbit/s TX + 700Mbit/s RX forwarded traffic
>
I dont understand your settings, they are very very small for your
setup. You want to flush cache every 2 seconds...
With 12GB of ram, you could have
/proc/sys/net/ipv4/route/gc_thresh:524288
/proc/sys/net/ipv4/route/max_size:8388608
/proc/sys/net/ipv4/route/secret_interval:3600
/proc/sys/net/ipv4/route/gc_elasticity:4
/proc/sys/net/ipv4/route/gc_interval:1
That would allow about 2 million entries in your route cache, using 768
Mbytes of ram, and a good cache hit ratio.
next prev parent reply other threads:[~2010-02-08 13:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-08 13:16 Problem wit route cache Paweł Staszewski
2010-02-08 13:28 ` Eric Dumazet
2010-02-08 13:33 ` Paweł Staszewski
2010-02-08 13:51 ` Eric Dumazet [this message]
2010-02-08 13:59 ` Paweł Staszewski
2010-02-08 14:06 ` Eric Dumazet
2010-02-08 14:16 ` Paweł Staszewski
2010-02-08 14:32 ` Eric Dumazet
2010-02-08 19:32 ` [PATCH] dst: call cond_resched() in dst_gc_task() Eric Dumazet
2010-02-08 23:01 ` David Miller
2010-02-09 6:07 ` Eric Dumazet
2010-02-08 23:26 ` Andrew Morton
2010-02-08 23:34 ` David Miller
2010-02-08 23:37 ` Andrew Morton
2010-02-08 23:50 ` David Miller
2010-02-08 23:50 ` Stephen Hemminger
2010-02-09 6:06 ` Eric Dumazet
2010-02-09 6:35 ` Andrew Morton
2010-02-09 7:20 ` Eric Dumazet
2010-02-09 7:31 ` Andrew Morton
2010-02-08 14:32 ` Problem wit route cache Paweł Staszewski
2010-02-08 14:45 ` Paweł Staszewski
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=1265637067.3048.14.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pstaszewski@itcare.pl \
/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