DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:from:to:subject:date:user-agent:organization:mime-version:content-type:content-transfer-encoding:content-disposition:message-id;
        b=K2DGsGtFZYJYRIoeKljcxVJ7yurSLNuKY4HQ4Aj5Lg079ZxafT5ttACd/mlsetaFJ/sHi7nclwQcPAIpeaakH3wdIqD5i2p8/wbYaewMnyRybSYqPOITi3/v1eF/sYayhIEWrAhDOu4kfjWwYr2AJlmCyIwgYiVy+IZtwwCpiZQ=
From: Vicente Feito <vicente.feito@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: workqueue - process context
Date: Sat, 19 Feb 2005 01:48:11 +0000
User-Agent: KMail/1.7.1
Organization: none
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200502190148.11334.vicente.feito@gmail.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1079
Lines: 22

I've been playing with workqueues, and I've found that once I unload the 
module, if I don't call destroy_workqueue(); then the workqueue I've created 
stays in the process list, [my_wq], I don't know if that's meant to be, or is 
it a bug, cause I believe there can be two options in here:

1) It's meant to be so you can unload your module and let the works run some 
time after you're already gone, that allows you to probe other modules or do 
whatever necesary without the need to wait for the workqueue to be emtpy.

2) It's a bug, cause the module allows to be unloaded, destroying the structs 
but not removing the workqueue from the process context.

Which one is it?I hope I'm being clear with my question.
I was about to try to find a solution to remove the queue but maybe it's meant 
to be, although not likely.

Vicente.
-
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/