All of lore.kernel.org
 help / color / mirror / Atom feed
From: tangchen@cn.fujitsu.com (Tang Chen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] mm: vmemmap: add vmemmap_verify check for hot-add node/memory case
Date: Fri, 12 Apr 2013 09:13:05 +0800	[thread overview]
Message-ID: <51675FA1.9000203@cn.fujitsu.com> (raw)
In-Reply-To: <CAE9FiQU-zqFdSz-7yq5EgV1YCzyNH_BY36Ym3tdHVEHHY6cdNg@mail.gmail.com>

On 04/11/2013 11:10 PM, Yinghai Lu wrote:
> On Thu, Apr 11, 2013 at 12:41 AM, Tang Chen<tangchen@cn.fujitsu.com>  wrote:
>>
>> 3. If we add flag to memblock, we can mark different memory. And I remember
>>     you mentioned before that we can use memblock to reserve local node data
>>     for node-life-cycle data, like vmemmap, pagetable.
>>
>>     So are you doing the similar work now ?
>
> No, i did not start it yet.
>
>>
>>     If not, I think I can merge it into mine, and push a new patch-set with
>>     hot-add, hot-remove code modified to support putting vmemmap, pagetable,
>>     pgdat, page_cgroup, ..., on local node.
>
> Need to have it separated with moving_zone.
>
> 1. rework memblock to keep alive all the way for hotplug usage.
> 2. put pagetable and vmemap on the local node range with help of memblock.
>

OK?thanks for the comments. I'll merge it into my work and post an RFC 
patch-set soon.

Thanks. :)

WARNING: multiple messages have this Message-ID (diff)
From: Tang Chen <tangchen@cn.fujitsu.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Lin Feng <linfeng@cn.fujitsu.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Christoph Lameter <cl@linux.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	will.deacon@arm.com, Arnd Bergmann <arnd@arndb.de>,
	tony@atomide.com, Ben Hutchings <ben@decadent.org.uk>,
	linux-arm-kernel@lists.infradead.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	the arch/x86 maintainers <x86@kernel.org>,
	Linux MM <linux-mm@kvack.org>,
	Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>,
	Jiang Liu <jiang.liu@huawei.com>
Subject: Re: [PATCH 0/2] mm: vmemmap: add vmemmap_verify check for hot-add node/memory case
Date: Fri, 12 Apr 2013 09:13:05 +0800	[thread overview]
Message-ID: <51675FA1.9000203@cn.fujitsu.com> (raw)
In-Reply-To: <CAE9FiQU-zqFdSz-7yq5EgV1YCzyNH_BY36Ym3tdHVEHHY6cdNg@mail.gmail.com>

On 04/11/2013 11:10 PM, Yinghai Lu wrote:
> On Thu, Apr 11, 2013 at 12:41 AM, Tang Chen<tangchen@cn.fujitsu.com>  wrote:
>>
>> 3. If we add flag to memblock, we can mark different memory. And I remember
>>     you mentioned before that we can use memblock to reserve local node data
>>     for node-life-cycle data, like vmemmap, pagetable.
>>
>>     So are you doing the similar work now ?
>
> No, i did not start it yet.
>
>>
>>     If not, I think I can merge it into mine, and push a new patch-set with
>>     hot-add, hot-remove code modified to support putting vmemmap, pagetable,
>>     pgdat, page_cgroup, ..., on local node.
>
> Need to have it separated with moving_zone.
>
> 1. rework memblock to keep alive all the way for hotplug usage.
> 2. put pagetable and vmemap on the local node range with help of memblock.
>

OK，thanks for the comments. I'll merge it into my work and post an RFC 
patch-set soon.

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: Yinghai Lu <yinghai@kernel.org>
Cc: Lin Feng <linfeng@cn.fujitsu.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Christoph Lameter <cl@linux.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	will.deacon@arm.com, Arnd Bergmann <arnd@arndb.de>,
	tony@atomide.com, Ben Hutchings <ben@decadent.org.uk>,
	linux-arm-kernel@lists.infradead.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	the arch/x86 maintainers <x86@kernel.org>,
	Linux MM <linux-mm@kvack.org>,
	Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>,
	Jiang Liu <jiang.liu@huawei.com>
