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

memory barrier after reading page's write generation

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Resolution: Done
    • None
    • WT1.0
    • None

    Description

      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

      Attachments

        Issue Links

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: