All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tang Chen <tangchen@cn.fujitsu.com>
To: Wanpeng Li <liwanp@linux.vnet.ibm.com>
Cc: mingo@redhat.com, hpa@zytor.com, akpm@linux-foundation.org,
	yinghai@kernel.org, jiang.liu@huawei.com, wency@cn.fujitsu.com,
	laijs@cn.fujitsu.com, isimatu.yasuaki@jp.fujitsu.com,
	tj@kernel.org, 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,
	x86@kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v3 12/13] x86, numa, acpi, memory-hotplug: Make movablecore=acpi have higher priority.
Date: Mon, 03 Jun 2013 15:37:06 +0800	[thread overview]
Message-ID: <51AC47A2.6020108@cn.fujitsu.com> (raw)
In-Reply-To: <20130603025924.GB7441@hacker.(null)>

On 06/03/2013 10:59 AM, Wanpeng Li wrote:
> On Fri, May 24, 2013 at 05:29:21PM +0800, Tang Chen wrote:
>> Arrange hotpluggable memory as ZONE_MOVABLE will cause NUMA performance decreased
>> because the kernel cannot use movable memory.
>>
>> For users who don't use memory hotplug and who don't want to lose their NUMA
>> performance, they need a way to disable this functionality.
>>
>> So, if users specify "movablecore=acpi" in kernel commandline, the kernel will
>> use SRAT to arrange ZONE_MOVABLE, and it has higher priority then original
>> movablecore and kernelcore boot option.
>>
>> For those who don't want this, just specify nothing.
>>
>
> Reviewed-by: Wanpeng Li<liwanp@linux.vnet.ibm.com>

Thank you very much for reviewing these patches. :)

--
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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Tang Chen <tangchen@cn.fujitsu.com>
To: Wanpeng Li <liwanp@linux.vnet.ibm.com>
Cc: mingo@redhat.com, hpa@zytor.com, akpm@linux-foundation.org,
	yinghai@kernel.org, jiang.liu@huawei.com, wency@cn.fujitsu.com,
	laijs@cn.fujitsu.com, isimatu.yasuaki@jp.fujitsu.com,
	tj@kernel.org, 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,
	x86@kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v3 12/13] x86, numa, acpi, memory-hotplug: Make movablecore=acpi have higher priority.
Date: Mon, 03 Jun 2013 15:37:06 +0800	[thread overview]
Message-ID: <51AC47A2.6020108@cn.fujitsu.com> (raw)
In-Reply-To: <20130603025924.GB7441@hacker.(null)>

On 06/03/2013 10:59 AM, Wanpeng Li wrote:
> On Fri, May 24, 2013 at 05:29:21PM +0800, Tang Chen wrote:
>> Arrange hotpluggable memory as ZONE_MOVABLE will cause NUMA performance decreased
>> because the kernel cannot use movable memory.
>>
>> For users who don't use memory hotplug and who don't want to lose their NUMA
>> performance, they need a way to disable this functionality.
>>
>> So, if users specify "movablecore=acpi" in kernel commandline, the kernel will
>> use SRAT to arrange ZONE_MOVABLE, and it has higher priority then original
>> movablecore and kernelcore boot option.
>>
>> For those who don't want this, just specify nothing.
>>
>
> Reviewed-by: Wanpeng Li<liwanp@linux.vnet.ibm.com>

