From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Date: Fri, 11 Jul 2014 20:20:51 +0000 Subject: Re: [RFC Patch V1 00/30] Enable memoryless node on x86 platforms Message-Id: <8761j3ve8s.fsf@tassilo.jf.intel.com> List-Id: References: <1405064267-11678-1-git-send-email-jiang.liu@linux.intel.com> <20140711082956.GC20603@laptop.programming.kicks-ass.net> <20140711153314.GA6155@kroah.com> In-Reply-To: <20140711153314.GA6155@kroah.com> (Greg KH's message of "Fri, 11 Jul 2014 08:33:14 -0700") MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Greg KH Cc: Jiang Liu , Peter Zijlstra , Andrew Morton , Mel Gorman , David Rientjes , Mike Galbraith , "Rafael J . Wysocki" , Tony Luck , linux-mm@kvack.org, linux-hotplug@vger.kernel.org, linux-kernel@vger.kernel.org Greg KH writes: > On Fri, Jul 11, 2014 at 10:29:56AM +0200, Peter Zijlstra wrote: >> On Fri, Jul 11, 2014 at 03:37:17PM +0800, Jiang Liu wrote: >> > Any comments are welcomed! >> >> Why would anybody _ever_ have a memoryless node? That's ridiculous. > > I'm with Peter here, why would this be a situation that we should even > support? Are there machines out there shipping like this? We've always had memory nodes. A classic case in the old days was a two socket system where someone didn't populate any DIMMs on the second socket. There are other cases too. -Andi -- ak@linux.intel.com -- Speaking for myself only From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pd0-f182.google.com (mail-pd0-f182.google.com [209.85.192.182]) by kanga.kvack.org (Postfix) with ESMTP id A6E266B0035 for ; Fri, 11 Jul 2014 16:21:24 -0400 (EDT) Received: by mail-pd0-f182.google.com with SMTP id p10so1615974pdj.13 for ; Fri, 11 Jul 2014 13:21:24 -0700 (PDT) Received: from mga01.intel.com (mga01.intel.com. [192.55.52.88]) by mx.google.com with ESMTP id j4si1760435pdb.273.2014.07.11.13.21.21 for ; Fri, 11 Jul 2014 13:21:22 -0700 (PDT) From: Andi Kleen Subject: Re: [RFC Patch V1 00/30] Enable memoryless node on x86 platforms References: <1405064267-11678-1-git-send-email-jiang.liu@linux.intel.com> <20140711082956.GC20603@laptop.programming.kicks-ass.net> <20140711153314.GA6155@kroah.com> Date: Fri, 11 Jul 2014 13:20:51 -0700 In-Reply-To: <20140711153314.GA6155@kroah.com> (Greg KH's message of "Fri, 11 Jul 2014 08:33:14 -0700") Message-ID: <8761j3ve8s.fsf@tassilo.jf.intel.com> MIME-Version: 1.0 Content-Type: text/plain Sender: owner-linux-mm@kvack.org List-ID: To: Greg KH Cc: Jiang Liu , Peter Zijlstra , Andrew Morton , Mel Gorman , David Rientjes , Mike Galbraith , "Rafael J . Wysocki" , Tony Luck , linux-mm@kvack.org, linux-hotplug@vger.kernel.org, linux-kernel@vger.kernel.org Greg KH writes: > On Fri, Jul 11, 2014 at 10:29:56AM +0200, Peter Zijlstra wrote: >> On Fri, Jul 11, 2014 at 03:37:17PM +0800, Jiang Liu wrote: >> > Any comments are welcomed! >> >> Why would anybody _ever_ have a memoryless node? That's ridiculous. > > I'm with Peter here, why would this be a situation that we should even > support? Are there machines out there shipping like this? We've always had memory nodes. A classic case in the old days was a two socket system where someone didn't populate any DIMMs on the second socket. There are other cases too. -Andi -- ak@linux.intel.com -- Speaking for myself only -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755311AbaGKUVX (ORCPT ); Fri, 11 Jul 2014 16:21:23 -0400 Received: from mga14.intel.com ([192.55.52.115]:14845 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752541AbaGKUVV (ORCPT ); Fri, 11 Jul 2014 16:21:21 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.01,644,1400050800"; d="scan'208";a="560664560" From: Andi Kleen To: Greg KH Cc: Jiang Liu , Peter Zijlstra , Andrew Morton , Mel Gorman , David Rientjes , Mike Galbraith , "Rafael J . Wysocki" , Tony Luck , linux-mm@kvack.org, linux-hotplug@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [RFC Patch V1 00/30] Enable memoryless node on x86 platforms References: <1405064267-11678-1-git-send-email-jiang.liu@linux.intel.com> <20140711082956.GC20603@laptop.programming.kicks-ass.net> <20140711153314.GA6155@kroah.com> Date: Fri, 11 Jul 2014 13:20:51 -0700 In-Reply-To: <20140711153314.GA6155@kroah.com> (Greg KH's message of "Fri, 11 Jul 2014 08:33:14 -0700") Message-ID: <8761j3ve8s.fsf@tassilo.jf.intel.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Greg KH writes: > On Fri, Jul 11, 2014 at 10:29:56AM +0200, Peter Zijlstra wrote: >> On Fri, Jul 11, 2014 at 03:37:17PM +0800, Jiang Liu wrote: >> > Any comments are welcomed! >> >> Why would anybody _ever_ have a memoryless node? That's ridiculous. > > I'm with Peter here, why would this be a situation that we should even > support? Are there machines out there shipping like this? We've always had memory nodes. A classic case in the old days was a two socket system where someone didn't populate any DIMMs on the second socket. There are other cases too. -Andi -- ak@linux.intel.com -- Speaking for myself only