From: Dmitry Rokosov <ddrokosov@salutedevices.com>
To: <hannes@cmpxchg.org>, <mhocko@kernel.org>,
<roman.gushchin@linux.dev>, <shakeelb@google.com>,
<muchun.song@linux.dev>, <akpm@linux-foundation.org>
Cc: <kernel@sberdevices.ru>, <rockosov@gmail.com>,
<cgroups@vger.kernel.org>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>, <bpf@vger.kernel.org>,
Dmitry Rokosov <ddrokosov@salutedevices.com>
Subject: [PATCH v3 3/3] mm: memcg: add reminder comment for the memcg v2 events
Date: Thu, 23 Nov 2023 10:19:45 +0300 [thread overview]
Message-ID: <20231123071945.25811-4-ddrokosov@salutedevices.com> (raw)
In-Reply-To: <20231123071945.25811-1-ddrokosov@salutedevices.com>
To maintain the correct state, it is important to ensure that events for
the memory cgroup v2 are aligned with the sample cgroup codes.
Signed-off-by: Dmitry Rokosov <ddrokosov@salutedevices.com>
---
mm/memcontrol.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index e8ca4bdcb03c..a75c4584f58f 100644
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -6555,6 +6555,10 @@ static ssize_t memory_max_write(struct kernfs_open_file *of,
return nbytes;
}
+/*
+ * Note: don't forget to update the 'samples/cgroup/memcg_event_listener'
+ * if any new events become available.
+ */
static void __memory_events_show(struct seq_file *m, atomic_long_t *events)
{
seq_printf(m, "low %lu\n", atomic_long_read(&events[MEMCG_LOW]));
--
2.36.0
next prev parent reply other threads:[~2023-11-23 7:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 7:19 [PATCH v3 0/3] samples: introduce cgroup events listeners Dmitry Rokosov
2023-11-23 7:19 ` [PATCH v3 1/3] samples: introduce new samples subdir for cgroup Dmitry Rokosov
2023-11-23 7:19 ` [PATCH v3 2/3] samples/cgroup: introduce memcg memory.events listener Dmitry Rokosov
2023-11-23 7:19 ` Dmitry Rokosov [this message]
2023-11-24 19:42 ` [PATCH v3 0/3] samples: introduce cgroup events listeners Andrew Morton
2023-11-24 20:06 ` Dmitry Rokosov
2023-11-25 8:07 ` Dmitry Rokosov
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=20231123071945.25811-4-ddrokosov@salutedevices.com \
--to=ddrokosov@salutedevices.com \
--cc=akpm@linux-foundation.org \
--cc=bpf@vger.kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kernel@sberdevices.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=rockosov@gmail.com \
--cc=roman.gushchin@linux.dev \
--cc=shakeelb@google.com \
/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