Re: [RFC] bridge: STP timer management range checking

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Valdis.Kletnieks
Date: Sunday, August 31, 2008 - 7:25 pm

On Sun, 31 Aug 2008 10:43:09 PDT, Stephen Hemminger said:


Did you mean "apparently working but *non*-standards conforming"?

Other than that, seems to be a sane application of "Be conservative in what you
send".  Our network is some 30K cat-5 ports, 1100 switches, 1300 wireless
access points, and we appreciate it every time somebody makes things more
bulletproof.  And yes, we prefer things to out-and-out *fail* rather than
run in a wonky configuration - hard failures usually get fixed in a few
minutes, wonkiness can drag on for months of mystifying symptoms...
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: ksoftirqd high cpu load on kernels 2.6.24 to 2.6.27-rc ..., Stephen Hemminger, (Sun Aug 31, 10:05 am)
[RFC] bridge: STP timer management range checking, Stephen Hemminger, (Sun Aug 31, 10:43 am)
Re: [RFC] bridge: STP timer management range checking, Stephen Hemminger, (Sun Aug 31, 4:29 pm)
Re: [RFC] bridge: STP timer management range checking, Valdis.Kletnieks, (Sun Aug 31, 7:25 pm)
Re: [RFC] bridge: STP timer management range checking, David Miller, (Tue Sep 2, 4:41 pm)
Re: [RFC] bridge: STP timer management range checking, David Miller, (Tue Sep 2, 5:28 pm)
[PATCH] bridge: don't allow setting hello time to zero, Stephen Hemminger, (Thu Sep 4, 3:47 pm)
Re: [PATCH] bridge: don't allow setting hello time to zero, Dushan Tcholich, (Mon Sep 8, 2:35 pm)
Re: [PATCH] bridge: don't allow setting hello time to zero, Stephen Hemminger, (Mon Sep 8, 3:33 pm)