From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: John Johansen <john.johansen@canonical.com>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Swapnil Sapkal <Swapnil.Sapkal@amd.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org,
Aaron Lu <aaron.lu@intel.com>,
x86@kernel.org, Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [tip: sched/core] sched: Fix performance regression introduced by mm_cid
Date: Fri, 23 Jun 2023 08:37:26 +0200 [thread overview]
Message-ID: <20230623063726.ejuc6v9D@linutronix.de> (raw)
In-Reply-To: <f94cd9fa-1a83-1f54-0259-123fcd86d549@canonical.com>
On 2023-06-21 16:59:31 [-0700], John Johansen wrote:
> > Which turned a per-cpu cache into a global memory pool protected by a spinlock. It may benefit RT, but it does not appear to be so great at scaling.
> >
> it is not. And I have a patch that needs some more formal testing for some stats.
> Ubuntu pulled it in last cycle so it has gotten a fair bit of use and is looking good
> on that end. There are probably some tweaks that can be done to improve it. The
> backoff in particular is something that has mostly been adjusted in response to some
> basic benchmarking.
>
> anyways patch below
>
> commit e057e9b47f1749882ea0efb4427d6b9671c761ab
I think I've been looking at this patch, or a former version of it, and
it looked good.
Sebastian
next prev parent reply other threads:[~2023-06-23 6:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-22 7:43 [tip: sched/core] sched: Fix performance regression introduced by mm_cid tip-bot2 for Mathieu Desnoyers
2023-06-20 8:14 ` Swapnil Sapkal
2023-06-20 9:11 ` Peter Zijlstra
2023-06-20 10:35 ` Swapnil Sapkal
2023-06-20 10:51 ` Mathieu Desnoyers
2023-06-21 16:36 ` Swapnil Sapkal
2023-06-21 18:51 ` Mathieu Desnoyers
2023-06-21 21:41 ` Mathieu Desnoyers
2023-06-21 23:59 ` John Johansen
2023-06-22 14:33 ` Mathieu Desnoyers
2023-06-22 16:09 ` John Johansen
2023-06-23 6:52 ` Sebastian Andrzej Siewior
2023-06-23 6:37 ` Sebastian Andrzej Siewior [this message]
2023-06-23 7:16 ` John Johansen
2023-06-23 8:15 ` Sebastian Andrzej Siewior
2023-06-23 7:35 ` John Johansen
2023-06-23 8:17 ` Sebastian Andrzej Siewior
2023-07-14 6:02 ` Swapnil Sapkal
2023-07-14 14:55 ` Mathieu Desnoyers
2023-07-18 6:01 ` Swapnil Sapkal
2023-06-23 13:12 ` Linux regression tracking #adding (Thorsten Leemhuis)
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=20230623063726.ejuc6v9D@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=Swapnil.Sapkal@amd.com \
--cc=aaron.lu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=john.johansen@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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.