tjh.dev / kernel
Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux
1
fork

Configure Feed

Select the types of activity you want to include in your feed.

Docs/admin-guide/mm/damon/usage: update context directory section label

The label for context DAMON sysfs directory section is having name
sysfs_contexts. The name would be better to be used for the contexts
directory. Rename it to represent a single context.

Link: https://lkml.kernel.org/r/20231213190338.54146-5-sj@kernel.org
Signed-off-by: SeongJae Park <sj@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>

authored by

SeongJae Park and committed by
Andrew Morton c7ae9634 1f1d83ca

+3 -3
+3 -3
Documentation/admin-guide/mm/damon/usage.rst
··· 164 164 details). At the moment, only one context per kdamond is supported, so only 165 165 ``0`` or ``1`` can be written to the file. 166 166 167 - .. _sysfs_contexts: 167 + .. _sysfs_context: 168 168 169 169 contexts/<N>/ 170 170 ------------- ··· 288 288 from the file and their meaning are as below. 289 289 290 290 Note that support of each action depends on the running DAMON operations set 291 - :ref:`implementation <sysfs_contexts>`. 291 + :ref:`implementation <sysfs_context>`. 292 292 293 293 - ``willneed``: Call ``madvise()`` for the region with ``MADV_WILLNEED``. 294 294 Supported by ``vaddr`` and ``fvaddr`` operations set. ··· 428 428 echo N > 1/matching 429 429 430 430 Note that ``anon`` and ``memcg`` filters are currently supported only when 431 - ``paddr`` :ref:`implementation <sysfs_contexts>` is being used. 431 + ``paddr`` :ref:`implementation <sysfs_context>` is being used. 432 432 433 433 Also, memory regions that are filtered out by ``addr`` or ``target`` filters 434 434 are not counted as the scheme has tried to those, while regions that filtered