From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Kurt Kanzenbach <kurt@linutronix.de>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Thomas Gleixner <tglx@linutronix.de>,
"Bouska, Zdenek" <zdenek.bouska@siemens.com>,
Will Deacon <will@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
Nishanth Menon <nm@ti.com>, Puranjay Mohan <p-mohan@ti.com>
Subject: Re: Unfair qspinlocks on ARM64 without LSE atomics => 3ms delay in interrupt handling
Date: Fri, 28 Apr 2023 09:30:16 +0200 [thread overview]
Message-ID: <20230428073016.YfrIGGoN@linutronix.de> (raw)
In-Reply-To: <871qk5782i.fsf@kurt>
On 2023-04-27 15:45:09 [+0200], Kurt Kanzenbach wrote:
> > Are we aware of other concrete case where it bites? Even with just
> > "normal" contented spin_lock usage?
>
> Well, some years ago I've observed a similar problem with ARM64
> spinlocks, cpu_relax() and retry loops (in the futex code). It also
> generated latency spikes up to 2-3ms. Back then, it was easily
> reproducible using stress-ng --ptrace 4.
That was fixed by
https://patchwork.kernel.org/project/linux-arm-kernel/patch/1399528508-2806-1-git-send-email-arjun.kv@samsung.com
if my memory serves me well.
> Thanks,
> Kurt
Sebastian
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-04-28 7:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AS1PR10MB567534190B05A4493674173BEB659@AS1PR10MB5675.EURPRD10.PROD.OUTLOOK.COM>
2023-04-26 21:29 ` Unfair qspinlocks on ARM64 without LSE atomics => 3ms delay in interrupt handling Thomas Gleixner
2023-04-27 9:38 ` Bouska, Zdenek
2023-04-27 10:06 ` Will Deacon
2023-04-27 13:14 ` Jan Kiszka
2023-04-27 13:45 ` Kurt Kanzenbach
2023-04-28 7:30 ` Sebastian Andrzej Siewior [this message]
2023-04-28 7:37 ` Kurt Kanzenbach
2023-03-24 8:43 Bouska, Zdenek
2023-03-24 17:01 ` Catalin Marinas
2023-03-24 18:09 ` Will Deacon
2023-03-28 9:39 ` Bouska, Zdenek
2023-03-27 5:44 ` Bouska, Zdenek
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=20230428073016.YfrIGGoN@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=catalin.marinas@arm.com \
--cc=jan.kiszka@siemens.com \
--cc=kurt@linutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=nm@ti.com \
--cc=p-mohan@ti.com \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=zdenek.bouska@siemens.com \
/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;
as well as URLs for NNTP newsgroup(s).