Merge branch 'akpm' (patchbomb from Andrew) into next

which you should use to make sure messages are matched to the right device

and driver, and are tagged with the right level:  dev_err(), dev_warn(),

dev_info(), and so forth.  For messages that aren't associated with a

particular device, <linux/printk.h> defines pr_debug() and pr_info().

particular device, <linux/printk.h> defines pr_notice(), pr_info(),

pr_warn(), pr_err(), etc.

Coming up with good debugging messages can be quite a challenge; and once

you have them, they can be a huge help for remote troubleshooting.  Such

messages should be compiled out when the DEBUG symbol is not defined (that

is, by default they are not included).  When you use dev_dbg() or pr_debug(),

that's automatic.  Many subsystems have Kconfig options to turn on -DDEBUG.

A related convention uses VERBOSE_DEBUG to add dev_vdbg() messages to the

ones already enabled by DEBUG.

you have them, they can be a huge help for remote troubleshooting.  However

debug message printing is handled differently than printing other non-debug

messages.  While the other pr_XXX() functions print unconditionally,

pr_debug() does not; it is compiled out by default, unless either DEBUG is

defined or CONFIG_DYNAMIC_DEBUG is set.  That is true for dev_dbg() also,

and a related convention uses VERBOSE_DEBUG to add dev_vdbg() messages to

the ones already enabled by DEBUG.

Many subsystems have Kconfig debug options to turn on -DDEBUG in the

corresponding Makefile; in other cases specific files #define DEBUG.  And

when a debug message should be unconditionally printed, such as if it is

already inside a debug-related #ifdef secton, printk(KERN_DEBUG ...) can be

used.

		Chapter 14: Allocating memory

2.7 Kernel Memory Extension (CONFIG_MEMCG_KMEM)

WARNING: Current implementation lacks reclaim support. That means allocation

	 attempts will fail when close to the limit even if there are plenty of

	 kmem available for reclaim. That makes this option unusable in real

	 life so DO NOT SELECT IT unless for development purposes.

With the Kernel memory extension, the Memory Controller is able to limit

the amount of kernel memory used by the system. Kernel memory is fundamentally

different than user memory, since it can't be swapped out, which makes it

5.3 swappiness

Similar to /proc/sys/vm/swappiness, but affecting a hierarchy of groups only.

Similar to /proc/sys/vm/swappiness, but only affecting reclaim that is

triggered by this cgroup's hard limit.  The tunable in the root cgroup

corresponds to the global swappiness setting.

Please note that unlike the global swappiness, memcg knob set to 0

really prevents from any swapping even if there is a swap storage

available. This might lead to memcg OOM killer if there are no file

pages to reclaim.

Following cgroups' swappiness can't be changed.

- root cgroup (uses /proc/sys/vm/swappiness).

- a cgroup which uses hierarchy and it has other cgroup(s) below it.

- a cgroup which uses hierarchy and not the root of hierarchy.

5.4 failcnt

A memory cgroup provides memory.failcnt and memory.memsw.failcnt files.

	#echo 1 > memory.oom_control

This operation is only allowed to the top cgroup of a sub-hierarchy.

If OOM-killer is disabled, tasks under cgroup will hang/sleep

in memory cgroup's OOM-waitqueue when they request accountable memory.

			Also note the kernel might malfunction if you disable

			some critical bits.

	cma=nn[MG]	[ARM,KNL]

			Sets the size of kernel global memory area for contiguous

	cma=nn[MG]@[start[MG][-end[MG]]]

			[ARM,X86,KNL]

			Sets the size of kernel global memory area for

			contiguous memory allocations and optionally the

			placement constraint by the physical address range of

			memory allocations. For more information, see

			include/linux/dma-contiguous.h

			for working out where the kernel is dying during

			startup.

	initcall_blacklist=  [KNL] Do not execute a comma-separated list of

			initcall functions.  Useful for debugging built-in

			modules and initcalls.

	initrd=		[BOOT] Specify the location of the initial ramdisk

	inport.irq=	[HW] Inport (ATI XL and Microsoft) busmouse driver

