From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: David Oberhollenzer <goliath@infraroot.at>
Cc: linux-rt-users@vger.kernel.org, williams@redhat.com, richard@nod.at
Subject: Re: [PATCH 0/4] Backport MEMCG changes from v5.17
Date: Wed, 3 Aug 2022 08:53:59 +0200 [thread overview]
Message-ID: <Yuobh/+/Sv8VTjTP@linutronix.de> (raw)
In-Reply-To: <20220712112238.18824-1-goliath@infraroot.at>
On 2022-07-12 13:22:34 [+0200], David Oberhollenzer 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.17.
This isn't the series that was merged upstream:
| 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
any reason why not backport those?
Sebastian
next prev parent reply other threads:[~2022-08-03 6:54 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 ` [PATCH 4/4] Allow MEMCG on PREEMPT_RT David Oberhollenzer
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 [this message]
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=Yuobh/+/Sv8VTjTP@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=goliath@infraroot.at \
--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