From: Julian Anastasov <ja@ssi.bg>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] two internet connections + filter?
Date: Tue, 01 Oct 2002 21:25:03 +0000 [thread overview]
Message-ID: <marc-lartc-103350750305441@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103321390812903@msgid-missing>
Hello,
On 30 Sep 2002, William L. Thomson Jr. wrote:
> I will go in order and below are the values I last tested, and the
> default values.
> # Default Values
> #echo 256 > /proc/sys/net/ipv4/route/gc_elasticity # 8
gc_elasticity can be 1..16, gc_elasticity*gc_thresh is
the desired number of entries we can live with, after
that point we start to worry about filling the cache.
> #echo 1 > /proc/sys/net/ipv4/route/gc_interval # 60
> #echo 0 > /proc/sys/net/ipv4/route/gc_timeout # 300
On each interval (gc_interval) up to gc_interval/gc_timeout
entries are checked for expiration. With the default parameters,
1/5 of the table on each 60sec, each cache entry lives up to 300sec
by default.
> #echo 0 > /proc/sys/net/ipv4/route/gc_min_interval # 5
gc_min_interval 0 means no restrictions for running GC,
may be it is good on load.
> #echo 128 > /proc/sys/net/ipv4/route/gc_thresh # 256
> #echo 1 > /proc/sys/net/ipv4/route/max_delay # 10
> #echo 1 > /proc/sys/net/ipv4/route/min_delay # 2
> #echo 0 > /proc/sys/net/ipv4/conf/eth1/rp_filter # 1
> #echo 0 > /proc/sys/net/ipv4/conf/eth2/rp_filter # 1
> The gc_timeout seems to be a timeout between gc's?
this is gc_interval
Regards
--
Julian Anastasov <ja@ssi.bg>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-10-01 21:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-28 11:36 [LARTC] two internet connections + filter? Dworf
2002-09-28 14:41 ` Jose Luis Domingo Lopez
2002-10-01 3:17 ` William L. Thomson Jr.
2002-10-01 21:25 ` Julian Anastasov [this message]
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=marc-lartc-103350750305441@msgid-missing \
--to=ja@ssi.bg \
--cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.