> # Two serious and interesting mistakes were made in the patch of
> # 1. Variance of hash chain turned out to be unexpectedly high, so
> # chain length at <=ip_rt_gc_elasticity results in strong growth of
> # cache misses. Set the threshould to 2*ip_rt_gc_elasticity.
> # And continue to think how to switch to mode when lots of cache
> # entries are used once or twice, so truncation should be done at 1.
I'll guess the setting was very much affected by DoS attacs discussion which
indicated very different flowlenths compared to our actual measurement for
Uppsala University which had 65 pkts per new DST entry. Proably due to the
"new" applications and lots of students.
For autotuning I think we can have help from a ratio of warm cache hits
and misses (in_slow_tot) to set threshhold to trim hash chain lengths.