Subject: Re: [PATCH 0/2] mm: vmemmap: add vmemmap_verify check for hot-add node/memory case
Date: Fri, 12 Apr 2013 09:13:05 +0800	[thread overview]
Message-ID: <51675FA1.9000203@cn.fujitsu.com> (raw)
In-Reply-To: <CAE9FiQU-zqFdSz-7yq5EgV1YCzyNH_BY36Ym3tdHVEHHY6cdNg@mail.gmail.com>

On 04/11/2013 11:10 PM, Yinghai Lu wrote:
> On Thu, Apr 11, 2013 at 12:41 AM, Tang Chen<tangchen@cn.fujitsu.com>  wrote:
>>
>> 3. If we add flag to memblock, we can mark different memory. And I remember
>>     you mentioned before that we can use memblock to reserve local node data
>>     for node-life-cycle data, like vmemmap, pagetable.
>>
>>     So are you doing the similar work now ?
>
> No, i did not start it yet.
>
>>
>>     If not, I think I can merge it into mine, and push a new patch-set with
>>     hot-add, hot-remove code modified to support putting vmemmap, pagetable,
>>     pgdat, page_cgroup, ..., on local node.
>
> Need to have it separated with moving_zone.
>
> 1. rework memblock to keep alive all the way for hotplug usage.
> 2. put pagetable and vmemap on the local node range with help of memblock.
>

OK，thanks for the comments. I'll merge it into my work and post an RFC 
patch-set soon.

Thanks. :)

  reply	other threads:[~2013-04-12  1:13 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-08  9:56 [PATCH 0/2] mm: vmemmap: add vmemmap_verify check for hot-add node/memory case Lin Feng
2013-04-08  9:56 ` Lin Feng
2013-04-08  9:56 ` Lin Feng
2013-04-08  9:56 ` [PATCH 1/2] mm: vmemmap: x86: add vmemmap_verify check for hot-add node case Lin Feng
2013-04-08  9:56   ` Lin Feng
2013-04-08  9:56   ` Lin Feng
2013-04-08 10:23   ` Lin Feng
2013-04-08 10:23     ` Lin Feng
2013-04-08 10:23     ` Lin Feng
2013-04-08  9:56 ` [PATCH 2/2] mm: vmemmap: arm64: " Lin Feng
2013-04-08  9:56   ` Lin Feng
2013-04-08  9:56   ` Lin Feng
2013-04-08 10:55   ` Will Deacon
2013-04-08 10:55     ` Will Deacon
2013-04-08 10:55     ` Will Deacon
2013-04-09  2:07     ` Lin Feng
2013-04-09  2:07       ` Lin Feng
2013-04-09  2:07       ` Lin Feng
2013-04-08 18:40 ` [PATCH 0/2] mm: vmemmap: add vmemmap_verify check for hot-add node/memory case Yinghai Lu
2013-04-08 18:40   ` Yinghai Lu
2013-04-08 18:40   ` Yinghai Lu
2013-04-08 20:55   ` Andrew Morton
2013-04-08 20:55     ` Andrew Morton
2013-04-08 20:55     ` Andrew Morton
2013-04-09  1:58     ` Lin Feng
2013-04-09  1:58       ` Lin Feng
2013-04-09  1:58       ` Lin Feng
2013-04-09  2:02   ` Lin Feng
2013-04-09  2:02     ` Lin Feng
2013-04-09  2:02     ` Lin Feng
2013-04-11  7:41   ` Tang Chen
2013-04-11  7:41     ` Tang Chen
2013-04-11  7:41     ` Tang Chen
2013-04-11 15:10     ` Yinghai Lu
2013-04-11 15:10       ` Yinghai Lu
2013-04-11 15:10       ` Yinghai Lu
2013-04-12  1:13       ` Tang Chen [this message]
2013-04-12  1:13         ` Tang Chen
2013-04-12  1:13         ` 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=51675FA1.9000203@cn.fujitsu.com \
    --to=tangchen@cn.fujitsu.com \
    --cc=linux-arm-kernel@lists.infradead.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.