From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: Re: [patch] rd: support XIP Date: Tue, 4 Dec 2007 03:26:20 -0800 Message-ID: <20071204032620.aaee039b.akpm@linux-foundation.org> References: <20071204042628.GA26636@wotan.suse.de> <200712041054.51599.borntraeger@de.ibm.com> <20071204101009.GB9618@wotan.suse.de> <20071204112100.GA20420@wotan.suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Christian Borntraeger , Linux Kernel Mailing List , linux-fsdevel@vger.kernel.org, "Eric W. Biederman" , rob@landley.net, Jens Axboe To: Nick Piggin Return-path: Received: from smtp2.linux-foundation.org ([207.189.120.14]:54496 "EHLO smtp2.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752068AbXLDL1K (ORCPT ); Tue, 4 Dec 2007 06:27:10 -0500 In-Reply-To: <20071204112100.GA20420@wotan.suse.de> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Tue, 4 Dec 2007 12:21:00 +0100 Nick Piggin wrote: > + * > + * Cannot support XIP and highmem, because our ->direct_access > + * routine for XIP must return memory that is always addressable. > + * If XIP was reworked to use pfns and kmap throughout, this > + * restriction might be able to be lifted. > */ > + gfp_flags = GFP_NOIO | __GFP_ZERO; > +#ifndef CONFIG_BLK_DEV_XIP > + gfp_flags |= __GFP_HIGHMEM; > +#endif A dubious tradeoff?