From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wen Congyang Subject: Re: [PATCH v3 06/12] memory-hotplug: unregister memory section on SPARSEMEM_VMEMMAP Date: Tue, 20 Nov 2012 17:37:49 +0800 Message-ID: <50AB4F6D.3050002@cn.fujitsu.com> References: <1351763083-7905-1-git-send-email-wency@cn.fujitsu.com> <1351763083-7905-7-git-send-email-wency@cn.fujitsu.com> <50AB21A4.8050709@gmail.com> <50AB2967.5010302@cn.fujitsu.com> <50AB2A1A.6040606@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from cn.fujitsu.com ([222.73.24.84]:59815 "EHLO song.cn.fujitsu.com" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1752073Ab2KTJbc (ORCPT ); Tue, 20 Nov 2012 04:31:32 -0500 In-Reply-To: <50AB2A1A.6040606@gmail.com> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Jaegeuk Hanse Cc: Yasuaki Ishimatsu , 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 , Jiang Liu , Len Brown , benh@kernel.crashing.org, paulus@samba.org, Christoph Lameter , Minchan Kim , Andrew Morton , KOSAKI Motohiro , Jianguo Wu At 11/20/2012 02:58 PM, Jaegeuk Hanse Wrote: > On 11/20/2012 02:55 PM, Wen Congyang wrote: >> At 11/20/2012 02:22 PM, Jaegeuk Hanse Wrote: >>> On 11/01/2012 05:44 PM, Wen Congyang wrote: >>>> From: Yasuaki Ishimatsu >>>> >>>> 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. > > Hi Congyang, > > Thanks for you reponse. But I mean why return (unsigned long)(mem_map - > (section_nr_to_pfn(pnum))); in function sparse_encode_mem_map, and then > return ((struct page *)coded_mem_map) + section_nr_to_pfn(pnum); in > funtion sparse_decode_mem_map instead of just store mem_map in > ms->section_mep_map directly. I don't know why. I try to find the reason, but I don't find any place to use the pfn stored in the mem_map except in the decode function. Maybe the designer doesn't want us to access the mem_map directly. Thanks Wen Congyang > > Regards, > Jaegeuk > >> >> Thanks >> Wen Congyang >> >>> Regards, >>> Jaegeuk >>> >>>> CC: David Rientjes >>>> CC: Jiang Liu >>>> CC: Len Brown >>>> CC: Christoph Lameter >>>> Cc: Minchan Kim >>>> CC: Andrew Morton >>>> CC: KOSAKI Motohiro >>>> CC: Wen Congyang >>>> Signed-off-by: Yasuaki Ishimatsu >>>> --- >>>> 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) >>> > > From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wen Congyang Date: Tue, 20 Nov 2012 09:37:49 +0000 Subject: Re: [PATCH v3 06/12] memory-hotplug: unregister memory section on SPARSEMEM_VMEMMAP Message-Id: <50AB4F6D.3050002@cn.fujitsu.com> List-Id: References: <1351763083-7905-1-git-send-email-wency@cn.fujitsu.com> <1351763083-7905-7-git-send-email-wency@cn.fujitsu.com> <50AB21A4.8050709@gmail.com> <50AB2967.5010302@cn.fujitsu.com> <50AB2A1A.6040606@gmail.com> In-Reply-To: <50AB2A1A.6040606@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Jaegeuk Hanse Cc: Yasuaki Ishimatsu , 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 , Jiang Liu , Len Brown , benh@kernel.crashing.org, paulus@samba.org, Christoph Lameter , Minchan Kim , Andrew Morton , KOSAKI Motohiro , Jianguo Wu At 11/20/2012 02:58 PM, Jaegeuk Hanse Wrote: > On 11/20/2012 02:55 PM, Wen Congyang wrote: >> At 11/20/2012 02:22 PM, Jaegeuk Hanse Wrote: >>> On 11/01/2012 05:44 PM, Wen Congyang wrote: >>>> From: Yasuaki Ishimatsu >>>> >>>> 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. > > Hi Congyang, > > Thanks for you reponse. But I mean why return (unsigned long)(mem_map - > (section_nr_to_pfn(pnum))); in function sparse_encode_mem_map, and then > return ((struct page *)coded_mem_map) + section_nr_to_pfn(pnum); in > funtion sparse_decode_mem_map instead of just store mem_map in > ms->section_mep_map directly. I don't know why. I try to find the reason, but I don't find any place to use the pfn stored in the mem_map except in the decode function. Maybe the designer doesn't want us to access the mem_map directly. Thanks Wen Congyang > > Regards, > Jaegeuk > >> >> Thanks >> Wen Congyang >> >>> Regards, >>> Jaegeuk >>> >>>> CC: David Rientjes >>>> CC: Jiang Liu >>>> CC: Len Brown >>>> CC: Christoph Lameter >>>> Cc: Minchan Kim >>>> CC: Andrew Morton >>>> CC: KOSAKI Motohiro >>>> CC: Wen Congyang >>>> Signed-off-by: Yasuaki Ishimatsu >>>> --- >>>> 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) >>> > > From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from song.cn.fujitsu.com (unknown [222.73.24.84]) by ozlabs.org (Postfix) with ESMTP id F38A22C0093 for ; Tue, 20 Nov 2012 20:31:31 +1100 (EST) Message-ID: <50AB4F6D.3050002@cn.fujitsu.com> Date: Tue, 20 Nov 2012 17:37:49 +0800 From: Wen Congyang MIME-Version: 1.0 To: Jaegeuk Hanse Subject: Re: [PATCH v3 06/12] memory-hotplug: unregister memory section on SPARSEMEM_VMEMMAP References: <1351763083-7905-1-git-send-email-wency@cn.fujitsu.com> <1351763083-7905-7-git-send-email-wency@cn.fujitsu.com> <50AB21A4.8050709@gmail.com> <50AB2967.5010302@cn.fujitsu.com> <50AB2A1A.6040606@gmail.com> In-Reply-To: <50AB2A1A.6040606@gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Cc: linux-s390@vger.kernel.org, linux-ia64@vger.kernel.org, Len Brown , linux-acpi@vger.kernel.org, linux-sh@vger.kernel.org, x86@kernel.org, linux-kernel@vger.kernel.org, cmetcalf@tilera.com, Jianguo Wu , linux-mm@kvack.org, Yasuaki Ishimatsu , paulus@samba.org, Minchan Kim , KOSAKI Motohiro , David Rientjes , sparclinux@vger.kernel.org, Christoph Lameter , linuxppc-dev@lists.ozlabs.org, Andrew Morton , Jiang Liu List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , At 11/20/2012 02:58 PM, Jaegeuk Hanse Wrote: > On 11/20/2012 02:55 PM, Wen Congyang wrote: >> At 11/20/2012 02:22 PM, Jaegeuk Hanse Wrote: >>> On 11/01/2012 05:44 PM, Wen Congyang wrote: >>>> From: Yasuaki Ishimatsu >>>> >>>> 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. > > Hi Congyang, > > Thanks for you reponse. But I mean why return (unsigned long)(mem_map - > (section_nr_to_pfn(pnum))); in function sparse_encode_mem_map, and then > return ((struct page *)coded_mem_map) + section_nr_to_pfn(pnum); in > funtion sparse_decode_mem_map instead of just store mem_map in > ms->section_mep_map directly. I don't know why. I try to find the reason, but I don't find any place to use the pfn stored in the mem_map except in the decode function. Maybe the designer doesn't want us to access the mem_map directly. Thanks Wen Congyang > > Regards, > Jaegeuk > >> >> Thanks >> Wen Congyang >> >>> Regards, >>> Jaegeuk >>> >>>> CC: David Rientjes >>>> CC: Jiang Liu >>>> CC: Len Brown >>>> CC: Christoph Lameter >>>> Cc: Minchan Kim >>>> CC: Andrew Morton >>>> CC: KOSAKI Motohiro >>>> CC: Wen Congyang >>>> Signed-off-by: Yasuaki Ishimatsu >>>> --- >>>> 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) >>> > > From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx182.postini.com [74.125.245.182]) by kanga.kvack.org (Postfix) with SMTP id AC8A36B0095 for ; Tue, 20 Nov 2012 04:31:31 -0500 (EST) Message-ID: <50AB4F6D.3050002@cn.fujitsu.com> Date: Tue, 20 Nov 2012 17:37:49 +0800 From: Wen Congyang MIME-Version: 1.0 Subject: Re: [PATCH v3 06/12] memory-hotplug: unregister memory section on SPARSEMEM_VMEMMAP References: <1351763083-7905-1-git-send-email-wency@cn.fujitsu.com> <1351763083-7905-7-git-send-email-wency@cn.fujitsu.com> <50AB21A4.8050709@gmail.com> <50AB2967.5010302@cn.fujitsu.com> <50AB2A1A.6040606@gmail.com> In-Reply-To: <50AB2A1A.6040606@gmail.com> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-linux-mm@kvack.org List-ID: To: Jaegeuk Hanse Cc: Yasuaki Ishimatsu , 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 , Jiang Liu , Len Brown , benh@kernel.crashing.org, paulus@samba.org, Christoph Lameter , Minchan Kim , Andrew Morton , KOSAKI Motohiro , Jianguo Wu At 11/20/2012 02:58 PM, Jaegeuk Hanse Wrote: > On 11/20/2012 02:55 PM, Wen Congyang wrote: >> At 11/20/2012 02:22 PM, Jaegeuk Hanse Wrote: >>> On 11/01/2012 05:44 PM, Wen Congyang wrote: >>>> From: Yasuaki Ishimatsu >>>> >>>> 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. > > Hi Congyang, > > Thanks for you reponse. But I mean why return (unsigned long)(mem_map - > (section_nr_to_pfn(pnum))); in function sparse_encode_mem_map, and then > return ((struct page *)coded_mem_map) + section_nr_to_pfn(pnum); in > funtion sparse_decode_mem_map instead of just store mem_map in > ms->section_mep_map directly. I don't know why. I try to find the reason, but I don't find any place to use the pfn stored in the mem_map except in the decode function. Maybe the designer doesn't want us to access the mem_map directly. Thanks Wen Congyang > > Regards, > Jaegeuk > >> >> Thanks >> Wen Congyang >> >>> Regards, >>> Jaegeuk >>> >>>> CC: David Rientjes >>>> CC: Jiang Liu >>>> CC: Len Brown >>>> CC: Christoph Lameter >>>> Cc: Minchan Kim >>>> CC: Andrew Morton >>>> CC: KOSAKI Motohiro >>>> CC: Wen Congyang >>>> Signed-off-by: Yasuaki Ishimatsu >>>> --- >>>> 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: email@kvack.org