| 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: Fri, 25 Feb 2022 08:05:13 +0000
From: SeongJae Park <sj@...nel.org>
To: xhao@...ux.alibaba.com
Cc: SeongJae Park <sj@...nel.org>, akpm@...ux-foundation.org,
corbet@....net, skhan@...uxfoundation.org, rientjes@...gle.com,
linux-damon@...zon.com, linux-mm@...ck.org,
linux-doc@...r.kernel.org, linux-kselftest@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/12] Introduce DAMON sysfs interface
Hi Xin,
On Fri, 25 Feb 2022 15:32:47 +0800 xhao@...ux.alibaba.com wrote:
> Hi SeongJae:
>
> On 2/23/22 11:20 PM, SeongJae Park wrote:
[...]
> > Introduction
> > ============
> >
> > DAMON's debugfs-based user interface (DAMON_DBGFS) served very well, so far.
> > However, it unnecessarily depends on debugfs, while DAMON is not aimed to be
> > used for only debugging. Also, the interface receives multiple values via one
> > file. For example, schemes file receives 18 values. As a result, it is
> > inefficient, hard to be used, and difficult to be extended. Especially,
> > keeping backward compatibility of user space tools is getting only challenging.
> > It would be better to implement another reliable and flexible interface and
> > deprecate DAMON_DBGFS in long term.
> >
> > For the reason, this patchset introduces a sysfs-based new user interface of
> > DAMON. The idea of the new interface is, using directory hierarchies and
> > having one dedicated file for each value. For a short example, users can do
> > the virtual address monitoring via the interface as below:
> >
> > # cd /sys/kernel/mm/damon/admin/
> > # echo 1 > kdamonds/nr
> > # echo 1 > kdamonds/0/contexts/nr
> > # echo vaddr > kdamonds/0/contexts/0/operations
> > # echo 1 > kdamonds/0/contexts/0/targets/nr
> > # echo $(pidof <workload>) > kdamonds/0/contexts/0/targets/0/pid
> > # echo on > kdamonds/0/state
> >
> > A brief representation of the files hierarchy of DAMON sysfs interface is as
> > below. Childs are represented with indentation, directories are having '/'
> > suffix, and files in each directory are separated by comma.
> >
> > /sys/kernel/mm/damon/admin
> > │ kdamonds/nr
> > │ │ 0/state,pid
> > │ │ │ contexts/nr
> > │ │ │ │ 0/operations
> > │ │ │ │ │ monitoring_attrs/
> > │ │ │ │ │ │ intervals/sample_us,aggr_us,update_us
> > │ │ │ │ │ │ nr_regions/min,max
> > │ │ │ │ │ targets/nr
> > │ │ │ │ │ │ 0/pid
> > │ │ │ │ │ │ │ regions/nr
> > │ │ │ │ │ │ │ │ 0/start,end
> > │ │ │ │ │ │ │ │ ...
> > │ │ │ │ │ │ ...
> > │ │ │ │ │ schemes/nr
> > │ │ │ │ │ 0/action
> > │ │ │ │ │ │ access_pattern/
> > │ │ │ │ │ │ │ sz/min,max
> > │ │ │ │ │ │ │ nr_accesses/min,max
> > │ │ │ │ │ │ │ age/min,max
> > │ │ │ │ │ │ quotas/ms,sz,reset_interval_ms
> > │ │ │ │ │ │ │ weights/sz,nr_accesses,age
> > │ │ │ │ │ │ watermarks/metric,interval_us,high,mid,low
> > │ │ │ │ │ │ stats/nr_tried,sz_tried,nr_applied,sz_applied,qt_exceeds
> > │ │ │ │ │ ...
> > │ │ ...
> >
> > Detailed usage of the files will be described in the final Documentation patch
> > of this patchset.
>
> The introduction of the sys DAMON interface makes DAMON seem more
> hierarchical, but it brings a problem. From a user's perspective,
>
> I find it difficult to operate. For example:
>
> step one:
>
> echo xxx > /sys/kernel/mm/damon/admin/kdamonds/0/contexts/0/targets/nr
>
> step two:
>
> echo /sys/kernel/mm/damon/admin/kdamonds/0/contexts/0/targets/nr/1/pid
>
> echo /sys/kernel/mm/damon/admin/kdamonds/0/contexts/0/targets/nr/0/pid
>
> .........
>
> Alas, it is really too troublesome to operate, can you make it as simple
> as possible, perhaps by referring to the implementation of cgroup.
Thank you very much for the great comments. I agree that this interface
requires quite a redundant works. Nevertheless, this interface is not aimed to
be used by human hand but user space tools. We provide the DAMON user-space
tool, damo, for the purpose. Damo already supports this interface while
introducing nearly-zero change to the end user interface. All you need to do
to use sysfs in background with damo is adding '--damon_interface sysfs' to the
command.
I guess someone might still want low level sysfs control for development and
testing purpose. For the case, damo is providing a new subcommand, fs[1], for
more low level sysfs control with better interface. It allows users to
read/write all hierarchies and values in DAMON sysfs via json format. For
example:
# ./damo/damo fs --damon_interface sysfs read
{
"kdamonds": {
"0": {
"contexts": {
"nr_contexts": "0\n"
},
"pid": "-1\n",
"state": "off\n"
},
"nr_kdamonds": "1\n"
}
}
# cat content.json
{
"kdamonds": {
"0": {
"contexts": {
"nr_contexts": "1\n"
}
}
}
}
# ./damo/damo fs --damon_interface sysfs write --content "$(cat content.json)"
# ./damo/damo fs --damon_interface sysfs read
{
"kdamonds": {
"0": {
"contexts": {
"0": {
"monitoring_attrs": {
"intervals": {
"aggr_us": "100000\n",
"sample_us": "5000\n",
"update_us": "60000000\n"
},
"nr_regions": {
"max": "1000\n",
"min": "10\n"
}
},
"operations": "vaddr\n",
"schemes": {
"nr_schemes": "0\n"
},
"targets": {
"nr_targets": "0\n"
}
},
"nr_contexts": "1\n"
},
"pid": "-1\n",
"state": "off\n"
},
"nr_kdamonds": "1\n"
}
}
I admit damo interface is still not perfect. It has many rooms for
improvement.
If even damo is too heavyweight for you, you could use some general scripts
that can do above work in similar manner:
https://github.com/sjp38/lazybox/blob/master/scripts/fs.py
Thanks,
SJ
Powered by blists - more mailing lists