From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Mike Galbraith <bitbucket@online.de>
Cc: Manfred Spraul <manfred@colorfullife.com>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [patch 1/3] ipc/sem: fix -rt livelock
Date: Fri, 04 Oct 2013 13:28:51 +0200 [thread overview]
Message-ID: <524EA673.5050400@linutronix.de> (raw)
In-Reply-To: <1380885410.5432.5.camel@marge.simpson.net>
On 10/04/2013 01:16 PM, Mike Galbraith wrote:
> Manfred's race fix also kills loop, and thereby the -rt livelock, so the
> only question is does -rt want to use his completion wakeup scheme, and
> does it want to do something about spin_unlock_wait() unconditionally
> grabbing/releasing every lock in the array.
So his patches went into v3.11 or so right? So all -RT released post
this point will have it fixed right?
However if this is something that bugs people using -RT it might worth
looking at it.
> -Mike
>
Sebastian
next prev parent reply other threads:[~2013-10-04 11:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1379051751.5455.112.camel@marge.simpson.net>
2013-09-13 6:12 ` [patch 1/3] ipc/sem: fix -rt livelock Mike Galbraith
2013-09-14 12:24 ` Manfred Spraul
2013-09-15 3:41 ` Mike Galbraith
2013-09-14 21:46 ` Manfred Spraul
2013-09-15 4:45 ` Mike Galbraith
2013-10-04 10:44 ` Sebastian Andrzej Siewior
2013-10-04 11:16 ` Mike Galbraith
2013-10-04 11:28 ` Sebastian Andrzej Siewior [this message]
2013-10-04 13:55 ` Mike Galbraith
2013-10-04 14:02 ` Manfred Spraul
2013-10-04 14:08 ` Mike Galbraith
2013-10-11 15:36 ` Sebastian Andrzej Siewior
2013-10-12 4:34 ` Mike Galbraith
2013-09-13 6:12 ` [patch 2/3] ipc/sem: revert ipc/sem: Rework semaphore wakeups Mike Galbraith
2013-09-13 6:12 ` [patch 3/3] ipc/sem: Add -RT compatible wakeup scheme Mike Galbraith
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=524EA673.5050400@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=a.p.zijlstra@chello.nl \
--cc=bitbucket@online.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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).