[mvapich-discuss] Odd behavior with memory registration / dreg / MVAPICH and MVAPICH2

[Eric A. Borisch]

I plan to move over and will as soon as the vendor we share an
interface with (also via Infiniband, but not MPI) moves over. (Out of
the scope of this discussion. :)

For now, it sounds like I'll be turning off this (LAZY_MEM_UNREGISTER)
option in the vapi code and running in that fashion.

Thanks for the help,
 Eric

On Jan 4, 2008 4:48 PM, Jeff Squyres <jsquyres at cisco.com> wrote:
> On Jan 4, 2008, at 5:27 PM, Matthew Koop wrote:
>
> > The problem is not an inherent issue with VAPI. Similar support
> > could be
> > ported to the VAPI device as well. Thus far, we have been including
> > new
> > features in the OpenFabrics/Gen2 device as vendors have mostly moved
> > support to Gen2.
>
> I'll second this: Cisco is doing all of its new HPC IB development
> with the OpenFabrics stack (and has been over over a year).  Open MPI
> has dropped VAPI support in its upcoming v1.3 release.
>
> We encourage all of our HPC customers to upgrade from VAPI-based
> stacks to OFED if possible.
>
> --
> Jeff Squyres
> Cisco Systems
>
>



-- 
Eric A. Borisch
eborisch at ieee.org