From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751868AbdJBVyt (ORCPT ); Mon, 2 Oct 2017 17:54:49 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:42096 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750927AbdJBVys (ORCPT ); Mon, 2 Oct 2017 17:54:48 -0400 Date: Mon, 2 Oct 2017 14:54:46 -0700 From: Andrew Morton To: Will Deacon Cc: Zhen Lei , Catalin Marinas , linux-kernel , linux-api , Greg Kroah-Hartman , Michal Hocko , linux-mm , Tianhong Ding , Hanjun Guo , Libin , Kefeng Wang Subject: Re: [PATCH v2 1/1] mm: only dispaly online cpus of the numa node Message-Id: <20171002145446.eade11c1f28d55e5f67aa4d0@linux-foundation.org> In-Reply-To: <20171002103806.GB3823@arm.com> References: <1506678805-15392-1-git-send-email-thunder.leizhen@huawei.com> <1506678805-15392-2-git-send-email-thunder.leizhen@huawei.com> <20171002103806.GB3823@arm.com> 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 On Mon, 2 Oct 2017 11:38:07 +0100 Will Deacon wrote: > > When I executed numactl -H(which read /sys/devices/system/node/nodeX/cpumap > > and display cpumask_of_node for each node), but I got different result on > > X86 and arm64. For each numa node, the former only displayed online CPUs, > > and the latter displayed all possible CPUs. Unfortunately, both Linux > > documentation and numactl manual have not described it clear. > > > > I sent a mail to ask for help, and Michal Hocko replied > > that he preferred to print online cpus because it doesn't really make much > > sense to bind anything on offline nodes. > > > > Signed-off-by: Zhen Lei > > Acked-by: Michal Hocko > > --- > > drivers/base/node.c | 12 ++++++++++-- > > 1 file changed, 10 insertions(+), 2 deletions(-) > > Which tree is this intended to go through? I'm happy to take it via arm64, > but I don't want to tread on anybody's toes in linux-next and it looks like > there are already queued changes to this file via Andrew's tree. I grabbed it. I suppose there's some small risk of userspace breakage so I suggest it be a 4.15-rc1 thing?