| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 16 Feb 2022 16:30:36 +0800
From: Xin Hao <xhao@...ux.alibaba.com>
To: sj@...nel.org
Cc: xhao@...ux.alibaba.com, rongwei.wang@...ux.alibaba.com,
akpm@...ux-foundation.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: [RFC PATCH V1 0/5] mm/damon: Add NUMA access statistics function support
On today's cloud computing service scenario, NUMA (non uniform memory access)
architecture server has been applied on a large scale. Using Damon function,
it can easily and lightweight identify hot and cold memory, but it can not
display the situation of locale and remote NUMA memory access.
The purpose of these serie patches is to identify the situation of NUMA access
in combination with DAMON, especially for remote NUMA access in hot memory.
We hope to detect this situation in the data center and use page migration or
multi backup page technology to optimize the behavior of memory access.
So next, we will further improve Damon NUMA function:
1. Support hugtlbfs NUMA access statistics.
2. Add the DAMO tool to parse NUMA local & remote in "damon_region" support.
3. For hot memory remote NUMA access, support page migration or multi backup page.
About DAMON correctness of numa access statistics
We wrote a test case, allocate about 1G memory, and use numa_alloc(), set 512M in
NUMA node0 and 512M in NUMA node1, and The test case alternately accesses the 1G of memory.
We used "perf record -e damon:damon_aggregated" and "perf script"
cmd to obtain data, like this:
kdamond.0 target_id=0 nr_regions=10 281473056325632-281473127964672:: 12 0 5243 5513
kdamond.0 target_id=0 nr_regions=10 281473127964672-281473238028288: 8 1 5427 5399
...
kdamond.0 target_id=0 nr_regions=10 281473056325632-281473127964672: 9 3 7669 7632
kdamond.0 target_id=0 nr_regions=10 281473127964672-281473238028288: 7 2 7913 7892
And compared with numastat like this:
Per-node process memory usage (in MBs) for PID 111676 (lt-numademo)
Node 0 Node 1 Node 2
--------------- --------------- ---------------
Huge 0.00 0.00 0.00
Heap 0.02 0.00 0.00
Stack 0.01 0.00 0.00
Private 565.24 564.00 0.00
---------------- --------------- --------------- ---------------
Total 565.27 564.00 0.00
This comparison can determine the accuracy of Damon NUMA memory access statistics.
About the impact of DAMON NUMA access on Performance
During the benchmakr test, we found that the MBW benchmark memcpy test item
will cause about 3% performance degradation, and there is no performance degradation
in other benchmarks.
So we added "numa_stat" switch in DAMON dbgfs interface, turn on this switch when NUMA access
statistics is required.
Xin Hao (5):
mm/damon: Add NUMA local and remote variables in 'damon_region'
mm/damon: Add 'damon_region' NUMA fault simulation support
mm/damon: Add 'damon_region' NUMA access statistics core
implementation
mm/damon/dbgfs: Add numa simulate switch
mm/damon/tracepoint: Add 'damon_region' NUMA access statistics support
include/linux/damon.h | 25 ++++++++++
include/trace/events/damon.h | 9 +++-
mm/damon/core.c | 94 +++++++++++++++++++++++++++++++++++-
mm/damon/dbgfs.c | 70 ++++++++++++++++++++++++---
mm/damon/paddr.c | 25 ++++++++--
mm/damon/prmtv-common.c | 44 +++++++++++++++++
mm/damon/prmtv-common.h | 3 ++
mm/damon/vaddr.c | 45 ++++++++++-------
mm/huge_memory.c | 5 ++
mm/memory.c | 5 ++
10 files changed, 292 insertions(+), 33 deletions(-)
--
2.27.0
Powered by blists - more mailing lists