public inbox for linux-mm@kvack.org
 help / color / mirror / Atom feed
From: Liew Rui Yan <aethernet65535@gmail.com>
To: sj@kernel.org
Cc: damon@list.linux.dev, linux-mm@kvack.org
Subject: [DAMON][Question] DAMON_STAT and DAMON_LRU_SORT module parameter conflict?
Date: Fri, 13 Mar 2026 19:09:53 +0800	[thread overview]
Message-ID: <20260313110953.37465-1-aethernet65535@gmail.com> (raw)

TL;DR
=====
When CONFIG_DAMON_STAT_ENABLED_DEFAULT=y, enabling damon_lru_sort via sysfs
"enabled" parameter returns -EBUSY. Is this expected behavior? If yes, should
this limitation be documented?

Reproduction
============
Environment:
- Kernel: 7.0.0-rc3+ (x86_64)
- VM: Virtme-ng (4G RAM, 2 CPUs)
- Config: CONFIG_DAMON_STAT_ENABLED_DEFAULT=y, CONFIG_DAMON_LRU_SORT=y

Steps:
1. cd /sys/module/damon_lru_sort/parameters
2. (optional) tune parameters: hot_thres_access_freq, cold_min_age, etc.
3. echo Y > enabled

Result:
  bash: echo: write error: Device or resource busy

Workaround:
  Disable CONFIG_DAMON_STAT_ENABLED_DEFAULT, or disable damon_stat at runtime
  before enabling damon_lru_sort.

Questions
=========
1. Is this resource conflict between damon_stat and damon_lru_sort expected?
2. If yes, should this limitation be documented in:
   - Documentation/admin-guide/mm/damon/lru_sort.rst
   - Documentation/admin-guide/mm/damon/stat.rst

Additional Context
==================
- On major distros (Arch/Fedora), CONFIG_DAMON_STAT_ENABLED_DEFAULT is typically
  unset (disabled), so this issue may not affect most users.
- However, for kernel developers or custom builds enabling both modules, clearer
  documentation or error handling would improve debuggability.

Best regards,
Liew Rui Yan


             reply	other threads:[~2026-03-13 11:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-13 11:09 Liew Rui Yan [this message]
2026-03-14  0:51 ` [DAMON][Question] DAMON_STAT and DAMON_LRU_SORT module parameter conflict? SeongJae Park
2026-03-14  2:35   ` Liew Rui Yan

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=20260313110953.37465-1-aethernet65535@gmail.com \
    --to=aethernet65535@gmail.com \
    --cc=damon@list.linux.dev \
    --cc=linux-mm@kvack.org \
    --cc=sj@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox