Subject: Re: [PATCH] [2.6.0-test3] request_firmware related problems.
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Andrew Morton <akpm@osdl.org>, ranty@debian.org,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
       willy@debian.org
In-Reply-To: <3F36CE8D.8090201@pobox.com>
References: <20030810210646.GA6746@ranty.pantax.net>
	 <20030810142928.4b734e8d.akpm@osdl.org> <3F36CD93.4010704@pobox.com>
	 <3F36CE8D.8090201@pobox.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Organization: 
Message-Id: <1060701706.21159.26.camel@dhcp22.swansea.linux.org.uk>
Mime-Version: 1.0
Date: 12 Aug 2003 16:21:46 +0100
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 844
Lines: 19

On Llu, 2003-08-11 at 00:00, Jeff Garzik wrote:
> > 2) ponder perhaps an implementation that would use generic keventd until 
> > a certain load is reached; then, create per-cpu kernel threads just like 
> > private workqueue creation occurs now.  i.e. switch from shared 
> > (keventd) to private at runtime.
> 
> 
> 3) offer private workqueue interface like we have now -- but one thread 
> only, not NN threads

4) Have one permanent thread running which kicks off another thread
whenever something has been on the queue for more than 5 seconds and
reaps threads when the queue is empty for 30 ?

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