Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753564Ab3GXQDw (ORCPT ); Wed, 24 Jul 2013 12:03:52 -0400 Received: from mail-gh0-f175.google.com ([209.85.160.175]:58369 "EHLO mail-gh0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750991Ab3GXQDu (ORCPT ); Wed, 24 Jul 2013 12:03:50 -0400 Date: Wed, 24 Jul 2013 12:03:42 -0400 From: Tejun Heo To: Tang Chen Cc: tglx@linutronix.de, mingo@elte.hu, hpa@zytor.com, akpm@linux-foundation.org, trenn@suse.de, yinghai@kernel.org, jiang.liu@huawei.com, wency@cn.fujitsu.com, laijs@cn.fujitsu.com, isimatu.yasuaki@jp.fujitsu.com, izumi.taku@jp.fujitsu.com, mgorman@suse.de, minchan@kernel.org, mina86@mina86.com, gong.chen@linux.intel.com, vasilis.liaskovitis@profitbricks.com, lwoodman@redhat.com, riel@redhat.com, jweiner@redhat.com, prarit@redhat.com, zhangyanfei@cn.fujitsu.com, yanghy@cn.fujitsu.com, x86@kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-acpi@vger.kernel.org Subject: Re: [PATCH 11/21] x86: get pg_data_t's memory from other node Message-ID: <20130724160342.GC20377@mtj.dyndns.org> References: <1374220774-29974-1-git-send-email-tangchen@cn.fujitsu.com> <1374220774-29974-12-git-send-email-tangchen@cn.fujitsu.com> <20130723200924.GP21100@mtj.dyndns.org> <51EF4F95.1050308@cn.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <51EF4F95.1050308@cn.fujitsu.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 975 Lines: 24 Hello, Tang. On Wed, Jul 24, 2013 at 11:52:53AM +0800, Tang Chen wrote: > The node data should be on local, I agree with that. I'm not saying I > won't do it. Just for now, it will be complicated to fix memory hot-remove > path. So I think pushing this patch for now, and do the local node things > in the next step. I see. As long as it's clearly noted in the patch description and as comment && the behavior is off unless explicitly enabled, it should be fine for now, I think. As currently implemented, the users of memory hotplug would have to pay pretty heavy price in terms of memory locality overhead in general and it could be that the ones missed here might not make noticeable difference anyway. Thanks. -- tejun -- 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/