From: Paolo Bonzini <pbonzini@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH 2/8] rcu: add rcu library
Date: Thu, 15 Jan 2015 12:08:49 +0100 [thread overview]
Message-ID: <54B79FC1.6040904@redhat.com> (raw)
In-Reply-To: <20150115103948.GA1587@ad.nay.redhat.com>
On 15/01/2015 11:39, Fam Zheng wrote:
>> +How is this possible? The basic idea is to split updates in two phases,
>> +"removal" and "reclamation". During removal, we ensure that subsequent
>> +readers will not be able to get a reference to the old data. After
>> +removal has completed, a critical section will not be able to access
>> +the old data. Therefore, critical sections that begin after removal
>> +do not matter; as soon as all previous critical sections have finished,
>> +there cannot be any readers who hold references to the data structure,
>> +which may not be safely reclaimed (e.g., freed or unref'ed).
>
> s/not/now/ ?
Both are correct depending on how you read the sentence, but it is
ambiguous. The idea was that "because of readers holding references,
the data structures cannot be safely reclaimed".
I will change the last line to "and these can now be safely reclaimed".
The "and" puts the sentence in relationship with "as soon as all
previous critical sections have finished", and "now" becomes
unambiguously correct.
>> +/*
>> + * Global grace period counter. Bit 0 is always one in rcu_gp_ctr.
>> + * Bits 1 and above are defined in synchronize_rcu/update_counter_and_wait.
>
> What is update_counter_and_wait?
It's part of URCU and is now merged into synchronize_rcu. I'll fix the
comment.
Paolo
next prev parent reply other threads:[~2015-01-15 11:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 17:52 [Qemu-devel] [PATCH 0/8] RCUification of the memory API, part 1 Paolo Bonzini
2015-01-13 17:52 ` [Qemu-devel] [PATCH 1/8] tls: require compiler support for __thread Paolo Bonzini
2015-01-13 18:40 ` Peter Maydell
2015-01-13 19:48 ` Paolo Bonzini
2015-01-13 20:00 ` Peter Maydell
2015-01-13 20:27 ` Paolo Bonzini
2015-01-13 22:07 ` Peter Maydell
2015-04-28 21:04 ` Emilio G. Cota
2015-04-29 11:09 ` Paolo Bonzini
2015-01-13 17:52 ` [Qemu-devel] [PATCH 2/8] rcu: add rcu library Paolo Bonzini
2015-01-15 10:39 ` Fam Zheng
2015-01-15 11:08 ` Paolo Bonzini [this message]
2015-01-13 17:52 ` [Qemu-devel] [PATCH 3/8] rcu: add rcutorture Paolo Bonzini
2015-01-16 2:04 ` Fam Zheng
2015-01-16 11:22 ` Paolo Bonzini
2015-01-13 17:52 ` [Qemu-devel] [PATCH 4/8] rcu: allow nesting of rcu_read_lock/rcu_read_unlock Paolo Bonzini
2015-01-13 17:52 ` [Qemu-devel] [PATCH 5/8] rcu: add call_rcu Paolo Bonzini
2015-01-13 17:52 ` [Qemu-devel] [PATCH 6/8] memory: remove assertion on memory_region_destroy Paolo Bonzini
2015-01-13 17:52 ` [Qemu-devel] [PATCH 7/8] memory: protect current_map by RCU Paolo Bonzini
2015-01-13 17:52 ` [Qemu-devel] [PATCH 8/8] memory: avoid ref/unref in memory_region_find Paolo Bonzini
2015-01-16 13:04 ` [Qemu-devel] [PATCH 0/8] RCUification of the memory API, part 1 Christian Borntraeger
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=54B79FC1.6040904@redhat.com \
--to=pbonzini@redhat.com \
--cc=famz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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.