| Remember that the point of IB and other operating-system bypass devices is that the driver is not involved in the fast path of sending / | receiving. One of the side-effects of that design point is that userspace does all the allocation of send / receive buffers.
That's a good point. It was not clear to me who and with what logic was allocating memory. But definitely for IB it makes sense that the user provides pointers to their memory. thanks Michael On Mon, Jul 8, 2013 at 1:07 PM, Jeff Squyres (jsquyres) <jsquy...@cisco.com>wrote: > On Jul 8, 2013, at 2:01 PM, Brice Goglin <brice.gog...@inria.fr> wrote: > > > The driver doesn't allocate much memory here. Maybe some small control > buffers, but nothing significantly involved in large message transfer > performance. Everything critical here is allocated by user-space (either > MPI lib or application), so we just have to make sure we bind the process > memory properly. I used hwloc-bind to do that. > > +1 > > Remember that the point of IB and other operating-system bypass devices is > that the driver is not involved in the fast path of sending / receiving. > One of the side-effects of that design point is that userspace does all > the allocation of send / receive buffers. > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > > _______________________________________________ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users >