[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <896a67ec-9f48-4137-9d34-4bb16861e284@phoronix.com>
Date: Tue, 22 Apr 2025 19:54:59 -0500
From: Michael Larabel <Michael@...ronix.com>
To: Shakeel Butt <shakeel.butt@...ux.dev>
Cc: Dave Airlie <airlied@...il.com>, Vlastimil Babka <vbabka@...e.cz>,
Alexei Starovoitov <alexei.starovoitov@...il.com>,
Sebastian Sewior <bigeasy@...utronix.de>,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Alexei Starovoitov <ast@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 6.15-rc3
On 4/22/25 7:12 PM, Shakeel Butt wrote:
> Ccing Michael
>
> On Tue, Apr 22, 2025 at 04:37:59PM -0700, Alexei Starovoitov wrote:
>> On Tue, Apr 22, 2025 at 4:01 PM Dave Airlie <airlied@...il.com> wrote:
>>>> Alexei Starovoitov (2):
>>>> locking/local_lock, mm: replace localtry_ helpers with
>>>> local_trylock_t type
>>> This seems to have upset some phoronix nginx workload
>>> https://www.phoronix.com/review/linux-615-nginx-regression/2
>> 3x regression? wow.
>> Thanks for heads up.
>> I'm staring at the patch and don't see it.
>> Adding more experts.
> Hi Michael,
>
> Can you please share a bit more on your nginx workload and how can we
> reproduce locally? In the mean time, I can try netperf locally to
> reproduce.
>
> I do have some followup optimizations [1, 2] which hopefully are aimed
> for next release but we can try those as well.
>
> [1] https://lkml.kernel.org/r/20250416180229.2902751-1-shakeel.butt@linux.dev
> [2] https://lkml.kernel.org/r/20250410025752.92159-1-shakeel.butt@linux.dev
>
> thanks,
> Shakeel
The Nginx test case is a fairly stock Nginx build measuring HTTPS
throughput for serving some static web page with Wrk used as the
stressor, all on the same host for stressing just the local host. All of
the assets and execution scripts used for that Nginx test in raw form
are here -
https://openbenchmarking.org/innhold/c7b555063f5732b4f1bb08444e258984d1dbb94b
Let me know if any problems reproducing, etc.
Thanks, I can try out those patches tomorrow. At the moment on that same
server currently running through some of the other workloads I also
found regressed on Linux 6.15 GIt to see if attributed to same commit or
not.
So far, when comparing 51339d99c0131bc0d16d378e9b05bc498d2967e2 as the
first bad commit against the parent commit
a30951d09c33c899f0e4aca80eb87fad5f10ecfa, I was able to reproduce a
regression for the OpenFOAM CFD software using drivaerFastback with the
small mesh size: 30.6 seconds on the bad commit, 23.6 seconds on the
parent. So that too seems to be related while the other tests are still
running at the moment.
Michael
Powered by blists - more mailing lists