From: Wen Congyang <wency@cn.fujitsu.com>
To: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
rientjes@google.com, liuj97@gmail.com, len.brown@intel.com,
benh@kernel.crashing.org, paulus@samba.org,
minchan.kim@gmail.com, akpm@linux-foundation.org,
kosaki.motohiro@jp.fujitsu.com
Subject: Re: [PATCH v3 0/9] bugfix for memory hotplug
Date: Fri, 19 Oct 2012 16:45:42 +0800 [thread overview]
Message-ID: <50811336.7070704@cn.fujitsu.com> (raw)
In-Reply-To: <50810D14.8020609@jp.fujitsu.com>
At 10/19/2012 04:19 PM, Yasuaki Ishimatsu Wrote:
> 2012/10/19 17:06, Yasuaki Ishimatsu wrote:
>> Hi Wen,
>>
>> Some bug fix patches have been merged into linux-next.
>> So the patches confuse me.
Sorry, I don't check linux-next tree.
>
> The following patches have been already merged into linux-next
> and mm-tree as long as I know.
>
>>> Wen Congyang (6):
>>> clear the memory to store struct page
>
>
>>> memory-hotplug: skip HWPoisoned page when offlining pages
>
> mm-tree
Hmm, I don't find this patch in this URL:
http://www.ozlabs.org/~akpm/mmotm/broken-out/
Do I miss something?
>
>>> memory-hotplug: update mce_bad_pages when removing the memory
>
>>> memory-hotplug: auto offline page_cgroup when onlining memory block
>>> failed
>
> mm-tree
>
>>> memory-hotplug: fix NR_FREE_PAGES mismatch
>
> mm-tree
>
>>> memory-hotplug: allocate zone's pcp before onlining pages
>
> mm-tree
>
>>>
>>> Yasuaki Ishimatsu (3):
>>> suppress "Device memoryX does not have a release() function" warning
>
> linux-next
>
>>> suppress "Device nodeX does not have a release() function" warning
>>> memory-hotplug: flush the work for the node when the node is offlined
>
> linux-next
I split this patch to two patches according to kosaki's comment.
Thanks
Wen Congyang
>
> Thanks,
> Yasuaki Ishimatsu
>
>> Why did you send same patches again?
>>
>> Thanks,
>> Yasuaki Ishimatsu
>>
>> 2012/10/19 15:46, wency@cn.fujitsu.com wrote:
>>> From: Wen Congyang <wency@cn.fujitsu.com>
>>>
>>> Changes from v2 to v3:
>>> Merge the bug fix from ishimatsu to this patchset(Patch 1-3)
>>> Patch 3: split it from patch as it fixes another bug.
>>> Patch 4: new patch, and fix bad-page state when hotadding a memory
>>> device after hotremoving it. I forgot to post this patch in v2.
>>> Patch 6: update it according to Dave Hansen's comment.
>>>
>>> Changes from v1 to v2:
>>> Patch 1: updated according to kosaki's suggestion
>>>
>>> Patch 2: new patch, and update mce_bad_pages when removing memory.
>>>
>>> Patch 4: new patch, and fix a NR_FREE_PAGES mismatch, and this bug
>>> cause oom in my test.
>>>
>>> Patch 5: new patch, and fix a new bug. When repeating to online/offline
>>> pages, the free pages will continue to decrease.
>>>
>>> Wen Congyang (6):
>>> clear the memory to store struct page
>>> memory-hotplug: skip HWPoisoned page when offlining pages
>>> memory-hotplug: update mce_bad_pages when removing the memory
>>> memory-hotplug: auto offline page_cgroup when onlining memory block
>>> failed
>>> memory-hotplug: fix NR_FREE_PAGES mismatch
>>> memory-hotplug: allocate zone's pcp before onlining pages
>>>
>>> Yasuaki Ishimatsu (3):
>>> suppress "Device memoryX does not have a release() function" warning
>>> suppress "Device nodeX does not have a release() function" warning
>>> memory-hotplug: flush the work for the node when the node is offlined
>>>
>>> drivers/base/memory.c | 9 ++++++++-
>>> drivers/base/node.c | 11 +++++++++++
>>> include/linux/page-isolation.h | 10 ++++++----
>>> mm/memory-failure.c | 2 +-
>>> mm/memory_hotplug.c | 14 ++++++++------
>>> mm/page_alloc.c | 37 ++++++++++++++++++++++++++++---------
>>> mm/page_cgroup.c | 3 +++
>>> mm/page_isolation.c | 27 ++++++++++++++++++++-------
>>> mm/sparse.c | 22 +++++++++++++++++++++-
>>> 9 files changed, 106 insertions(+), 29 deletions(-)
>>>
>>
>>
>> --
>> 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/
>>
>
>
>
--
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: Wen Congyang <wency@cn.fujitsu.com>
To: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
rientjes@google.com, liuj97@gmail.com, len.brown@intel.com,
benh@kernel.crashing.org, paulus@samba.org,
minchan.kim@gmail.com, akpm@linux-foundation.org,
kosaki.motohiro@jp.fujitsu.com
Subject: Re: [PATCH v3 0/9] bugfix for memory hotplug
Date: Fri, 19 Oct 2012 16:45:42 +0800 [thread overview]
Message-ID: <50811336.7070704@cn.fujitsu.com> (raw)
In-Reply-To: <50810D14.8020609@jp.fujitsu.com>
At 10/19/2012 04:19 PM, Yasuaki Ishimatsu Wrote:
> 2012/10/19 17:06, Yasuaki Ishimatsu wrote:
>> Hi Wen,
>>
>> Some bug fix patches have been merged into linux-next.
>> So the patches confuse me.
Sorry, I don't check linux-next tree.
>
> The following patches have been already merged into linux-next
> and mm-tree as long as I know.
>
>>> Wen Congyang (6):
>>> clear the memory to store struct page
>
>
>>> memory-hotplug: skip HWPoisoned page when offlining pages
>
> mm-tree
Hmm, I don't find this patch in this URL:
http://www.ozlabs.org/~akpm/mmotm/broken-out/
Do I miss something?
>
>>> memory-hotplug: update mce_bad_pages when removing the memory
>
>>> memory-hotplug: auto offline page_cgroup when onlining memory block
>>> failed
>
> mm-tree
>
>>> memory-hotplug: fix NR_FREE_PAGES mismatch
>
> mm-tree
>
>>> memory-hotplug: allocate zone's pcp before onlining pages
>
> mm-tree
>
>>>
>>> Yasuaki Ishimatsu (3):
>>> suppress "Device memoryX does not have a release() function" warning
>
> linux-next
>
>>> suppress "Device nodeX does not have a release() function" warning
>>> memory-hotplug: flush the work for the node when the node is offlined
>
> linux-next
I split this patch to two patches according to kosaki's comment.
Thanks
Wen Congyang
>
> Thanks,
> Yasuaki Ishimatsu
>
>> Why did you send same patches again?
>>
>> Thanks,
>> Yasuaki Ishimatsu
>>
>> 2012/10/19 15:46, wency@cn.fujitsu.com wrote:
>>> From: Wen Congyang <wency@cn.fujitsu.com>
>>>
>>> Changes from v2 to v3:
>>> Merge the bug fix from ishimatsu to this patchset(Patch 1-3)
>>> Patch 3: split it from patch as it fixes another bug.
>>> Patch 4: new patch, and fix bad-page state when hotadding a memory
>>> device after hotremoving it. I forgot to post this patch in v2.
>>> Patch 6: update it according to Dave Hansen's comment.
>>>
>>> Changes from v1 to v2:
>>> Patch 1: updated according to kosaki's suggestion
>>>
>>> Patch 2: new patch, and update mce_bad_pages when removing memory.
>>>
>>> Patch 4: new patch, and fix a NR_FREE_PAGES mismatch, and this bug
>>> cause oom in my test.
>>>
>>> Patch 5: new patch, and fix a new bug. When repeating to online/offline
>>> pages, the free pages will continue to decrease.
>>>
>>> Wen Congyang (6):
>>> clear the memory to store struct page
>>> memory-hotplug: skip HWPoisoned page when offlining pages
>>> memory-hotplug: update mce_bad_pages when removing the memory
>>> memory-hotplug: auto offline page_cgroup when onlining memory block
>>> failed
>>> memory-hotplug: fix NR_FREE_PAGES mismatch
>>> memory-hotplug: allocate zone's pcp before onlining pages
>>>
>>> Yasuaki Ishimatsu (3):
>>> suppress "Device memoryX does not have a release() function" warning
>>> suppress "Device nodeX does not have a release() function" warning
>>> memory-hotplug: flush the work for the node when the node is offlined
>>>
>>> drivers/base/memory.c | 9 ++++++++-
>>> drivers/base/node.c | 11 +++++++++++
>>> include/linux/page-isolation.h | 10 ++++++----
>>> mm/memory-failure.c | 2 +-
>>> mm/memory_hotplug.c | 14 ++++++++------
>>> mm/page_alloc.c | 37 ++++++++++++++++++++++++++++---------
>>> mm/page_cgroup.c | 3 +++
>>> mm/page_isolation.c | 27 ++++++++++++++++++++-------
>>> mm/sparse.c | 22 +++++++++++++++++++++-
>>> 9 files changed, 106 insertions(+), 29 deletions(-)
>>>
>>
>>
>> --
>> 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/
>>
>
>
>
next prev parent reply other threads:[~2012-10-19 8:40 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-19 6:46 [PATCH v3 0/9] bugfix for memory hotplug wency
2012-10-19 6:46 ` wency
2012-10-19 6:46 ` [PATCH v3 1/9] suppress "Device memoryX does not have a release() function" warning wency
2012-10-19 6:46 ` wency
2012-10-19 6:46 ` [PATCH v3 2/9] suppress "Device nodeX " wency
2012-10-19 6:46 ` wency
2012-10-19 6:53 ` KOSAKI Motohiro
2012-10-19 6:53 ` KOSAKI Motohiro
2012-10-22 22:52 ` Andrew Morton
2012-10-22 22:52 ` Andrew Morton
2012-10-22 23:00 ` Greg KH
2012-10-22 23:00 ` Greg KH
2012-10-19 6:46 ` [PATCH v3 3/9] memory-hotplug: flush the work for the node when the node is offlined wency
2012-10-19 6:46 ` wency
2012-10-19 7:01 ` KOSAKI Motohiro
2012-10-19 7:01 ` KOSAKI Motohiro
2012-10-19 7:28 ` Wen Congyang
2012-10-19 7:28 ` Wen Congyang
2012-10-19 6:46 ` [PATCH v3 4/9] clear the memory to store struct page wency
2012-10-19 6:46 ` wency
2012-10-19 7:02 ` KOSAKI Motohiro
2012-10-19 7:02 ` KOSAKI Motohiro
2012-10-26 9:44 ` Wen Congyang
2012-10-26 9:44 ` Wen Congyang
2012-10-29 21:10 ` Andrew Morton
2012-10-29 21:10 ` Andrew Morton
2012-10-30 2:18 ` Wen Congyang
2012-10-30 2:18 ` Wen Congyang
2012-10-30 2:41 ` Andrew Morton
2012-10-30 2:41 ` Andrew Morton
2012-10-30 2:48 ` Wen Congyang
2012-10-30 2:48 ` Wen Congyang
2012-10-19 6:46 ` [PATCH v3 5/9] memory-hotplug: skip HWPoisoned page when offlining pages wency
2012-10-19 6:46 ` wency
2012-10-19 6:46 ` [PATCH v3 6/9] memory-hotplug: update mce_bad_pages when removing the memory wency
2012-10-19 6:46 ` wency
2012-10-19 7:06 ` KOSAKI Motohiro
2012-10-19 7:06 ` KOSAKI Motohiro
2012-10-19 7:18 ` Wen Congyang
2012-10-19 7:18 ` Wen Congyang
2012-10-19 6:46 ` [PATCH v3 7/9] memory-hotplug: auto offline page_cgroup when onlining memory block failed wency
2012-10-19 6:46 ` wency
2012-10-19 6:46 ` [PATCH v3 8/9] memory-hotplug: fix NR_FREE_PAGES mismatch wency
2012-10-19 6:46 ` wency
2012-10-19 7:41 ` KOSAKI Motohiro
2012-10-19 7:41 ` KOSAKI Motohiro
2012-10-19 8:41 ` Wen Congyang
2012-10-19 8:41 ` Wen Congyang
2012-10-19 6:46 ` [PATCH v3 9/9] memory-hotplug: allocate zone's pcp before onlining pages wency
2012-10-19 6:46 ` wency
2012-10-19 7:07 ` KOSAKI Motohiro
2012-10-19 7:07 ` KOSAKI Motohiro
2012-10-19 8:06 ` [PATCH v3 0/9] bugfix for memory hotplug Yasuaki Ishimatsu
2012-10-19 8:06 ` Yasuaki Ishimatsu
2012-10-19 8:19 ` Yasuaki Ishimatsu
2012-10-19 8:19 ` Yasuaki Ishimatsu
2012-10-19 8:45 ` Wen Congyang [this message]
2012-10-19 8:45 ` Wen Congyang
2012-10-19 9:39 ` Yasuaki Ishimatsu
2012-10-19 9:39 ` Yasuaki Ishimatsu
2012-10-19 10:15 ` Wen Congyang
2012-10-19 10:15 ` Wen Congyang
2012-10-22 22:38 ` Andrew Morton
2012-10-22 22:38 ` Andrew Morton
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=50811336.7070704@cn.fujitsu.com \
--to=wency@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuj97@gmail.com \
--cc=minchan.kim@gmail.com \
--cc=paulus@samba.org \
--cc=rientjes@google.com \
/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.