Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267588AbUJLTXc (ORCPT ); Tue, 12 Oct 2004 15:23:32 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267576AbUJLTXc (ORCPT ); Tue, 12 Oct 2004 15:23:32 -0400 Received: from cpu1185.adsl.bellglobal.com ([207.236.110.166]:43203 "EHLO mail.rtr.ca") by vger.kernel.org with ESMTP id S267678AbUJLTUO (ORCPT ); Tue, 12 Oct 2004 15:20:14 -0400 Message-ID: <416C2DFE.2030006@rtr.ca> Date: Tue, 12 Oct 2004 15:18:22 -0400 From: Mark Lord User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040913 X-Accept-Language: en, en-us MIME-Version: 1.0 To: Jeff Garzik Cc: James Bottomley , Christoph Hellwig , Mark Lord , Linux Kernel , SCSI Mailing List Subject: Re: driver hacking tips (was Re: [PATCH] QStor SATA/RAID driver for 2.6.9-rc3) References: <4161A06D.8010601@rtr.ca> <416547B6.5080505@rtr.ca> <20041007150709.B12688@i nfradead.org> <4165624C.5060405@rtr.ca> <416565DB.4050006@pobox.com> <4165 A 4 5D.2090200@rtr.ca> <4165A766.1040104@pobox.com> <4165A85D.7080704@rtr.ca > <4 165AB1B.8000204@pobox.com> <4165ACF8.8060208@rtr.ca> <20041007221537. A17 712@infradead.org> <1097241583.2412.15.camel@mulgrave> <4166AF2F.607090 4@rtr.ca> <1097249266.1678.40.camel@mulgrave> <4166B48E.3020006@rtr.ca> <1097250465.2412.49.camel@mulgrave> <416C0D55.1020603@rtr.ca> <1097601478.2044.103.camel@mulgrave> <416C12CC.1050301@rtr.ca> <1097602220.2044.119.camel@mulgrave> <416C157A.6030400@rtr.ca> <416C177B.6030504@pobox.com> <416C19B9.7000806@rtr.ca> <416C2189.4080302@pobox.com> In-Reply-To: <416C2189.4080302@pobox.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 720 Lines: 20 >Storage drivers that want to handle long-running events, >or events that need process context, typically want to >either fire off events _asynchronously_ via schedule_work(), >or have a long-running thread that does nothing but processes >an internal driver event queue. At driver module unload time, is there any way to guarantee that all pending "schedule_work()" events have been processed? How? Thanks -- Mark Lord (hdparm keeper & the original "Linux IDE Guy") - 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/