From: Wen Congyang <wency@cn.fujitsu.com>
To: Jaegeuk Hanse <jaegeuk.hanse@gmail.com>
Cc: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>,
x86@kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-acpi@vger.kernel.org,
linux-s390@vger.kernel.org, linux-sh@vger.kernel.org,
linux-ia64@vger.kernel.org, cmetcalf@tilera.com,
sparclinux@vger.kernel.org, David Rientjes <rientjes@google.com>,
Jiang Liu <liuj97@gmail.com>, Len Brown <len.brown@intel.com>,
benh@kernel.crashing.org, paulus@samba.org,
Christoph Lameter <cl@linux.com>,
Minchan Kim <minchan.kim@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Jianguo Wu <wujianguo@huawei.com>
Subject: Re: [PATCH v3 06/12] memory-hotplug: unregister memory section on SPARSEMEM_VMEMMAP
Date: Tue, 20 Nov 2012 14:55:35 +0800 [thread overview]
Message-ID: <50AB2967.5010302@cn.fujitsu.com> (raw)
In-Reply-To: <50AB21A4.8050709@gmail.com>
At 11/20/2012 02:22 PM, Jaegeuk Hanse Wrote:
> On 11/01/2012 05:44 PM, Wen Congyang wrote:
>> From: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
>>
>> Currently __remove_section for SPARSEMEM_VMEMMAP does nothing. But
>> even if
>> we use SPARSEMEM_VMEMMAP, we can unregister the memory_section.
>>
>> So the patch add unregister_memory_section() into __remove_section().
>
> Hi Yasuaki,
>
> In order to review this patch, I should dig sparse memory codes in
> advance. But I have some confuse of codes. Why need encode/decode mem
> map instead of set mem_map to ms->section_mem_map directly?
The memmap is aligned, and the low bits are zero. We store some information
in these bits. So we need to encode/decode memmap here.
Thanks
Wen Congyang
>
> Regards,
> Jaegeuk
>
>>
>> CC: David Rientjes <rientjes@google.com>
>> CC: Jiang Liu <liuj97@gmail.com>
>> CC: Len Brown <len.brown@intel.com>
>> CC: Christoph Lameter <cl@linux.com>
>> Cc: Minchan Kim <minchan.kim@gmail.com>
>> CC: Andrew Morton <akpm@linux-foundation.org>
>> CC: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
>> CC: Wen Congyang <wency@cn.fujitsu.com>
>> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
>> ---
>> mm/memory_hotplug.c | 13 ++++++++-----
>> 1 file changed, 8 insertions(+), 5 deletions(-)
>>
>> diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
>> index ca07433..66a79a7 100644
>> --- a/mm/memory_hotplug.c
>> +++ b/mm/memory_hotplug.c
>> @@ -286,11 +286,14 @@ static int __meminit __add_section(int nid,
>> struct zone *zone,
>> #ifdef CONFIG_SPARSEMEM_VMEMMAP
>> static int __remove_section(struct zone *zone, struct mem_section *ms)
>> {
>> - /*
>> - * XXX: Freeing memmap with vmemmap is not implement yet.
>> - * This should be removed later.
>> - */
>> - return -EBUSY;
>> + int ret = -EINVAL;
>> +
>> + if (!valid_section(ms))
>> + return ret;
>> +
>> + ret = unregister_memory_section(ms);
>> +
>> + return ret;
>> }
>> #else
>> static int __remove_section(struct zone *zone, struct mem_section *ms)
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Wen Congyang <wency@cn.fujitsu.com>
To: Jaegeuk Hanse <jaegeuk.hanse@gmail.com>
Cc: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>,
x86@kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-acpi@vger.kernel.org,
linux-s390@vger.kernel.org, linux-sh@vger.kernel.org,
linux-ia64@vger.kernel.org, cmetcalf@tilera.com,
sparclinux@vger.kernel.org, David Rientjes <rientjes@google.com>,
Jiang Liu <liuj97@gmail.com>, Len Brown <len.brown@intel.com>,
benh@kernel.crashing.org, paulus@samba.org,
Christoph Lameter <cl@linux.com>,
Minchan Kim <minchan.kim@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Jianguo Wu <wujianguo@huawei.com>
Subject: Re: [PATCH v3 06/12] memory-hotplug: unregister memory section on SPARSEMEM_VMEMMAP
Date: Tue, 20 Nov 2012 06:55:35 +0000 [thread overview]
Message-ID: <50AB2967.5010302@cn.fujitsu.com> (raw)
In-Reply-To: <50AB21A4.8050709@gmail.com>
At 11/20/2012 02:22 PM, Jaegeuk Hanse Wrote:
> On 11/01/2012 05:44 PM, Wen Congyang wrote:
>> From: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
>>
>> Currently __remove_section for SPARSEMEM_VMEMMAP does nothing. But
>> even if
>> we use SPARSEMEM_VMEMMAP, we can unregister the memory_section.
>>
>> So the patch add unregister_memory_section() into __remove_section().
>
> Hi Yasuaki,
>
> In order to review this patch, I should dig sparse memory codes in
> advance. But I have some confuse of codes. Why need encode/decode mem
> map instead of set mem_map to ms->section_mem_map directly?
The memmap is aligned, and the low bits are zero. We store some information
in these bits. So we need to encode/decode memmap here.
Thanks
Wen Congyang
>
> Regards,
> Jaegeuk
>
>>
>> CC: David Rientjes <rientjes@google.com>
>> CC: Jiang Liu <liuj97@gmail.com>
>> CC: Len Brown <len.brown@intel.com>
>> CC: Christoph Lameter <cl@linux.com>
>> Cc: Minchan Kim <minchan.kim@gmail.com>
>> CC: Andrew Morton <akpm@linux-foundation.org>
>> CC: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
>> CC: Wen Congyang <wency@cn.fujitsu.com>
>> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
>> ---
>> mm/memory_hotplug.c | 13 ++++++++-----
>> 1 file changed, 8 insertions(+), 5 deletions(-)
>>
>> diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
>> index ca07433..66a79a7 100644
>> --- a/mm/memory_hotplug.c
>> +++ b/mm/memory_hotplug.c
>> @@ -286,11 +286,14 @@ static int __meminit __add_section(int nid,
>> struct zone *zone,
>> #ifdef CONFIG_SPARSEMEM_VMEMMAP
>> static int __remove_section(struct zone *zone, struct mem_section *ms)
>> {
>> - /*
>> - * XXX: Freeing memmap with vmemmap is not implement yet.
>> - * This should be removed later.
>> - */
>> - return -EBUSY;
>> + int ret = -EINVAL;
>> +
>> + if (!valid_section(ms))
>> + return ret;
>> +
>> + ret = unregister_memory_section(ms);
>> +
>> + return ret;
>> }
>> #else
>> static int __remove_section(struct zone *zone, struct mem_section *ms)
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Wen Congyang <wency@cn.fujitsu.com>
To: Jaegeuk Hanse <jaegeuk.hanse@gmail.com>
Cc: linux-s390@vger.kernel.org, linux-ia64@vger.kernel.org,
Len Brown <len.brown@intel.com>,
linux-acpi@vger.kernel.org, linux-sh@vger.kernel.org,
x86@kernel.org, linux-kernel@vger.kernel.org,
cmetcalf@tilera.com, Jianguo Wu <wujianguo@huawei.com>,
linux-mm@kvack.org,
Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>,
paulus@samba.org, Minchan Kim <minchan.kim@gmail.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
David Rientjes <rientjes@google.com>,
sparclinux@vger.kernel.org, Christoph Lameter <cl@linux.com>,
linuxppc-dev@lists.ozlabs.org,
Andrew Morton <akpm@linux-foundation.org>,
Jiang Liu <liuj97@gmail.com>
Subject: Re: [PATCH v3 06/12] memory-hotplug: unregister memory section on SPARSEMEM_VMEMMAP
Date: Tue, 20 Nov 2012 14:55:35 +0800 [thread overview]
Message-ID: <50AB2967.5010302@cn.fujitsu.com> (raw)
In-Reply-To: <50AB21A4.8050709@gmail.com>
At 11/20/2012 02:22 PM, Jaegeuk Hanse Wrote:
> On 11/01/2012 05:44 PM, Wen Congyang wrote:
>> From: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
>>
>> Currently __remove_section for SPARSEMEM_VMEMMAP does nothing. But
>> even if
>> we use SPARSEMEM_VMEMMAP, we can unregister the memory_section.
>>
>> So the patch add unregister_memory_section() into __remove_section().
>
> Hi Yasuaki,
>
> In order to review this patch, I should dig sparse memory codes in
> advance. But I have some confuse of codes. Why need encode/decode mem
> map instead of set mem_map to ms->section_mem_map directly?
The memmap is aligned, and the low bits are zero. We store some information
in these bits. So we need to encode/decode memmap here.
Thanks
Wen Congyang
>
> Regards,
> Jaegeuk
>
>>
>> CC: David Rientjes <rientjes@google.com>
>> CC: Jiang Liu <liuj97@gmail.com>
>> CC: Len Brown <len.brown@intel.com>
>> CC: Christoph Lameter <cl@linux.com>
>> Cc: Minchan Kim <minchan.kim@gmail.com>
>> CC: Andrew Morton <akpm@linux-foundation.org>
>> CC: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
>> CC: Wen Congyang <wency@cn.fujitsu.com>
>> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
>> ---
>> mm/memory_hotplug.c | 13 ++++++++-----
>> 1 file changed, 8 insertions(+), 5 deletions(-)
>>
>> diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
>> index ca07433..66a79a7 100644
>> --- a/mm/memory_hotplug.c
>> +++ b/mm/memory_hotplug.c
>> @@ -286,11 +286,14 @@ static int __meminit __add_section(int nid,
>> struct zone *zone,
>> #ifdef CONFIG_SPARSEMEM_VMEMMAP
>> static int __remove_section(struct zone *zone, struct mem_section *ms)
>> {
>> - /*
>> - * XXX: Freeing memmap with vmemmap is not implement yet.
>> - * This should be removed later.
>> - */
>> - return -EBUSY;
>> + int ret = -EINVAL;
>> +
>> + if (!valid_section(ms))
>> + return ret;
>> +
>> + ret = unregister_memory_section(ms);
>> +
>> + return ret;
>> }
>> #else
>> static int __remove_section(struct zone *zone, struct mem_section *ms)
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Wen Congyang <wency@cn.fujitsu.com>
To: Jaegeuk Hanse <jaegeuk.hanse@gmail.com>
Cc: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>,
x86@kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-acpi@vger.kernel.org,
linux-s390@vger.kernel.org, linux-sh@vger.kernel.org,
linux-ia64@vger.kernel.org, cmetcalf@tilera.com,
sparclinux@vger.kernel.org, David Rientjes <rientjes@google.com>,
Jiang Liu <liuj97@gmail.com>, Len Brown <len.brown@intel.com>,
benh@kernel.crashing.org, paulus@samba.org,
Christoph Lameter <cl@linux.com>,
Minchan Kim <minchan.kim@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Jianguo Wu <wujianguo@huawei.com>
Subject: Re: [PATCH v3 06/12] memory-hotplug: unregister memory section on SPARSEMEM_VMEMMAP
Date: Tue, 20 Nov 2012 14:55:35 +0800 [thread overview]
Message-ID: <50AB2967.5010302@cn.fujitsu.com> (raw)
In-Reply-To: <50AB21A4.8050709@gmail.com>
At 11/20/2012 02:22 PM, Jaegeuk Hanse Wrote:
> On 11/01/2012 05:44 PM, Wen Congyang wrote:
>> From: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
>>
>> Currently __remove_section for SPARSEMEM_VMEMMAP does nothing. But
>> even if
>> we use SPARSEMEM_VMEMMAP, we can unregister the memory_section.
>>
>> So the patch add unregister_memory_section() into __remove_section().
>
> Hi Yasuaki,
>
> In order to review this patch, I should dig sparse memory codes in
> advance. But I have some confuse of codes. Why need encode/decode mem
> map instead of set mem_map to ms->section_mem_map directly?
The memmap is aligned, and the low bits are zero. We store some information
in these bits. So we need to encode/decode memmap here.
Thanks
Wen Congyang
>
> Regards,
> Jaegeuk
>
>>
>> CC: David Rientjes <rientjes@google.com>
>> CC: Jiang Liu <liuj97@gmail.com>
>> CC: Len Brown <len.brown@intel.com>
>> CC: Christoph Lameter <cl@linux.com>
>> Cc: Minchan Kim <minchan.kim@gmail.com>
>> CC: Andrew Morton <akpm@linux-foundation.org>
>> CC: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
>> CC: Wen Congyang <wency@cn.fujitsu.com>
>> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
>> ---
>> mm/memory_hotplug.c | 13 ++++++++-----
>> 1 file changed, 8 insertions(+), 5 deletions(-)
>>
>> diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
>> index ca07433..66a79a7 100644
>> --- a/mm/memory_hotplug.c
>> +++ b/mm/memory_hotplug.c
>> @@ -286,11 +286,14 @@ static int __meminit __add_section(int nid,
>> struct zone *zone,
>> #ifdef CONFIG_SPARSEMEM_VMEMMAP
>> static int __remove_section(struct zone *zone, struct mem_section *ms)
>> {
>> - /*
>> - * XXX: Freeing memmap with vmemmap is not implement yet.
>> - * This should be removed later.
>> - */
>> - return -EBUSY;
>> + int ret = -EINVAL;
>> +
>> + if (!valid_section(ms))
>> + return ret;
>> +
>> + ret = unregister_memory_section(ms);
>> +
>> + return ret;
>> }
>> #else
>> static int __remove_section(struct zone *zone, struct mem_section *ms)
>
>
--
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>
next prev parent reply other threads:[~2012-11-20 6:55 UTC|newest]
Thread overview: 146+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-01 9:44 [PATCH v3 00/12] memory-hotplug: hot-remove physical memory Wen Congyang
2012-11-01 9:44 ` Wen Congyang
2012-11-01 9:44 ` Wen Congyang
2012-11-01 9:44 ` Wen Congyang
2012-11-01 9:44 ` [PATCH v3 01/12] memory-hotplug: try to offline the memory twice to avoid dependence Wen Congyang
2012-11-01 9:44 ` Wen Congyang
2012-11-01 9:44 ` Wen Congyang
2012-11-01 9:44 ` Wen Congyang
2012-11-01 9:44 ` [PATCH v3 02/12] memory-hotplug: check whether all memory blocks are offlined or not when removing memory Wen Congyang
2012-11-01 9:44 ` Wen Congyang
2012-11-01 9:44 ` Wen Congyang
2012-11-01 9:44 ` [PATCH v3 02/12] memory-hotplug: check whether all memory blocks are offlined or not when removing m Wen Congyang
2012-11-01 9:44 ` [PATCH v3 03/12] memory-hotplug: remove redundant codes Wen Congyang
2012-11-01 9:44 ` Wen Congyang
2012-11-01 9:44 ` Wen Congyang
2012-11-01 9:44 ` Wen Congyang
2012-11-01 9:44 ` [PATCH v3 04/12] memory-hotplug: remove /sys/firmware/memmap/X sysfs Wen Congyang
2012-11-01 9:44 ` Wen Congyang
2012-11-01 9:44 ` Wen Congyang
2012-11-01 9:44 ` Wen Congyang
2012-11-01 9:44 ` [PATCH v3 05/12] memory-hotplug: introduce new function arch_remove_memory() for removing page table depends on architecture Wen Congyang
2012-11-01 9:44 ` Wen Congyang
2012-11-01 9:44 ` Wen Congyang
2012-11-01 9:44 ` [PATCH v3 05/12] memory-hotplug: introduce new function arch_remove_memory() for removing page table Wen Congyang
2012-11-01 9:44 ` [PATCH v3 06/12] memory-hotplug: unregister memory section on SPARSEMEM_VMEMMAP Wen Congyang
2012-11-01 9:44 ` Wen Congyang
2012-11-01 9:44 ` Wen Congyang
2012-11-01 9:44 ` Wen Congyang
2012-11-20 6:22 ` Jaegeuk Hanse
2012-11-20 6:22 ` Jaegeuk Hanse
2012-11-20 6:22 ` Jaegeuk Hanse
2012-11-20 6:22 ` Jaegeuk Hanse
2012-11-20 6:22 ` Jaegeuk Hanse
2012-11-20 6:55 ` Wen Congyang [this message]
2012-11-20 6:55 ` Wen Congyang
2012-11-20 6:55 ` Wen Congyang
2012-11-20 6:55 ` Wen Congyang
2012-11-20 6:58 ` Jaegeuk Hanse
2012-11-20 6:58 ` Jaegeuk Hanse
2012-11-20 6:58 ` Jaegeuk Hanse
2012-11-20 6:58 ` Jaegeuk Hanse
2012-11-20 9:37 ` Wen Congyang
2012-11-20 9:37 ` Wen Congyang
2012-11-20 9:37 ` Wen Congyang
2012-11-20 9:37 ` Wen Congyang
2012-11-20 11:03 ` Jaegeuk Hanse
2012-11-20 11:03 ` Jaegeuk Hanse
2012-11-20 11:03 ` Jaegeuk Hanse
2012-11-20 11:03 ` Jaegeuk Hanse
2012-11-20 11:16 ` Jaegeuk Hanse
2012-11-20 11:16 ` Jaegeuk Hanse
2012-11-20 11:16 ` Jaegeuk Hanse
2012-11-20 11:16 ` Jaegeuk Hanse
2012-11-20 11:16 ` Jaegeuk Hanse
2012-11-21 2:59 ` Wen Congyang
2012-11-21 3:05 ` Wen Congyang
2012-11-21 3:05 ` Wen Congyang
2012-11-21 3:05 ` Wen Congyang
2012-11-21 2:59 ` Wen Congyang
2012-11-21 2:59 ` Wen Congyang
2012-11-21 4:22 ` Jaegeuk Hanse
2012-11-21 4:22 ` Jaegeuk Hanse
2012-11-21 4:22 ` Jaegeuk Hanse
2012-11-21 4:22 ` Jaegeuk Hanse
2012-11-21 4:42 ` Wen Congyang
2012-11-21 4:42 ` Wen Congyang
2012-11-21 4:42 ` Wen Congyang
2012-11-21 4:42 ` Wen Congyang
2012-11-21 5:03 ` Jaegeuk Hanse
2012-11-21 5:03 ` Jaegeuk Hanse
2012-11-21 5:03 ` Jaegeuk Hanse
2012-11-21 5:03 ` Jaegeuk Hanse
2012-11-21 5:12 ` Wen Congyang
2012-11-21 5:12 ` Wen Congyang
2012-11-21 5:12 ` Wen Congyang
2012-11-21 5:12 ` Wen Congyang
2012-11-21 5:28 ` Wen Congyang
2012-11-21 5:28 ` Wen Congyang
2012-11-21 5:28 ` Wen Congyang
2012-11-21 5:28 ` Wen Congyang
2012-11-01 9:44 ` [PATCH v3 07/12] memory-hotplug: implement register_page_bootmem_info_section of sparse-vmemmap Wen Congyang
2012-11-01 9:44 ` Wen Congyang
2012-11-01 9:44 ` Wen Congyang
2012-11-01 9:44 ` Wen Congyang
2012-11-01 9:44 ` [PATCH v3 08/12] memory-hotplug: remove memmap " Wen Congyang
2012-11-01 9:44 ` Wen Congyang
2012-11-01 9:44 ` Wen Congyang
2012-11-01 9:44 ` Wen Congyang
2012-11-27 5:47 ` Jianguo Wu
2012-11-27 5:47 ` Jianguo Wu
2012-11-27 5:47 ` Jianguo Wu
2012-11-27 5:47 ` Jianguo Wu
2012-11-27 6:39 ` Wen Congyang
2012-11-27 6:39 ` Wen Congyang
2012-11-27 6:39 ` Wen Congyang
2012-11-27 6:39 ` Wen Congyang
2012-11-27 6:49 ` Wen Congyang
2012-11-27 6:49 ` Wen Congyang
2012-11-27 6:49 ` Wen Congyang
2012-11-27 6:49 ` Wen Congyang
2012-11-27 7:14 ` Jianguo Wu
2012-11-27 7:14 ` Jianguo Wu
2012-11-27 7:14 ` Jianguo Wu
2012-11-27 7:14 ` Jianguo Wu
2012-11-27 7:14 ` Jianguo Wu
2012-11-01 9:44 ` [PATCH v3 09/12] memory-hotplug: remove page table of x86_64 architecture Wen Congyang
2012-11-01 9:44 ` Wen Congyang
2012-11-01 9:44 ` Wen Congyang
2012-11-01 9:44 ` Wen Congyang
2012-11-01 9:44 ` [PATCH v3 10/12] memory-hotplug: memory_hotplug: clear zone when removing the memory Wen Congyang
2012-11-01 9:44 ` Wen Congyang
2012-11-01 9:44 ` Wen Congyang
2012-11-01 9:44 ` Wen Congyang
2012-11-01 9:44 ` [PATCH v3 11/12] memory-hotplug: remove sysfs file of node Wen Congyang
2012-11-01 9:44 ` Wen Congyang
2012-11-01 9:44 ` Wen Congyang
2012-11-01 9:44 ` Wen Congyang
2012-11-19 10:08 ` Yasuaki Ishimatsu
2012-11-19 10:08 ` Yasuaki Ishimatsu
2012-11-19 10:08 ` Yasuaki Ishimatsu
2012-11-19 10:08 ` Yasuaki Ishimatsu
2012-11-19 10:08 ` Yasuaki Ishimatsu
2012-11-20 9:35 ` Wen Congyang
2012-11-20 9:35 ` Wen Congyang
2012-11-20 9:35 ` Wen Congyang
2012-11-20 9:35 ` Wen Congyang
2012-11-26 14:27 ` Jianguo Wu
2012-11-26 14:27 ` Jianguo Wu
2012-11-26 14:27 ` Jianguo Wu
2012-11-26 14:27 ` Jianguo Wu
2012-11-27 2:24 ` Wen Congyang
2012-11-27 2:24 ` Wen Congyang
2012-11-27 2:24 ` Wen Congyang
2012-11-27 2:24 ` Wen Congyang
2012-11-01 9:44 ` [PATCH v3 12/12] memory-hotplug: free node_data when a node is offlined Wen Congyang
2012-11-01 9:44 ` Wen Congyang
2012-11-01 9:44 ` Wen Congyang
2012-11-01 9:44 ` Wen Congyang
2012-11-16 11:55 ` [PATCH v3 00/12] memory-hotplug: hot-remove physical memory Wen Congyang
2012-11-16 11:55 ` Wen Congyang
2012-11-16 11:55 ` Wen Congyang
2012-11-16 11:55 ` Wen Congyang
2012-11-22 1:33 ` Yasuaki Ishimatsu
2012-11-22 1:33 ` Yasuaki Ishimatsu
2012-11-22 1:33 ` Yasuaki Ishimatsu
2012-11-22 1:33 ` Yasuaki Ishimatsu
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=50AB2967.5010302@cn.fujitsu.com \
--to=wency@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=cl@linux.com \
--cc=cmetcalf@tilera.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=jaegeuk.hanse@gmail.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=liuj97@gmail.com \
--cc=minchan.kim@gmail.com \
--cc=paulus@samba.org \
--cc=rientjes@google.com \
--cc=sparclinux@vger.kernel.org \
--cc=wujianguo@huawei.com \
--cc=x86@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.