1 .. SPDX-License-Identifier: GPL-2.0 1 .. SPDX-License-Identifier: GPL-2.0
2 2
3 DAMON Maintainer Entry Profile 3 DAMON Maintainer Entry Profile
4 ============================== 4 ==============================
5 5
6 The DAMON subsystem covers the files that are 6 The DAMON subsystem covers the files that are listed in 'DATA ACCESS MONITOR'
7 section of 'MAINTAINERS' file. 7 section of 'MAINTAINERS' file.
8 8
9 The mailing lists for the subsystem are damon@ 9 The mailing lists for the subsystem are damon@lists.linux.dev and
10 linux-mm@kvack.org. Patches should be made ag !! 10 linux-mm@kvack.org. Patches should be made against the mm-unstable tree [1]_
11 <https://git.kernel.org/akpm/mm/h/mm-unstable> !! 11 whenever possible and posted to the mailing lists.
12 to the mailing lists. <<
13 12
14 SCM Trees 13 SCM Trees
15 --------- 14 ---------
16 15
17 There are multiple Linux trees for DAMON devel 16 There are multiple Linux trees for DAMON development. Patches under
18 development or testing are queued in `damon/ne !! 17 development or testing are queued in damon/next [2]_ by the DAMON maintainer.
19 <https://git.kernel.org/sj/h/damon/next>`_ by !! 18 Sufficiently reviewed patches will be queued in mm-unstable [1]_ by the memory
20 Sufficiently reviewed patches will be queued i !! 19 management subsystem maintainer. After more sufficient tests, the patches will
21 <https://git.kernel.org/akpm/mm/h/mm-unstable> !! 20 be queued in mm-stable [3]_ , and finally pull-requested to the mainline by the
22 subsystem maintainer. After more sufficient t !! 21 memory management subsystem maintainer.
23 in `mm-stable <https://git.kernel.org/akpm/mm/ !! 22
24 pull-requested to the mainline by the memory m !! 23 Note again the patches for review should be made against the mm-unstable
25 !! 24 tree[1] whenever possible. damon/next is only for preview of others' works in
26 Note again the patches for `mm-unstable tree !! 25 progress.
27 <https://git.kernel.org/akpm/mm/h/mm-unstable> <<
28 management subsystem maintainer. If the patch <<
29 `damon/next tree <https://git.kernel.org/sj/h/ <<
30 in mm-unstable, please make sure the requireme <<
31 26
32 Submit checklist addendum 27 Submit checklist addendum
33 ------------------------- 28 -------------------------
34 29
35 When making DAMON changes, you should do below 30 When making DAMON changes, you should do below.
36 31
37 - Build changes related outputs including kern 32 - Build changes related outputs including kernel and documents.
38 - Ensure the builds introduce no new errors or 33 - Ensure the builds introduce no new errors or warnings.
39 - Run and ensure no new failures for DAMON `se !! 34 - Run and ensure no new failures for DAMON selftests [4]_ and kunittests [5]_ .
40 <https://github.com/damonitor/damon-tests/bl <<
41 `kunittests <<
42 <https://github.com/damonitor/damon-tests/bl <<
43 35
44 Further doing below and putting the results wi 36 Further doing below and putting the results will be helpful.
45 37
46 - Run `damon-tests/corr !! 38 - Run damon-tests/corr [6]_ for normal changes.
47 <https://github.com/damonitor/damon-tests/tr !! 39 - Run damon-tests/perf [7]_ for performance changes.
48 changes. <<
49 - Run `damon-tests/perf <<
50 <https://github.com/damonitor/damon-tests/tr <<
51 changes. <<
52 40
53 Key cycle dates 41 Key cycle dates
54 --------------- 42 ---------------
55 43
56 Patches can be sent anytime. Key cycle dates !! 44 Patches can be sent anytime. Key cycle dates of the mm-unstable[1] and
57 <https://git.kernel.org/akpm/mm/h/mm-unstable> !! 45 mm-stable[3] trees depend on the memory management subsystem maintainer.
58 <https://git.kernel.org/akpm/mm/h/mm-stable>`_ <<
59 management subsystem maintainer. <<
60 46
61 Review cadence 47 Review cadence
62 -------------- 48 --------------
63 49
64 The DAMON maintainer does the work on the usua 50 The DAMON maintainer does the work on the usual work hour (09:00 to 17:00,
65 Mon-Fri) in PT (Pacific Time). The response t !! 51 Mon-Fri) in PST. The response to patches will occasionally be slow. Do not
66 slow. Do not hesitate to send a ping if you h !! 52 hesitate to send a ping if you have not heard back within a week of sending a
67 of sending a patch. !! 53 patch.
68 !! 54
69 Mailing tool !! 55
70 ------------ !! 56 .. [1] https://git.kernel.org/akpm/mm/h/mm-unstable
71 !! 57 .. [2] https://git.kernel.org/sj/h/damon/next
72 Like many other Linux kernel subsystems, DAMON !! 58 .. [3] https://git.kernel.org/akpm/mm/h/mm-stable
73 (damon@lists.linux.dev and linux-mm@kvack.org) !! 59 .. [4] https://github.com/awslabs/damon-tests/blob/master/corr/run.sh#L49
74 channel. There is a simple tool called `HacKe !! 60 .. [5] https://github.com/awslabs/damon-tests/blob/master/corr/tests/kunit.sh
75 <https://github.com/damonitor/hackermail>`_ (` !! 61 .. [6] https://github.com/awslabs/damon-tests/tree/master/corr
76 are not very familiar with the mailing lists b !! 62 .. [7] https://github.com/awslabs/damon-tests/tree/master/perf
77 could be particularly helpful for DAMON commun <<
78 and maintained by DAMON maintainer. The tool <<
79 support DAMON and general Linux kernel develop <<
80 <<
81 In other words, `hkml <https://github.com/damo <<
82 tool for DAMON community, which DAMON maintain <<
83 Please feel free to try and report issues or f <<
84 the maintainer. <<
85 <<
86 Community meetup <<
87 ---------------- <<
88 <<
89 DAMON community is maintaining two bi-weekly m <<
90 members who prefer synchronous conversations o <<
91 <<
92 The first one is for any discussion between ev <<
93 reservation is needed. <<
94 <<
95 The seconds one is for discussions on specific <<
96 members including the maintainer. The maintai <<
97 slots, and attendees should reserve one of tho <<
98 time slot, by reaching out to the maintainer. <<
99 <<
100 Schedules and available reservation time slots <<
101 <https://docs.google.com/document/d/1v43Kcj3ly <<
102 There is also a public Google `calendar <<
103 <https://calendar.google.com/calendar/u/0?cid= <<
104 that has the events. Anyone can subscribe it. <<
105 provide periodic reminder to the mailing list <<
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.