> 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.
Have you already forgotten the whole day lost staring to some impossible
numbers for number of misses? :-)
The only output which you can get from ratio hits/misses is to _increase_
size of cache when number of misses growth. It is not only useless, it
is exactly opposite to the behaviour which you want to see.
We want to shrink it at DoS, remember? I still do not know any criterium,
apparently it should be based not on ratio hits/misses, but on absolute
rates or something like that. average/max = 1/2 is always acceptable,
perfect at normal flow rates and not disasterous even for 1packet/flow.