1.3. Unit of Memory online/offline operation

------------

Memory hotplug uses SPARSEMEM memory model. SPARSEMEM divides the whole memory

into chunks of the same size. The chunk is called a "section". The size of

a section is architecture dependent. For example, power uses 16MiB, ia64 uses

1GiB. The unit of online/offline operation is "one section". (see Section 3.)

Memory hotplug uses SPARSEMEM memory model which allows memory to be divided

into chunks of the same size. These chunks are called "sections". The size of

a memory section is architecture dependent. For example, power uses 16MiB, ia64

uses 1GiB.

To determine the size of sections, please read this file:

Memory sections are combined into chunks referred to as "memory blocks". The

size of a memory block is architecture dependent and represents the logical

unit upon which memory online/offline operations are to be performed. The

default size of a memory block is the same as memory section size unless an

architecture specifies otherwise. (see Section 3.)

To determine the size (in bytes) of a memory block please read this file:

/sys/devices/system/memory/block_size_bytes

This file shows the size of sections in byte.

-----------------------

2. Kernel Configuration

    (CONFIG_ACPI_CONTAINER).

    This option can be kernel module too.

--------------------------------

4 sysfs files for memory hotplug

3 sysfs files for memory hotplug

--------------------------------

All sections have their device information in sysfs.  Each section is part of

a memory block under /sys/devices/system/memory as

All memory blocks have their device information in sysfs.  Each memory block

is described under /sys/devices/system/memory as

/sys/devices/system/memory/memoryXXX

(XXX is the section id.)

(XXX is the memory block id.)

Now, XXX is defined as (start_address_of_section / section_size) of the first

section contained in the memory block.  The files 'phys_index' and

'end_phys_index' under each directory report the beginning and end section id's

for the memory block covered by the sysfs directory.  It is expected that all

For the memory block covered by the sysfs directory.  It is expected that all

memory sections in this range are present and no memory holes exist in the

range. Currently there is no way to determine if there is a memory hole, but

the existence of one should not affect the hotplug capabilities of the memory

block.

For example, assume 1GiB section size. A device for a memory starting at

For example, assume 1GiB memory block size. A device for a memory starting at

0x100000000 is /sys/device/system/memory/memory4

(0x100000000 / 1Gib = 4)

This device covers address range [0x100000000 ... 0x140000000)

Under each section, you can see 4 or 5 files, the end_phys_index file being

a recent addition and not present on older kernels.

Under each memory block, you can see 4 files:

/sys/devices/system/memory/memoryXXX/start_phys_index

/sys/devices/system/memory/memoryXXX/end_phys_index

/sys/devices/system/memory/memoryXXX/phys_index

/sys/devices/system/memory/memoryXXX/phys_device

/sys/devices/system/memory/memoryXXX/state

/sys/devices/system/memory/memoryXXX/removable

'phys_index'      : read-only and contains section id of the first section

		    in the memory block, same as XXX.

'end_phys_index'  : read-only and contains section id of the last section

		    in the memory block.

'phys_index'      : read-only and contains memory block id, same as XXX.

'state'           : read-write

                    at read:  contains online/offline state of memory.

                    at write: user can specify "online_kernel",

A backlink will also be created:

/sys/devices/system/memory/memory9/node0 -> ../../node/node0

--------------------------------

4. Physical memory hot-add phase

--------------------------------

% echo start_address_of_new_memory > /sys/devices/system/memory/probe

Then, [start_address_of_new_memory, start_address_of_new_memory + section_size)

memory range is hot-added. In this case, hotplug script is not called (in

current implementation). You'll have to online memory by yourself.

Please see "How to online memory" in this text.

Then, [start_address_of_new_memory, start_address_of_new_memory +

memory_block_size] memory range is hot-added. In this case, hotplug script is

