linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Wanpeng Li <liwanp@linux.vnet.ibm.com>
To: Tang Chen <tangchen@cn.fujitsu.com>
Cc: rjw@sisk.pl, lenb@kernel.org, tglx@linutronix.de, mingo@elte.hu,
	hpa@zytor.com, akpm@linux-foundation.org, tj@kernel.org,
	trenn@suse.de, yinghai@kernel.org, jiang.liu@huawei.com,
	wency@cn.fujitsu.com, laijs@cn.fujitsu.com,
	isimatu.yasuaki@jp.fujitsu.com, izumi.taku@jp.fujitsu.com,
	mgorman@suse.de, minchan@kernel.org, mina86@mina86.com,
	gong.chen@linux.intel.com, vasilis.liaskovitis@profitbricks.com,
	lwoodman@redhat.com, riel@redhat.com, jweiner@redhat.com,
	prarit@redhat.com, zhangyanfei@cn.fujitsu.com, x86@kernel.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH 00/11] x86, memblock: Allocate memory near kernel image before SRAT parsed.
Date: Wed, 28 Aug 2013 16:03:11 +0800	[thread overview]
Message-ID: <20130828080311.GA608@hacker.(null)> (raw)
In-Reply-To: <1377596268-31552-1-git-send-email-tangchen@cn.fujitsu.com>

Hi Tang,
On Tue, Aug 27, 2013 at 05:37:37PM +0800, Tang Chen wrote:
>This patch-set is based on tj's suggestion, and not fully tested. 
>Just for review and discussion.
>
>
>[Problem]
>
>The current Linux cannot migrate pages used by the kerenl because
>of the kernel direct mapping. In Linux kernel space, va = pa + PAGE_OFFSET.
>When the pa is changed, we cannot simply update the pagetable and
>keep the va unmodified. So the kernel pages are not migratable.
>
>There are also some other issues will cause the kernel pages not migratable.
>For example, the physical address may be cached somewhere and will be used.
>It is not to update all the caches.
>
>When doing memory hotplug in Linux, we first migrate all the pages in one
>memory device somewhere else, and then remove the device. But if pages are
>used by the kernel, they are not migratable. As a result, memory used by
>the kernel cannot be hot-removed.
>
>Modifying the kernel direct mapping mechanism is too difficult to do. And
>it may cause the kernel performance down and unstable. So we use the following
>way to do memory hotplug.
>
>
>[What we are doing]
>
>In Linux, memory in one numa node is divided into several zones. One of the
>zones is ZONE_MOVABLE, which the kernel won't use.
>
>In order to implement memory hotplug in Linux, we are going to arrange all
>hotpluggable memory in ZONE_MOVABLE so that the kernel won't use these memory.
>To do this, we need ACPI's help.
>
>In ACPI, SRAT(System Resource Affinity Table) contains NUMA info. The memory
>affinities in SRAT record every memory range in the system, and also, flags
>specifying if the memory range is hotpluggable.
>(Please refer to ACPI spec 5.0 5.2.16)
>
>With the help of SRAT, we have to do the following two things to achieve our
>goal:
>
>1. When doing memory hot-add, allow the users arranging hotpluggable as
>   ZONE_MOVABLE.
>   (This has been done by the MOVABLE_NODE functionality in Linux.)
>
>2. when the system is booting, prevent bootmem allocator from allocating
>   hotpluggable memory for the kernel before the memory initialization
>   finishes.
>
>The problem 2 is the key problem we are going to solve. But before solving it,
>we need some preparation. Please see below.
>
>
>[Preparation]
>
>Bootloader has to load the kernel image into memory. And this memory must be 
>unhotpluggable. We cannot prevent this anyway. So in a memory hotplug system, 
>we can assume any node the kernel resides in is not hotpluggable.
>
>Before SRAT is parsed, we don't know which memory ranges are hotpluggable. But
>memblock has already started to work. In the current kernel, memblock allocates 
>the following memory before SRAT is parsed:
>
>setup_arch()
> |->memblock_x86_fill()            /* memblock is ready */
> |......
> |->early_reserve_e820_mpc_new()   /* allocate memory under 1MB */
> |->reserve_real_mode()            /* allocate memory under 1MB */
> |->init_mem_mapping()             /* allocate page tables, about 2MB to map 1GB memory */
> |->dma_contiguous_reserve()       /* specified by user, should be low */
> |->setup_log_buf()                /* specified by user, several mega bytes */
> |->relocate_initrd()              /* could be large, but will be freed after boot, should reorder */
> |->acpi_initrd_override()         /* several mega bytes */
> |->reserve_crashkernel()          /* could be large, should reorder */
> |......
> |->initmem_init()                 /* Parse SRAT */
>
>According to Tejun's advice, before SRAT is parsed, we should try our best to
>allocate memory near the kernel image. Since the whole node the kernel resides 
>in won't be hotpluggable, and for a modern server, a node may have at least 16GB
>memory, allocating several mega bytes memory around the kernel image won't cross
>to hotpluggable memory.
>
>
>[About this patch-set]
>
>So this patch-set does the following:
>
>1. Make memblock be able to allocate memory from low address to high address.

