From: Manfred Spraul <manfred@colorfullife.com>
To: paulmck@us.ibm.com
Cc: Manfred Spraul <manfred@dbl.q-ag.de>,
linux-kernel@vger.kernel.org, lse-tech@lists.sourceforge.net
Subject: Re: [Lse-tech] [RFC, PATCH] 5/5 rcu lock update: Hierarchical rcu_cpu_mask bitmap
Date: Wed, 21 Jul 2004 22:35:25 +0200 [thread overview]
Message-ID: <40FED38D.7050401@colorfullife.com> (raw)
In-Reply-To: <20040716233803.GA1293@us.ibm.com>
Paul E. McKenney wrote:
>I don't understand how the following helps, given that the CPU being
>offlined is supposed to be completely dead by the time we get here.
>Can't see anything that it really hurts other than a bit of delay in
>an extremely infrequent operation, but...
>
>
>
>>+ spin_unlock_wait(&rcu_state.mutex);
>> cpu_quiet(cpu, 1);
>>
>>
I was concerned about a race of cpu_quiet for the dead cpu (last cpu in
a group) with a concurrent cpu_quiet for another cpu in another cpu
group. A stale bit in either rcu_state.outstanding or
rcu_groups[].outstanding would lock up the rcu subsystem. I've thought
about it again and I agree with you - there is no race.
I agree with most of your other points - the patch is a proof of
concept, it definitively needs a big cleanup before is should be
considered for merging [+ a system that needs it]
--
Manfred
prev parent reply other threads:[~2004-07-21 20:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-25 5:35 [RFC, PATCH] 5/5 rcu lock update: Hierarchical rcu_cpu_mask bitmap Manfred Spraul
2004-07-16 23:38 ` [Lse-tech] " Paul E. McKenney
2004-07-21 20:35 ` Manfred Spraul [this message]
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=40FED38D.7050401@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=manfred@dbl.q-ag.de \
--cc=paulmck@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