Open MPI logo

Open MPI Development Mailing List Archives
  |   Home   |   Support   |   FAQ   |   all Development mailing list
 About
  Publications
  Open MPI Team
  FAQ
  Videos
 Open MPI Software
  Download
  Documentation
  Source Code Access
  Bug Tracking
  Regression Testing
  Version Information
 Sub-Projects
  Hardware Locality
  MPI Testing Tool
  Portable Linux Processor Affinity
  Open MPI User Docs
  Open Tool for Parameter Optimization
 Community
  Mailing Lists
    OMPI announce archives
    OMPI users archives
    OMPI devel archives
    OMPI docs archives
    hwloc announce archives
    hwloc users archives
    hwloc devel archives
    MTT announce archives
    MTT users archives
    MTT developers archives
    ORCM users archives
    ORCM devel archives
  Getting Help/Support
  Contribute
  Mirrors
  Contact
  License
 
Date view Thread view Subject view Author view

From: Brian Barrett (bbarrett_at_[hidden])
Date: 2007-07-14 13:27:34

On Jul 14, 2007, at 11:16 AM, George Bosilca wrote:

> Instead of failing at configure time, we might want to disable the
> threading features and the shared memory device if we detect that we
> don't have support for atomics on a specified platform. In a non
> threaded build, the shared memory device is the only place where we
> need support for memory barrier. I'll look in the code to see why we
> need support for compare-and-swap on a non threaded build.

George -

Disabling SM and threads if there's no atomic support would
definitely be one option. The compare-and-swap is used by the LIFO
used for ompi free lists.

Brian

Date view Thread view Subject view Author view
[Flag]
 Indiana University (Main Open MPI server)
This site is located in: Bloomington, IN, USA
Page last modified: 14-Jul-2007
©2004-2013 The Open MPI Project