Rick Jones fb811395cd net: add explicit logging and stat for neighbour table overflow
Add an explicit neighbour table overflow message (ratelimited) and
statistic to make diagnosing neighbour table overflows tractable in
the wild.

Diagnosing a neighbour table overflow can be quite difficult in the wild
because there is no explicit dmesg logged.  Callers to neighbour code
seem to use net_dbg_ratelimit when the neighbour call fails which means
the "base message" is not emitted and the callback suppressed messages
from the ratelimiting can end-up juxtaposed with unrelated messages.
Further, a forced garbage collection will increment a stat on each call
whether it was successful in freeing-up a table entry or not, so that
statistic is only a hint.  So, add a net_info_ratelimited message and
explicit statistic to the neighbour code.

Signed-off-by: Rick Jones <rick.jones2@hp.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2015-08-10 13:46:21 -07:00
..
2015-06-11 23:37:37 +02:00
2015-06-14 12:55:49 -07:00
2014-09-18 10:54:36 +02:00
2015-03-04 00:23:23 -05:00
2015-06-28 16:55:44 -07:00
2015-07-23 17:10:49 +02:00
2015-03-06 21:50:02 -05:00
2015-07-21 10:39:05 -07:00
2013-11-07 19:28:58 -05:00
2014-09-30 01:02:26 -04:00
2015-03-12 14:39:40 -04:00
2014-06-04 22:46:38 -07:00
2015-01-18 01:56:32 -05:00
2015-03-12 14:39:40 -04:00
2015-07-29 22:44:04 -07:00
2014-01-03 20:56:48 -05:00
2015-07-21 10:39:05 -07:00
2015-06-10 12:24:33 +02:00
2014-06-02 11:00:41 -07:00
2015-03-12 22:58:12 -04:00
2014-05-22 14:57:15 -04:00