Re: [PATCH v5 05/10] seqlock: Better document raw_write_seqcount_latch()

[Peter Zijlstra]

On Mon, Apr 13, 2015 at 06:32:02PM +0200, Ingo Molnar wrote:
> 
> Btw., I realize this is just a sample, but couldn't this be written 
> more optimally as:
> 
> 	do {
> 		seq = READ_ONCE(latch->seq);
> 		smp_read_barrier_depends();
> 
> 		idx = seq & 0x01;
> 		entry = data_query(latch->data[idx], ...);
> 
> 		smp_rmb();
> 	} while (seq != latch->seq);
> 

So in the actual code we use raw_read_seqcount() which includes the rmb.

This is true for the existing __ktime_get_fast_ns() as we as the new
latch_tee_find().

Should we look at introducing yet another seq primitive?

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/