I want to know if there is fragmentation degree difference here?

Regards,
Wanpeng Li 

>   Also introduce low limit to prevent memblock allocating memory too low.
>
>2. Improve init_mem_mapping() to support allocate page tables from low address 
>   to high address.
>
>3. Introduce "movablenode" boot option to enable and disable this functionality.
>
>PS: Reordering of relocate_initrd() and reserve_crashkernel() has not been done 
>    yet. acpi_initrd_override() needs to access initrd with virtual address. So 
>    relocate_initrd() must be done before acpi_initrd_override().
>
>
>Tang Chen (11):
>  memblock: Rename current_limit to current_limit_high in memblock.
>  memblock: Rename memblock_set_current_limit() to
>    memblock_set_current_limit_high().
>  memblock: Introduce lowest limit in memblock.
>  memblock: Introduce memblock_set_current_limit_low() to set lower
>    limit of memblock.
>  memblock: Introduce allocation order to memblock.
>  memblock: Improve memblock to support allocation from lower address.
>  x86, memblock: Set lowest limit for memblock_alloc_base_nid().
>  x86, acpi, memblock: Use __memblock_alloc_base() in
>    acpi_initrd_override()
>  mem-hotplug: Introduce movablenode boot option to {en|dis}able using
>    SRAT.
>  x86, mem-hotplug: Support initialize page tables from low to high.
>  x86, mem_hotplug: Allocate memory near kernel image before SRAT is
>    parsed.
>
> Documentation/kernel-parameters.txt |   15 ++++
> arch/arm/mm/mmu.c                   |    2 +-
> arch/arm64/mm/mmu.c                 |    4 +-
> arch/microblaze/mm/init.c           |    2 +-
> arch/powerpc/mm/40x_mmu.c           |    4 +-
> arch/powerpc/mm/44x_mmu.c           |    2 +-
> arch/powerpc/mm/fsl_booke_mmu.c     |    4 +-
> arch/powerpc/mm/hash_utils_64.c     |    4 +-
> arch/powerpc/mm/init_32.c           |    4 +-
> arch/powerpc/mm/ppc_mmu_32.c        |    4 +-
> arch/powerpc/mm/tlb_nohash.c        |    4 +-
> arch/unicore32/mm/mmu.c             |    2 +-
> arch/x86/kernel/setup.c             |   41 ++++++++++-
> arch/x86/mm/init.c                  |  119 ++++++++++++++++++++++++--------
> drivers/acpi/osl.c                  |    4 +-
> include/linux/memblock.h            |   33 ++++++++--
> include/linux/memory_hotplug.h      |    5 ++
> mm/memblock.c                       |  131 +++++++++++++++++++++++++++++-----
> mm/memory_hotplug.c                 |    9 +++
> mm/nobootmem.c                      |    4 +-
> 20 files changed, 320 insertions(+), 77 deletions(-)
>
>--
>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>

