[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230623081557.gf5xCGdD@linutronix.de>
Date: Fri, 23 Jun 2023 10:15:57 +0200
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: John Johansen <john.johansen@...onical.com>
Cc: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Swapnil Sapkal <Swapnil.Sapkal@....com>,
Peter Zijlstra <peterz@...radead.org>,
linux-kernel@...r.kernel.org, linux-tip-commits@...r.kernel.org,
Aaron Lu <aaron.lu@...el.com>, x86@...nel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [tip: sched/core] sched: Fix performance regression introduced
by mm_cid
On 2023-06-23 00:16:35 [-0700], John Johansen wrote:
> With that said the patch does work, and seems to be stable in the broader
> testing it has gotten. Its more complicated than I would like, and wanted to
> play with ideas around improving it. I also wanted get some better benchmark data.
> All things I just haven't had time for
If you tell me what to do (as in run this) I could try to run it on a
machine. The current version, your proposal and kmalloc() instead.
> I am also not opposed to using some version of this patch now, to solve the
> immediate needs and working to improve it after the fact.
Sebastian
Powered by blists - more mailing lists