From: David Miller <davem@davemloft.net>
To: tytso@mit.edu
Cc: dwalker@mvista.com, herbert@gondor.apana.org.au,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
mchan@broadcom.com
Subject: Re: [PATCH -rt DO NOT APPLY] Fix for tg3 networking lockup
Date: Thu, 03 Aug 2006 14:45:58 -0700 (PDT) [thread overview]
Message-ID: <20060803.144558.02298663.davem@davemloft.net> (raw)
In-Reply-To: <20060803171731.GE20603@thunk.org>
From: Theodore Tso <tytso@mit.edu>
Date: Thu, 3 Aug 2006 13:17:31 -0400
> The tg3_timer() code, for example, is trigger by the device driver but
> isn't associated with a process for boosting purposes, and creating a
> process just so that tg3_timer() can be boosted seems like the Wrong
Ted please make sure the tg3 chips you have actually do need
that periodic poking code that tg3_timer() has, most chips do
not.
You don't need the periodic poke unless TG3_FLAG_TAGGED_STATUS is
cleared, and that is only the case for two chips 1) 5700 and 2) 5788.
The only thing left is the link status and that is not so concerned
about mild forms of latency in the timer firing.
next prev parent reply other threads:[~2006-08-03 21:45 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060803075704.GC27835@thunk.org>
2006-08-03 10:00 ` [PATCH -rt DO NOT APPLY] Fix for tg3 networking lockup Herbert Xu
2006-08-03 16:32 ` Theodore Tso
2006-08-03 16:46 ` Daniel Walker
2006-08-03 17:17 ` Theodore Tso
2006-08-03 21:45 ` David Miller [this message]
2006-08-03 16:49 ` Randy.Dunlap
2006-08-03 17:04 ` Alistair John Strachan
2006-08-03 21:43 ` David Miller
2006-08-03 17:28 ` Theodore Tso
2006-08-03 18:36 ` Michael Chan
2006-08-03 20:17 ` Theodore Tso
2006-08-03 21:48 ` David Miller
2006-08-03 23:28 ` Michael Chan
2006-08-03 23:43 ` David Miller
2006-08-04 0:07 ` Theodore Tso
2006-08-04 0:20 ` David Miller
2006-08-04 0:25 ` Arjan van de Ven
2006-08-04 3:23 ` Theodore Tso
2006-08-04 3:45 ` Michael Chan
2006-08-05 20:26 ` Theodore Tso
2006-08-08 6:36 ` Michael Chan
2006-08-25 22:33 ` Marc Bevand
2006-08-25 22:55 ` Michael Chan
2006-08-25 23:48 ` Marc Bevand
2006-08-26 0:01 ` Michael Chan
2006-08-03 23:53 ` Theodore Tso
2006-08-03 23:56 ` David Miller
2006-08-03 23:59 ` Herbert Xu
2006-08-04 0:01 ` David Miller
2006-08-04 0:16 ` Michael Chan
2006-08-04 0:03 ` Daniel Walker
2006-08-07 5:34 ` Steven Rostedt
2006-08-07 6:18 ` David Miller
2006-08-08 12:24 ` Steven Rostedt
2006-08-08 13:13 ` Steven Rostedt
2006-08-08 22:00 ` David Miller
2006-08-08 22:27 ` Steven Rostedt
2006-08-09 11:29 ` Roman Zippel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060803.144558.02298663.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dwalker@mvista.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).