From: Tang Chen <tangchen@cn.fujitsu.com>
To: Vasilis Liaskovitis <vasilis.liaskovitis@profitbricks.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,
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 07/13] x86, numa, mem-hotplug: Mark nodes which the kernel resides in.
Date: Thu, 06 Jun 2013 17:42:27 +0800 [thread overview]
Message-ID: <51B05983.5060009@cn.fujitsu.com> (raw)
In-Reply-To: <20130603131823.GA4729@dhcp-192-168-178-175.profitbricks.localdomain>
Hi Vasilis,
On 06/03/2013 09:18 PM, Vasilis Liaskovitis wrote:
......
>>
>> In such an early time, I think we can only get nid from
>> numa_meminfo. So as I
>> said above, I'd like to fix this problem by making memblock has correct nid.
>>
>> And I read the patch below. I think if we get nid from numa_meminfo,
>> than we
>> don't need to call memblock_get_region_node().
>>
>
> ok. If we update the memblock nid fields from numa_meminfo,
> memblock_get_region_node will always return the correct node id.
>
I have fixed this problem in this way. And I'll send the new patches
next week.
Thanks. :)
--
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: Vasilis Liaskovitis <vasilis.liaskovitis@profitbricks.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,
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 07/13] x86, numa, mem-hotplug: Mark nodes which the kernel resides in.
Date: Thu, 06 Jun 2013 17:42:27 +0800 [thread overview]
Message-ID: <51B05983.5060009@cn.fujitsu.com> (raw)
In-Reply-To: <20130603131823.GA4729@dhcp-192-168-178-175.profitbricks.localdomain>
Hi Vasilis,
On 06/03/2013 09:18 PM, Vasilis Liaskovitis wrote:
......
>>
>> In such an early time, I think we can only get nid from
>> numa_meminfo. So as I
>> said above, I'd like to fix this problem by making memblock has correct nid.
>>
>> And I read the patch below. I think if we get nid from numa_meminfo,
>> than we
>> don't need to call memblock_get_region_node().
>>
>
> ok. If we update the memblock nid fields from numa_meminfo,
> memblock_get_region_node will always return the correct node id.
>
I have fixed this problem in this way. And I'll send the new patches
next week.
Thanks. :)
next prev parent reply other threads:[~2013-06-06 9:39 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:59 ` Tang Chen
2013-06-03 1:59 ` Tang Chen
2013-06-03 1:30 ` Wanpeng Li
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 [this message]
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 7:37 ` Tang Chen
2013-06-03 7:37 ` Tang Chen
2013-06-03 2:59 ` Wanpeng Li
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=51B05983.5060009@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=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.