Structured Deferral: Synchronization via Procrastination.

The article discusses synchronization via procrastination as a structured deferral in software design. Topics covered include lazy approaches like reference counting, garbage collection and lazy evaluation, the significant time needed to detect hardware failure, and the usefulness of synchronization...

Full description

Bibliographic Details
Published in:Communications of the ACM Vol. 56; no. 7; pp. 40 - 50
Main Author: MCKENNEY, PAUL E.
Format: Article
Published: Association for Computing Machinery Jul2013
Subjects:
Online Access:View this record in EBSCOhost
fields @attributes:
  recordID: 1
pdfLink:
plink: https://search.ebscohost.com/login.aspx?direct=true&db=hlh&AN=90078933&site=ehost-live
header:
  @attributes:
    shortDbName: hlh
    uiTerm: 90078933
    longDbName: Humanities International Complete
    uiTag: AN
  controlInfo:
    bkinfo:
    jinfo:
      jid:
        00010782
        ACM
      jtl: Communications of the ACM
      issn: 00010782
      maglogo: N
    pubinfo:
      dt: Jul2013
      vid: 56
      iid: 7
      pid: 68
      pub: Association for Computing Machinery
    artinfo:
      ui:
        90078933
        10.1145/2483852.2483867
      ppf: 40
      ppct: 10
      formats:
      tig:
        atl: Structured Deferral: Synchronization via Procrastination.
      aug:
        au: MCKENNEY, PAUL E.
        affil: Distinguished Engineer, IBM's Linux Technology Center
      su:
        Synchronization
        Software architecture
        Time measurements
        Computer software
        Computer software development
        Computer memory management
      sug:
        subj:
          Synchronization
          Software architecture
          Time measurements
          Computer software
          Computer software development
          Computer memory management
      ab: The article discusses synchronization via procrastination as a structured deferral in software design. Topics covered include lazy approaches like reference counting, garbage collection and lazy evaluation, the significant time needed to detect hardware failure, and the usefulness of synchronization via procrastination when interacting with external state. Also mentioned are the key insight behind hazard pointers, the shortcomings inherent in the strengths of hazard pointers, and the read-side disagreements on current state.
      pubtype: Periodical
      doctype: Article
      src: R
    language: English
    refInfo:
    copyright:
      @attributes:
        flag: Y
      dt:
        @attributes:
          year: 2013
    holdings:
      @attributes:
        islocal: N