From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "Feldman, Scott" <scott.feldman@intel.com>
Cc: "'Troy Wilson'" <tcw@tempest.prismnet.com>,
linux-kernel@vger.kernel.org, Martin.Bligh@us.ibm.com,
tcw@prismnet.com, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: mdelay causes BUG, please use udelay
Date: Tue, 20 Aug 2002 20:59:25 -0400 [thread overview]
Message-ID: <3D62E5ED.6020707@mandrakesoft.com> (raw)
In-Reply-To: 288F9BF66CD9D5118DF400508B68C4460283E4AF@orsmsx113.jf.intel.com
Feldman, Scott wrote:
>>- msec_delay(10);
>>+ usec_delay(10000);
>
>
> Jeff, 10000 seems on the border of what's OK. If it's acceptable, then
> let's go for that. Otherwise, we're going to have to chain several
> mod_timer callbacks together to do a controller reset.
That definitely wants fixing. Since I like doing resets and similar
slow-paths in process context -- sleep for as long as you want -- I
would say kick over to a function called via schedule_task()
Just make sure other parts of the driver that may be called
asynchronously, such as ethtool ioctls, are disabled. Remember that
tx_timeout holds the dev->xmit_lock as well, so spending a long time in
there is a bad idea in general.
I would probably call netif_carrier_off() first thing in tx_timeout, too.
Jeff
next prev parent reply other threads:[~2002-08-21 0:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-21 0:20 mdelay causes BUG, please use udelay Feldman, Scott
2002-08-21 0:27 ` Benjamin LaHaise
2002-08-21 0:28 ` H. Peter Anvin
2002-08-21 0:28 ` Alan Cox
2002-08-21 0:59 ` Jeff Garzik [this message]
2002-08-21 16:04 ` Martin J. Bligh
2002-08-21 16:45 ` Chris Friesen
2002-08-21 16:56 ` Martin J. Bligh
2002-08-21 17:21 ` Dave Hansen
-- strict thread matches above, loose matches on Subject: below --
2002-08-21 0:59 Feldman, Scott
2002-08-20 23:50 Troy Wilson
2002-08-21 1:00 ` Jeff Garzik
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=3D62E5ED.6020707@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=Martin.Bligh@us.ibm.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=scott.feldman@intel.com \
--cc=tcw@prismnet.com \
--cc=tcw@tempest.prismnet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.