Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751408AbWCBHVv (ORCPT ); Thu, 2 Mar 2006 02:21:51 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751411AbWCBHVu (ORCPT ); Thu, 2 Mar 2006 02:21:50 -0500 Received: from ns.virtualhost.dk ([195.184.98.160]:12359 "EHLO virtualhost.dk") by vger.kernel.org with ESMTP id S1751408AbWCBHVu (ORCPT ); Thu, 2 Mar 2006 02:21:50 -0500 Date: Thu, 2 Mar 2006 08:21:29 +0100 From: Jens Axboe To: Pierre Ossman , LKML Subject: Re: How to map high memory for block io Message-ID: <20060302072128.GQ4816@suse.de> References: <43DA84B2.8010501@drzeus.cx> <43DA97A3.4080408@drzeus.cx> <20060127225428.GD2767@flint.arm.linux.org.uk> <20060128191759.GC9750@suse.de> <43DBC6E2.4000305@drzeus.cx> <20060129152228.GF13831@suse.de> <43DDC6F9.6070007@drzeus.cx> <20060130080930.GB4209@suse.de> <43DFAEC6.3090205@drzeus.cx> <20060301232913.GC4024@flint.arm.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060301232913.GC4024@flint.arm.linux.org.uk> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1678 Lines: 46 On Wed, Mar 01 2006, Russell King wrote: > On Tue, Jan 31, 2006 at 07:39:02PM +0100, Pierre Ossman wrote: > > Jens Axboe wrote: > > > On Mon, Jan 30 2006, Pierre Ossman wrote: > > > > > >> Jens Axboe wrote: > > >> > > >>> > > >>> Ah, you need to disable clustering to prevent that from happening! I was > > >>> confused there for a while. > > >>> > > >>> > > >>> > > >> And which is the lesser evil, highmem bounce buffers or disabling > > >> clustering? I'd probably vote for the former since the MMC overhead can > > >> be quite large. > > >> > > > > > > Disabling clustering is by far the least expensive way to accomplish it. > > > > > > > > > > Russell, what's your view on this? And how should we handle it with > > regard to MMC drivers? > > Okay, I've hit this same problem (but in a slightly different way) with > mmci.c. The way I'm proposing to fix this for mmci is to introduce a > new capability which says "clustering is supported by this driver." > > I'm unconvinced that we can safely fiddle with the queue's flags once > the queue is in use, hence why I've gone for the init-time only solution. > Maybe Jens can comment on that? You can set it anytime, basically, provided you use the atomic bit operations on it. Of course you may be left with clustered and non-clustered requests in the queue until everything has drained out, but I doubt that would be a problem :-) -- Jens Axboe - 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/