Stephen Hemminger 8d4698f7a5 bridge: don't allow setting hello time to zero ... Dushan Tcholich reports that on his system ksoftirqd can consume between %6 to %10 of cpu time, and cause ~200 context switches per second. He then correlated this with a report by bdupree@techfinesse.com: http://marc.info/?l=linux-kernel&m=119613299024398&w=2 and the culprit cause seems to be starting the bridge interface. In particular, when starting the bridge interface, his scripts are specifying a hello timer interval of "0". The bridge hello time can't be safely set to values less than 1 second, otherwise it is possible to end up with a runaway timer. Signed-off-by: Stephen Hemminger <shemminger@vyatta.com> Signed-off-by: David S. Miller <davem@davemloft.net>		2008-09-08 13:46:54 -07:00
..
netfilter
br_device.c	bridge: show offload settings	2008-08-15 19:51:07 -07:00
br_fdb.c
br_forward.c
br_if.c
br_input.c
br_ioctl.c	bridge: don't allow setting hello time to zero	2008-09-08 13:46:54 -07:00
br_netfilter.c	bridge: fix compile warning in net/bridge/br_netfilter.c	2008-08-05 01:21:22 -07:00
br_netlink.c
br_notify.c
br_private_stp.h
br_private.h
br_stp_bpdu.c
br_stp_if.c
br_stp_timer.c
br_stp.c	bridge: Eliminate unnecessary forward delay	2008-08-05 18:42:51 -07:00
br_sysfs_br.c	bridge: don't allow setting hello time to zero	2008-09-08 13:46:54 -07:00
br_sysfs_if.c
br.c
Kconfig
Makefile