33c3fc71c8
Knowing the portion of memory that is not used by a certain application or
memory cgroup (idle memory) can be useful for partitioning the system
efficiently, e.g. by setting memory cgroup limits appropriately.
Currently, the only means to estimate the amount of idle memory provided
by the kernel is /proc/PID/{clear_refs,smaps}: the user can clear the
access bit for all pages mapped to a particular process by writing 1 to
clear_refs, wait for some time, and then count smaps:Referenced. However,
this method has two serious shortcomings:
- it does not count unmapped file pages
- it affects the reclaimer logic
To overcome these drawbacks, this patch introduces two new page flags,
Idle and Young, and a new sysfs file, /sys/kernel/mm/page_idle/bitmap.
A page's Idle flag can only be set from userspace by setting bit in
/sys/kernel/mm/page_idle/bitmap at the offset corresponding to the page,
and it is cleared whenever the page is accessed either through page tables
(it is cleared in page_referenced() in this case) or using the read(2)
system call (mark_page_accessed()). Thus by setting the Idle flag for
pages of a particular workload, which can be found e.g. by reading
/proc/PID/pagemap, waiting for some time to let the workload access its
working set, and then reading the bitmap file, one can estimate the amount
of pages that are not used by the workload.
The Young page flag is used to avoid interference with the memory
reclaimer. A page's Young flag is set whenever the Access bit of a page
table entry pointing to the page is cleared by writing to the bitmap file.
If page_referenced() is called on a Young page, it will add 1 to its
return value, therefore concealing the fact that the Access bit was
cleared.
Note, since there is no room for extra page flags on 32 bit, this feature
uses extended page flags when compiled on 32 bit.
[akpm@linux-foundation.org: fix build]
[akpm@linux-foundation.org: kpageidle requires an MMU]
[akpm@linux-foundation.org: decouple from page-flags rework]
Signed-off-by: Vladimir Davydov <vdavydov@parallels.com>
Reviewed-by: Andres Lagar-Cavilla <andreslc@google.com>
Cc: Minchan Kim <minchan@kernel.org>
Cc: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>
Cc: Michal Hocko <mhocko@suse.cz>
Cc: Greg Thelen <gthelen@google.com>
Cc: Michel Lespinasse <walken@google.com>
Cc: David Rientjes <rientjes@google.com>
Cc: Pavel Emelyanov <xemul@parallels.com>
Cc: Cyrill Gorcunov <gorcunov@openvz.org>
Cc: Jonathan Corbet <corbet@lwn.net>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
98 lines
4.8 KiB
Text
98 lines
4.8 KiB
Text
MOTIVATION
|
|
|
|
The idle page tracking feature allows to track which memory pages are being
|
|
accessed by a workload and which are idle. This information can be useful for
|
|
estimating the workload's working set size, which, in turn, can be taken into
|
|
account when configuring the workload parameters, setting memory cgroup limits,
|
|
or deciding where to place the workload within a compute cluster.
|
|
|
|
It is enabled by CONFIG_IDLE_PAGE_TRACKING=y.
|
|
|
|
USER API
|
|
|
|
The idle page tracking API is located at /sys/kernel/mm/page_idle. Currently,
|
|
it consists of the only read-write file, /sys/kernel/mm/page_idle/bitmap.
|
|
|
|
The file implements a bitmap where each bit corresponds to a memory page. The
|
|
bitmap is represented by an array of 8-byte integers, and the page at PFN #i is
|
|
mapped to bit #i%64 of array element #i/64, byte order is native. When a bit is
|
|
set, the corresponding page is idle.
|
|
|
|
A page is considered idle if it has not been accessed since it was marked idle
|
|
(for more details on what "accessed" actually means see the IMPLEMENTATION
|
|
DETAILS section). To mark a page idle one has to set the bit corresponding to
|
|
the page by writing to the file. A value written to the file is OR-ed with the
|
|
current bitmap value.
|
|
|
|
Only accesses to user memory pages are tracked. These are pages mapped to a
|
|
process address space, page cache and buffer pages, swap cache pages. For other
|
|
page types (e.g. SLAB pages) an attempt to mark a page idle is silently ignored,
|
|
and hence such pages are never reported idle.
|
|
|
|
For huge pages the idle flag is set only on the head page, so one has to read
|
|
/proc/kpageflags in order to correctly count idle huge pages.
|
|
|
|
Reading from or writing to /sys/kernel/mm/page_idle/bitmap will return
|
|
-EINVAL if you are not starting the read/write on an 8-byte boundary, or
|
|
if the size of the read/write is not a multiple of 8 bytes. Writing to
|
|
this file beyond max PFN will return -ENXIO.
|
|
|
|
That said, in order to estimate the amount of pages that are not used by a
|
|
workload one should:
|
|
|
|
1. Mark all the workload's pages as idle by setting corresponding bits in
|
|
/sys/kernel/mm/page_idle/bitmap. The pages can be found by reading
|
|
/proc/pid/pagemap if the workload is represented by a process, or by
|
|
filtering out alien pages using /proc/kpagecgroup in case the workload is
|
|
placed in a memory cgroup.
|
|
|
|
2. Wait until the workload accesses its working set.
|
|
|
|
3. Read /sys/kernel/mm/page_idle/bitmap and count the number of bits set. If
|
|
one wants to ignore certain types of pages, e.g. mlocked pages since they
|
|
are not reclaimable, he or she can filter them out using /proc/kpageflags.
|
|
|
|
See Documentation/vm/pagemap.txt for more information about /proc/pid/pagemap,
|
|
/proc/kpageflags, and /proc/kpagecgroup.
|
|
|
|
IMPLEMENTATION DETAILS
|
|
|
|
The kernel internally keeps track of accesses to user memory pages in order to
|
|
reclaim unreferenced pages first on memory shortage conditions. A page is
|
|
considered referenced if it has been recently accessed via a process address
|
|
space, in which case one or more PTEs it is mapped to will have the Accessed bit
|
|
set, or marked accessed explicitly by the kernel (see mark_page_accessed()). The
|
|
latter happens when:
|
|
|
|
- a userspace process reads or writes a page using a system call (e.g. read(2)
|
|
or write(2))
|
|
|
|
- a page that is used for storing filesystem buffers is read or written,
|
|
because a process needs filesystem metadata stored in it (e.g. lists a
|
|
directory tree)
|
|
|
|
- a page is accessed by a device driver using get_user_pages()
|
|
|
|
When a dirty page is written to swap or disk as a result of memory reclaim or
|
|
exceeding the dirty memory limit, it is not marked referenced.
|
|
|
|
The idle memory tracking feature adds a new page flag, the Idle flag. This flag
|
|
is set manually, by writing to /sys/kernel/mm/page_idle/bitmap (see the USER API
|
|
section), and cleared automatically whenever a page is referenced as defined
|
|
above.
|
|
|
|
When a page is marked idle, the Accessed bit must be cleared in all PTEs it is
|
|
mapped to, otherwise we will not be able to detect accesses to the page coming
|
|
from a process address space. To avoid interference with the reclaimer, which,
|
|
as noted above, uses the Accessed bit to promote actively referenced pages, one
|
|
more page flag is introduced, the Young flag. When the PTE Accessed bit is
|
|
cleared as a result of setting or updating a page's Idle flag, the Young flag
|
|
is set on the page. The reclaimer treats the Young flag as an extra PTE
|
|
Accessed bit and therefore will consider such a page as referenced.
|
|
|
|
Since the idle memory tracking feature is based on the memory reclaimer logic,
|
|
it only works with pages that are on an LRU list, other pages are silently
|
|
ignored. That means it will ignore a user memory page if it is isolated, but
|
|
since there are usually not many of them, it should not affect the overall
|
|
result noticeably. In order not to stall scanning of the idle page bitmap,
|
|
locked pages may be skipped too.
|