--
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>

  parent reply	other threads:[~2013-08-28  8:03 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-27  9:37 Tang Chen
2013-08-27  9:37 ` [PATCH 01/11] memblock: Rename current_limit to current_limit_high in memblock Tang Chen
2013-08-27  9:37 ` [PATCH 02/11] memblock: Rename memblock_set_current_limit() to memblock_set_current_limit_high() Tang Chen
2013-08-27  9:37 ` [PATCH 03/11] memblock: Introduce lowest limit in memblock Tang Chen
2013-08-27  9:37 ` [PATCH 04/11] memblock: Introduce memblock_set_current_limit_low() to set lower limit of memblock Tang Chen
2013-08-27  9:37 ` [PATCH 05/11] memblock: Introduce allocation order to memblock Tang Chen
2013-09-05  9:16   ` Wanpeng Li
2013-09-05  9:21     ` Tang Chen
2013-09-05  9:27       ` Wanpeng Li
2013-09-05  9:27       ` Wanpeng Li
2013-09-05  9:16   ` Wanpeng Li
2013-08-27  9:37 ` [PATCH 06/11] memblock: Improve memblock to support allocation from lower address Tang Chen
2013-09-04  0:24   ` Toshi Kani
2013-09-04  1:00     ` Tang Chen
2013-08-27  9:37 ` [PATCH 07/11] x86, memblock: Set lowest limit for memblock_alloc_base_nid() Tang Chen
2013-09-04  0:37   ` Toshi Kani
2013-09-04  2:05     ` Tang Chen
2013-09-04 15:22       ` Toshi Kani
2013-08-27  9:37 ` [PATCH 08/11] x86, acpi, memblock: Use __memblock_alloc_base() in acpi_initrd_override() Tang Chen
2013-08-28  0:04   ` Rafael J. Wysocki
2013-08-27  9:37 ` [PATCH 09/11] mem-hotplug: Introduce movablenode boot option to {en|dis}able using SRAT Tang Chen
2013-08-27  9:37 ` [PATCH 10/11] x86, mem-hotplug: Support initialize page tables from low to high Tang Chen
2013-09-05 13:30   ` Wanpeng Li
2013-09-06  1:34     ` Tang Chen
2013-09-06  2:16       ` Wanpeng Li
2013-09-06  2:16       ` Wanpeng Li
2013-09-06  3:09         ` Tang Chen
2013-09-05 13:30   ` Wanpeng Li
2013-08-27  9:37 ` [PATCH 11/11] x86, mem_hotplug: Allocate memory near kernel image before SRAT is parsed Tang Chen
2013-09-04 19:40   ` Toshi Kani
2013-08-28  8:03 ` Wanpeng Li [this message]
2013-08-28  9:34   ` [PATCH 00/11] x86, memblock: Allocate memory near kernel image before SRAT parsed Tang Chen
2013-08-28  8:03 ` Wanpeng Li
2013-08-28 15:19 ` Tejun Heo
2013-08-29  1:30   ` Tang Chen
2013-08-29  1:36     ` Wanpeng Li
2013-08-29  1:53       ` Tang Chen
2013-08-29  1:36     ` Wanpeng Li
2013-09-02  1:03 ` Tang Chen
2013-09-04 19:22 ` Tejun Heo
2013-09-05  9:01   ` Tang Chen
2013-09-06  8:58   ` Wanpeng Li
2013-09-06  8:58   ` Wanpeng Li
     [not found]   ` <52299935.0302450a.26c9.ffffb240SMTPIN_ADDED_BROKEN@mx.google.com>
2013-09-06 15:15     ` Tejun Heo
2013-09-06 15:47       ` H. Peter Anvin
2013-09-09 12:04         ` Wanpeng Li
2013-09-09 12:04         ` Wanpeng Li
2013-09-09 11:56       ` Wanpeng Li
2013-09-09 11:56       ` Wanpeng Li
     [not found]       ` <522db781.22ab440a.41b1.ffffd825SMTPIN_ADDED_BROKEN@mx.google.com>
2013-09-09 13:58         ` Tejun Heo
2013-09-09 23:58           ` Wanpeng Li
2013-09-09 23:58           ` Wanpeng Li

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='20130828080311.GA608@hacker.(null)' \
    --to=liwanp@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=gong.chen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=isimatu.yasuaki@jp.fujitsu.com \
    --cc=izumi.taku@jp.fujitsu.com \
    --cc=jiang.liu@huawei.com \
    --cc=jweiner@redhat.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --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@elte.hu \
    --cc=prarit@redhat.com \
    --cc=riel@redhat.com \
    --cc=rjw@sisk.pl \
    --cc=tangchen@cn.fujitsu.com \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.org \
    --cc=trenn@suse.de \
    --cc=vasilis.liaskovitis@profitbricks.com \
    --cc=wency@cn.fujitsu.com \
    --cc=x86@kernel.org \
    --cc=yinghai@kernel.org \
    --cc=zhangyanfei@cn.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox