d311d8acf1
implementations. I dont want to overload the memcpy functions, therefore people interested in using the high performance memcpy should use directly opal_memcpy instead. Notice, that there are 2 other versions of memcpy available, which use a destination or a source described as iovecs. This commit was SVN r9532.
31 строка
766 B
C
31 строка
766 B
C
/*
|
|
* Copyright (c) 2004-2005 The University of Tennessee and The University
|
|
* of Tennessee Research Foundation. All rights
|
|
* reserved.
|
|
* $COPYRIGHT$
|
|
*
|
|
* Additional copyrights may follow
|
|
*
|
|
* $HEADER$
|
|
*/
|
|
|
|
#include "opal_config.h"
|
|
|
|
#include "opal/constants.h"
|
|
#include "opal/mca/mca.h"
|
|
#include "opal/mca/base/base.h"
|
|
#include "opal/mca/memcpy/memcpy.h"
|
|
#include "opal/mca/memcpy/base/base.h"
|
|
|
|
|
|
int opal_memcpy_base_close(void)
|
|
{
|
|
/* Close all components that are still open (this should only
|
|
happen during laminfo). */
|
|
mca_base_components_close(0, &opal_memcpy_base_components_opened, NULL);
|
|
OBJ_DESTRUCT(&opal_memcpy_base_components_opened);
|
|
|
|
/* All done */
|
|
return OPAL_SUCCESS;
|
|
}
|