2) for cases where we haven't implemented dynamic
table growth, specifying a proper limit argument
to the hash table allocation is a sufficient
solution for the time being
Agreed, just we don't know what the proper limits are.
I guess it would need someone running quite a lot of benchmarks.
Anyone volunteering? @)
In my original post I noted how it is quite easy to consume
the whole 1Gb of RAM on i686 PC (and it's only 4,194,304 entries)
it looks like with more IP addresses it is not that hard to
consume much more memory.
Or do some cheesy default and document the options to change
it clearly and wait for feedback from users on what works for
them?
Kirill
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html