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

Subject: Re: [OMPI devel] RFC: sm Latency
From: Eugene Loh (Eugene.Loh_at_[hidden])
Date: 2009-01-21 20:00:37

Ron Brightwell wrote: 
If you poll only the queue that correspond to a posted receive, you only optimize micro-benchmarks, until they start using ANY_SOURCE.
    
Note that the HPCC RandomAccess benchmark only uses MPI_ANY_SOURCE (and
MPI_ANY_TAG).
But HPCC RandomAccess also just uses non-blocking receives.  So, it's kind of outside the scope of the original ideas here (bypassing the PML receive-request data structure).

It's possibly not even a poster child for the single-queue idea either.  Single queue probably shines best when you have to poll all connections for a few messages.  In contrast, RandomAccess (I think) loads all connections up randomly (pseudo-evenly).
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: 22-Jan-2009
©2004-2013 The Open MPI Project