From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Sebastien Dugue <sebastien.dugue@bull.net>,
Nick Piggin <nickpiggin@yahoo.com.au>,
Linux-rt <linux-rt-users@vger.kernel.org>,
linux-ppc <linuxppc-dev@ozlabs.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <michael@ellerman.id.au>,
Tim Chavez <tinytim@us.ibm.com>,
Jean Pierre Dion <jean-pierre.dion@bull.net>,
Gilles Carry <Gilles.Carry@ext.bull.net>
Subject: Re: [PATCH 2/2][RT] powerpc - Make the irq reverse mapping radix tree lockless
Date: Fri, 25 Jul 2008 18:27:20 +1000 [thread overview]
Message-ID: <1216974440.11188.100.camel@pasglop> (raw)
In-Reply-To: <1216972177.7257.351.camel@twins>
On Fri, 2008-07-25 at 09:49 +0200, Peter Zijlstra wrote:
>
>
> The only advantage of the concurrent radix tree over this model is that
> it can potentially do multiple modification operations at the same time.
Yup, we do not need that for the irq revmap... concurrent lookup is all we need.
Cheers,
Ben.
next prev parent reply other threads:[~2008-07-25 8:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-24 10:23 [PATCH 0/2][RT] powerpc - fix bug in irq reverse mapping radix tree (Resend) Sebastien Dugue
2008-07-24 10:48 ` [PATCH 1/2][RT] powerpc - XICS: move the call to irq_radix_revmap from xics_startup to xics_host_map Sebastien Dugue
2008-07-24 10:50 ` [PATCH 2/2][RT] powerpc - Make the irq reverse mapping radix tree lockless Sebastien Dugue
2008-07-24 11:11 ` Nick Piggin
2008-07-24 12:18 ` Sebastien Dugue
2008-07-25 7:49 ` Peter Zijlstra
2008-07-25 8:27 ` Benjamin Herrenschmidt [this message]
2008-07-25 8:36 ` Sebastien Dugue
2008-07-25 8:40 ` Benjamin Herrenschmidt
2008-07-25 8:47 ` Sebastien Dugue
2008-07-25 8:34 ` Sebastien Dugue
2008-07-25 5:13 ` Benjamin Herrenschmidt
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=1216974440.11188.100.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=Gilles.Carry@ext.bull.net \
--cc=jean-pierre.dion@bull.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
--cc=nickpiggin@yahoo.com.au \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=sebastien.dugue@bull.net \
--cc=tinytim@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox