Re: [OMPI devel] [devel-core] Collective Communications Optimization - MeetingScheduled in Albuquerque!

Hotels near the airport / university area, I pulled this off of this site: http://www.airnav.com/airport/KABQ Miles Price ($) FAIRFIELD INN BY MARRIOTT ALBUQUERQUE UNIVERSITY AREA 4.8 79-80 COMFORT INN AIRPORT 1.3 52-101 COURTYARD BY MARRIOTT ALBUQUERQUE AIRPORT 1.6 74-139 SLEEP INN

Re: [OMPI devel] ticket 1023

Hi Ralph, My answer has 2 parts: 1. I'm not familiar with bproc but I assume that when working with bproc there is a component that reads the RMAPS information somehow and launches the local process. In that case you can add the affinity there according the slot_list (new member in the map) from

Re: [OMPI devel] Bproc support

Do you feel like updating http://www.open-mpi.org/faq/?category=bproc ? :D On Jul 10, 2007, at 10:17 AM, Ralph H Castain wrote: Yo all I have upgraded the support for Bproc on the Open MPI trunk as of r15328. We now support Bproc environments that do not utilize resource managers - in

Re: [OMPI devel] Multi-environment builds

Point taken. Is this an accurate summary? 1. "Best practices" should be documented, to include sysadmins specifically itemizing what components should be used on their systems (e.g., in an environment variable or the system-wide MCA parameters file). 2. It may be useful to have some

Re: [OMPI devel] Multi-environment builds

On Jul 10, 2007, at 9:51 AM, Brian Barrett wrote: Actually, there are --with-slurm/--without-slurm options. We default to building slurm support automatically on linux and aix, but not on other platforms. On a mostly unrelated note... We should probably also now build the SLURM component for

Re: [OMPI devel] ticket 1023

On Jul 10, 2007, at 11:18 AM, Sharon Melamed wrote: The responsibility for mapping rank to processor is in the ODLS component. I didn't touch the orted code. If you doesn't use orted - you steel use the ODLS component (like ODLS bproc). Any way you mast have a component in the end machine that

Re: [OMPI devel] ticket 1023

Ah, I see the problem. I think you have misunderstood the ODLS framework. The ODLS is the "Orte Daemon Launch Subsystem" and is used by the orted to launch the local procs. Mpirun also accesses the ODLS, but only to construct the add_procs message that gets sent to the daemons. The problem is,

Re: [OMPI devel] Multi-environment builds

On Jul 10, 2007, at 7:09 AM, Tim Prins wrote: Jeff Squyres wrote: 2. The "--enable-mca-no-build" option takes a comma-delimited list of components that will then not be built. Granted, this option isn't exactly intuitive, but it was the best that we could think of at the time to present a

Re: [OMPI devel] ticket 1023

As I understood our original discussions, this would move responsibility for mapping rank to processor back into the orted - is that still true? Reason I ask is to again clarify for people if we are doing so as it (a) impacts those systems that don't use our orteds (e.g., will affinity still work

[OMPI devel] ticket 1023

Hello All, In the recent few weeks I implemented ticket 1023 (https://svn.open-mpi.org/trac/ompi/ticket/1023 ). In a few words, the purpose of ticket 1023 is to expand the hostfile syntax to precisely specify slot location (in terms of virtual

Re: [OMPI devel] Multi-environment builds

Jeff Squyres wrote: 2. The "--enable-mca-no-build" option takes a comma-delimited list of components that will then not be built. Granted, this option isn't exactly intuitive, but it was the best that we could think of at the time to present a general solution for inhibiting the build of a

Re: [OMPI devel] Multi-environment builds

Actually, I was talking specifically about configuration at build time. I realize there are trade-offs here, and suspect we can find a common ground. The problem with using the options Jeff described is that they require knowledge on the part of the builder as to what environments have had their

Re: [OMPI devel] Multi-environment builds

On Jul 10, 2007, at 6:07 AM, Bogdan Costescu wrote: For example, I can readily find machines that are running TM, but also have LSF and SLURM libraries installed (although those environments are not "active" - the libraries in some cases are old and stale, usually present because either someone

Re: [OMPI devel] Multi-environment builds

* Jeff Squyres wrote on Tue, Jul 10, 2007 at 01:28:40PM CEST: > On Jul 10, 2007, at 2:42 AM, Ralf Wildenhues wrote: > > >> 1. The most obvious one (to me, at least) is to require that > >> people provide > >> "--with-xx" when they build the system. > > > > I'll throw in another one for good

Re: [OMPI devel] Multi-environment builds

On Jul 10, 2007, at 2:42 AM, Ralf Wildenhues wrote: 1. The most obvious one (to me, at least) is to require that people provide "--with-xx" when they build the system. I'll throw in another one for good measure: If --with-xx is given, build with the component. If --without-xx is given,

Re: [OMPI devel] Multi-environment builds

On Mon, 9 Jul 2007, Ralph Castain wrote: For example, I can readily find machines that are running TM, but also have LSF and SLURM libraries installed (although those environments are not "active" - the libraries in some cases are old and stale, usually present because either someone wanted

Re: [OMPI devel] Multi-environment builds

Hello Ralph, * Ralph Castain wrote on Tue, Jul 10, 2007 at 03:51:06AM CEST: > > The problem is that our Open MPI build system automatically detects the > presence of those libraries, builds the corresponding components, and then > links those libraries into our system. Unfortunately, this causes