Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S270648AbTHCU7H (ORCPT ); Sun, 3 Aug 2003 16:59:07 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S271106AbTHCU7G (ORCPT ); Sun, 3 Aug 2003 16:59:06 -0400 Received: from pc1-cwma1-5-cust4.swan.cable.ntl.com ([80.5.120.4]:45465 "EHLO lxorguk.ukuu.org.uk") by vger.kernel.org with ESMTP id S270648AbTHCU7D (ORCPT ); Sun, 3 Aug 2003 16:59:03 -0400 Subject: Re: sleeping in dev->tx_timeout? From: Alan Cox To: Jeff Garzik Cc: Abraham van der Merwe , Zwane Mwaikambo , Linux Kernel Discussions In-Reply-To: <3F2D6727.8070203@pobox.com> References: <20030803183707.GA13728@oasis.frogfoot.net> <20030803193708.GA13992@oasis.frogfoot.net> <3F2D6727.8070203@pobox.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1059944094.31901.5.camel@dhcp22.swansea.linux.org.uk> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 03 Aug 2003 21:54:54 +0100 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 687 Lines: 15 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/