Thinking about this adventurous locking some more: I think you are misunderstanding what a seqlock is. It is *not* a spinlock.
The critical read section with the reading of a version before and after allows you access to a certain version of memory how it is or was some time ago (caching effect). It does not mean that the current state of memory is fixed and neither does it allow syncing when an item is added to the list. So it could be that you are traversing a list that is missing one item because it is not visible to this processor yet. You may just see a state from the past. I would think that you will need a real lock in order to get the desired effect. ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
