요약·해설과 원문, 전문 번역을 서로 분리했습니다. API 이름, symbol, source path는 원문 표기를 사용합니다.
1. 요약·해설
원문의 핵심 논리와 kernel programming 관점의 보충 설명입니다. 아래의 전문 번역과는 별도로 작성했습니다.
2. 영어 원문 전체
번역 기준이 된 Linux v6.18.37 원문입니다. 줄 번호는 이 버전의 파일 좌표입니다.
원문 전체 펼치기
.. SPDX-License-Identifier: GPL-2.0
DAMON Maintainer Entry Profile
==============================
The DAMON subsystem covers the files that are listed in 'DATA ACCESS MONITOR'
section of 'MAINTAINERS' file.
The mailing lists for the subsystem are [email protected] and
[email protected]. Patches should be made against the `mm-new tree
<https://git.kernel.org/akpm/mm/h/mm-new>`_ whenever possible and posted to the
mailing lists.
SCM Trees
---------
There are multiple Linux trees for DAMON development. Patches under
development or testing are queued in `damon/next
<https://git.kernel.org/sj/h/damon/next>`_ by the DAMON maintainer.
Sufficiently reviewed patches will be queued in `mm-new
<https://git.kernel.org/akpm/mm/h/mm-new>`_ by the memory management subsystem
maintainer. As more sufficient tests are done, the patches will move to
`mm-unstable <https://git.kernel.org/akpm/mm/h/mm-unstable>`_ and then to
`mm-stable <https://git.kernel.org/akpm/mm/h/mm-stable>`_. And finally those
will be pull-requested to the mainline by the memory management subsystem
maintainer.
Note again the patches for `mm-new tree
<https://git.kernel.org/akpm/mm/h/mm-new>`_ are queued by the memory management
subsystem maintainer. If the patches requires some patches in `damon/next tree
<https://git.kernel.org/sj/h/damon/next>`_ which not yet merged in mm-new,
please make sure the requirement is clearly specified.
Submit checklist addendum
-------------------------
When making DAMON changes, you should do below.
- Build changes related outputs including kernel and documents.
- Ensure the builds introduce no new errors or warnings.
- Run and ensure no new failures for DAMON `selftests
<https://github.com/damonitor/damon-tests/blob/master/corr/run.sh#L49>`_ and
`kunittests
<https://github.com/damonitor/damon-tests/blob/master/corr/tests/kunit.sh>`_.
Further doing below and putting the results will be helpful.
- Run `damon-tests/corr
<https://github.com/damonitor/damon-tests/tree/master/corr>`_ for normal
changes.
- Run `damon-tests/perf
<https://github.com/damonitor/damon-tests/tree/master/perf>`_ for performance
changes.
Key cycle dates
---------------
Patches can be sent anytime. Key cycle dates of the `mm-new
<https://git.kernel.org/akpm/mm/h/mm-new>`_, `mm-unstable
<https://git.kernel.org/akpm/mm/h/mm-unstable>`_and `mm-stable
<https://git.kernel.org/akpm/mm/h/mm-stable>`_ trees depend on the memory
management subsystem maintainer.
Review cadence
--------------
The DAMON maintainer does the work on the usual work hour (09:00 to 17:00,
Mon-Fri) in PT (Pacific Time). The response to patches will occasionally be
slow. Do not hesitate to send a ping if you have not heard back within a week
of sending a patch.
Mailing tool
------------
Like many other Linux kernel subsystems, DAMON uses the mailing lists
([email protected] and [email protected]) as the major communication
channel. There is a simple tool called `HacKerMaiL
<https://github.com/damonitor/hackermail>`_ (``hkml``), which is for people who
are not very familiar with the mailing lists based communication. The tool
could be particularly helpful for DAMON community members since it is developed
and maintained by DAMON maintainer. The tool is also officially announced to
support DAMON and general Linux kernel development workflow.
In other words, `hkml <https://github.com/damonitor/hackermail>`_ is a mailing
tool for DAMON community, which DAMON maintainer is committed to support.
Please feel free to try and report issues or feature requests for the tool to
the maintainer.
Community meetup
----------------
DAMON community has a bi-weekly meetup series for members who prefer
synchronous conversations over mails. It is for discussions on specific topics
between a group of members including the maintainer. The maintainer shares the
available time slots, and attendees should reserve one of those at least 24
hours before the time slot, by reaching out to the maintainer.
Schedules and reservation status are available at the Google `doc
<https://docs.google.com/document/d/1v43Kcj3ly4CYqmAkMaZzLiM2GEnWfgdGbZAH3mi2vpM/edit?usp=sharing>`_.
There is also a public Google `calendar
<https://calendar.google.com/calendar/u/0?cid=ZDIwOTA4YTMxNjc2MDQ3NTIyMmUzYTM5ZmQyM2U4NDA0ZGIwZjBiYmJlZGQxNDM0MmY4ZTRjOTE0NjdhZDRiY0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t>`_
that has the events. Anyone can subscribe it. DAMON maintainer will also
provide periodic reminder to the mailing list ([email protected]).
3. 한국어 전문 번역
영어 원문의 문단 순서와 의미를 유지한 전체 번역입니다. 코드, 함수명, symbol과 URL은 원문 표기를 유지합니다.
관리 범위와 mailing list
1-12DAMON subsystem의 관리 범위는 `MAINTAINERS` 파일의 `DATA ACCESS MONITOR` 절에 나열된 파일입니다.
Subsystem mailing list는 `[email protected]`와 `[email protected]`입니다. 가능하면 patch는 `https://git.kernel.org/akpm/mm/h/mm-new`의 `mm-new` tree를 기준으로 만들고 두 mailing list에 게시해야 합니다.
.. SPDX-License-Identifier: GPL-2.0
DAMON Maintainer Entry Profile
==============================
The DAMON subsystem covers the files that are listed in 'DATA ACCESS MONITOR'
section of 'MAINTAINERS' file.
The mailing lists for the subsystem are [email protected] and
[email protected]. Patches should be made against the `mm-new tree
<https://git.kernel.org/akpm/mm/h/mm-new>`_ whenever possible and posted to the
mailing lists.
SCM tree와 patch 이동 경로
13-32DAMON 개발에는 여러 Linux tree가 사용됩니다. 개발 또는 시험 중인 patch는 DAMON maintainer가 `https://git.kernel.org/sj/h/damon/next`의 `damon/next`에 queue합니다. 충분히 검토된 patch는 memory management subsystem maintainer가 `https://git.kernel.org/akpm/mm/h/mm-new`의 `mm-new`에 queue합니다.
시험이 더 충분히 진행되면 patch는 `mm-unstable`, 이어서 `mm-stable`로 이동하고 마지막에는 memory management subsystem maintainer가 mainline으로 pull request를 보냅니다.
`mm-new`에 patch를 queue하는 주체는 memory management subsystem maintainer입니다. patch가 아직 `mm-new`에 merge되지 않은 `damon/next` patch를 필요로 한다면 그 의존성을 명확히 밝혀야 합니다.
SCM Trees
---------
There are multiple Linux trees for DAMON development. Patches under
development or testing are queued in `damon/next
<https://git.kernel.org/sj/h/damon/next>`_ by the DAMON maintainer.
Sufficiently reviewed patches will be queued in `mm-new
<https://git.kernel.org/akpm/mm/h/mm-new>`_ by the memory management subsystem
maintainer. As more sufficient tests are done, the patches will move to
`mm-unstable <https://git.kernel.org/akpm/mm/h/mm-unstable>`_ and then to
`mm-stable <https://git.kernel.org/akpm/mm/h/mm-stable>`_. And finally those
will be pull-requested to the mainline by the memory management subsystem
maintainer.
Note again the patches for `mm-new tree
<https://git.kernel.org/akpm/mm/h/mm-new>`_ are queued by the memory management
subsystem maintainer. If the patches requires some patches in `damon/next tree
<https://git.kernel.org/sj/h/damon/next>`_ which not yet merged in mm-new,
please make sure the requirement is clearly specified.
제출 checklist 추가 항목
33-54DAMON 변경을 만들 때 다음 작업을 수행해야 합니다.
- Kernel과 문서를 포함해 변경과 관련된 결과물을 build합니다.
- Build에 새로운 error나 warning이 생기지 않았는지 확인합니다.
- DAMON `selftests`와 `kunittests`를 실행하고 새로운 실패가 없는지 확인합니다.
다음 시험도 수행하고 결과를 함께 제시하면 도움이 됩니다.
- 일반 변경에는 `https://github.com/damonitor/damon-tests/tree/master/corr`의 `damon-tests/corr`를 실행합니다.
- 성능 변경에는 `https://github.com/damonitor/damon-tests/tree/master/perf`의 `damon-tests/perf`를 실행합니다.
Submit checklist addendum
-------------------------
When making DAMON changes, you should do below.
- Build changes related outputs including kernel and documents.
- Ensure the builds introduce no new errors or warnings.
- Run and ensure no new failures for DAMON `selftests
<https://github.com/damonitor/damon-tests/blob/master/corr/run.sh#L49>`_ and
`kunittests
<https://github.com/damonitor/damon-tests/blob/master/corr/tests/kunit.sh>`_.
Further doing below and putting the results will be helpful.
- Run `damon-tests/corr
<https://github.com/damonitor/damon-tests/tree/master/corr>`_ for normal
changes.
- Run `damon-tests/perf
<https://github.com/damonitor/damon-tests/tree/master/perf>`_ for performance
changes.
주요 cycle 날짜와 review 주기
55-70Patch는 언제든 보낼 수 있습니다. `mm-new`, `mm-unstable`, `mm-stable` tree의 주요 cycle 날짜는 memory management subsystem maintainer 일정에 따릅니다.
DAMON maintainer는 보통 Pacific Time 기준 월요일부터 금요일 09:00~17:00에 작업합니다. Patch 응답이 때때로 늦을 수 있으며, patch를 보낸 뒤 일주일 동안 답이 없으면 주저하지 말고 ping을 보내십시오.
Key cycle dates
---------------
Patches can be sent anytime. Key cycle dates of the `mm-new
<https://git.kernel.org/akpm/mm/h/mm-new>`_, `mm-unstable
<https://git.kernel.org/akpm/mm/h/mm-unstable>`_and `mm-stable
<https://git.kernel.org/akpm/mm/h/mm-stable>`_ trees depend on the memory
management subsystem maintainer.
Review cadence
--------------
The DAMON maintainer does the work on the usual work hour (09:00 to 17:00,
Mon-Fri) in PT (Pacific Time). The response to patches will occasionally be
slow. Do not hesitate to send a ping if you have not heard back within a week
of sending a patch.
Mailing 도구 hkml
71-88다른 많은 Linux kernel subsystem처럼 DAMON은 `[email protected]`와 `[email protected]` mailing list를 주요 소통 채널로 사용합니다.
Mailing list 기반 소통에 익숙하지 않은 사람을 위한 간단한 도구 `HacKerMaiL`, 즉 `hkml`이 `https://github.com/damonitor/hackermail`에 있습니다. DAMON maintainer가 개발하고 관리하므로 DAMON community 구성원에게 특히 유용할 수 있으며, DAMON과 일반 Linux kernel 개발 workflow 지원 도구로 공식 발표됐습니다.
다시 말해 `hkml`은 DAMON maintainer가 지원하기로 약속한 DAMON community용 mailing 도구입니다. 자유롭게 사용해 보고 issue나 기능 요청을 maintainer에게 보고할 수 있습니다.
Mailing tool
------------
Like many other Linux kernel subsystems, DAMON uses the mailing lists
([email protected] and [email protected]) as the major communication
channel. There is a simple tool called `HacKerMaiL
<https://github.com/damonitor/hackermail>`_ (``hkml``), which is for people who
are not very familiar with the mailing lists based communication. The tool
could be particularly helpful for DAMON community members since it is developed
and maintained by DAMON maintainer. The tool is also officially announced to
support DAMON and general Linux kernel development workflow.
In other words, `hkml <https://github.com/damonitor/hackermail>`_ is a mailing
tool for DAMON community, which DAMON maintainer is committed to support.
Please feel free to try and report issues or feature requests for the tool to
the maintainer.
Community meetup
89-103DAMON community는 mail보다 동기식 대화를 선호하는 구성원을 위해 격주 meetup을 운영합니다. Maintainer를 포함한 구성원 그룹이 구체적인 주제를 논의하는 자리입니다.
Maintainer가 가능한 시간대를 공유하면 참석자는 maintainer에게 연락해 해당 시간보다 적어도 24시간 전에 하나를 예약해야 합니다. 일정과 예약 상태는 Google 문서 `https://docs.google.com/document/d/1v43Kcj3ly4CYqmAkMaZzLiM2GEnWfgdGbZAH3mi2vpM/edit?usp=sharing`에서 확인할 수 있습니다.
행사가 들어 있는 공개 Google calendar도 있으며 누구나 구독할 수 있습니다. DAMON maintainer는 `[email protected]`에도 주기적으로 reminder를 보냅니다.
Community meetup
----------------
DAMON community has a bi-weekly meetup series for members who prefer
synchronous conversations over mails. It is for discussions on specific topics
between a group of members including the maintainer. The maintainer shares the
available time slots, and attendees should reserve one of those at least 24
hours before the time slot, by reaching out to the maintainer.
Schedules and reservation status are available at the Google `doc
<https://docs.google.com/document/d/1v43Kcj3ly4CYqmAkMaZzLiM2GEnWfgdGbZAH3mi2vpM/edit?usp=sharing>`_.
There is also a public Google `calendar
<https://calendar.google.com/calendar/u/0?cid=ZDIwOTA4YTMxNjc2MDQ3NTIyMmUzYTM5ZmQyM2U4NDA0ZGIwZjBiYmJlZGQxNDM0MmY4ZTRjOTE0NjdhZDRiY0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t>`_
that has the events. Anyone can subscribe it. DAMON maintainer will also
provide periodic reminder to the mailing list ([email protected]).
요약·해설
maintainer-profile.rst:1-103DAMON patch는 보통 `mm-new` 기준으로 작성해 DAMON 및 linux-mm mailing list에 보내며, 개발·검토·시험 수준에 따라 `damon/next`, `mm-new`, `mm-unstable`, `mm-stable`, mainline 순서로 이동합니다.
각 단계에서 검토와 시험이 축적되고 마지막에 mainline pull request가 만들어집니다.
필수 확인과 변경 성격에 따른 추가 시험입니다.