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 criti
On Tue, 01/13 18:52, Paolo Bonzini wrote:
> This includes a (mangled) copy of the liburcu code. The main changes
> are: 1) removing dependencies on many other header files in liburcu; 2)
> removing for simplicity the tentative busy waiting in synchronize_rcu,
> which has limited performance effect
This includes a (mangled) copy of the liburcu code. The main changes
are: 1) removing dependencies on many other header files in liburcu; 2)
removing for simplicity the tentative busy waiting in synchronize_rcu,
which has limited performance effects; 3) replacing futexes in
synchronize_rcu with Qe