not called (in current implementation). You'll have to online memory by

yourself.  Please see "How to online memory" in this text.

------------------------------

5.1. State of memory

------------

To see (online/offline) state of memory section, read 'state' file.

To see (online/offline) state of a memory block, read 'state' file.

% cat /sys/device/system/memory/memoryXXX/state

If the memory section is online, you'll read "online".

If the memory section is offline, you'll read "offline".

If the memory block is online, you'll read "online".

If the memory block is offline, you'll read "offline".

5.2. How to online memory

------------

Even if the memory is hot-added, it is not at ready-to-use state.

For using newly added memory, you have to "online" the memory section.

For using newly added memory, you have to "online" the memory block.

For onlining, you have to write "online" to the section's state file as:

For onlining, you have to write "online" to the memory block's state file as:

% echo online > /sys/devices/system/memory/memoryXXX/state

This onlining will not change the ZONE type of the target memory section,

If the memory section is in ZONE_NORMAL, you can change it to ZONE_MOVABLE:

This onlining will not change the ZONE type of the target memory block,

If the memory block is in ZONE_NORMAL, you can change it to ZONE_MOVABLE:

% echo online_movable > /sys/devices/system/memory/memoryXXX/state

(NOTE: current limit: this memory section must be adjacent to ZONE_MOVABLE)

(NOTE: current limit: this memory block must be adjacent to ZONE_MOVABLE)

And if the memory section is in ZONE_MOVABLE, you can change it to ZONE_NORMAL:

And if the memory block is in ZONE_MOVABLE, you can change it to ZONE_NORMAL:

% echo online_kernel > /sys/devices/system/memory/memoryXXX/state

(NOTE: current limit: this memory section must be adjacent to ZONE_NORMAL)

(NOTE: current limit: this memory block must be adjacent to ZONE_NORMAL)

After this, section memoryXXX's state will be 'online' and the amount of

After this, memory block XXX's state will be 'online' and the amount of

available memory will be increased.

Currently, newly added memory is added as ZONE_NORMAL (for powerpc, ZONE_DMA).

6.1 Memory offline and ZONE_MOVABLE

------------

Memory offlining is more complicated than memory online. Because memory offline

has to make the whole memory section be unused, memory offline can fail if

the section includes memory which cannot be freed.

has to make the whole memory block be unused, memory offline can fail if

the memory block includes memory which cannot be freed.

In general, memory offline can use 2 techniques.

(1) reclaim and free all memory in the section.

(2) migrate all pages in the section.

(1) reclaim and free all memory in the memory block.

(2) migrate all pages in the memory block.

In the current implementation, Linux's memory offline uses method (2), freeing

all  pages in the section by page migration. But not all pages are

all  pages in the memory block by page migration. But not all pages are

migratable. Under current Linux, migratable pages are anonymous pages and

page caches. For offlining a section by migration, the kernel has to guarantee

that the section contains only migratable pages.

page caches. For offlining a memory block by migration, the kernel has to

guarantee that the memory block contains only migratable pages.

Now, a boot option for making a section which consists of migratable pages is

supported. By specifying "kernelcore=" or "movablecore=" boot option, you can

Now, a boot option for making a memory block which consists of migratable pages

is supported. By specifying "kernelcore=" or "movablecore=" boot option, you can

create ZONE_MOVABLE...a zone which is just used for movable pages.

(See also Documentation/kernel-parameters.txt)

  Size of memory for movable pages (for offline) is ZZZZ.

Note) Unfortunately, there is no information to show which section belongs

Note: Unfortunately, there is no information to show which memory block belongs

to ZONE_MOVABLE. This is TBD.

6.2. How to offline memory

------------

You can offline a section by using the same sysfs interface that was used in

memory onlining.

You can offline a memory block by using the same sysfs interface that was used

in memory onlining.

% echo offline > /sys/devices/system/memory/memoryXXX/state

If offline succeeds, the state of the memory section is changed to be "offline".

