From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Abraham van der Merwe <abz@frogfoot.net>,
Zwane Mwaikambo <zwane@arm.linux.org.uk>,
Linux Kernel Discussions <linux-kernel@vger.kernel.org>
Subject: Re: sleeping in dev->tx_timeout?
Date: 03 Aug 2003 21:54:54 +0100 [thread overview]
Message-ID: <1059944094.31901.5.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <3F2D6727.8070203@pobox.com>
On Sul, 2003-08-03 at 20:48, Jeff Garzik wrote:
> These days drivers often need quite a while for hardware reset. I am
> pushing to move this code, long term, into process context. So, in
> tx_timeout:
> * disable NIC and interrupts as best you can, quickly
> * schedule_task/schedule_work to schedule the full hardware reset
And if the hardware is hard to recover or needs messy recovery code take
a look at the PCI layer tricks in -ac
prev parent reply other threads:[~2003-08-03 20:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-03 18:37 sleeping in dev->tx_timeout? Abraham van der Merwe
2003-08-03 19:10 ` Zwane Mwaikambo
2003-08-03 19:37 ` Abraham van der Merwe
2003-08-03 19:48 ` Jeff Garzik
2003-08-03 20:54 ` Alan Cox [this message]
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=1059944094.31901.5.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=abz@frogfoot.net \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@arm.linux.org.uk \
/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