2018-03-21 19:22:35 +00:00
|
|
|
.. _page_owner:
|
|
|
|
|
|
|
|
==================================================
|
2014-12-13 00:56:07 +00:00
|
|
|
page owner: Tracking about who allocated each page
|
2018-03-21 19:22:35 +00:00
|
|
|
==================================================
|
2014-12-13 00:56:07 +00:00
|
|
|
|
2018-03-21 19:22:35 +00:00
|
|
|
Introduction
|
|
|
|
============
|
2014-12-13 00:56:07 +00:00
|
|
|
|
|
|
|
page owner is for the tracking about who allocated each page.
|
|
|
|
It can be used to debug memory leak or to find a memory hogger.
|
|
|
|
When allocation happens, information about allocation such as call stack
|
|
|
|
and order of pages is stored into certain storage for each page.
|
|
|
|
When we need to know about status of all pages, we can get and analyze
|
|
|
|
this information.
|
|
|
|
|
|
|
|
Although we already have tracepoint for tracing page allocation/free,
|
|
|
|
using it for analyzing who allocate each page is rather complex. We need
|
|
|
|
to enlarge the trace buffer for preventing overlapping until userspace
|
|
|
|
program launched. And, launched program continually dump out the trace
|
2020-10-22 14:26:53 +00:00
|
|
|
buffer for later analysis and it would change system behaviour with more
|
2014-12-13 00:56:07 +00:00
|
|
|
possibility rather than just keeping it in memory, so bad for debugging.
|
|
|
|
|
|
|
|
page owner can also be used for various purposes. For example, accurate
|
|
|
|
fragmentation statistics can be obtained through gfp flag information of
|
|
|
|
each page. It is already implemented and activated if page owner is
|
|
|
|
enabled. Other usages are more than welcome.
|
|
|
|
|
2022-02-23 13:41:04 +00:00
|
|
|
page owner is disabled by default. So, if you'd like to use it, you need
|
|
|
|
to add "page_owner=on" to your boot cmdline. If the kernel is built
|
|
|
|
with page owner and page owner is disabled in runtime due to not enabling
|
2014-12-13 00:56:07 +00:00
|
|
|
boot option, runtime overhead is marginal. If disabled in runtime, it
|
|
|
|
doesn't require memory to store owner information, so there is no runtime
|
|
|
|
memory overhead. And, page owner inserts just two unlikely branches into
|
2016-03-15 21:56:12 +00:00
|
|
|
the page allocator hotpath and if not enabled, then allocation is done
|
|
|
|
like as the kernel without page owner. These two unlikely branches should
|
|
|
|
not affect to allocation performance, especially if the static keys jump
|
|
|
|
label patching functionality is available. Following is the kernel's code
|
|
|
|
size change due to this facility.
|
2014-12-13 00:56:07 +00:00
|
|
|
|
2018-03-21 19:22:35 +00:00
|
|
|
- Without page owner::
|
|
|
|
|
2014-12-13 00:56:07 +00:00
|
|
|
text data bss dec hex filename
|
2020-12-15 03:04:49 +00:00
|
|
|
48392 2333 644 51369 c8a9 mm/page_alloc.o
|
2018-03-21 19:22:35 +00:00
|
|
|
|
|
|
|
- With page owner::
|
2014-12-13 00:56:07 +00:00
|
|
|
|
|
|
|
text data bss dec hex filename
|
2020-12-15 03:04:49 +00:00
|
|
|
48800 2445 644 51889 cab1 mm/page_alloc.o
|
2021-04-30 05:54:57 +00:00
|
|
|
6662 108 29 6799 1a8f mm/page_owner.o
|
2020-12-15 03:04:49 +00:00
|
|
|
1025 8 8 1041 411 mm/page_ext.o
|
2014-12-13 00:56:07 +00:00
|
|
|
|
2020-12-15 03:04:49 +00:00
|
|
|
Although, roughly, 8 KB code is added in total, page_alloc.o increase by
|
|
|
|
520 bytes and less than half of it is in hotpath. Building the kernel with
|
2014-12-13 00:56:07 +00:00
|
|
|
page owner and turning it on if needed would be great option to debug
|
|
|
|
kernel memory problem.
|
|
|
|
|
|
|
|
There is one notice that is caused by implementation detail. page owner
|
|
|
|
stores information into the memory from struct page extension. This memory
|
|
|
|
is initialized some time later than that page allocator starts in sparse
|
|
|
|
memory system, so, until initialization, many pages can be allocated and
|
|
|
|
they would have no owner information. To fix it up, these early allocated
|
|
|
|
pages are investigated and marked as allocated in initialization phase.
|
|
|
|
Although it doesn't mean that they have the right owner information,
|
|
|
|
at least, we can tell whether the page is allocated or not,
|
|
|
|
more accurately. On 2GB memory x86-64 VM box, 13343 early allocated pages
|
|
|
|
are catched and marked, although they are mostly allocated from struct
|
|
|
|
page extension feature. Anyway, after that, no page is left in
|
|
|
|
un-tracking state.
|
|
|
|
|
2018-03-21 19:22:35 +00:00
|
|
|
Usage
|
|
|
|
=====
|
|
|
|
|
|
|
|
1) Build user-space helper::
|
2014-12-13 00:56:07 +00:00
|
|
|
|
|
|
|
cd tools/vm
|
|
|
|
make page_owner_sort
|
|
|
|
|
2018-03-21 19:22:35 +00:00
|
|
|
2) Enable page owner: add "page_owner=on" to boot cmdline.
|
2014-12-13 00:56:07 +00:00
|
|
|
|
2022-03-25 01:09:20 +00:00
|
|
|
3) Do the job that you want to debug.
|
2014-12-13 00:56:07 +00:00
|
|
|
|
2018-03-21 19:22:35 +00:00
|
|
|
4) Analyze information from page owner::
|
|
|
|
|
2014-12-13 00:56:07 +00:00
|
|
|
cat /sys/kernel/debug/page_owner > page_owner_full.txt
|
2020-06-03 23:03:22 +00:00
|
|
|
./page_owner_sort page_owner_full.txt sorted_page_owner.txt
|
2014-12-13 00:56:07 +00:00
|
|
|
|
2022-02-24 19:35:07 +00:00
|
|
|
The general output of ``page_owner_full.txt`` is as follows::
|
tools/vm/page_owner_sort.c: count and sort by mem
When viewing page owner information, we may be more concerned about the
total memory rather than the times of stack appears. Therefore, the
following adjustments are made:
1. Added the statistics on the total number of pages.
2. Added the optional parameter "-m" to configure the program to sort by
memory (total pages).
The general output of page_owner is as follows:
Page allocated via order XXX, ...
PFN XXX ...
// Detailed stack
Page allocated via order XXX, ...
PFN XXX ...
// Detailed stack
The original page_owner_sort ignores PFN rows, puts the remaining rows
in buf, counts the times of buf, and finally sorts them according to the
times. General output:
XXX times:
Page allocated via order XXX, ...
// Detailed stack
Now, we use regexp to extract the page order value from the buf, and
count the total pages for the buf. General output:
XXX times, XXX pages:
Page allocated via order XXX, ...
// Detailed stack
By default, it is still sorted by the times of buf; If you want to sort
by the pages nums of buf, use the new -m parameter.
Link: https://lkml.kernel.org/r/1631678242-41033-1-git-send-email-weizhenliang@huawei.com
Signed-off-by: Zhenliang Wei <weizhenliang@huawei.com>
Cc: Tang Bin <tangbin@cmss.chinamobile.com>
Cc: Zhang Shengju <zhangshengju@cmss.chinamobile.com>
Cc: Zhenliang Wei <weizhenliang@huawei.com>
Cc: Xiaoming Ni <nixiaoming@huawei.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2021-11-05 20:42:55 +00:00
|
|
|
|
|
|
|
Page allocated via order XXX, ...
|
|
|
|
PFN XXX ...
|
2022-03-25 01:08:59 +00:00
|
|
|
// Detailed stack
|
tools/vm/page_owner_sort.c: count and sort by mem
When viewing page owner information, we may be more concerned about the
total memory rather than the times of stack appears. Therefore, the
following adjustments are made:
1. Added the statistics on the total number of pages.
2. Added the optional parameter "-m" to configure the program to sort by
memory (total pages).
The general output of page_owner is as follows:
Page allocated via order XXX, ...
PFN XXX ...
// Detailed stack
Page allocated via order XXX, ...
PFN XXX ...
// Detailed stack
The original page_owner_sort ignores PFN rows, puts the remaining rows
in buf, counts the times of buf, and finally sorts them according to the
times. General output:
XXX times:
Page allocated via order XXX, ...
// Detailed stack
Now, we use regexp to extract the page order value from the buf, and
count the total pages for the buf. General output:
XXX times, XXX pages:
Page allocated via order XXX, ...
// Detailed stack
By default, it is still sorted by the times of buf; If you want to sort
by the pages nums of buf, use the new -m parameter.
Link: https://lkml.kernel.org/r/1631678242-41033-1-git-send-email-weizhenliang@huawei.com
Signed-off-by: Zhenliang Wei <weizhenliang@huawei.com>
Cc: Tang Bin <tangbin@cmss.chinamobile.com>
Cc: Zhang Shengju <zhangshengju@cmss.chinamobile.com>
Cc: Zhenliang Wei <weizhenliang@huawei.com>
Cc: Xiaoming Ni <nixiaoming@huawei.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2021-11-05 20:42:55 +00:00
|
|
|
|
|
|
|
Page allocated via order XXX, ...
|
|
|
|
PFN XXX ...
|
2022-03-25 01:08:59 +00:00
|
|
|
// Detailed stack
|
tools/vm/page_owner_sort.c: count and sort by mem
When viewing page owner information, we may be more concerned about the
total memory rather than the times of stack appears. Therefore, the
following adjustments are made:
1. Added the statistics on the total number of pages.
2. Added the optional parameter "-m" to configure the program to sort by
memory (total pages).
The general output of page_owner is as follows:
Page allocated via order XXX, ...
PFN XXX ...
// Detailed stack
Page allocated via order XXX, ...
PFN XXX ...
// Detailed stack
The original page_owner_sort ignores PFN rows, puts the remaining rows
in buf, counts the times of buf, and finally sorts them according to the
times. General output:
XXX times:
Page allocated via order XXX, ...
// Detailed stack
Now, we use regexp to extract the page order value from the buf, and
count the total pages for the buf. General output:
XXX times, XXX pages:
Page allocated via order XXX, ...
// Detailed stack
By default, it is still sorted by the times of buf; If you want to sort
by the pages nums of buf, use the new -m parameter.
Link: https://lkml.kernel.org/r/1631678242-41033-1-git-send-email-weizhenliang@huawei.com
Signed-off-by: Zhenliang Wei <weizhenliang@huawei.com>
Cc: Tang Bin <tangbin@cmss.chinamobile.com>
Cc: Zhang Shengju <zhangshengju@cmss.chinamobile.com>
Cc: Zhenliang Wei <weizhenliang@huawei.com>
Cc: Xiaoming Ni <nixiaoming@huawei.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2021-11-05 20:42:55 +00:00
|
|
|
|
|
|
|
The ``page_owner_sort`` tool ignores ``PFN`` rows, puts the remaining rows
|
|
|
|
in buf, uses regexp to extract the page order value, counts the times
|
2022-03-25 01:08:56 +00:00
|
|
|
and pages of buf, and finally sorts them according to the parameter(s).
|
tools/vm/page_owner_sort.c: count and sort by mem
When viewing page owner information, we may be more concerned about the
total memory rather than the times of stack appears. Therefore, the
following adjustments are made:
1. Added the statistics on the total number of pages.
2. Added the optional parameter "-m" to configure the program to sort by
memory (total pages).
The general output of page_owner is as follows:
Page allocated via order XXX, ...
PFN XXX ...
// Detailed stack
Page allocated via order XXX, ...
PFN XXX ...
// Detailed stack
The original page_owner_sort ignores PFN rows, puts the remaining rows
in buf, counts the times of buf, and finally sorts them according to the
times. General output:
XXX times:
Page allocated via order XXX, ...
// Detailed stack
Now, we use regexp to extract the page order value from the buf, and
count the total pages for the buf. General output:
XXX times, XXX pages:
Page allocated via order XXX, ...
// Detailed stack
By default, it is still sorted by the times of buf; If you want to sort
by the pages nums of buf, use the new -m parameter.
Link: https://lkml.kernel.org/r/1631678242-41033-1-git-send-email-weizhenliang@huawei.com
Signed-off-by: Zhenliang Wei <weizhenliang@huawei.com>
Cc: Tang Bin <tangbin@cmss.chinamobile.com>
Cc: Zhang Shengju <zhangshengju@cmss.chinamobile.com>
Cc: Zhenliang Wei <weizhenliang@huawei.com>
Cc: Xiaoming Ni <nixiaoming@huawei.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2021-11-05 20:42:55 +00:00
|
|
|
|
2018-03-21 19:22:35 +00:00
|
|
|
See the result about who allocated each page
|
2022-02-24 19:35:07 +00:00
|
|
|
in the ``sorted_page_owner.txt``. General output::
|
tools/vm/page_owner_sort.c: count and sort by mem
When viewing page owner information, we may be more concerned about the
total memory rather than the times of stack appears. Therefore, the
following adjustments are made:
1. Added the statistics on the total number of pages.
2. Added the optional parameter "-m" to configure the program to sort by
memory (total pages).
The general output of page_owner is as follows:
Page allocated via order XXX, ...
PFN XXX ...
// Detailed stack
Page allocated via order XXX, ...
PFN XXX ...
// Detailed stack
The original page_owner_sort ignores PFN rows, puts the remaining rows
in buf, counts the times of buf, and finally sorts them according to the
times. General output:
XXX times:
Page allocated via order XXX, ...
// Detailed stack
Now, we use regexp to extract the page order value from the buf, and
count the total pages for the buf. General output:
XXX times, XXX pages:
Page allocated via order XXX, ...
// Detailed stack
By default, it is still sorted by the times of buf; If you want to sort
by the pages nums of buf, use the new -m parameter.
Link: https://lkml.kernel.org/r/1631678242-41033-1-git-send-email-weizhenliang@huawei.com
Signed-off-by: Zhenliang Wei <weizhenliang@huawei.com>
Cc: Tang Bin <tangbin@cmss.chinamobile.com>
Cc: Zhang Shengju <zhangshengju@cmss.chinamobile.com>
Cc: Zhenliang Wei <weizhenliang@huawei.com>
Cc: Xiaoming Ni <nixiaoming@huawei.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2021-11-05 20:42:55 +00:00
|
|
|
|
|
|
|
XXX times, XXX pages:
|
|
|
|
Page allocated via order XXX, ...
|
2022-03-25 01:08:59 +00:00
|
|
|
// Detailed stack
|
tools/vm/page_owner_sort.c: count and sort by mem
When viewing page owner information, we may be more concerned about the
total memory rather than the times of stack appears. Therefore, the
following adjustments are made:
1. Added the statistics on the total number of pages.
2. Added the optional parameter "-m" to configure the program to sort by
memory (total pages).
The general output of page_owner is as follows:
Page allocated via order XXX, ...
PFN XXX ...
// Detailed stack
Page allocated via order XXX, ...
PFN XXX ...
// Detailed stack
The original page_owner_sort ignores PFN rows, puts the remaining rows
in buf, counts the times of buf, and finally sorts them according to the
times. General output:
XXX times:
Page allocated via order XXX, ...
// Detailed stack
Now, we use regexp to extract the page order value from the buf, and
count the total pages for the buf. General output:
XXX times, XXX pages:
Page allocated via order XXX, ...
// Detailed stack
By default, it is still sorted by the times of buf; If you want to sort
by the pages nums of buf, use the new -m parameter.
Link: https://lkml.kernel.org/r/1631678242-41033-1-git-send-email-weizhenliang@huawei.com
Signed-off-by: Zhenliang Wei <weizhenliang@huawei.com>
Cc: Tang Bin <tangbin@cmss.chinamobile.com>
Cc: Zhang Shengju <zhangshengju@cmss.chinamobile.com>
Cc: Zhenliang Wei <weizhenliang@huawei.com>
Cc: Xiaoming Ni <nixiaoming@huawei.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2021-11-05 20:42:55 +00:00
|
|
|
|
|
|
|
By default, ``page_owner_sort`` is sorted according to the times of buf.
|
2022-03-25 01:08:56 +00:00
|
|
|
If you want to sort by the page nums of buf, use the ``-m`` parameter.
|
|
|
|
The detailed parameters are:
|
|
|
|
|
2022-04-27 19:41:59 +00:00
|
|
|
fundamental function::
|
2022-03-25 01:08:56 +00:00
|
|
|
|
|
|
|
Sort:
|
|
|
|
-a Sort by memory allocation time.
|
|
|
|
-m Sort by total memory.
|
|
|
|
-p Sort by pid.
|
2022-03-25 01:09:26 +00:00
|
|
|
-P Sort by tgid.
|
2022-03-25 01:09:31 +00:00
|
|
|
-n Sort by task command name.
|
2022-03-25 01:08:56 +00:00
|
|
|
-r Sort by memory release time.
|
|
|
|
-s Sort by stack trace.
|
|
|
|
-t Sort by times (default).
|
|
|
|
|
2022-04-27 19:41:59 +00:00
|
|
|
additional function::
|
2022-03-25 01:08:56 +00:00
|
|
|
|
|
|
|
Cull:
|
tools/vm/page_owner_sort.c: support for user-defined culling rules
When viewing page owner information, we may want to cull blocks of
information with our own rules. So it is important to enhance culling
function to provide the support for customizing culling rules.
Therefore, following adjustments are made:
1. Add --cull option to support the culling of blocks of information
with user-defined culling rules.
./page_owner_sort <input> <output> --cull=<rules>
./page_owner_sort <input> <output> --cull <rules>
<rules> is a single argument in the form of a comma-separated list to
specify individual culling rules, by the sequence of keys k1,k2, ....
Mixed use of abbreviated and complete-form of keys is allowed.
For reference, please see the document(Documentation/vm/page_owner.rst).
Now, assuming two blocks in the input file are as follows:
Page allocated via order 0, mask xxxx, pid 1, tgid 1 (task_name_demo)
PFN xxxx
prep_new_page+0xd0/0xf8
get_page_from_freelist+0x4a0/0x1290
__alloc_pages+0x168/0x340
alloc_pages+0xb0/0x158
Page allocated via order 0, mask xxxx, pid 32, tgid 32 (task_name_demo)
PFN xxxx
prep_new_page+0xd0/0xf8
get_page_from_freelist+0x4a0/0x1290
__alloc_pages+0x168/0x340
alloc_pages+0xb0/0x158
If we want to cull the blocks by stacktrace and task command name, we can
use this command:
./page_owner_sort <input> <output> --cull=stacktrace,name
The output would be like:
2 times, 2 pages, task_comm_name: task_name_demo
prep_new_page+0xd0/0xf8
get_page_from_freelist+0x4a0/0x1290
__alloc_pages+0x168/0x340
alloc_pages+0xb0/0x158
As we can see, these two blocks are culled successfully, for they share
the same pid and task command name.
However, if we want to cull the blocks by pid, stacktrace and task command
name, we can this command:
./page_owner_sort <input> <output> --cull=stacktrace,name,pid
The output would be like:
1 times, 1 pages, PID 1, task_comm_name: task_name_demo
prep_new_page+0xd0/0xf8
get_page_from_freelist+0x4a0/0x1290
__alloc_pages+0x168/0x340
alloc_pages+0xb0/0x158
1 times, 1 pages, PID 32, task_comm_name: task_name_demo
prep_new_page+0xd0/0xf8
get_page_from_freelist+0x4a0/0x1290
__alloc_pages+0x168/0x340
alloc_pages+0xb0/0x158
As we can see, these two blocks are failed to cull, for their PIDs are
different.
2. Add explanations of --cull options to the document.
This work is coauthored by
Yixuan Cao
Shenghong Han
Yinan Zhang
Chongxi Zhao
Yuhong Feng
Link: https://lkml.kernel.org/r/20220312145834.624-1-yejiajian2018@email.szu.edu.cn
Signed-off-by: Jiajian Ye <yejiajian2018@email.szu.edu.cn>
Cc: Yixuan Cao <caoyixuan2019@email.szu.edu.cn>
Cc: Shenghong Han <hanshenghong2019@email.szu.edu.cn>
Cc: Yinan Zhang <zhangyinan2019@email.szu.edu.cn>
Cc: Chongxi Zhao <zhaochongxi2019@email.szu.edu.cn>
Cc: Yuhong Feng <yuhongf@szu.edu.cn>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Sean Anderson <seanga2@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2022-03-25 01:09:38 +00:00
|
|
|
--cull <rules>
|
|
|
|
Specify culling rules.Culling syntax is key[,key[,...]].Choose a
|
|
|
|
multi-letter key from the **STANDARD FORMAT SPECIFIERS** section.
|
|
|
|
|
|
|
|
<rules> is a single argument in the form of a comma-separated list,
|
|
|
|
which offers a way to specify individual culling rules. The recognized
|
|
|
|
keywords are described in the **STANDARD FORMAT SPECIFIERS** section below.
|
|
|
|
<rules> can be specified by the sequence of keys k1,k2, ..., as described in
|
|
|
|
the STANDARD SORT KEYS section below. Mixed use of abbreviated and
|
|
|
|
complete-form of keys is allowed.
|
|
|
|
|
|
|
|
Examples:
|
|
|
|
./page_owner_sort <input> <output> --cull=stacktrace
|
|
|
|
./page_owner_sort <input> <output> --cull=st,pid,name
|
|
|
|
./page_owner_sort <input> <output> --cull=n,f
|
2022-03-25 01:08:56 +00:00
|
|
|
|
|
|
|
Filter:
|
2022-03-25 01:09:20 +00:00
|
|
|
-f Filter out the information of blocks whose memory has been released.
|
tools/vm/page_owner_sort.c: support for selecting by PID, TGID or task command name
When viewing page owner information, we may also need to select the blocks
by PID, TGID or task command name, which helps to get more accurate page
allocation information as needed.
Therefore, following adjustments are made:
1. Add three new options, including --pid, --tgid and --name, to support
the selection of information blocks by a specific pid, tgid and task
command name. In addtion, multiple options are allowed to be used at
the same time.
./page_owner_sort [input] [output] --pid <PID>
./page_owner_sort [input] [output] --tgid <TGID>
./page_owner_sort [input] [output] --name <TASK_COMMAND_NAME>
Assuming a scenario when a multi-threaded program, ./demo (PID =
5280), is running, and ./demo creates a child process (PID = 5281).
$ps
PID TTY TIME CMD
5215 pts/0 00:00:00 bash
5280 pts/0 00:00:00 ./demo
5281 pts/0 00:00:00 ./demo
5282 pts/0 00:00:00 ps
It would be better to filter out the records with tgid=5280 and the
task name "demo" when debugging the parent process, and the specific
usage is
./page_owner_sort [input] [output] --tgid 5280 --name demo
2. Add explanations of three new options, including --pid, --tgid and
--name, to the document.
This work is coauthored by
Shenghong Han <hanshenghong2019@email.szu.edu.cn>,
Yixuan Cao <caoyixuan2019@email.szu.edu.cn>,
Yinan Zhang <zhangyinan2019@email.szu.edu.cn>,
Chongxi Zhao <zhaochongxi2019@email.szu.edu.cn>,
Yuhong Feng <yuhongf@szu.edu.cn>.
Link: https://lkml.kernel.org/r/1646835223-7584-1-git-send-email-yejiajian2018@email.szu.edu.cn
Signed-off-by: Jiajian Ye <yejiajian2018@email.szu.edu.cn>
Cc: Sean Anderson <seanga2@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Zhenliang Wei <weizhenliang@huawei.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2022-03-25 01:09:34 +00:00
|
|
|
|
|
|
|
Select:
|
tools/vm/page_owner_sort.c: support for multi-value selection in single argument
When viewing page owner information, we may want to select blocks whose
PID/TGID/TASK_COMM_NAME appears in a user-specified list for data analysis
and aggregation. But currently page_owner_sort only supports selecting
blocks associated with only one specified PID/TGID/TASK_COMM_NAME.
Therefore, following adjustments are made to fix the problem:
1. Enhance selecting function to support the selection of multiple
PIDs/TGIDs/TASK_COMM_NAMEs.
The enhanced usages are as follows:
--pid <pidlist> Select by pid. This selects the blocks whose PID
numbers appear in <pidlist>.
--tgid <tgidlist> Select by tgid. This selects the blocks whose
TGID numbers appear in <tgidlist>.
--name <cmdlist> Select by task command name. This selects the
blocks whose task command name appear in <cmdlist>.
Where <pidlist>, <tgidlist>, <cmdlist> are single arguments in the form of
a comma-separated list,which offers a way to specify individual selecting
rules.
For example, if you want to select blocks whose tgids are 1, 2 or 3, you
have to use 4 commands as follows:
./page_owner_sort <input> <output1> --tgid=1
./page_owner_sort <input> <output2> --tgid=2
./page_owner_sort <input> <output3> --tgid=3
cat <output1> <output2> <output3> > <output>
With this patch, you can use only 1 command to obtain the same result as
above:
./page_owner_sort <input> <output1> --tgid=1,2,3
2. Update explanations of --pid, --tgid and --name in the function
usage() and the document(Documents/vm/page_owner.rst).
This work is coauthored by
Yixuan Cao
Shenghong Han
Yinan Zhang
Chongxi Zhao
Yuhong Feng
Yongqiang Liu
Link: https://lkml.kernel.org/r/20220401024856.767-2-yejiajian2018@email.szu.edu.cn
Signed-off-by: Jiajian Ye <yejiajian2018@email.szu.edu.cn>
Cc: Chongxi Zhao <zhaochongxi2019@email.szu.edu.cn>
Cc: Shenghong Han <hanshenghong2019@email.szu.edu.cn>
Cc: Yinan Zhang <zhangyinan2019@email.szu.edu.cn>
Cc: Yixuan Cao <caoyixuan2019@email.szu.edu.cn>
Cc: Yongqiang Liu <liuyongqiang13@huawei.com>
Cc: Yuhong Feng <yuhongf@szu.edu.cn>
Cc: Haowen Bai <baihaowen@meizu.com>
Cc: Sean Anderson <seanga2@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
2022-04-29 06:15:56 +00:00
|
|
|
--pid <pidlist> Select by pid. This selects the blocks whose process ID
|
|
|
|
numbers appear in <pidlist>.
|
|
|
|
--tgid <tgidlist> Select by tgid. This selects the blocks whose thread
|
|
|
|
group ID numbers appear in <tgidlist>.
|
|
|
|
--name <cmdlist> Select by task command name. This selects the blocks whose
|
|
|
|
task command name appear in <cmdlist>.
|
|
|
|
|
|
|
|
<pidlist>, <tgidlist>, <cmdlist> are single arguments in the form of a comma-separated list,
|
|
|
|
which offers a way to specify individual selecting rules.
|
|
|
|
|
|
|
|
|
|
|
|
Examples:
|
|
|
|
./page_owner_sort <input> <output> --pid=1
|
|
|
|
./page_owner_sort <input> <output> --tgid=1,2,3
|
|
|
|
./page_owner_sort <input> <output> --name name1,name2
|
tools/vm/page_owner_sort.c: support for user-defined culling rules
When viewing page owner information, we may want to cull blocks of
information with our own rules. So it is important to enhance culling
function to provide the support for customizing culling rules.
Therefore, following adjustments are made:
1. Add --cull option to support the culling of blocks of information
with user-defined culling rules.
./page_owner_sort <input> <output> --cull=<rules>
./page_owner_sort <input> <output> --cull <rules>
<rules> is a single argument in the form of a comma-separated list to
specify individual culling rules, by the sequence of keys k1,k2, ....
Mixed use of abbreviated and complete-form of keys is allowed.
For reference, please see the document(Documentation/vm/page_owner.rst).
Now, assuming two blocks in the input file are as follows:
Page allocated via order 0, mask xxxx, pid 1, tgid 1 (task_name_demo)
PFN xxxx
prep_new_page+0xd0/0xf8
get_page_from_freelist+0x4a0/0x1290
__alloc_pages+0x168/0x340
alloc_pages+0xb0/0x158
Page allocated via order 0, mask xxxx, pid 32, tgid 32 (task_name_demo)
PFN xxxx
prep_new_page+0xd0/0xf8
get_page_from_freelist+0x4a0/0x1290
__alloc_pages+0x168/0x340
alloc_pages+0xb0/0x158
If we want to cull the blocks by stacktrace and task command name, we can
use this command:
./page_owner_sort <input> <output> --cull=stacktrace,name
The output would be like:
2 times, 2 pages, task_comm_name: task_name_demo
prep_new_page+0xd0/0xf8
get_page_from_freelist+0x4a0/0x1290
__alloc_pages+0x168/0x340
alloc_pages+0xb0/0x158
As we can see, these two blocks are culled successfully, for they share
the same pid and task command name.
However, if we want to cull the blocks by pid, stacktrace and task command
name, we can this command:
./page_owner_sort <input> <output> --cull=stacktrace,name,pid
The output would be like:
1 times, 1 pages, PID 1, task_comm_name: task_name_demo
prep_new_page+0xd0/0xf8
get_page_from_freelist+0x4a0/0x1290
__alloc_pages+0x168/0x340
alloc_pages+0xb0/0x158
1 times, 1 pages, PID 32, task_comm_name: task_name_demo
prep_new_page+0xd0/0xf8
get_page_from_freelist+0x4a0/0x1290
__alloc_pages+0x168/0x340
alloc_pages+0xb0/0x158
As we can see, these two blocks are failed to cull, for their PIDs are
different.
2. Add explanations of --cull options to the document.
This work is coauthored by
Yixuan Cao
Shenghong Han
Yinan Zhang
Chongxi Zhao
Yuhong Feng
Link: https://lkml.kernel.org/r/20220312145834.624-1-yejiajian2018@email.szu.edu.cn
Signed-off-by: Jiajian Ye <yejiajian2018@email.szu.edu.cn>
Cc: Yixuan Cao <caoyixuan2019@email.szu.edu.cn>
Cc: Shenghong Han <hanshenghong2019@email.szu.edu.cn>
Cc: Yinan Zhang <zhangyinan2019@email.szu.edu.cn>
Cc: Chongxi Zhao <zhaochongxi2019@email.szu.edu.cn>
Cc: Yuhong Feng <yuhongf@szu.edu.cn>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Sean Anderson <seanga2@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2022-03-25 01:09:38 +00:00
|
|
|
|
|
|
|
STANDARD FORMAT SPECIFIERS
|
|
|
|
==========================
|
2022-04-27 19:41:59 +00:00
|
|
|
::
|
tools/vm/page_owner_sort.c: support for user-defined culling rules
When viewing page owner information, we may want to cull blocks of
information with our own rules. So it is important to enhance culling
function to provide the support for customizing culling rules.
Therefore, following adjustments are made:
1. Add --cull option to support the culling of blocks of information
with user-defined culling rules.
./page_owner_sort <input> <output> --cull=<rules>
./page_owner_sort <input> <output> --cull <rules>
<rules> is a single argument in the form of a comma-separated list to
specify individual culling rules, by the sequence of keys k1,k2, ....
Mixed use of abbreviated and complete-form of keys is allowed.
For reference, please see the document(Documentation/vm/page_owner.rst).
Now, assuming two blocks in the input file are as follows:
Page allocated via order 0, mask xxxx, pid 1, tgid 1 (task_name_demo)
PFN xxxx
prep_new_page+0xd0/0xf8
get_page_from_freelist+0x4a0/0x1290
__alloc_pages+0x168/0x340
alloc_pages+0xb0/0x158
Page allocated via order 0, mask xxxx, pid 32, tgid 32 (task_name_demo)
PFN xxxx
prep_new_page+0xd0/0xf8
get_page_from_freelist+0x4a0/0x1290
__alloc_pages+0x168/0x340
alloc_pages+0xb0/0x158
If we want to cull the blocks by stacktrace and task command name, we can
use this command:
./page_owner_sort <input> <output> --cull=stacktrace,name
The output would be like:
2 times, 2 pages, task_comm_name: task_name_demo
prep_new_page+0xd0/0xf8
get_page_from_freelist+0x4a0/0x1290
__alloc_pages+0x168/0x340
alloc_pages+0xb0/0x158
As we can see, these two blocks are culled successfully, for they share
the same pid and task command name.
However, if we want to cull the blocks by pid, stacktrace and task command
name, we can this command:
./page_owner_sort <input> <output> --cull=stacktrace,name,pid
The output would be like:
1 times, 1 pages, PID 1, task_comm_name: task_name_demo
prep_new_page+0xd0/0xf8
get_page_from_freelist+0x4a0/0x1290
__alloc_pages+0x168/0x340
alloc_pages+0xb0/0x158
1 times, 1 pages, PID 32, task_comm_name: task_name_demo
prep_new_page+0xd0/0xf8
get_page_from_freelist+0x4a0/0x1290
__alloc_pages+0x168/0x340
alloc_pages+0xb0/0x158
As we can see, these two blocks are failed to cull, for their PIDs are
different.
2. Add explanations of --cull options to the document.
This work is coauthored by
Yixuan Cao
Shenghong Han
Yinan Zhang
Chongxi Zhao
Yuhong Feng
Link: https://lkml.kernel.org/r/20220312145834.624-1-yejiajian2018@email.szu.edu.cn
Signed-off-by: Jiajian Ye <yejiajian2018@email.szu.edu.cn>
Cc: Yixuan Cao <caoyixuan2019@email.szu.edu.cn>
Cc: Shenghong Han <hanshenghong2019@email.szu.edu.cn>
Cc: Yinan Zhang <zhangyinan2019@email.szu.edu.cn>
Cc: Chongxi Zhao <zhaochongxi2019@email.szu.edu.cn>
Cc: Yuhong Feng <yuhongf@szu.edu.cn>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Sean Anderson <seanga2@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2022-03-25 01:09:38 +00:00
|
|
|
|
|
|
|
KEY LONG DESCRIPTION
|
|
|
|
p pid process ID
|
|
|
|
tg tgid thread group ID
|
|
|
|
n name task command name
|
|
|
|
f free whether the page has been released or not
|
|
|
|
st stacktrace stace trace of the page allocation
|