From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH -rt DO NOT APPLY] Fix for tg3 networking lockup Date: Tue, 08 Aug 2006 15:00:06 -0700 (PDT) Message-ID: <20060808.150006.48399434.davem@davemloft.net> References: <20060806.231846.71090637.davem@davemloft.net> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: tytso@mit.edu, mchan@broadcom.com, herbert@gondor.apana.org.au, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, tglx@linutronix.de, mingo@elte.hu Return-path: Received: from dsl027-180-168.sfo1.dsl.speakeasy.net ([216.27.180.168]:44717 "EHLO sunset.davemloft.net") by vger.kernel.org with ESMTP id S1030278AbWHHWAC (ORCPT ); Tue, 8 Aug 2006 18:00:02 -0400 To: rostedt@goodmis.org In-Reply-To: Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org From: Steven Rostedt Date: Tue, 8 Aug 2006 08:24:10 -0400 (EDT) > Of the 4 timers, only one is a timeout. The other three expire every time, > forcing the timer wheel into effect. Even though it's one timer > implementing 4, it's expensive to use it as a watchdog. It's not a watchdog, the timer continually fires. It is the on-chip ASF firmware that "times out" if it does not see the heartbeat message from the driver within 5 seconds. The driver timer in question runs every 2 seconds to write this heartbeat message to the chip.