Searched hist:"8 d4698f7a54a492a1b96c505b30fe750ae3e61d5" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/net/bridge/ |
| H A D | br_ioctl.c | diff 8d4698f7a54a492a1b96c505b30fe750ae3e61d5 Mon Sep 08 15:44:40 CDT 2008 Stephen Hemminger <shemminger@vyatta.com> 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>
|
| H A D | br_sysfs_br.c | diff 8d4698f7a54a492a1b96c505b30fe750ae3e61d5 Mon Sep 08 15:44:40 CDT 2008 Stephen Hemminger <shemminger@vyatta.com> 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>
|