2006-07-18 02:08:55 +04:00
|
|
|
/*
|
|
|
|
* Copyright (c) 2004-2005 The Trustees of Indiana University.
|
|
|
|
* All rights reserved.
|
|
|
|
* Copyright (c) 2004-2005 The Trustees of the University of Tennessee.
|
|
|
|
* All rights reserved.
|
|
|
|
* Copyright (c) 2004-2005 High Performance Computing Center Stuttgart,
|
|
|
|
* University of Stuttgart. All rights reserved.
|
|
|
|
* Copyright (c) 2004-2005 The Regents of the University of California.
|
|
|
|
* All rights reserved.
|
2007-05-24 19:41:24 +04:00
|
|
|
* Copyright (c) 2007 Los Alamos National Security, LLC. All rights
|
|
|
|
* reserved.
|
2010-07-20 22:45:48 +04:00
|
|
|
* Copyright (c) 2010 Cisco Systems, Inc. All rights reserved.
|
2006-07-18 02:08:55 +04:00
|
|
|
* $COPYRIGHT$
|
|
|
|
*
|
|
|
|
* Additional copyrights may follow
|
|
|
|
*
|
|
|
|
* $HEADER$
|
|
|
|
*/
|
|
|
|
|
2006-08-03 04:10:19 +04:00
|
|
|
#ifndef OMPI_OSC_RDMA_REPLYREQ_H
|
|
|
|
#define OMPI_OSC_RDMA_REPLYREQ_H
|
2006-07-18 02:08:55 +04:00
|
|
|
|
|
|
|
#include "osc_rdma.h"
|
|
|
|
#include "osc_rdma_longreq.h"
|
|
|
|
|
|
|
|
#include "opal/class/opal_list.h"
|
- Split the datatype engine into two parts: an MPI specific part in
OMPI
and a language agnostic part in OPAL. The convertor is completely
moved into OPAL. This offers several benefits as described in RFC
http://www.open-mpi.org/community/lists/devel/2009/07/6387.php
namely:
- Fewer basic types (int* and float* types, boolean and wchar
- Fixing naming scheme to ompi-nomenclature.
- Usability outside of the ompi-layer.
- Due to the fixed nature of simple opal types, their information is
completely
known at compile time and therefore constified
- With fewer datatypes (22), the actual sizes of bit-field types may be
reduced
from 64 to 32 bits, allowing reorganizing the opal_datatype
structure, eliminating holes and keeping data required in convertor
(upon send/recv) in one cacheline...
This has implications to the convertor-datastructure and other parts
of the code.
- Several performance tests have been run, the netpipe latency does not
change with
this patch on Linux/x86-64 on the smoky cluster.
- Extensive tests have been done to verify correctness (no new
regressions) using:
1. mpi_test_suite on linux/x86-64 using clean ompi-trunk and
ompi-ddt:
a. running both trunk and ompi-ddt resulted in no differences
(except for MPI_SHORT_INT and MPI_TYPE_MIX_LB_UB do now run
correctly).
b. with --enable-memchecker and running under valgrind (one buglet
when run with static found in test-suite, commited)
2. ibm testsuite on linux/x86-64 using clean ompi-trunk and ompi-ddt:
all passed (except for the dynamic/ tests failed!! as trunk/MTT)
3. compilation and usage of HDF5 tests on Jaguar using PGI and
PathScale compilers.
4. compilation and usage on Scicortex.
- Please note, that for the heterogeneous case, (-m32 compiled
binaries/ompi), neither
ompi-trunk, nor ompi-ddt branch would successfully launch.
This commit was SVN r21641.
2009-07-13 08:56:31 +04:00
|
|
|
#include "ompi/datatype/ompi_datatype.h"
|
|
|
|
#include "opal/datatype/opal_convertor.h"
|
2006-07-18 02:08:55 +04:00
|
|
|
#include "ompi/communicator/communicator.h"
|
|
|
|
#include "ompi/proc/proc.h"
|
2008-04-16 17:29:55 +04:00
|
|
|
#include "ompi/memchecker.h"
|
2006-07-18 02:08:55 +04:00
|
|
|
|
|
|
|
|
|
|
|
struct ompi_osc_rdma_replyreq_t {
|
|
|
|
opal_list_item_t super;
|
|
|
|
|
|
|
|
/** pointer to the module that created the replyreq */
|
|
|
|
ompi_osc_rdma_module_t *rep_module;
|
|
|
|
|
|
|
|
/** Datatype for the target side of the operation */
|
|
|
|
struct ompi_datatype_t *rep_target_datatype;
|
|
|
|
/** Convertor for the target. Always setup for send. */
|
- Split the datatype engine into two parts: an MPI specific part in
OMPI
and a language agnostic part in OPAL. The convertor is completely
moved into OPAL. This offers several benefits as described in RFC
http://www.open-mpi.org/community/lists/devel/2009/07/6387.php
namely:
- Fewer basic types (int* and float* types, boolean and wchar
- Fixing naming scheme to ompi-nomenclature.
- Usability outside of the ompi-layer.
- Due to the fixed nature of simple opal types, their information is
completely
known at compile time and therefore constified
- With fewer datatypes (22), the actual sizes of bit-field types may be
reduced
from 64 to 32 bits, allowing reorganizing the opal_datatype
structure, eliminating holes and keeping data required in convertor
(upon send/recv) in one cacheline...
This has implications to the convertor-datastructure and other parts
of the code.
- Several performance tests have been run, the netpipe latency does not
change with
this patch on Linux/x86-64 on the smoky cluster.
- Extensive tests have been done to verify correctness (no new
regressions) using:
1. mpi_test_suite on linux/x86-64 using clean ompi-trunk and
ompi-ddt:
a. running both trunk and ompi-ddt resulted in no differences
(except for MPI_SHORT_INT and MPI_TYPE_MIX_LB_UB do now run
correctly).
b. with --enable-memchecker and running under valgrind (one buglet
when run with static found in test-suite, commited)
2. ibm testsuite on linux/x86-64 using clean ompi-trunk and ompi-ddt:
all passed (except for the dynamic/ tests failed!! as trunk/MTT)
3. compilation and usage of HDF5 tests on Jaguar using PGI and
PathScale compilers.
4. compilation and usage on Scicortex.
- Please note, that for the heterogeneous case, (-m32 compiled
binaries/ompi), neither
ompi-trunk, nor ompi-ddt branch would successfully launch.
This commit was SVN r21641.
2009-07-13 08:56:31 +04:00
|
|
|
opal_convertor_t rep_target_convertor;
|
2006-07-18 02:08:55 +04:00
|
|
|
/** packed size of message on the target side */
|
|
|
|
size_t rep_target_bytes_packed;
|
|
|
|
|
|
|
|
/** rank in module's communicator for origin of operation */
|
|
|
|
int rep_origin_rank;
|
|
|
|
/** pointer to the proc structure for the origin of the operation */
|
|
|
|
ompi_proc_t *rep_origin_proc;
|
|
|
|
|
|
|
|
ompi_ptr_t rep_origin_sendreq;
|
|
|
|
};
|
|
|
|
typedef struct ompi_osc_rdma_replyreq_t ompi_osc_rdma_replyreq_t;
|
|
|
|
OBJ_CLASS_DECLARATION(ompi_osc_rdma_replyreq_t);
|
|
|
|
|
|
|
|
|
|
|
|
/** allocate and populate a replyreq structure. datatype is
|
|
|
|
RETAINed for the life of the replyreq */
|
|
|
|
int
|
|
|
|
ompi_osc_rdma_replyreq_alloc_init(ompi_osc_rdma_module_t *module,
|
|
|
|
int origin,
|
|
|
|
ompi_ptr_t origin_request,
|
2010-07-20 22:45:48 +04:00
|
|
|
OPAL_PTRDIFF_TYPE target_displacement,
|
2006-07-18 02:08:55 +04:00
|
|
|
int target_count,
|
|
|
|
struct ompi_datatype_t *datatype,
|
|
|
|
ompi_osc_rdma_replyreq_t **replyreq);
|
|
|
|
|
|
|
|
|
|
|
|
static inline int
|
|
|
|
ompi_osc_rdma_replyreq_alloc(ompi_osc_rdma_module_t *module,
|
|
|
|
int origin_rank,
|
|
|
|
ompi_osc_rdma_replyreq_t **replyreq)
|
|
|
|
{
|
|
|
|
int ret;
|
|
|
|
opal_free_list_item_t *item;
|
2007-05-24 19:41:24 +04:00
|
|
|
ompi_proc_t *proc = ompi_comm_peer_lookup( module->m_comm, origin_rank );
|
2006-07-18 02:08:55 +04:00
|
|
|
|
|
|
|
/* BWB - FIX ME - is this really the right return code? */
|
|
|
|
if (NULL == proc) return OMPI_ERR_OUT_OF_RESOURCE;
|
|
|
|
|
2007-05-24 19:41:24 +04:00
|
|
|
OPAL_FREE_LIST_GET(&mca_osc_rdma_component.c_replyreqs,
|
2006-07-18 02:08:55 +04:00
|
|
|
item, ret);
|
|
|
|
if (OMPI_SUCCESS != ret) return ret;
|
|
|
|
*replyreq = (ompi_osc_rdma_replyreq_t*) item;
|
|
|
|
|
|
|
|
(*replyreq)->rep_module = module;
|
|
|
|
(*replyreq)->rep_origin_rank = origin_rank;
|
|
|
|
(*replyreq)->rep_origin_proc = proc;
|
|
|
|
|
|
|
|
return OMPI_SUCCESS;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
static inline int
|
|
|
|
ompi_osc_rdma_replyreq_init_target(ompi_osc_rdma_replyreq_t *replyreq,
|
|
|
|
void *target_addr,
|
|
|
|
int target_count,
|
|
|
|
struct ompi_datatype_t *target_dt)
|
|
|
|
{
|
|
|
|
OBJ_RETAIN(target_dt);
|
|
|
|
replyreq->rep_target_datatype = target_dt;
|
|
|
|
|
- Split the datatype engine into two parts: an MPI specific part in
OMPI
and a language agnostic part in OPAL. The convertor is completely
moved into OPAL. This offers several benefits as described in RFC
http://www.open-mpi.org/community/lists/devel/2009/07/6387.php
namely:
- Fewer basic types (int* and float* types, boolean and wchar
- Fixing naming scheme to ompi-nomenclature.
- Usability outside of the ompi-layer.
- Due to the fixed nature of simple opal types, their information is
completely
known at compile time and therefore constified
- With fewer datatypes (22), the actual sizes of bit-field types may be
reduced
from 64 to 32 bits, allowing reorganizing the opal_datatype
structure, eliminating holes and keeping data required in convertor
(upon send/recv) in one cacheline...
This has implications to the convertor-datastructure and other parts
of the code.
- Several performance tests have been run, the netpipe latency does not
change with
this patch on Linux/x86-64 on the smoky cluster.
- Extensive tests have been done to verify correctness (no new
regressions) using:
1. mpi_test_suite on linux/x86-64 using clean ompi-trunk and
ompi-ddt:
a. running both trunk and ompi-ddt resulted in no differences
(except for MPI_SHORT_INT and MPI_TYPE_MIX_LB_UB do now run
correctly).
b. with --enable-memchecker and running under valgrind (one buglet
when run with static found in test-suite, commited)
2. ibm testsuite on linux/x86-64 using clean ompi-trunk and ompi-ddt:
all passed (except for the dynamic/ tests failed!! as trunk/MTT)
3. compilation and usage of HDF5 tests on Jaguar using PGI and
PathScale compilers.
4. compilation and usage on Scicortex.
- Please note, that for the heterogeneous case, (-m32 compiled
binaries/ompi), neither
ompi-trunk, nor ompi-ddt branch would successfully launch.
This commit was SVN r21641.
2009-07-13 08:56:31 +04:00
|
|
|
opal_convertor_copy_and_prepare_for_send(replyreq->rep_origin_proc->proc_convertor,
|
|
|
|
&(target_dt->super),
|
2006-07-18 02:08:55 +04:00
|
|
|
target_count,
|
|
|
|
target_addr,
|
|
|
|
0,
|
|
|
|
&(replyreq->rep_target_convertor));
|
- Split the datatype engine into two parts: an MPI specific part in
OMPI
and a language agnostic part in OPAL. The convertor is completely
moved into OPAL. This offers several benefits as described in RFC
http://www.open-mpi.org/community/lists/devel/2009/07/6387.php
namely:
- Fewer basic types (int* and float* types, boolean and wchar
- Fixing naming scheme to ompi-nomenclature.
- Usability outside of the ompi-layer.
- Due to the fixed nature of simple opal types, their information is
completely
known at compile time and therefore constified
- With fewer datatypes (22), the actual sizes of bit-field types may be
reduced
from 64 to 32 bits, allowing reorganizing the opal_datatype
structure, eliminating holes and keeping data required in convertor
(upon send/recv) in one cacheline...
This has implications to the convertor-datastructure and other parts
of the code.
- Several performance tests have been run, the netpipe latency does not
change with
this patch on Linux/x86-64 on the smoky cluster.
- Extensive tests have been done to verify correctness (no new
regressions) using:
1. mpi_test_suite on linux/x86-64 using clean ompi-trunk and
ompi-ddt:
a. running both trunk and ompi-ddt resulted in no differences
(except for MPI_SHORT_INT and MPI_TYPE_MIX_LB_UB do now run
correctly).
b. with --enable-memchecker and running under valgrind (one buglet
when run with static found in test-suite, commited)
2. ibm testsuite on linux/x86-64 using clean ompi-trunk and ompi-ddt:
all passed (except for the dynamic/ tests failed!! as trunk/MTT)
3. compilation and usage of HDF5 tests on Jaguar using PGI and
PathScale compilers.
4. compilation and usage on Scicortex.
- Please note, that for the heterogeneous case, (-m32 compiled
binaries/ompi), neither
ompi-trunk, nor ompi-ddt branch would successfully launch.
This commit was SVN r21641.
2009-07-13 08:56:31 +04:00
|
|
|
opal_convertor_get_packed_size(&replyreq->rep_target_convertor,
|
2006-07-18 02:08:55 +04:00
|
|
|
&replyreq->rep_target_bytes_packed);
|
|
|
|
|
|
|
|
return OMPI_SUCCESS;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
static inline int
|
|
|
|
ompi_osc_rdma_replyreq_init_origin(ompi_osc_rdma_replyreq_t *replyreq,
|
|
|
|
ompi_ptr_t origin_request)
|
|
|
|
{
|
|
|
|
replyreq->rep_origin_sendreq = origin_request;
|
|
|
|
|
|
|
|
return OMPI_SUCCESS;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
static inline int
|
|
|
|
ompi_osc_rdma_replyreq_free(ompi_osc_rdma_replyreq_t *replyreq)
|
|
|
|
{
|
2008-04-16 17:29:55 +04:00
|
|
|
MEMCHECKER(
|
|
|
|
memchecker_convertor_call(&opal_memchecker_base_mem_defined,
|
|
|
|
&replyreq->rep_target_convertor);
|
|
|
|
);
|
- Split the datatype engine into two parts: an MPI specific part in
OMPI
and a language agnostic part in OPAL. The convertor is completely
moved into OPAL. This offers several benefits as described in RFC
http://www.open-mpi.org/community/lists/devel/2009/07/6387.php
namely:
- Fewer basic types (int* and float* types, boolean and wchar
- Fixing naming scheme to ompi-nomenclature.
- Usability outside of the ompi-layer.
- Due to the fixed nature of simple opal types, their information is
completely
known at compile time and therefore constified
- With fewer datatypes (22), the actual sizes of bit-field types may be
reduced
from 64 to 32 bits, allowing reorganizing the opal_datatype
structure, eliminating holes and keeping data required in convertor
(upon send/recv) in one cacheline...
This has implications to the convertor-datastructure and other parts
of the code.
- Several performance tests have been run, the netpipe latency does not
change with
this patch on Linux/x86-64 on the smoky cluster.
- Extensive tests have been done to verify correctness (no new
regressions) using:
1. mpi_test_suite on linux/x86-64 using clean ompi-trunk and
ompi-ddt:
a. running both trunk and ompi-ddt resulted in no differences
(except for MPI_SHORT_INT and MPI_TYPE_MIX_LB_UB do now run
correctly).
b. with --enable-memchecker and running under valgrind (one buglet
when run with static found in test-suite, commited)
2. ibm testsuite on linux/x86-64 using clean ompi-trunk and ompi-ddt:
all passed (except for the dynamic/ tests failed!! as trunk/MTT)
3. compilation and usage of HDF5 tests on Jaguar using PGI and
PathScale compilers.
4. compilation and usage on Scicortex.
- Please note, that for the heterogeneous case, (-m32 compiled
binaries/ompi), neither
ompi-trunk, nor ompi-ddt branch would successfully launch.
This commit was SVN r21641.
2009-07-13 08:56:31 +04:00
|
|
|
opal_convertor_cleanup(&replyreq->rep_target_convertor);
|
2006-07-18 02:08:55 +04:00
|
|
|
|
|
|
|
OBJ_RELEASE(replyreq->rep_target_datatype);
|
|
|
|
|
2007-05-24 19:41:24 +04:00
|
|
|
OPAL_FREE_LIST_RETURN(&mca_osc_rdma_component.c_replyreqs,
|
2006-07-18 02:08:55 +04:00
|
|
|
(opal_list_item_t*) replyreq);
|
|
|
|
|
|
|
|
return OMPI_SUCCESS;
|
|
|
|
}
|
|
|
|
|
2006-08-03 04:10:19 +04:00
|
|
|
#endif /* OMPI_OSC_RDMA_REPLYREQ_H */
|