If offline succeeds, the state of the memory block is changed to be "offline".

If it fails, some error core (like -EBUSY) will be returned by the kernel.

Even if a section does not belong to ZONE_MOVABLE, you can try to offline it.

If it doesn't contain 'unmovable' memory, you'll get success.

Even if a memory block does not belong to ZONE_MOVABLE, you can try to offline

it.  If it doesn't contain 'unmovable' memory, you'll get success.

A section under ZONE_MOVABLE is considered to be able to be offlined easily.

But under some busy state, it may return -EBUSY. Even if a memory section

cannot be offlined due to -EBUSY, you can retry offlining it and may be able to

offline it (or not).

(For example, a page is referred to by some kernel internal call and released

 soon.)

A memory block under ZONE_MOVABLE is considered to be able to be offlined

easily.  But under some busy state, it may return -EBUSY. Even if a memory

block cannot be offlined due to -EBUSY, you can retry offlining it and may be

able to offline it (or not). (For example, a page is referred to by some kernel

internal call and released soon.)

Consideration:

Memory hotplug's design direction is to make the possibility of memory offlining

  Generated to begin the process of offlining memory. Allocations are no

  longer possible from the memory but some of the memory to be offlined

  is still in use. The callback can be used to free memory known to a

  subsystem from the indicated memory section.

  subsystem from the indicated memory block.

MEMORY_CANCEL_OFFLINE

  Generated if MEMORY_GOING_OFFLINE fails. Memory is available again from

  the section that we attempted to offline.

  the memory block that we attempted to offline.

MEMORY_OFFLINE

  Generated after offlining memory is complete.

--------------

  - allowing memory hot-add to ZONE_MOVABLE. maybe we need some switch like

    sysctl or new control file.

  - showing memory section and physical device relationship.

  - showing memory section is under ZONE_MOVABLE or not

  - showing memory block and physical device relationship.

  - showing memory block is under ZONE_MOVABLE or not

  - test and make it better memory offlining.

  - support HugeTLB page migration and offlining.

  - memmap removing at memory offline.

vfs_cache_pressure

------------------

Controls the tendency of the kernel to reclaim the memory which is used for

caching of directory and inode objects.

This percentage value controls the tendency of the kernel to reclaim

the memory which is used for caching of directory and inode objects.

At the default value of vfs_cache_pressure=100 the kernel will attempt to

reclaim dentries and inodes at a "fair" rate with respect to pagecache and

lead to out-of-memory conditions. Increasing vfs_cache_pressure beyond 100

causes the kernel to prefer to reclaim dentries and inodes.

Increasing vfs_cache_pressure significantly beyond 100 may have negative

performance impact. Reclaim code needs to take various locks to find freeable

directory and inode objects. With vfs_cache_pressure=1000, it will look for

ten times more freeable objects than there are.

==============================================================

zone_reclaim_mode:

2	= Zone reclaim writes dirty pages out

4	= Zone reclaim swaps pages

zone_reclaim_mode is set during bootup to 1 if it is determined that pages

from remote zones will cause a measurable performance reduction. The

page allocator will then reclaim easily reusable pages (those page

cache pages that are currently not used) before allocating off node pages.

It may be beneficial to switch off zone reclaim if the system is

used for a file server and all of memory should be used for caching files

from disk. In that case the caching effect is more important than

zone_reclaim_mode is disabled by default.  For file servers or workloads

that benefit from having their data cached, zone_reclaim_mode should be

left disabled as the caching effect is likely to be more important than

data locality.

zone_reclaim may be enabled if it's known that the workload is partitioned

such that each partition fits within a NUMA node and that accessing remote

memory would cause a measurable performance reduction.  The page allocator

will then reclaim easily reusable pages (those page cache pages that are

currently not used) before allocating off node pages.

Allowing zone reclaim to write out pages stops processes that are

writing large amounts of data from dirtying pages on other nodes. Zone

reclaim will write out dirty pages if a zone fills up and so effectively