From: Eric Dumazet <eric.dumazet@gmail.com>
To: john stultz <johnstul@us.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>, Avi Kivity <avi@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Richard Cochran <richard.cochran@omicron.at>,
ben@iagu.net, Oleg Nesterov <oleg@redhat.com>
Subject: Re: [PATCH] posix-timers: RCU conversion
Date: Mon, 04 Apr 2011 21:47:16 +0200 [thread overview]
Message-ID: <1301946437.3021.7.camel@edumazet-laptop> (raw)
In-Reply-To: <1301940501.2319.25.camel@work-vm>
Le lundi 04 avril 2011 à 11:08 -0700, john stultz a écrit :
> On Sun, 2011-04-03 at 18:54 +0200, Eric Dumazet wrote:
> > Andrew, I submitted this patch some time ago and got no feedback from
> > Thomas, John, Richard or Paul.
>
> Sorry about that. Its been on my list.
>
> It looks ok to me, but I not very familiar with idr locking rules
> (though looking at the code the comments state that idr_find can be
> safely called the way you do here).
Not only comments, but ipc uses rcu locking as well ;)
Nadia Derbey did the work on idr and ipc in commits :
983bfb7db303cfde56ae5bbf4e0f2f46e38c9576
(ipc: call idr_find() without locking in ipc_lock())
f9c46d6ea5ce138a886c3a0f10a46130afab75f5
(idr: make idr_find rcu-safe)
next prev parent reply other threads:[~2011-04-04 19:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTikZZ4MXZjx_+6u-vKVSgxULQo2BkQKRO6K_vzFy@mail.gmail.com>
[not found] ` <20110318123031.GB6066@8bytes.org>
[not found] ` <AANLkTin2k1ZSLa0NG6pKBvHYnKEV21t8pEqzeJWNn_rR@mail.gmail.com>
[not found] ` <4D871F6C.40207@redhat.com>
[not found] ` <AANLkTintxnKRQ4rD4Wo8_MHU4yJVzYaRhR=GjnDMGwNj@mail.gmail.com>
[not found] ` <AANLkTin8ZoUAVR2ajoV6cBFiUSe_Dof0_k60dcAGW3r-@mail.gmail.com>
[not found] ` <4D875842.9050308@redhat.com>
[not found] ` <AANLkTikWQS281kTtJ32-qo5U+w_BAak7qUwVhUQgOxxv@mail.gmail.com>
[not found] ` <4D8773AA.8030408@redhat.com>
[not found] ` <AANLkTin3Si1EAa=Va6f45vW-tYQ1Yk8dETXpHJHHHkxe@mail.gmail.com>
[not found] ` <1300726498.2884.493.camel@edumazet-laptop>
[not found] ` <4D8784A9.8040303@redhat.com>
[not found] ` <1300727545.2884.513.camel@edumazet-laptop>
[not found] ` <AANLkTinn7OKKKvBYe7KWsrReuYDdma5+8gHJHXdCacDY@mail.gmail.com>
2011-03-21 22:27 ` [RFC] " Eric Dumazet
2011-03-22 7:09 ` [PATCH] " Eric Dumazet
2011-03-22 8:59 ` Ben Nagy
2011-03-22 10:35 ` Avi Kivity
2011-04-04 3:30 ` Ben Nagy
2011-04-04 7:18 ` Avi Kivity
2011-04-05 7:49 ` Peter Zijlstra
2011-04-05 8:16 ` Avi Kivity
2011-04-05 8:48 ` Peter Zijlstra
2011-04-05 8:56 ` Avi Kivity
2011-04-05 9:03 ` Peter Zijlstra
2011-04-05 9:08 ` Avi Kivity
2011-04-05 9:50 ` Ben Nagy
2011-04-05 8:56 ` Mike Galbraith
2011-04-03 16:54 ` Eric Dumazet
2011-04-04 18:08 ` john stultz
2011-04-04 19:47 ` Eric Dumazet [this message]
2011-04-05 14:48 ` Oleg Nesterov
2011-04-05 15:18 ` [PATCH v2] " Eric Dumazet
2011-04-05 15:43 ` Oleg Nesterov
2011-05-16 15:10 ` Avi Kivity
2011-05-16 15:30 ` Eric Dumazet
2011-04-08 18:28 ` [PATCH] " Paul E. McKenney
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=1301946437.3021.7.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=avi@redhat.com \
--cc=ben@iagu.net \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=richard.cochran@omicron.at \
--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
all inboxes | Powered by JetHome®