Re: [ovs-dev] [PATCH v2] rculist: Remove postponed poisoning.

> On Jun 11, 2015, at 5:01 PM, Alex Wang wrote: > > Looks good to me, thx for adding these comments~! > Thanks for the hard work and the review, Alex! Pushed to master, Jarno > On Thu, Jun 11, 2015 at 4:49 PM, Jarno Rajahalme > wrote: > I sent a v3 that comp

Re: [ovs-dev] [PATCH v2] rculist: Remove postponed poisoning.

Looks good to me, thx for adding these comments~! On Thu, Jun 11, 2015 at 4:49 PM, Jarno Rajahalme wrote: > I sent a v3 that compiles also on clang. > > Jarno > > > On Jun 11, 2015, at 11:06 AM, Jarno Rajahalme > wrote: > > > > Postponed 'next' member poisoning was based on the faulty assumpt

Re: [ovs-dev] [PATCH v2] rculist: Remove postponed poisoning.

I sent a v3 that compiles also on clang. Jarno > On Jun 11, 2015, at 11:06 AM, Jarno Rajahalme wrote: > > Postponed 'next' member poisoning was based on the faulty assumption > that postponed functions would be called in the order they were > postponed. This assumption holds only for the fun

[ovs-dev] [PATCH v2] rculist: Remove postponed poisoning.

Postponed 'next' member poisoning was based on the faulty assumption that postponed functions would be called in the order they were postponed. This assumption holds only for the functions postponed by any single thread. When functions are postponed by different threads, there are no guarantees o