From: SeongJae Park <sj@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: SeongJae Park <sj@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Steven Rostedt <rostedt@goodmis.org>,
damon@lists.linux.dev, linux-mm@kvack.org,
linux-doc@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 00/11] mm/damon: misc fixups for documents, comments and its tracepoint
Date: Thu, 7 Sep 2023 02:29:18 +0000 [thread overview]
Message-ID: <20230907022929.91361-1-sj@kernel.org> (raw)
This patchset contains miscellaneous simple fixups for documents, comments and
tracepoint of DAMON.
SeongJae Park (11):
Docs/admin-guide/mm/damon/usage: fixup missed :ref: keyword
Docs/admin-guide/mm/damon/usage: place debugfs usage at the bottom
Docs/admin-guide/mm/damon/usage: move debugfs intro to the bottom of
the section
Docs/mm/damon/design: explicitly introduce ``nr_accesses``
Docs/admin-guide/mm/damon/usage: explain the format of damon_aggregate
tracepoint
Docs/mm/damon/design: add a section for kdamond and DAMON context
Docs/admin-guide/mm/damon/usage: link design doc for details of
kdamond and context
mm/damon/core: fix a comment about damon_set_attrs() call timings
mm/damon/core: add more comments for nr_accesses
mm/damon/core: remove duplicated comment for watermarks-based
deactivation
mm/damon/core: remove 'struct target *' parameter from
damon_aggregated tracepoint
Documentation/admin-guide/mm/damon/usage.rst | 86 +++++++++++---------
Documentation/mm/damon/design.rst | 23 +++++-
include/linux/damon.h | 22 ++---
include/trace/events/damon.h | 6 +-
mm/damon/core.c | 8 +-
5 files changed, 90 insertions(+), 55 deletions(-)
base-commit: ac8e8303c9c11b5c2e1d2e110866eb66c9fd771e
--
2.25.1
next reply other threads:[~2023-09-07 2:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 2:29 SeongJae Park [this message]
2023-09-07 2:29 ` [PATCH 01/11] Docs/admin-guide/mm/damon/usage: fixup missed :ref: keyword SeongJae Park
2023-09-07 2:29 ` [PATCH 02/11] Docs/admin-guide/mm/damon/usage: place debugfs usage at the bottom SeongJae Park
2023-09-07 2:29 ` [PATCH 03/11] Docs/admin-guide/mm/damon/usage: move debugfs intro to the bottom of the section SeongJae Park
2023-09-07 2:29 ` [PATCH 04/11] Docs/mm/damon/design: explicitly introduce ``nr_accesses`` SeongJae Park
2023-09-07 2:29 ` [PATCH 05/11] Docs/admin-guide/mm/damon/usage: explain the format of damon_aggregate tracepoint SeongJae Park
2023-09-07 2:29 ` [PATCH 06/11] Docs/mm/damon/design: add a section for kdamond and DAMON context SeongJae Park
2023-09-07 2:29 ` [PATCH 07/11] Docs/admin-guide/mm/damon/usage: link design doc for details of kdamond and context SeongJae Park
2023-09-07 2:29 ` [PATCH 08/11] mm/damon/core: fix a comment about damon_set_attrs() call timings SeongJae Park
2023-09-07 2:29 ` [PATCH 09/11] mm/damon/core: add more comments for nr_accesses SeongJae Park
2023-09-07 2:29 ` [PATCH 10/11] mm/damon/core: remove duplicated comment for watermarks-based deactivation SeongJae Park
2023-09-07 2:29 ` [PATCH 11/11] mm/damon/core: remove 'struct target *' parameter from damon_aggregated tracepoint SeongJae Park
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230907022929.91361-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=damon@lists.linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.