Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753341AbbEHUtF (ORCPT ); Fri, 8 May 2015 16:49:05 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:33013 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751363AbbEHUtC (ORCPT ); Fri, 8 May 2015 16:49:02 -0400 Date: Fri, 8 May 2015 13:49:01 -0700 From: Andrew Morton To: Tony Luck Cc: Linux Kernel Mailing List , "linux-mm@kvack.org" Subject: Re: [PATCHv2 0/3] Find mirrored memory, use for boot time allocations Message-Id: <20150508134901.e3e7585b359b073253788c22@linux-foundation.org> In-Reply-To: References: <20150508130307.e9bfedcfc66cbe6e6b009f19@linux-foundation.org> X-Mailer: Sylpheed 3.4.1 (GTK+ 2.24.23; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 727 Lines: 16 On Fri, 8 May 2015 13:38:52 -0700 Tony Luck wrote: > > Will surplus ZONE_MIRROR memory be available for regular old movable > > allocations? > ZONE_MIRROR and ZONE_MOVABLE are pretty much opposites. We > only want kernel allocations in mirror memory, and we can't allow any > kernel allocations in movable (cause they'll pin it). What I mean is: allow userspace to consume ZONE_MIRROR memory because we can snatch it back if it is needed for kernel memory. -- 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/