From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Mike Galbraith <bitbucket@online.de>
Cc: paulmck@linux.vnet.ibm.com, linux-rt-users@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] rcu: Eliminate softirq processing from rcutree
Date: Fri, 24 Jan 2014 20:50:14 +0100 [thread overview]
Message-ID: <20140124195014.GB29981@linutronix.de> (raw)
In-Reply-To: <1390015514.5444.46.camel@marge.simpson.net>
* Mike Galbraith | 2014-01-18 04:25:14 [+0100]:
>> ># timers-do-not-raise-softirq-unconditionally.patch
>> ># rtmutex-use-a-trylock-for-waiter-lock-in-trylock.patch
>> >
>> >..those two out does seem to have stabilized the thing.
>>
>> timers-do-not-raise-softirq-unconditionally.patch is on its way out.
>>
>> rtmutex-use-a-trylock-for-waiter-lock-in-trylock.patch confues me.
>> Didn't you report once that your box deadlocks without this patch? Now
>> your 64way box on the other hand does not work with it?
>
>If 'do not raise' is applied, 'use a trylock' won't save you. If 'do
is this just an observation or you do know why it won't save me?
Currently I think to go back to the version where the waiter_lock was
taken with irqs off. However I would prefer to trigger this myself so I
would know what is going on instead blindly apply patches.
>-Mike
Sebastian
next prev parent reply other threads:[~2014-01-24 19:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-21 19:39 [PATCH] rcu: Eliminate softirq processing from rcutree Sebastian Andrzej Siewior
2013-12-22 3:07 ` Mike Galbraith
2013-12-22 8:57 ` Mike Galbraith
2013-12-23 4:38 ` Mike Galbraith
2013-12-23 5:12 ` Mike Galbraith
2014-01-24 19:46 ` Sebastian Andrzej Siewior
2014-01-25 5:20 ` Mike Galbraith
2013-12-24 19:36 ` Paul E. McKenney
2013-12-25 3:07 ` Mike Galbraith
2013-12-25 7:55 ` Paul E. McKenney
2013-12-25 17:37 ` Mike Galbraith
2014-01-17 17:14 ` Sebastian Andrzej Siewior
2014-01-18 3:25 ` Mike Galbraith
2014-01-24 19:50 ` Sebastian Andrzej Siewior [this message]
2014-01-25 5:12 ` Mike Galbraith
2014-01-27 5:10 ` Mike Galbraith
2014-01-27 16:54 ` Paul E. McKenney
2014-01-27 17:03 ` Mike Galbraith
2013-12-26 10:03 ` Mike Galbraith
2014-01-17 17:23 ` Sebastian Andrzej Siewior
2014-01-18 3:30 ` 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=20140124195014.GB29981@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=bitbucket@online.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.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).