From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,sj@kernel.org,lirongqing@baidu.com,akpm@linux-foundation.org
Subject: [merged mm-stable] mm-damon-remove-__read_mostly-from-memory_idle_ms_percentiles.patch removed from -mm tree
Date: Fri, 06 Feb 2026 15:48:15 -0800 [thread overview]
Message-ID: <20260206234816.5ADA6C116C6@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm/damon/stat: remove __read_mostly from memory_idle_ms_percentiles
has been removed from the -mm tree. Its filename was
mm-damon-remove-__read_mostly-from-memory_idle_ms_percentiles.patch
This patch was dropped because it was merged into the mm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Li RongQing <lirongqing@baidu.com>
Subject: mm/damon/stat: remove __read_mostly from memory_idle_ms_percentiles
Date: Fri, 30 Jan 2026 03:56:03 -0500
The 'memory_idle_ms_percentiles' array in DAMON_STAT is updated frequently
by the kernel to reflect the latest idle time statistics. Marking it as
'__read_mostly' is inappropriate for data that is regularly written to, as
it can lead to cache pollution in the read-mostly section.
Remove the '__read_mostly' annotation to accurately reflect the
variable's usage pattern.
Link: https://lkml.kernel.org/r/20260130085603.1814-1-lirongqing@baidu.com
Signed-off-by: Li RongQing <lirongqing@baidu.com>
Reviewed-by: SeongJae Park <sj@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/damon/stat.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/mm/damon/stat.c~mm-damon-remove-__read_mostly-from-memory_idle_ms_percentiles
+++ a/mm/damon/stat.c
@@ -34,7 +34,7 @@ module_param(estimated_memory_bandwidth,
MODULE_PARM_DESC(estimated_memory_bandwidth,
"Estimated memory bandwidth usage in bytes per second");
-static long memory_idle_ms_percentiles[101] __read_mostly = {0,};
+static long memory_idle_ms_percentiles[101] = {0,};
module_param_array(memory_idle_ms_percentiles, long, NULL, 0400);
MODULE_PARM_DESC(memory_idle_ms_percentiles,
"Memory idle time percentiles in milliseconds");
_
Patches currently in -mm which might be from lirongqing@baidu.com are
reply other threads:[~2026-02-06 23:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260206234816.5ADA6C116C6@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=lirongqing@baidu.com \
--cc=mm-commits@vger.kernel.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 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.