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

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Rick Jones
Date: Tuesday, September 2, 2008 - 5:00 pm

David Miller wrote:

But tuning TCP_RTO_MAX isn't permitted right?  I'm drawing (perhaps 
flawed) parallels/distinctions between what is/isn't permitted to tweak 
for timers for one protocol versus another and wondering which may be a 
case of sauce for the goose/gander.

rick jones
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
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, Rick Jones, (Tue Sep 2, 5:00 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)