Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Development mailing list

Subject: Re: [OMPI devel] RFC: CUDA register sm and openib host memory
From: Rolf vandeVaart (rvandevaart_at_[hidden])
Date: 2011-08-02 10:39:42

Yes, here it is attached.



From: devel-bounces_at_[hidden] [mailto:devel-bounces_at_[hidden]] On Behalf Of Jeff Squyres (jsquyres)
Sent: Tuesday, August 02, 2011 10:33 AM
To: Open MPI Developers
Cc: Open MPI Developers
Subject: Re: [OMPI devel] RFC: CUDA register sm and openib host memory

Rolf -

Can you send a cumulative SVN diff against the SVN HEAD?

Sent from my phone. No type good.

On Jul 28, 2011, at 5:52 PM, "Rolf vandeVaart" <rvandevaart_at_[hidden]<mailto:rvandevaart_at_[hidden]>> wrote:
WHAT: Add CUDA registration of host memory in sm and openib BTLs.

TIMEOUT: 8/4/2011

DETAILS: In order to improve performance of sending GPU device memory,
we need to register the host memory with the CUDA framework. These
changes allow that to happen. These changes are somewhat different
from what I proposed a while ago and I think a lot cleaner. There is
a new memory pool flag that indicates whether a piece of memory
should be registered. This allows us to register the sm memory and
the pre-posted openib memory.

The CUDA specific code is in the ompi/mca/common/cuda directory.

Do not look at the configure.m4 code, as that is still not done.

Here a link to the proposed changes:

Here is a list of files that would change.
M ompi/mca/btl/openib/btl_openib_component.c
M ompi/mca/btl/openib/
M ompi/mca/mpool/sm/
M ompi/mca/mpool/sm/mpool_sm_module.c
M ompi/mca/mpool/mpool.h
M ompi/mca/pml/ob1/pml_ob1_sendreq.h
A ompi/mca/common/cuda
A ompi/mca/common/cuda/configure.m4
A ompi/mca/common/cuda/common_cuda.c
A ompi/mca/common/cuda/help-mpi-common-cuda.txt
A ompi/mca/common/cuda/
A ompi/mca/common/cuda/common_cuda.h
M ompi/class/ompi_free_list.c

This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
devel mailing list