Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1423516AbWJaP6W (ORCPT ); Tue, 31 Oct 2006 10:58:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1423521AbWJaP6W (ORCPT ); Tue, 31 Oct 2006 10:58:22 -0500 Received: from wohnheim.fh-wedel.de ([213.39.233.138]:57240 "EHLO wohnheim.fh-wedel.de") by vger.kernel.org with ESMTP id S1423516AbWJaP6V (ORCPT ); Tue, 31 Oct 2006 10:58:21 -0500 Date: Tue, 31 Oct 2006 16:57:56 +0100 From: =?iso-8859-1?Q?J=F6rn?= Engel To: Pierre Ossman Cc: Arnd Bergmann , Christoph Hellwig , Jiri Slaby , Linux Kernel Mailing List , Adrian Bunk , Dominik Brodowski , Harald Welte , Arjan van de Ven , Jean Delvare Subject: Re: feature-removal-schedule obsoletes Message-ID: <20061031155756.GA23021@wohnheim.fh-wedel.de> References: <45324658.1000203@gmail.com> <20061016133352.GA23391@lst.de> <200610242124.49911.arnd@arndb.de> <4543162B.7030701@drzeus.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <4543162B.7030701@drzeus.cx> User-Agent: Mutt/1.5.9i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 801 Lines: 21 On Sat, 28 October 2006 10:34:51 +0200, Pierre Ossman wrote: > > What should be used to replace it? The MMC block driver uses it to > manage the block device queue. I am not that intimate with the block > layer so I do not know the proper fix. Why does the MMC block driver use a thread? Is there a technical reason for this or could it be done in original process context as well, removing some code and useless cpu scheduler overhead? J?rn -- When people work hard for you for a pat on the back, you've got to give them that pat. -- Robert Heinlein - 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/