Messages in this thread | | | Date | Mon, 26 Feb 2024 11:12:43 +0100 | Subject | Re: regression/bisected commit 773688a6cb24b0b3c2ba40354d883348a2befa38 make my system completely unusable under high load | From | Vlastimil Babka <> |
| |
On 2/26/24 10:25, Marco Elver wrote: > On Tue, 20 Feb 2024 at 19:51, Marco Elver <elver@google.com> wrote: >> >> While it would be nice if 6.8 would not regress over 6.7 (performance >> is mostly fixed, memory usage is not), waiting for confirmation what >> the rcutorture issue from the bot is about might be good. >> >> Mikhail: since you are testing mainline, in about 4 weeks the fixes >> should then reach 6.9-rc in the next merge window. Until then, if it's >> not too difficult for you, you can apply those 2 patches in your own >> tree. > > There are more issues that are fixed by "[PATCH v2 1/2] stackdepot: > use variable size records for non-evictable entries". See > https://lore.kernel.org/all/ZdxYXQdZDuuhcqiv@elver.google.com/ > > This will eventually reach stable, but it might be good to reconsider > mainlining it earlier.
I believe I can see that patch, together with "kasan: revert eviction of stack traces in generic mode" in mm-hotfixes-stable so it should be on track for 6.8.
> Thanks, > -- Marco
| |