mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Larabel <Michael@phoronix.com>
To: Shakeel Butt <shakeel.butt@linux.dev>
Cc: Dave Airlie <airlied@gmail.com>, Vlastimil Babka <vbabka@suse.cz>,
	Alexei Starovoitov <alexei.starovoitov@gmail.com>,
	Sebastian Sewior <bigeasy@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Alexei Starovoitov <ast@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 6.15-rc3
Date: Tue, 22 Apr 2025 19:54:59 -0500	[thread overview]
Message-ID: <896a67ec-9f48-4137-9d34-4bb16861e284@phoronix.com> (raw)
In-Reply-To: <mhewqdlvb5ahqordw2nuebq7yvsxo7xvdas4vl6gehmbmypcil@v3fn7nzllglj>

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@gmail.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



  reply	other threads:[~2025-04-23  1:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-20 21:01 Linus Torvalds
2025-04-20 23:03 ` Linus Torvalds
2025-04-21 13:20 ` Guenter Roeck
2025-04-22 23:01 ` Dave Airlie
2025-04-22 23:37   ` Alexei Starovoitov
2025-04-23  0:12     ` Shakeel Butt
2025-04-23  0:54       ` Michael Larabel [this message]
2025-04-23  8:42         ` Vlastimil Babka
2025-04-23 13:57           ` Michael Larabel
2025-04-23 15:41           ` Alexei Starovoitov
2025-04-23 16:05             ` Linus Torvalds
2025-04-23  7:14     ` Vlastimil Babka
2025-04-23  8:03       ` Vlastimil Babka
2025-04-23  8:08         ` Vlastimil Babka
2025-04-23 14:38           ` Michael Larabel
2025-04-23 15:06         ` Alexei Starovoitov

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=896a67ec-9f48-4137-9d34-4bb16861e284@phoronix.com \
    --to=michael@phoronix.com \
    --cc=airlied@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=alexei.starovoitov@gmail.com \
    --cc=ast@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shakeel.butt@linux.dev \
    --cc=torvalds@linux-foundation.org \
    --cc=vbabka@suse.cz \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®