Thank you very much for reviewing these patches. :)


  reply	other threads:[~2013-06-03  7:34 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-24  9:29 [PATCH v3 00/13] Arrange hotpluggable memory in SRAT as ZONE_MOVABLE Tang Chen
2013-05-24  9:29 ` Tang Chen
2013-05-24  9:29 ` [PATCH v3 01/13] x86: get pg_data_t's memory from other node Tang Chen
2013-05-24  9:29   ` Tang Chen
2013-06-03  0:31   ` Wanpeng Li
2013-06-03  0:31   ` Wanpeng Li
2013-05-24  9:29 ` [PATCH v3 02/13] acpi: Print Hot-Pluggable Field in SRAT Tang Chen
2013-05-24  9:29   ` Tang Chen
2013-06-03  0:50   ` Wanpeng Li
2013-06-03  0:50   ` Wanpeng Li
2013-05-24  9:29 ` [PATCH v3 03/13] page_alloc, mem-hotplug: Improve movablecore to {en|dis}able using SRAT Tang Chen
2013-05-24  9:29   ` Tang Chen
2013-06-03  0:52   ` Wanpeng Li
2013-06-03  0:52   ` Wanpeng Li
2013-05-24  9:29 ` [PATCH v3 04/13] x86, numa, acpi, memory-hotplug: Introduce hotplug info into struct numa_meminfo Tang Chen
2013-05-24  9:29   ` Tang Chen
2013-05-24  9:29 ` [PATCH v3 05/13] x86, numa, acpi, memory-hotplug: Consider hotplug info when cleanup numa_meminfo Tang Chen
2013-05-24  9:29   ` Tang Chen
2013-05-24  9:29 ` [PATCH v3 06/13] memblock, numa: Introduce flag into memblock Tang Chen
2013-05-24  9:29   ` Tang Chen
2013-06-03  1:30   ` Wanpeng Li
2013-06-03  1:30   ` Wanpeng Li
2013-06-03  1:59     ` Tang Chen
2013-06-03  1:59       ` Tang Chen
2013-05-24  9:29 ` [PATCH v3 07/13] x86, numa, mem-hotplug: Mark nodes which the kernel resides in Tang Chen
2013-05-24  9:29   ` Tang Chen
2013-05-31 16:24   ` Vasilis Liaskovitis
2013-05-31 16:24     ` Vasilis Liaskovitis
2013-06-03  7:35     ` Tang Chen
2013-06-03  7:35       ` Tang Chen
2013-06-03 13:18       ` Vasilis Liaskovitis
2013-06-03 13:18         ` Vasilis Liaskovitis
2013-06-06  9:42         ` Tang Chen
2013-06-06  9:42           ` Tang Chen
2013-05-24  9:29 ` [PATCH v3 08/13] x86, numa: Move memory_add_physaddr_to_nid() to CONFIG_NUMA Tang Chen
2013-05-24  9:29   ` Tang Chen
2013-05-24  9:29 ` [PATCH v3 09/13] x86, numa, memblock: Introduce MEMBLK_LOCAL_NODE to mark and reserve node-life-cycle data Tang Chen
2013-05-24  9:29   ` Tang Chen
2013-05-24  9:29 ` [PATCH v3 10/13] x86, acpi, numa, mem-hotplug: Introduce MEMBLK_HOTPLUGGABLE to mark and reserve hotpluggable memory Tang Chen
2013-05-24  9:29   ` Tang Chen
2013-05-31 16:15   ` Vasilis Liaskovitis
2013-05-31 16:15     ` Vasilis Liaskovitis
2013-05-24  9:29 ` [PATCH v3 11/13] x86, memblock, mem-hotplug: Free hotpluggable memory reserved by memblock Tang Chen
2013-05-24  9:29   ` Tang Chen
2013-06-03  2:57   ` Wanpeng Li
2013-06-03  2:57   ` Wanpeng Li
2013-05-24  9:29 ` [PATCH v3 12/13] x86, numa, acpi, memory-hotplug: Make movablecore=acpi have higher priority Tang Chen
2013-05-24  9:29   ` Tang Chen
2013-06-03  2:59   ` Wanpeng Li
2013-06-03  2:59   ` Wanpeng Li
2013-06-03  7:37     ` Tang Chen [this message]
2013-06-03  7:37       ` Tang Chen
2013-05-24  9:29 ` [PATCH v3 13/13] doc, page_alloc, acpi, mem-hotplug: Add doc for movablecore=acpi boot option Tang Chen
2013-05-24  9:29   ` Tang Chen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51AC47A2.6020108@cn.fujitsu.com \
    --to=tangchen@cn.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=gong.chen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=isimatu.yasuaki@jp.fujitsu.com \
    --cc=jiang.liu@huawei.com \
    --cc=jweiner@redhat.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=liwanp@linux.vnet.ibm.com \
    --cc=lwoodman@redhat.com \
    --cc=mgorman@suse.de \
    --cc=mina86@mina86.com \
    --cc=minchan@kernel.org \
    --cc=mingo@redhat.com \
    --cc=prarit@redhat.com \
    --cc=riel@redhat.com \
    --cc=tj@kernel.org \
    --cc=vasilis.liaskovitis@profitbricks.com \
    --cc=wency@cn.fujitsu.com \
    --cc=x86@kernel.org \
    --cc=yinghai@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.