Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-104

memory barrier after reading page's write generation

    • Type: Icon: Task Task
    • Resolution: Done
    • WT1.0
    • Affects Version/s: None
    • Component/s: None

      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

            Assignee:
            keith.bostic@mongodb.com Keith Bostic (Inactive)
            Reporter:
            wiredtiger WiredTiger
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: