From: Daniel Wagner <wagi@monom.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-kernel@vger.kernel.org,
Daniel Wagner <daniel.wagner@siemens.com>,
Peter Zijlstra <peterz@infradead.org>,
Will Deacon <will.deacon@arm.com>,
x86@kernel.org, Linus Torvalds <torvalds@linux-foundation.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Boqun Feng <boqun.feng@gmail.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: [Problem] Cache line starvation
Date: Tue, 2 Oct 2018 08:31:59 +0200 [thread overview]
Message-ID: <20181002063159.r4hxljpzyxpsdg5s@helium.monom.org> (raw)
In-Reply-To: <20180921120226.6xjgr4oiho22ex75@linutronix.de>
On Fri, Sep 21, 2018 at 02:02:26PM +0200, Sebastian Andrzej Siewior wrote:
> This matches Daniel Wagner's observations which he described in [0] on
> v4.4-RT.
Peter Z recommended to drop to ticket spinlocks instead trying to port
back all the qspinlock changes to v4.4-rt.
With ticket spinlocks, 'stress-ng --ptrace 4' run for 50 hours without
a problem (before it was seconds) and my normal workload for -rt testing
for 60 hours without a problem (before it broke within 24h).
The cyclictest max values went slightly down from 32us to 30us but
that might just be coincidence.
Thanks,
Daniel
prev parent reply other threads:[~2018-10-02 6:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 12:02 [Problem] Cache line starvation Sebastian Andrzej Siewior
2018-09-21 12:13 ` Thomas Gleixner
2018-09-21 12:50 ` Sebastian Andrzej Siewior
2018-09-21 12:20 ` Peter Zijlstra
2018-09-21 12:54 ` Thomas Gleixner
2018-10-03 7:51 ` Catalin Marinas
2018-10-03 8:07 ` Thomas Gleixner
2018-10-03 8:28 ` Peter Zijlstra
2018-10-03 10:43 ` Thomas Gleixner
2018-10-03 8:23 ` Peter Zijlstra
2018-09-26 7:34 ` Peter Zijlstra
2018-09-26 8:04 ` Thomas Gleixner
2018-09-26 12:53 ` Will Deacon
2018-09-27 14:25 ` Kurt Kanzenbach
2018-09-27 14:41 ` Kurt Kanzenbach
2018-09-27 14:47 ` Thomas Gleixner
2018-09-28 9:05 ` Kurt Kanzenbach
2018-09-28 15:26 ` Kurt Kanzenbach
2018-09-28 19:26 ` Sebastian Andrzej Siewior
2018-09-28 19:34 ` Thomas Gleixner
2018-10-02 6:31 ` Daniel Wagner [this message]
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=20181002063159.r4hxljpzyxpsdg5s@helium.monom.org \
--to=wagi@monom.org \
--cc=bigeasy@linutronix.de \
--cc=boqun.feng@gmail.com \
--cc=daniel.wagner@siemens.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
--cc=will.deacon@arm.com \
--cc=x86@kernel.org \
/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).