From: Clark Williams <williams@redhat.com>
To: Joseph Salisbury <joseph.salisbury@canonical.com>
Cc: "Gleixner, Thomas" <tglx@linutronix.de>, linux-rt-users@vger.kernel.org
Subject: Re: Question Regarding [PATCH 098/167] in the 5.15 real-time patchset
Date: Wed, 6 Jul 2022 21:46:34 +0000 [thread overview]
Message-ID: <CAMLffL8pUzD+=FAnJoTuqpGi3x9LjeA=Kyui7Z5xv=DOQW=ZzQ@mail.gmail.com> (raw)
In-Reply-To: <45632dfb-5671-b6d6-3c84-e047d1257dbb@canonical.com>
I know we've had latency issues in the past with memory cgroups.
If there is a change in behavior in 5.16rt+ we can consider
backporting down to 5.15-rt
Clark
On Wed, Jul 6, 2022 at 8:25 PM Joseph Salisbury
<joseph.salisbury@canonical.com> wrote:
>
> Hello,
>
> An end user reported a bug[1] when attempting to use an Ubuntu kernel with the 5.15 real-time patches applied. The user reports an issue with missing cg memory when Kubernetes is used with the 5.15 patchset.
>
> After an investigation, it was found the issue is happens if the CONFIG_MEMCG config is not enabled. That config is usually enabled for the generic Ubuntu kernel. However, the config is disabled by the following patch in the 5.15 real-time patch set:
>
> [PATCH 098/167] mm/memcontrol: Disable on PREEMPT_RT
>
> I don't see this patch in the 5.16 and newer patch sets. Is there a fix in mainline or in the newer 5.16 patches that allows the 'mm/memcontrol: Disable on PREEMPT_RT' patch to be dropped? If so, I could assist with backporting the fix to 5.15 and older.
>
> Thanks in advance!
>
> Joe
>
>
>
> [0] https://bugs.launchpad.net/ubuntu-realtime/+bug/1978814
>
>
>
next parent reply other threads:[~2022-07-06 21:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <45632dfb-5671-b6d6-3c84-e047d1257dbb@canonical.com>
2022-07-06 21:46 ` Clark Williams [this message]
2022-07-06 20:23 Question Regarding [PATCH 098/167] in the 5.15 real-time patchset Joseph Salisbury
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='CAMLffL8pUzD+=FAnJoTuqpGi3x9LjeA=Kyui7Z5xv=DOQW=ZzQ@mail.gmail.com' \
--to=williams@redhat.com \
--cc=joseph.salisbury@canonical.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.