From: David Oberhollenzer <goliath@infraroot.at>
To: linux-rt-users@vger.kernel.org
Cc: williams@redhat.com, bigeasy@linutronix.de, richard@nod.at,
David Oberhollenzer <goliath@infraroot.at>
Subject: [PATCH 4/4] Allow MEMCG on PREEMPT_RT
Date: Tue, 12 Jul 2022 13:22:38 +0200 [thread overview]
Message-ID: <20220712112238.18824-5-goliath@infraroot.at> (raw)
In-Reply-To: <20220712112238.18824-1-goliath@infraroot.at>
With these backported, it is safe to use MEMCG again:
mm/memcg: Add a local_lock_t for IRQ and TASK object.
mm/memcg: Protect per-CPU counter by disabling preemption on PREEMPT_RT where needed.
mm/memcg: Disable threshold event handlers on PREEMPT_RT
Signed-off-by: David Oberhollenzer <goliath@infraroot.at>
---
init/Kconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/init/Kconfig b/init/Kconfig
index 160f836f81c7..1646c25f6ec5 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -943,7 +943,6 @@ config PAGE_COUNTER
config MEMCG
bool "Memory controller"
- depends on !PREEMPT_RT
select PAGE_COUNTER
select EVENTFD
help
--
2.36.1
next prev parent reply other threads:[~2022-07-12 11:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 11:22 [PATCH 0/4] Backport MEMCG changes from v5.17 David Oberhollenzer
2022-07-12 11:22 ` [PATCH 1/4] mm/memcg: Disable threshold event handlers on PREEMPT_RT David Oberhollenzer
2022-07-12 11:22 ` [PATCH 2/4] mm/memcg: Protect per-CPU counter by disabling preemption on PREEMPT_RT where needed David Oberhollenzer
2022-07-12 11:22 ` [PATCH 3/4] mm/memcg: Add a local_lock_t for IRQ and TASK object David Oberhollenzer
2022-07-12 11:22 ` David Oberhollenzer [this message]
2022-07-27 20:35 ` [PATCH 0/4] Backport MEMCG changes from v5.17 Joseph Salisbury
2022-07-29 16:14 ` Sebastian Andrzej Siewior
2022-07-29 16:37 ` Joseph Salisbury
2022-08-01 18:17 ` Joseph Salisbury
2022-08-01 22:36 ` Joseph Salisbury
2022-08-02 12:28 ` Clark Williams
2022-08-03 6:53 ` Sebastian Andrzej Siewior
2022-08-03 9:17 ` David Oberhollenzer
2022-08-03 9:37 ` Sebastian Andrzej Siewior
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=20220712112238.18824-5-goliath@infraroot.at \
--to=goliath@infraroot.at \
--cc=bigeasy@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=richard@nod.at \
--cc=williams@redhat.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