wiredtiger/wiredtiger.github.com — Issue #103: memory barrier after reading page's write generation
Author: wiredtiger
Created: 2012-01-31 17:32:30+00:00
State: open

It occurred to me -- in the page-search code, we copy the page's write generation, then search the page.

It occurs to me we should probably have a memory barrier instruction after we copy the write generation, otherwise the compiler might re-order that read after we've actually searched the page? (Or make page->write_gen volatile?)

--keith