Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751100AbVKASeP (ORCPT ); Tue, 1 Nov 2005 13:34:15 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751102AbVKASeP (ORCPT ); Tue, 1 Nov 2005 13:34:15 -0500 Received: from dsl092-053-140.phl1.dsl.speakeasy.net ([66.92.53.140]:28863 "EHLO grelber.thyrsus.com") by vger.kernel.org with ESMTP id S1751100AbVKASeP (ORCPT ); Tue, 1 Nov 2005 13:34:15 -0500 From: Rob Landley Organization: Boundaries Unlimited To: Ingo Molnar Subject: Re: [Lhms-devel] [PATCH 0/7] Fragmentation Avoidance V19 Date: Tue, 1 Nov 2005 12:33:35 -0600 User-Agent: KMail/1.8 Cc: Mel Gorman , Nick Piggin , "Martin J. Bligh" , Andrew Morton , kravetz@us.ibm.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org, lhms-devel@lists.sourceforge.net References: <20051030235440.6938a0e9.akpm@osdl.org> <20051101144622.GC9911@elte.hu> In-Reply-To: <20051101144622.GC9911@elte.hu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511011233.36713.rob@landley.net> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 691 Lines: 17 On Tuesday 01 November 2005 08:46, Ingo Molnar wrote: > how will the 100% solution handle a simple kmalloc()-ed kernel buffer, > that is pinned down, and to/from which live pointers may exist? That > alone can prevent RAM from being removable. Would you like to apply your "100% or nothing" argument to the virtual memory management subsystem and see how it sounds in that context? (As an argument that we shouldn't _have_ one?) > Ingo Rob - 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/