Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965904AbWKXSMR (ORCPT ); Fri, 24 Nov 2006 13:12:17 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965906AbWKXSMR (ORCPT ); Fri, 24 Nov 2006 13:12:17 -0500 Received: from smtp.osdl.org ([65.172.181.25]:55703 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S965904AbWKXSMR (ORCPT ); Fri, 24 Nov 2006 13:12:17 -0500 Date: Fri, 24 Nov 2006 10:11:55 -0800 (PST) From: Linus Torvalds To: Christoph Lameter cc: Mel Gorman , linux-mm@kvack.org, Linux Kernel Mailing List Subject: Re: [PATCH 1/11] Add __GFP_MOVABLE flag and update callers In-Reply-To: Message-ID: References: <20061121225022.11710.72178.sendpatchset@skynet.skynet.ie> <20061121225042.11710.15200.sendpatchset@skynet.skynet.ie> <20061123163613.GA25818@skynet.ie> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 941 Lines: 24 On Fri, 24 Nov 2006, Christoph Lameter wrote: > > So please do not require movable pages to be user allocations. I don't think you read the whole sentence I wrote. Go back: USER just means "it it can fail much more eagerly". It really has nothing to do with user-mode per se. It's just not so core that the kernel cannot handle allocation failures, so it doesn't get to retry the allocation so eagerly. THAT is why "movable" is almost guaranteed to also imply USER. Not because it's not a "kernel" allocation. After all, _all_ page allocations are kernel allocations, it's just that some are more likely to be associated with direct user requests, and some are more internal. Linus - 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/