From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: paulmck@linux.vnet.ibm.com, Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org, tony@bakeyournoodle.com,
paulus@samba.org, dino@in.ibm.com, tytso@us.ibm.com,
dvhltc@us.ibm.com, niv@us.ibm.com, antonb@us.ibm.com,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH, RFC] improved hacks to allow -rt to run kernbench on POWER
Date: Tue, 13 Nov 2007 22:09:02 +1100 [thread overview]
Message-ID: <1194952142.18185.104.camel@pasglop> (raw)
In-Reply-To: <1194948338.6983.20.camel@twins>
On Tue, 2007-11-13 at 11:05 +0100, Peter Zijlstra wrote:
> Looking at the code:
>
> /* radix tree not lockless safe ! we use a brlock-type mecanism
> * for now, until we can use a lockless radix tree
> */
> static void irq_radix_wrlock(unsigned long *flags)
>
> The RCU radix tree stuffs have gone upstream long ago.
>
> Anyway, it seems its the generic irq stuff that uses raw_spinlock_t
> and
> disables IRQs, so there isn't much we can do from the ARCH level I'm
> afraid :-(
>
> Ingo, any sane ideas?
As discussed on IRC< there are a couple of other related issues, though
part of them go away if I can get rid of the brlock I have in there
thanks to the new RCU based radix tree.
I'll give that some thoughts and come back to you tomorrow or thursday
hopefully with a patch.
Cheers,
Ben.
next prev parent reply other threads:[~2007-11-13 11:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 18:10 [PATCH, RFC] improved hacks to allow -rt to run kernbench on POWER Paul E. McKenney
2007-11-09 20:52 ` Benjamin Herrenschmidt
2007-11-09 22:07 ` Paul E. McKenney
2007-11-11 3:59 ` Benjamin Herrenschmidt
2007-11-11 14:45 ` Steven Rostedt
2007-11-11 20:48 ` Benjamin Herrenschmidt
2007-11-12 17:05 ` Paul E. McKenney
2007-11-12 19:15 ` Paul E. McKenney
2007-11-12 21:12 ` Benjamin Herrenschmidt
2007-11-13 9:10 ` Peter Zijlstra
2007-11-13 9:43 ` Benjamin Herrenschmidt
2007-11-13 10:05 ` Peter Zijlstra
2007-11-13 10:59 ` Peter Zijlstra
2007-11-13 11:09 ` Benjamin Herrenschmidt [this message]
2007-11-10 1:18 ` Nick Piggin
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=1194952142.18185.104.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=antonb@us.ibm.com \
--cc=dino@in.ibm.com \
--cc=dvhltc@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=niv@us.ibm.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tony@bakeyournoodle.com \
--cc=tytso@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.