From: "Michael Chan" <mchan@broadcom.com>
To: "Andy Gospodarek" <andy@greyhouse.net>
Cc: "Herbert Xu" <herbert@gondor.apana.org.au>,
shawvrana@gmail.com, netdev@vger.kernel.org,
auke-jan.h.kok@intel.com, davem@davemloft.net, jgarzik@pobox.com
Subject: Re: e1000_down and tx_timeout worker race cleaning the transmit buffers
Date: Fri, 21 Apr 2006 12:00:31 -0700 [thread overview]
Message-ID: <1145646031.3843.5.camel@rh4> (raw)
In-Reply-To: <bdfc5d6e0604211301k682b35d1r52a52cd3fec80ddc@mail.gmail.com>
On Fri, 2006-04-21 at 16:01 -0400, Andy Gospodarek wrote:
> I just hate to see extra resources used to solve problems that good
> coding can solve (not that my suggestion is necessarily a 'good' one),
> so I was trying to think of a way to resolve this without explicitly
> adding another workqueue.
If you don't want to add another workqueue, then look at tg3, bnx2, and
one of the smc drivers on how to effectively wait for the driver's
workqueue task to finish without deadlocking with linkwatch_event.
next prev parent reply other threads:[~2006-04-21 20:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200604201035.00100.shaw@vranix.com>
2006-04-20 23:36 ` e1000_down and tx_timeout worker race cleaning the transmit buffers Herbert Xu
2006-04-20 23:51 ` Herbert Xu
2006-04-20 22:36 ` Michael Chan
2006-04-21 1:27 ` Herbert Xu
2006-04-21 1:33 ` Herbert Xu
2006-04-21 0:10 ` Michael Chan
2006-04-21 2:37 ` Herbert Xu
2006-04-21 2:40 ` Herbert Xu
2006-04-21 1:24 ` Michael Chan
2006-04-21 13:27 ` Andy Gospodarek
2006-04-21 15:28 ` Michael Chan
2006-04-21 20:01 ` Andy Gospodarek
2006-04-21 19:00 ` Michael Chan [this message]
2006-04-21 20:46 ` Andy Gospodarek
2006-04-27 0:14 ` Shaw
2006-04-27 4:55 ` Auke Kok
2006-04-29 21:57 ` Shaw Vrana
2006-04-21 2:42 ` Shaw Vrana
2006-04-21 1:33 ` Michael Chan
2006-04-21 3:05 ` shaw
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=1145646031.3843.5.camel@rh4 \
--to=mchan@broadcom.com \
--cc=andy@greyhouse.net \
--cc=auke-jan.h.kok@intel.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jgarzik@pobox.com \
--cc=netdev@vger.kernel.org \
--cc=shawvrana@gmail.com \
/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).