aboutsummaryrefslogtreecommitdiffstats
path: root/fs/dlm/lock.c
diff options
context:
space:
mode:
authorStephen Hemminger <shemminger@vyatta.com>2008-09-08 16:44:40 -0400
committerDavid S. Miller <davem@davemloft.net>2008-09-08 16:46:54 -0400
commit8d4698f7a54a492a1b96c505b30fe750ae3e61d5 (patch)
tree4bec6c7dcf06bb5df9645d702d554a071007b83a /fs/dlm/lock.c
parentd315492b1a6ba29da0fa2860759505ae1b2db857 (diff)
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>
Diffstat (limited to 'fs/dlm/lock.c')
0 files changed, 0 insertions, 0 deletions