From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Richard Weinberger <richard@nod.at>
Cc: linux-rt-users@vger.kernel.org, williams@redhat.com
Subject: Re: [v5.15 0/4] Backport MEMCG changes from v5.16
Date: Thu, 23 Jun 2022 13:23:18 +0200 [thread overview]
Message-ID: <YrRNJqo94yLPDa7Z@linutronix.de> (raw)
In-Reply-To: <20220622110506.10534-1-richard@nod.at>
On 2022-06-22 13:05:02 [+0200], Richard Weinberger wrote:
> This is a backport of Sebastian's MEMCG changes to v5.15, with these patches applied,
> it is possible to use memory cgroups together with PREEMPT_RT on v5.15, just like on v5.16.
>
> Richard Weinberger (1):
> Allow MEMCG on PREEMPT_RT
>
> Sebastian Andrzej Siewior (3):
> mm/memcg: Disable threshold event handlers on PREEMPT_RT
> mm/memcg: Protect per-CPU counter by disabling preemption on
> PREEMPT_RT where needed.
> mm/memcg: Add a local_lock_t for IRQ and TASK object.
So you took the four patches from v5.16 and added it to v5.15.
I would prefer taking what ended up in v5.17 as of v5.17.1-rt17
- 0001-mm-memcg-Revert-mm-memcg-optimize-user-context-objec.patch
- 0002-mm-memcg-Disable-threshold-event-handlers-on-PREEMPT.patch
- 0003-mm-memcg-Protect-per-CPU-counter-by-disabling-preemp.patch
- 0004-mm-memcg-Opencode-the-inner-part-of-obj_cgroup_uncha.patch
- 0005-mm-memcg-Protect-memcg_stock-with-a-local_lock_t.patch
- 0006-mm-memcg-Disable-migration-instead-of-preemption-in-.patch
- 0007-mm-memcg-Add-missing-counter-index-which-are-not-upd.patch
- 0008-mm-memcg-Add-a-comment-regarding-the-release-obj.patch
- mm-memcg-Only-perform-the-debug-checks-on-PREEMPT_RT.patch
since this is what finally landed upstream. So we don't have an
intermediate step from an not supported kernel in a supported one.
Sebastian
next prev parent reply other threads:[~2022-06-23 11:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 11:05 [v5.15 0/4] Backport MEMCG changes from v5.16 Richard Weinberger
2022-06-22 11:05 ` [v5.15 1/4] mm/memcg: Disable threshold event handlers on PREEMPT_RT Richard Weinberger
2022-06-22 11:05 ` [v5.15 2/4] mm/memcg: Protect per-CPU counter by disabling preemption on PREEMPT_RT where needed Richard Weinberger
2022-06-22 11:05 ` [v5.15 3/4] mm/memcg: Add a local_lock_t for IRQ and TASK object Richard Weinberger
2022-06-22 11:05 ` [v5.15 4/4] Allow MEMCG on PREEMPT_RT Richard Weinberger
2022-06-23 11:23 ` Sebastian Andrzej Siewior [this message]
2022-06-23 12:02 ` [v5.15 0/4] Backport MEMCG changes from v5.16 Richard Weinberger
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=YrRNJqo94yLPDa7Z@linutronix.de \
--to=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