2013-07-20 02:13:58 +04:00
|
|
|
/*
|
2016-01-30 18:34:20 +03:00
|
|
|
* Copyright (c) 2013-2016 Cisco Systems, Inc. All rights reserved.
|
2013-07-20 02:13:58 +04:00
|
|
|
* $COPYRIGHT$
|
|
|
|
*
|
|
|
|
* Additional copyrights may follow
|
|
|
|
*
|
|
|
|
* $HEADER$
|
|
|
|
*/
|
|
|
|
|
|
|
|
#ifndef BTL_USNIC_SEND_H
|
|
|
|
#define BTL_USNIC_SEND_H
|
|
|
|
|
|
|
|
#include "btl_usnic.h"
|
|
|
|
#include "btl_usnic_frag.h"
|
|
|
|
#include "btl_usnic_ack.h"
|
|
|
|
#if MSGDEBUG1
|
|
|
|
#include "btl_usnic_util.h"
|
|
|
|
#endif
|
|
|
|
|
|
|
|
/*
|
2014-07-31 00:56:15 +04:00
|
|
|
* Check if conditions are right, and if so, put endpoint on
|
2013-07-20 02:13:58 +04:00
|
|
|
* list of endpoints that have sends to be done
|
|
|
|
*/
|
|
|
|
static inline void
|
George did the work and deserves all the credit for it. Ralph did the merge, and deserves whatever blame results from errors in it :-)
WHAT: Open our low-level communication infrastructure by moving all necessary components (btl/rcache/allocator/mpool) down in OPAL
All the components required for inter-process communications are currently deeply integrated in the OMPI layer. Several groups/institutions have express interest in having a more generic communication infrastructure, without all the OMPI layer dependencies. This communication layer should be made available at a different software level, available to all layers in the Open MPI software stack. As an example, our ORTE layer could replace the current OOB and instead use the BTL directly, gaining access to more reactive network interfaces than TCP. Similarly, external software libraries could take advantage of our highly optimized AM (active message) communication layer for their own purpose. UTK with support from Sandia, developped a version of Open MPI where the entire communication infrastucture has been moved down to OPAL (btl/rcache/allocator/mpool). Most of the moved components have been updated to match the new schema, with few exceptions (mainly BTLs where I have no way of compiling/testing them). Thus, the completion of this RFC is tied to being able to completing this move for all BTLs. For this we need help from the rest of the Open MPI community, especially those supporting some of the BTLs. A non-exhaustive list of BTLs that qualify here is: mx, portals4, scif, udapl, ugni, usnic.
This commit was SVN r32317.
2014-07-26 04:47:28 +04:00
|
|
|
opal_btl_usnic_check_rts(
|
|
|
|
opal_btl_usnic_endpoint_t *endpoint)
|
2013-07-20 02:13:58 +04:00
|
|
|
{
|
|
|
|
/*
|
|
|
|
* If endpoint not already ready,
|
|
|
|
* and has packets to send,
|
|
|
|
* and it has send credits,
|
|
|
|
* and its retransmission window is open,
|
|
|
|
* make it ready
|
|
|
|
*/
|
|
|
|
if (!endpoint->endpoint_ready_to_send &&
|
|
|
|
!opal_list_is_empty(&endpoint->endpoint_frag_send_queue) &&
|
|
|
|
endpoint->endpoint_send_credits > 0 &&
|
|
|
|
WINDOW_OPEN(endpoint)) {
|
|
|
|
opal_list_append(&endpoint->endpoint_module->endpoints_with_sends,
|
|
|
|
&endpoint->super);
|
|
|
|
endpoint->endpoint_ready_to_send = true;
|
|
|
|
#if MSGDEBUG1
|
2013-08-30 03:24:14 +04:00
|
|
|
opal_output(0, "make endpoint %p RTS\n", (void*)endpoint);
|
2013-07-20 02:13:58 +04:00
|
|
|
} else {
|
|
|
|
opal_output(0, "rts:%d empty:%d cred:%d open%d\n",
|
|
|
|
endpoint->endpoint_ready_to_send,
|
|
|
|
opal_list_is_empty(&endpoint->endpoint_frag_send_queue),
|
|
|
|
endpoint->endpoint_send_credits,
|
|
|
|
WINDOW_OPEN(endpoint));
|
|
|
|
#endif
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
2014-12-03 00:09:46 +03:00
|
|
|
* Common point for posting a segment
|
2013-07-20 02:13:58 +04:00
|
|
|
*/
|
|
|
|
static inline void
|
George did the work and deserves all the credit for it. Ralph did the merge, and deserves whatever blame results from errors in it :-)
WHAT: Open our low-level communication infrastructure by moving all necessary components (btl/rcache/allocator/mpool) down in OPAL
All the components required for inter-process communications are currently deeply integrated in the OMPI layer. Several groups/institutions have express interest in having a more generic communication infrastructure, without all the OMPI layer dependencies. This communication layer should be made available at a different software level, available to all layers in the Open MPI software stack. As an example, our ORTE layer could replace the current OOB and instead use the BTL directly, gaining access to more reactive network interfaces than TCP. Similarly, external software libraries could take advantage of our highly optimized AM (active message) communication layer for their own purpose. UTK with support from Sandia, developped a version of Open MPI where the entire communication infrastucture has been moved down to OPAL (btl/rcache/allocator/mpool). Most of the moved components have been updated to match the new schema, with few exceptions (mainly BTLs where I have no way of compiling/testing them). Thus, the completion of this RFC is tied to being able to completing this move for all BTLs. For this we need help from the rest of the Open MPI community, especially those supporting some of the BTLs. A non-exhaustive list of BTLs that qualify here is: mx, portals4, scif, udapl, ugni, usnic.
This commit was SVN r32317.
2014-07-26 04:47:28 +04:00
|
|
|
opal_btl_usnic_post_segment(
|
|
|
|
opal_btl_usnic_module_t *module,
|
|
|
|
opal_btl_usnic_endpoint_t *endpoint,
|
|
|
|
opal_btl_usnic_send_segment_t *sseg)
|
2013-07-20 02:13:58 +04:00
|
|
|
{
|
|
|
|
int ret;
|
|
|
|
|
2014-12-03 00:09:46 +03:00
|
|
|
/* get channel and remote channel */
|
|
|
|
opal_btl_usnic_channel_id_t channel_id = sseg->ss_channel;
|
|
|
|
opal_btl_usnic_channel_t *channel = &module->mod_channels[channel_id];
|
|
|
|
|
2013-07-20 02:13:58 +04:00
|
|
|
#if MSGDEBUG1
|
2014-12-03 00:09:46 +03:00
|
|
|
opal_output(0, "post_send: type=%s, ep=%p, remote_addr=%p, addr=%p, len=%"
|
|
|
|
PRIsize_t,
|
|
|
|
usnic_seg_type_str(sseg->ss_base.us_type),
|
|
|
|
(void*) channel->ep,
|
|
|
|
(void*) endpoint->endpoint_remote_addrs[channel_id],
|
|
|
|
(void*) sseg->ss_ptr,
|
|
|
|
sseg->ss_len);
|
2013-07-20 02:13:58 +04:00
|
|
|
#endif
|
2014-12-04 01:44:50 +03:00
|
|
|
|
2016-01-30 18:34:20 +03:00
|
|
|
assert(channel_id == USNIC_DATA_CHANNEL);
|
|
|
|
|
2014-12-03 00:09:46 +03:00
|
|
|
/* Send the segment */
|
2014-12-04 01:44:50 +03:00
|
|
|
ret = fi_send(channel->ep,
|
2014-12-03 00:09:46 +03:00
|
|
|
sseg->ss_ptr,
|
2015-07-09 21:58:00 +03:00
|
|
|
sseg->ss_len + mca_btl_usnic_component.prefix_send_offset,
|
2014-12-03 00:09:46 +03:00
|
|
|
NULL,
|
|
|
|
endpoint->endpoint_remote_addrs[channel_id],
|
|
|
|
sseg);
|
2013-07-20 02:13:58 +04:00
|
|
|
if (OPAL_UNLIKELY(0 != ret)) {
|
2014-12-04 01:44:50 +03:00
|
|
|
opal_btl_usnic_util_abort("fi_send() failed",
|
2014-07-31 00:52:06 +04:00
|
|
|
__FILE__, __LINE__);
|
2013-07-20 02:13:58 +04:00
|
|
|
/* Never returns */
|
|
|
|
}
|
|
|
|
|
|
|
|
/* track # of time non-ACKs are posted */
|
George did the work and deserves all the credit for it. Ralph did the merge, and deserves whatever blame results from errors in it :-)
WHAT: Open our low-level communication infrastructure by moving all necessary components (btl/rcache/allocator/mpool) down in OPAL
All the components required for inter-process communications are currently deeply integrated in the OMPI layer. Several groups/institutions have express interest in having a more generic communication infrastructure, without all the OMPI layer dependencies. This communication layer should be made available at a different software level, available to all layers in the Open MPI software stack. As an example, our ORTE layer could replace the current OOB and instead use the BTL directly, gaining access to more reactive network interfaces than TCP. Similarly, external software libraries could take advantage of our highly optimized AM (active message) communication layer for their own purpose. UTK with support from Sandia, developped a version of Open MPI where the entire communication infrastucture has been moved down to OPAL (btl/rcache/allocator/mpool). Most of the moved components have been updated to match the new schema, with few exceptions (mainly BTLs where I have no way of compiling/testing them). Thus, the completion of this RFC is tied to being able to completing this move for all BTLs. For this we need help from the rest of the Open MPI community, especially those supporting some of the BTLs. A non-exhaustive list of BTLs that qualify here is: mx, portals4, scif, udapl, ugni, usnic.
This commit was SVN r32317.
2014-07-26 04:47:28 +04:00
|
|
|
if (sseg->ss_base.us_type != OPAL_BTL_USNIC_SEG_ACK) {
|
2013-07-20 02:13:58 +04:00
|
|
|
++sseg->ss_send_posted;
|
|
|
|
++sseg->ss_parent_frag->sf_seg_post_cnt;
|
|
|
|
}
|
|
|
|
|
2014-12-03 00:09:46 +03:00
|
|
|
/* Stats */
|
|
|
|
++module->stats.num_total_sends;
|
|
|
|
++channel->num_channel_sends;
|
|
|
|
--channel->credits;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Common point for posting an ACK
|
|
|
|
*/
|
|
|
|
static inline void
|
|
|
|
opal_btl_usnic_post_ack(
|
|
|
|
opal_btl_usnic_module_t *module,
|
|
|
|
opal_btl_usnic_endpoint_t *endpoint,
|
|
|
|
opal_btl_usnic_send_segment_t *sseg)
|
|
|
|
{
|
|
|
|
int ret;
|
|
|
|
|
|
|
|
/* get channel and remote channel */
|
|
|
|
opal_btl_usnic_channel_id_t channel_id = sseg->ss_channel;
|
|
|
|
opal_btl_usnic_channel_t *channel = &module->mod_channels[channel_id];
|
|
|
|
|
|
|
|
#if MSGDEBUG1
|
|
|
|
opal_output(0, "post_send ACK: type=%s, ep=%p, remote_addr=%p, addr=%p, len=%"
|
|
|
|
PRIsize_t,
|
|
|
|
usnic_seg_type_str(sseg->ss_base.us_type),
|
|
|
|
(void*) channel->ep,
|
|
|
|
(void*) endpoint->endpoint_remote_addrs[channel_id],
|
|
|
|
(void*) sseg->ss_ptr,
|
|
|
|
sseg->ss_len);
|
|
|
|
#endif
|
|
|
|
|
2016-01-30 18:34:20 +03:00
|
|
|
assert(channel_id == USNIC_PRIORITY_CHANNEL);
|
|
|
|
|
2014-12-04 01:44:50 +03:00
|
|
|
ret = fi_send(channel->ep,
|
2014-12-03 00:09:46 +03:00
|
|
|
sseg->ss_ptr,
|
2015-07-09 21:58:00 +03:00
|
|
|
sseg->ss_len + mca_btl_usnic_component.prefix_send_offset,
|
2014-12-03 00:09:46 +03:00
|
|
|
NULL,
|
|
|
|
endpoint->endpoint_remote_addrs[channel_id],
|
|
|
|
sseg);
|
|
|
|
if (OPAL_UNLIKELY(0 != ret)) {
|
2014-12-04 01:44:50 +03:00
|
|
|
opal_btl_usnic_util_abort("fi_send() failed",
|
2014-12-03 00:09:46 +03:00
|
|
|
__FILE__, __LINE__);
|
|
|
|
/* Never returns */
|
|
|
|
}
|
2013-07-20 02:13:58 +04:00
|
|
|
|
|
|
|
/* Stats */
|
Move all usNIC stats to _stats.c|h and export them as MPI_T pvars.
This commit moves all the module stats into their own struct so that
the stats only need to appear as a single line in the module_t
definition, and then moves all the logic for reporting the stats into
btl_usnic_stats.c|h.
Further, the stats are now exported as MPI_T_BIND_NO_OBJECT entities
(i.e., not bound to any particular MPI handle), and are marked as
READONLY and CONTINUOUS. They currently all default to verbose level
5 ("Application tuner / detailed", according to
https://svn.open-mpi.org/trac/ompi/wiki/MCAParamLevels).
Most of the statistics are counters, but a small number are high
watermark values. Due to how counters are reported via MPI_T, none of
the counters are exported through MPI_T if the MCA param
btl_usnic_stats_relative=1 (i.e., the module resets the stats back to
zero at a given frequency).
When MPI_T_pvar_handle_alloc() is invoked on any of these pvars, it
will return a count that is equal to the number of active usnic BTL
modules. The values returned for any given pvar (e.g.,
num_total_sends) are an array containing one value for each active
usnic BTL module. The ordering of values in the array is both
consistent across all usnic pvars and stable throughout a single job:
array slot 0 corresponds to module X, array slot 1 corresponds to
module Y, etc.
Mapping which array slot corresponds to which underlying Linux usnic_X
device works as follows:
* The btl_usnic_devices MPI_T state pvar is associated with a
btl_usnic_device MPI_T enum, and be obtained via
MPI_T_pvar_get_info().
* If all usNIC pvars are of length N, the values [0,N) in the
btl_usnic_device enum are associated with strings of the
corresponding underlying Linux device.
For exampe, to look up which Linux device is reported in all usNIC
pvars' array slot 1, look up the int value 1 in the btl_usnic_devices
enum. Its corresponding string value is underlying Linux device name
(e.g., "usnic_1").
cmr=v1.7.4:subject="usnic BTL MPI_T pvars"
This commit was SVN r29545.
2013-10-29 02:23:08 +04:00
|
|
|
++module->stats.num_total_sends;
|
2013-07-20 02:13:58 +04:00
|
|
|
++channel->num_channel_sends;
|
2014-12-03 00:09:46 +03:00
|
|
|
--channel->credits;
|
2013-07-20 02:13:58 +04:00
|
|
|
}
|
2014-12-03 00:09:46 +03:00
|
|
|
|
2013-07-20 02:13:58 +04:00
|
|
|
/*
|
2014-12-03 00:09:46 +03:00
|
|
|
* Post a send to the work queue
|
2013-07-20 02:13:58 +04:00
|
|
|
*/
|
|
|
|
static inline void
|
George did the work and deserves all the credit for it. Ralph did the merge, and deserves whatever blame results from errors in it :-)
WHAT: Open our low-level communication infrastructure by moving all necessary components (btl/rcache/allocator/mpool) down in OPAL
All the components required for inter-process communications are currently deeply integrated in the OMPI layer. Several groups/institutions have express interest in having a more generic communication infrastructure, without all the OMPI layer dependencies. This communication layer should be made available at a different software level, available to all layers in the Open MPI software stack. As an example, our ORTE layer could replace the current OOB and instead use the BTL directly, gaining access to more reactive network interfaces than TCP. Similarly, external software libraries could take advantage of our highly optimized AM (active message) communication layer for their own purpose. UTK with support from Sandia, developped a version of Open MPI where the entire communication infrastucture has been moved down to OPAL (btl/rcache/allocator/mpool). Most of the moved components have been updated to match the new schema, with few exceptions (mainly BTLs where I have no way of compiling/testing them). Thus, the completion of this RFC is tied to being able to completing this move for all BTLs. For this we need help from the rest of the Open MPI community, especially those supporting some of the BTLs. A non-exhaustive list of BTLs that qualify here is: mx, portals4, scif, udapl, ugni, usnic.
This commit was SVN r32317.
2014-07-26 04:47:28 +04:00
|
|
|
opal_btl_usnic_endpoint_send_segment(
|
|
|
|
opal_btl_usnic_module_t *module,
|
|
|
|
opal_btl_usnic_send_segment_t *sseg)
|
2013-07-20 02:13:58 +04:00
|
|
|
{
|
George did the work and deserves all the credit for it. Ralph did the merge, and deserves whatever blame results from errors in it :-)
WHAT: Open our low-level communication infrastructure by moving all necessary components (btl/rcache/allocator/mpool) down in OPAL
All the components required for inter-process communications are currently deeply integrated in the OMPI layer. Several groups/institutions have express interest in having a more generic communication infrastructure, without all the OMPI layer dependencies. This communication layer should be made available at a different software level, available to all layers in the Open MPI software stack. As an example, our ORTE layer could replace the current OOB and instead use the BTL directly, gaining access to more reactive network interfaces than TCP. Similarly, external software libraries could take advantage of our highly optimized AM (active message) communication layer for their own purpose. UTK with support from Sandia, developped a version of Open MPI where the entire communication infrastucture has been moved down to OPAL (btl/rcache/allocator/mpool). Most of the moved components have been updated to match the new schema, with few exceptions (mainly BTLs where I have no way of compiling/testing them). Thus, the completion of this RFC is tied to being able to completing this move for all BTLs. For this we need help from the rest of the Open MPI community, especially those supporting some of the BTLs. A non-exhaustive list of BTLs that qualify here is: mx, portals4, scif, udapl, ugni, usnic.
This commit was SVN r32317.
2014-07-26 04:47:28 +04:00
|
|
|
opal_btl_usnic_send_frag_t *frag;
|
|
|
|
opal_btl_usnic_endpoint_t *endpoint;
|
2013-07-20 02:13:58 +04:00
|
|
|
uint16_t sfi;
|
|
|
|
|
|
|
|
frag = sseg->ss_parent_frag;
|
|
|
|
endpoint = frag->sf_endpoint;
|
|
|
|
|
|
|
|
/* Do we have room in the endpoint's sender window?
|
|
|
|
|
|
|
|
Sender window:
|
|
|
|
|
|
|
|
|-------- WINDOW_SIZE ----------|
|
|
|
|
+---------------------------------+
|
|
|
|
| next_seq_to_send |
|
|
|
|
| somewhere in this range |
|
|
|
|
^+---------------------------------+
|
|
|
|
|
|
|
|
|
+-- ack_seq_rcvd: one less than the window left edge
|
|
|
|
|
|
|
|
Assuming that next_seq_to_send is > ack_seq_rcvd (verified
|
|
|
|
by assert), then the good condition to send is:
|
|
|
|
|
|
|
|
next_seq_to_send <= ack_seq_rcvd + WINDOW_SIZE
|
|
|
|
|
|
|
|
And therefore the bad condition is
|
|
|
|
|
|
|
|
next_seq_to_send > ack_seq_rcvd + WINDOW_SIZE
|
|
|
|
*/
|
2014-02-26 11:40:10 +04:00
|
|
|
assert(SEQ_GT(endpoint->endpoint_next_seq_to_send,
|
|
|
|
endpoint->endpoint_ack_seq_rcvd));
|
2013-07-20 02:13:58 +04:00
|
|
|
assert(WINDOW_OPEN(endpoint));
|
|
|
|
|
|
|
|
/* Assign sequence number and increment */
|
2014-02-26 11:40:10 +04:00
|
|
|
sseg->ss_base.us_btl_header->pkt_seq =
|
|
|
|
endpoint->endpoint_next_seq_to_send++;
|
2013-07-20 02:13:58 +04:00
|
|
|
|
|
|
|
/* Fill in remote address to indicate PUT or not */
|
|
|
|
sseg->ss_base.us_btl_header->put_addr =
|
2014-07-10 21:18:03 +04:00
|
|
|
frag->sf_base.uf_remote_seg[0].seg_addr.pval;
|
2013-07-20 02:13:58 +04:00
|
|
|
|
|
|
|
/* piggy-back an ACK if needed */
|
George did the work and deserves all the credit for it. Ralph did the merge, and deserves whatever blame results from errors in it :-)
WHAT: Open our low-level communication infrastructure by moving all necessary components (btl/rcache/allocator/mpool) down in OPAL
All the components required for inter-process communications are currently deeply integrated in the OMPI layer. Several groups/institutions have express interest in having a more generic communication infrastructure, without all the OMPI layer dependencies. This communication layer should be made available at a different software level, available to all layers in the Open MPI software stack. As an example, our ORTE layer could replace the current OOB and instead use the BTL directly, gaining access to more reactive network interfaces than TCP. Similarly, external software libraries could take advantage of our highly optimized AM (active message) communication layer for their own purpose. UTK with support from Sandia, developped a version of Open MPI where the entire communication infrastucture has been moved down to OPAL (btl/rcache/allocator/mpool). Most of the moved components have been updated to match the new schema, with few exceptions (mainly BTLs where I have no way of compiling/testing them). Thus, the completion of this RFC is tied to being able to completing this move for all BTLs. For this we need help from the rest of the Open MPI community, especially those supporting some of the BTLs. A non-exhaustive list of BTLs that qualify here is: mx, portals4, scif, udapl, ugni, usnic.
This commit was SVN r32317.
2014-07-26 04:47:28 +04:00
|
|
|
opal_btl_usnic_piggyback_ack(endpoint, sseg);
|
2013-07-20 02:13:58 +04:00
|
|
|
|
|
|
|
#if MSGDEBUG1
|
|
|
|
{
|
2014-12-03 00:09:46 +03:00
|
|
|
char local_ip[32];
|
|
|
|
char remote_ip[32];
|
|
|
|
|
|
|
|
opal_btl_usnic_snprintf_ipv4_addr(local_ip, sizeof(local_ip),
|
|
|
|
module->local_modex.ipv4_addr,
|
|
|
|
module->local_modex.netmask);
|
|
|
|
opal_btl_usnic_snprintf_ipv4_addr(remote_ip, sizeof(remote_ip),
|
|
|
|
endpoint->endpoint_remote_modex.ipv4_addr,
|
|
|
|
endpoint->endpoint_remote_modex.netmask);
|
|
|
|
|
|
|
|
opal_output(0, "--> Sending %s: seq: %" UDSEQ ", sender: 0x%016lx from device %s, IP %s, port %u, seg %p, room %d, wc len %u, remote IP %s, port %u",
|
George did the work and deserves all the credit for it. Ralph did the merge, and deserves whatever blame results from errors in it :-)
WHAT: Open our low-level communication infrastructure by moving all necessary components (btl/rcache/allocator/mpool) down in OPAL
All the components required for inter-process communications are currently deeply integrated in the OMPI layer. Several groups/institutions have express interest in having a more generic communication infrastructure, without all the OMPI layer dependencies. This communication layer should be made available at a different software level, available to all layers in the Open MPI software stack. As an example, our ORTE layer could replace the current OOB and instead use the BTL directly, gaining access to more reactive network interfaces than TCP. Similarly, external software libraries could take advantage of our highly optimized AM (active message) communication layer for their own purpose. UTK with support from Sandia, developped a version of Open MPI where the entire communication infrastucture has been moved down to OPAL (btl/rcache/allocator/mpool). Most of the moved components have been updated to match the new schema, with few exceptions (mainly BTLs where I have no way of compiling/testing them). Thus, the completion of this RFC is tied to being able to completing this move for all BTLs. For this we need help from the rest of the Open MPI community, especially those supporting some of the BTLs. A non-exhaustive list of BTLs that qualify here is: mx, portals4, scif, udapl, ugni, usnic.
This commit was SVN r32317.
2014-07-26 04:47:28 +04:00
|
|
|
(sseg->ss_parent_frag->sf_base.uf_type == OPAL_BTL_USNIC_FRAG_LARGE_SEND)?
|
2014-12-03 00:09:46 +03:00
|
|
|
"CHUNK" : "FRAG",
|
|
|
|
sseg->ss_base.us_btl_header->pkt_seq,
|
|
|
|
sseg->ss_base.us_btl_header->sender,
|
2016-08-20 05:07:14 +03:00
|
|
|
endpoint->endpoint_module->linux_device_name,
|
2014-12-03 00:09:46 +03:00
|
|
|
local_ip,
|
|
|
|
module->local_modex.ports[sseg->ss_channel],
|
|
|
|
(void*)sseg,
|
|
|
|
sseg->ss_hotel_room,
|
|
|
|
sseg->ss_ptr,
|
|
|
|
remote_ip,
|
|
|
|
endpoint->endpoint_remote_modex.ports[sseg->ss_channel]);
|
2013-07-20 02:13:58 +04:00
|
|
|
}
|
|
|
|
#endif
|
|
|
|
|
|
|
|
/* do the actual send */
|
George did the work and deserves all the credit for it. Ralph did the merge, and deserves whatever blame results from errors in it :-)
WHAT: Open our low-level communication infrastructure by moving all necessary components (btl/rcache/allocator/mpool) down in OPAL
All the components required for inter-process communications are currently deeply integrated in the OMPI layer. Several groups/institutions have express interest in having a more generic communication infrastructure, without all the OMPI layer dependencies. This communication layer should be made available at a different software level, available to all layers in the Open MPI software stack. As an example, our ORTE layer could replace the current OOB and instead use the BTL directly, gaining access to more reactive network interfaces than TCP. Similarly, external software libraries could take advantage of our highly optimized AM (active message) communication layer for their own purpose. UTK with support from Sandia, developped a version of Open MPI where the entire communication infrastucture has been moved down to OPAL (btl/rcache/allocator/mpool). Most of the moved components have been updated to match the new schema, with few exceptions (mainly BTLs where I have no way of compiling/testing them). Thus, the completion of this RFC is tied to being able to completing this move for all BTLs. For this we need help from the rest of the Open MPI community, especially those supporting some of the BTLs. A non-exhaustive list of BTLs that qualify here is: mx, portals4, scif, udapl, ugni, usnic.
This commit was SVN r32317.
2014-07-26 04:47:28 +04:00
|
|
|
opal_btl_usnic_post_segment(module, endpoint, sseg);
|
2013-07-20 02:13:58 +04:00
|
|
|
|
|
|
|
/* Track this header by stashing in an array on the endpoint that
|
|
|
|
is the same length as the sender's window (i.e., WINDOW_SIZE).
|
|
|
|
To find a unique slot in this array, use (seq % WINDOW_SIZE).
|
|
|
|
*/
|
2014-02-26 11:40:10 +04:00
|
|
|
sfi = WINDOW_SIZE_MOD(sseg->ss_base.us_btl_header->pkt_seq);
|
2013-07-20 02:13:58 +04:00
|
|
|
endpoint->endpoint_sent_segs[sfi] = sseg;
|
|
|
|
sseg->ss_ack_pending = true;
|
|
|
|
|
|
|
|
/* bookkeeping */
|
|
|
|
--endpoint->endpoint_send_credits;
|
|
|
|
|
|
|
|
/* Stats */
|
|
|
|
if (sseg->ss_parent_frag->sf_base.uf_type
|
George did the work and deserves all the credit for it. Ralph did the merge, and deserves whatever blame results from errors in it :-)
WHAT: Open our low-level communication infrastructure by moving all necessary components (btl/rcache/allocator/mpool) down in OPAL
All the components required for inter-process communications are currently deeply integrated in the OMPI layer. Several groups/institutions have express interest in having a more generic communication infrastructure, without all the OMPI layer dependencies. This communication layer should be made available at a different software level, available to all layers in the Open MPI software stack. As an example, our ORTE layer could replace the current OOB and instead use the BTL directly, gaining access to more reactive network interfaces than TCP. Similarly, external software libraries could take advantage of our highly optimized AM (active message) communication layer for their own purpose. UTK with support from Sandia, developped a version of Open MPI where the entire communication infrastucture has been moved down to OPAL (btl/rcache/allocator/mpool). Most of the moved components have been updated to match the new schema, with few exceptions (mainly BTLs where I have no way of compiling/testing them). Thus, the completion of this RFC is tied to being able to completing this move for all BTLs. For this we need help from the rest of the Open MPI community, especially those supporting some of the BTLs. A non-exhaustive list of BTLs that qualify here is: mx, portals4, scif, udapl, ugni, usnic.
This commit was SVN r32317.
2014-07-26 04:47:28 +04:00
|
|
|
== OPAL_BTL_USNIC_FRAG_LARGE_SEND) {
|
Move all usNIC stats to _stats.c|h and export them as MPI_T pvars.
This commit moves all the module stats into their own struct so that
the stats only need to appear as a single line in the module_t
definition, and then moves all the logic for reporting the stats into
btl_usnic_stats.c|h.
Further, the stats are now exported as MPI_T_BIND_NO_OBJECT entities
(i.e., not bound to any particular MPI handle), and are marked as
READONLY and CONTINUOUS. They currently all default to verbose level
5 ("Application tuner / detailed", according to
https://svn.open-mpi.org/trac/ompi/wiki/MCAParamLevels).
Most of the statistics are counters, but a small number are high
watermark values. Due to how counters are reported via MPI_T, none of
the counters are exported through MPI_T if the MCA param
btl_usnic_stats_relative=1 (i.e., the module resets the stats back to
zero at a given frequency).
When MPI_T_pvar_handle_alloc() is invoked on any of these pvars, it
will return a count that is equal to the number of active usnic BTL
modules. The values returned for any given pvar (e.g.,
num_total_sends) are an array containing one value for each active
usnic BTL module. The ordering of values in the array is both
consistent across all usnic pvars and stable throughout a single job:
array slot 0 corresponds to module X, array slot 1 corresponds to
module Y, etc.
Mapping which array slot corresponds to which underlying Linux usnic_X
device works as follows:
* The btl_usnic_devices MPI_T state pvar is associated with a
btl_usnic_device MPI_T enum, and be obtained via
MPI_T_pvar_get_info().
* If all usNIC pvars are of length N, the values [0,N) in the
btl_usnic_device enum are associated with strings of the
corresponding underlying Linux device.
For exampe, to look up which Linux device is reported in all usNIC
pvars' array slot 1, look up the int value 1 in the btl_usnic_devices
enum. Its corresponding string value is underlying Linux device name
(e.g., "usnic_1").
cmr=v1.7.4:subject="usnic BTL MPI_T pvars"
This commit was SVN r29545.
2013-10-29 02:23:08 +04:00
|
|
|
++module->stats.num_chunk_sends;
|
2013-07-20 02:13:58 +04:00
|
|
|
} else {
|
Move all usNIC stats to _stats.c|h and export them as MPI_T pvars.
This commit moves all the module stats into their own struct so that
the stats only need to appear as a single line in the module_t
definition, and then moves all the logic for reporting the stats into
btl_usnic_stats.c|h.
Further, the stats are now exported as MPI_T_BIND_NO_OBJECT entities
(i.e., not bound to any particular MPI handle), and are marked as
READONLY and CONTINUOUS. They currently all default to verbose level
5 ("Application tuner / detailed", according to
https://svn.open-mpi.org/trac/ompi/wiki/MCAParamLevels).
Most of the statistics are counters, but a small number are high
watermark values. Due to how counters are reported via MPI_T, none of
the counters are exported through MPI_T if the MCA param
btl_usnic_stats_relative=1 (i.e., the module resets the stats back to
zero at a given frequency).
When MPI_T_pvar_handle_alloc() is invoked on any of these pvars, it
will return a count that is equal to the number of active usnic BTL
modules. The values returned for any given pvar (e.g.,
num_total_sends) are an array containing one value for each active
usnic BTL module. The ordering of values in the array is both
consistent across all usnic pvars and stable throughout a single job:
array slot 0 corresponds to module X, array slot 1 corresponds to
module Y, etc.
Mapping which array slot corresponds to which underlying Linux usnic_X
device works as follows:
* The btl_usnic_devices MPI_T state pvar is associated with a
btl_usnic_device MPI_T enum, and be obtained via
MPI_T_pvar_get_info().
* If all usNIC pvars are of length N, the values [0,N) in the
btl_usnic_device enum are associated with strings of the
corresponding underlying Linux device.
For exampe, to look up which Linux device is reported in all usNIC
pvars' array slot 1, look up the int value 1 in the btl_usnic_devices
enum. Its corresponding string value is underlying Linux device name
(e.g., "usnic_1").
cmr=v1.7.4:subject="usnic BTL MPI_T pvars"
This commit was SVN r29545.
2013-10-29 02:23:08 +04:00
|
|
|
++module->stats.num_frag_sends;
|
2013-07-20 02:13:58 +04:00
|
|
|
}
|
|
|
|
|
|
|
|
/* If we have room in the sender's window, we also have room in
|
|
|
|
endpoint hotel */
|
|
|
|
opal_hotel_checkin_with_res(&endpoint->endpoint_hotel, sseg,
|
|
|
|
&sseg->ss_hotel_room);
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* This enqueues a fragment send into the system. A send of a fragment
|
|
|
|
* may result in the sending of multiple segments
|
|
|
|
*/
|
|
|
|
static inline int
|
George did the work and deserves all the credit for it. Ralph did the merge, and deserves whatever blame results from errors in it :-)
WHAT: Open our low-level communication infrastructure by moving all necessary components (btl/rcache/allocator/mpool) down in OPAL
All the components required for inter-process communications are currently deeply integrated in the OMPI layer. Several groups/institutions have express interest in having a more generic communication infrastructure, without all the OMPI layer dependencies. This communication layer should be made available at a different software level, available to all layers in the Open MPI software stack. As an example, our ORTE layer could replace the current OOB and instead use the BTL directly, gaining access to more reactive network interfaces than TCP. Similarly, external software libraries could take advantage of our highly optimized AM (active message) communication layer for their own purpose. UTK with support from Sandia, developped a version of Open MPI where the entire communication infrastucture has been moved down to OPAL (btl/rcache/allocator/mpool). Most of the moved components have been updated to match the new schema, with few exceptions (mainly BTLs where I have no way of compiling/testing them). Thus, the completion of this RFC is tied to being able to completing this move for all BTLs. For this we need help from the rest of the Open MPI community, especially those supporting some of the BTLs. A non-exhaustive list of BTLs that qualify here is: mx, portals4, scif, udapl, ugni, usnic.
This commit was SVN r32317.
2014-07-26 04:47:28 +04:00
|
|
|
opal_btl_usnic_endpoint_enqueue_frag(
|
|
|
|
opal_btl_usnic_endpoint_t *endpoint,
|
|
|
|
opal_btl_usnic_send_frag_t *frag)
|
2013-07-20 02:13:58 +04:00
|
|
|
{
|
|
|
|
#if MSGDEBUG1
|
2013-09-17 11:29:40 +04:00
|
|
|
opal_output(0, "enq_frag: frag=%p, endpoint=%p, %s, len=%lu\n",
|
2013-09-17 11:20:44 +04:00
|
|
|
(void*)frag, (void*)endpoint,
|
|
|
|
usnic_frag_type(frag->sf_base.uf_type),
|
2013-09-17 11:29:40 +04:00
|
|
|
(long unsigned)frag->sf_base.uf_base.des_src->seg_len);
|
George did the work and deserves all the credit for it. Ralph did the merge, and deserves whatever blame results from errors in it :-)
WHAT: Open our low-level communication infrastructure by moving all necessary components (btl/rcache/allocator/mpool) down in OPAL
All the components required for inter-process communications are currently deeply integrated in the OMPI layer. Several groups/institutions have express interest in having a more generic communication infrastructure, without all the OMPI layer dependencies. This communication layer should be made available at a different software level, available to all layers in the Open MPI software stack. As an example, our ORTE layer could replace the current OOB and instead use the BTL directly, gaining access to more reactive network interfaces than TCP. Similarly, external software libraries could take advantage of our highly optimized AM (active message) communication layer for their own purpose. UTK with support from Sandia, developped a version of Open MPI where the entire communication infrastucture has been moved down to OPAL (btl/rcache/allocator/mpool). Most of the moved components have been updated to match the new schema, with few exceptions (mainly BTLs where I have no way of compiling/testing them). Thus, the completion of this RFC is tied to being able to completing this move for all BTLs. For this we need help from the rest of the Open MPI community, especially those supporting some of the BTLs. A non-exhaustive list of BTLs that qualify here is: mx, portals4, scif, udapl, ugni, usnic.
This commit was SVN r32317.
2014-07-26 04:47:28 +04:00
|
|
|
if (frag->sf_base.uf_type == OPAL_BTL_USNIC_FRAG_LARGE_SEND) {
|
|
|
|
opal_btl_usnic_large_send_frag_t *lfrag;
|
|
|
|
lfrag = (opal_btl_usnic_large_send_frag_t *)frag;
|
2013-08-30 03:24:14 +04:00
|
|
|
opal_output(0, " large size=%zd\n", lfrag->lsf_base.sf_size);
|
2013-07-20 02:13:58 +04:00
|
|
|
}
|
|
|
|
#endif
|
|
|
|
|
|
|
|
/* add to tail of in-progress list */
|
|
|
|
opal_list_append(&endpoint->endpoint_frag_send_queue,
|
|
|
|
&frag->sf_base.uf_base.super.super);
|
|
|
|
|
|
|
|
/* possibly make this endpoint ready to send again */
|
George did the work and deserves all the credit for it. Ralph did the merge, and deserves whatever blame results from errors in it :-)
WHAT: Open our low-level communication infrastructure by moving all necessary components (btl/rcache/allocator/mpool) down in OPAL
All the components required for inter-process communications are currently deeply integrated in the OMPI layer. Several groups/institutions have express interest in having a more generic communication infrastructure, without all the OMPI layer dependencies. This communication layer should be made available at a different software level, available to all layers in the Open MPI software stack. As an example, our ORTE layer could replace the current OOB and instead use the BTL directly, gaining access to more reactive network interfaces than TCP. Similarly, external software libraries could take advantage of our highly optimized AM (active message) communication layer for their own purpose. UTK with support from Sandia, developped a version of Open MPI where the entire communication infrastucture has been moved down to OPAL (btl/rcache/allocator/mpool). Most of the moved components have been updated to match the new schema, with few exceptions (mainly BTLs where I have no way of compiling/testing them). Thus, the completion of this RFC is tied to being able to completing this move for all BTLs. For this we need help from the rest of the Open MPI community, especially those supporting some of the BTLs. A non-exhaustive list of BTLs that qualify here is: mx, portals4, scif, udapl, ugni, usnic.
This commit was SVN r32317.
2014-07-26 04:47:28 +04:00
|
|
|
opal_btl_usnic_check_rts(endpoint);
|
2013-07-20 02:13:58 +04:00
|
|
|
|
George did the work and deserves all the credit for it. Ralph did the merge, and deserves whatever blame results from errors in it :-)
WHAT: Open our low-level communication infrastructure by moving all necessary components (btl/rcache/allocator/mpool) down in OPAL
All the components required for inter-process communications are currently deeply integrated in the OMPI layer. Several groups/institutions have express interest in having a more generic communication infrastructure, without all the OMPI layer dependencies. This communication layer should be made available at a different software level, available to all layers in the Open MPI software stack. As an example, our ORTE layer could replace the current OOB and instead use the BTL directly, gaining access to more reactive network interfaces than TCP. Similarly, external software libraries could take advantage of our highly optimized AM (active message) communication layer for their own purpose. UTK with support from Sandia, developped a version of Open MPI where the entire communication infrastucture has been moved down to OPAL (btl/rcache/allocator/mpool). Most of the moved components have been updated to match the new schema, with few exceptions (mainly BTLs where I have no way of compiling/testing them). Thus, the completion of this RFC is tied to being able to completing this move for all BTLs. For this we need help from the rest of the Open MPI community, especially those supporting some of the BTLs. A non-exhaustive list of BTLs that qualify here is: mx, portals4, scif, udapl, ugni, usnic.
This commit was SVN r32317.
2014-07-26 04:47:28 +04:00
|
|
|
return OPAL_SUCCESS;
|
2013-07-20 02:13:58 +04:00
|
|
|
}
|
|
|
|
|
2013-09-17 11:27:39 +04:00
|
|
|
static inline void
|
George did the work and deserves all the credit for it. Ralph did the merge, and deserves whatever blame results from errors in it :-)
WHAT: Open our low-level communication infrastructure by moving all necessary components (btl/rcache/allocator/mpool) down in OPAL
All the components required for inter-process communications are currently deeply integrated in the OMPI layer. Several groups/institutions have express interest in having a more generic communication infrastructure, without all the OMPI layer dependencies. This communication layer should be made available at a different software level, available to all layers in the Open MPI software stack. As an example, our ORTE layer could replace the current OOB and instead use the BTL directly, gaining access to more reactive network interfaces than TCP. Similarly, external software libraries could take advantage of our highly optimized AM (active message) communication layer for their own purpose. UTK with support from Sandia, developped a version of Open MPI where the entire communication infrastucture has been moved down to OPAL (btl/rcache/allocator/mpool). Most of the moved components have been updated to match the new schema, with few exceptions (mainly BTLs where I have no way of compiling/testing them). Thus, the completion of this RFC is tied to being able to completing this move for all BTLs. For this we need help from the rest of the Open MPI community, especially those supporting some of the BTLs. A non-exhaustive list of BTLs that qualify here is: mx, portals4, scif, udapl, ugni, usnic.
This commit was SVN r32317.
2014-07-26 04:47:28 +04:00
|
|
|
opal_btl_usnic_release_send_segment(
|
|
|
|
opal_btl_usnic_module_t *module,
|
|
|
|
opal_btl_usnic_send_frag_t *frag,
|
|
|
|
opal_btl_usnic_send_segment_t *sseg)
|
2013-09-17 11:27:39 +04:00
|
|
|
{
|
2014-07-31 00:56:15 +04:00
|
|
|
/* We only return CHUNK segments because they are the only send-style
|
2013-09-17 11:27:39 +04:00
|
|
|
* segments that are dynamically allocated.
|
|
|
|
*/
|
George did the work and deserves all the credit for it. Ralph did the merge, and deserves whatever blame results from errors in it :-)
WHAT: Open our low-level communication infrastructure by moving all necessary components (btl/rcache/allocator/mpool) down in OPAL
All the components required for inter-process communications are currently deeply integrated in the OMPI layer. Several groups/institutions have express interest in having a more generic communication infrastructure, without all the OMPI layer dependencies. This communication layer should be made available at a different software level, available to all layers in the Open MPI software stack. As an example, our ORTE layer could replace the current OOB and instead use the BTL directly, gaining access to more reactive network interfaces than TCP. Similarly, external software libraries could take advantage of our highly optimized AM (active message) communication layer for their own purpose. UTK with support from Sandia, developped a version of Open MPI where the entire communication infrastucture has been moved down to OPAL (btl/rcache/allocator/mpool). Most of the moved components have been updated to match the new schema, with few exceptions (mainly BTLs where I have no way of compiling/testing them). Thus, the completion of this RFC is tied to being able to completing this move for all BTLs. For this we need help from the rest of the Open MPI community, especially those supporting some of the BTLs. A non-exhaustive list of BTLs that qualify here is: mx, portals4, scif, udapl, ugni, usnic.
This commit was SVN r32317.
2014-07-26 04:47:28 +04:00
|
|
|
if (sseg->ss_base.us_type == OPAL_BTL_USNIC_SEG_CHUNK) {
|
|
|
|
opal_btl_usnic_chunk_segment_return(module, sseg);
|
2013-09-17 11:27:39 +04:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
George did the work and deserves all the credit for it. Ralph did the merge, and deserves whatever blame results from errors in it :-)
WHAT: Open our low-level communication infrastructure by moving all necessary components (btl/rcache/allocator/mpool) down in OPAL
All the components required for inter-process communications are currently deeply integrated in the OMPI layer. Several groups/institutions have express interest in having a more generic communication infrastructure, without all the OMPI layer dependencies. This communication layer should be made available at a different software level, available to all layers in the Open MPI software stack. As an example, our ORTE layer could replace the current OOB and instead use the BTL directly, gaining access to more reactive network interfaces than TCP. Similarly, external software libraries could take advantage of our highly optimized AM (active message) communication layer for their own purpose. UTK with support from Sandia, developped a version of Open MPI where the entire communication infrastucture has been moved down to OPAL (btl/rcache/allocator/mpool). Most of the moved components have been updated to match the new schema, with few exceptions (mainly BTLs where I have no way of compiling/testing them). Thus, the completion of this RFC is tied to being able to completing this move for all BTLs. For this we need help from the rest of the Open MPI community, especially those supporting some of the BTLs. A non-exhaustive list of BTLs that qualify here is: mx, portals4, scif, udapl, ugni, usnic.
This commit was SVN r32317.
2014-07-26 04:47:28 +04:00
|
|
|
void opal_btl_usnic_frag_complete(opal_btl_usnic_send_frag_t *frag);
|
2013-07-20 02:13:58 +04:00
|
|
|
|
George did the work and deserves all the credit for it. Ralph did the merge, and deserves whatever blame results from errors in it :-)
WHAT: Open our low-level communication infrastructure by moving all necessary components (btl/rcache/allocator/mpool) down in OPAL
All the components required for inter-process communications are currently deeply integrated in the OMPI layer. Several groups/institutions have express interest in having a more generic communication infrastructure, without all the OMPI layer dependencies. This communication layer should be made available at a different software level, available to all layers in the Open MPI software stack. As an example, our ORTE layer could replace the current OOB and instead use the BTL directly, gaining access to more reactive network interfaces than TCP. Similarly, external software libraries could take advantage of our highly optimized AM (active message) communication layer for their own purpose. UTK with support from Sandia, developped a version of Open MPI where the entire communication infrastucture has been moved down to OPAL (btl/rcache/allocator/mpool). Most of the moved components have been updated to match the new schema, with few exceptions (mainly BTLs where I have no way of compiling/testing them). Thus, the completion of this RFC is tied to being able to completing this move for all BTLs. For this we need help from the rest of the Open MPI community, especially those supporting some of the BTLs. A non-exhaustive list of BTLs that qualify here is: mx, portals4, scif, udapl, ugni, usnic.
This commit was SVN r32317.
2014-07-26 04:47:28 +04:00
|
|
|
void opal_btl_usnic_frag_send_complete(opal_btl_usnic_module_t *module,
|
|
|
|
opal_btl_usnic_send_segment_t *sseg);
|
2013-07-20 02:13:58 +04:00
|
|
|
|
George did the work and deserves all the credit for it. Ralph did the merge, and deserves whatever blame results from errors in it :-)
WHAT: Open our low-level communication infrastructure by moving all necessary components (btl/rcache/allocator/mpool) down in OPAL
All the components required for inter-process communications are currently deeply integrated in the OMPI layer. Several groups/institutions have express interest in having a more generic communication infrastructure, without all the OMPI layer dependencies. This communication layer should be made available at a different software level, available to all layers in the Open MPI software stack. As an example, our ORTE layer could replace the current OOB and instead use the BTL directly, gaining access to more reactive network interfaces than TCP. Similarly, external software libraries could take advantage of our highly optimized AM (active message) communication layer for their own purpose. UTK with support from Sandia, developped a version of Open MPI where the entire communication infrastucture has been moved down to OPAL (btl/rcache/allocator/mpool). Most of the moved components have been updated to match the new schema, with few exceptions (mainly BTLs where I have no way of compiling/testing them). Thus, the completion of this RFC is tied to being able to completing this move for all BTLs. For this we need help from the rest of the Open MPI community, especially those supporting some of the BTLs. A non-exhaustive list of BTLs that qualify here is: mx, portals4, scif, udapl, ugni, usnic.
This commit was SVN r32317.
2014-07-26 04:47:28 +04:00
|
|
|
void opal_btl_usnic_chunk_send_complete(opal_btl_usnic_module_t *module,
|
|
|
|
opal_btl_usnic_send_segment_t *sseg);
|
2013-07-20 02:13:58 +04:00
|
|
|
|
2013-11-05 02:52:03 +04:00
|
|
|
int
|
George did the work and deserves all the credit for it. Ralph did the merge, and deserves whatever blame results from errors in it :-)
WHAT: Open our low-level communication infrastructure by moving all necessary components (btl/rcache/allocator/mpool) down in OPAL
All the components required for inter-process communications are currently deeply integrated in the OMPI layer. Several groups/institutions have express interest in having a more generic communication infrastructure, without all the OMPI layer dependencies. This communication layer should be made available at a different software level, available to all layers in the Open MPI software stack. As an example, our ORTE layer could replace the current OOB and instead use the BTL directly, gaining access to more reactive network interfaces than TCP. Similarly, external software libraries could take advantage of our highly optimized AM (active message) communication layer for their own purpose. UTK with support from Sandia, developped a version of Open MPI where the entire communication infrastucture has been moved down to OPAL (btl/rcache/allocator/mpool). Most of the moved components have been updated to match the new schema, with few exceptions (mainly BTLs where I have no way of compiling/testing them). Thus, the completion of this RFC is tied to being able to completing this move for all BTLs. For this we need help from the rest of the Open MPI community, especially those supporting some of the BTLs. A non-exhaustive list of BTLs that qualify here is: mx, portals4, scif, udapl, ugni, usnic.
This commit was SVN r32317.
2014-07-26 04:47:28 +04:00
|
|
|
opal_btl_usnic_finish_put_or_send(
|
|
|
|
opal_btl_usnic_module_t *module,
|
|
|
|
opal_btl_usnic_endpoint_t *endpoint,
|
|
|
|
opal_btl_usnic_send_frag_t *frag,
|
2013-11-05 02:52:03 +04:00
|
|
|
mca_btl_base_tag_t tag)
|
|
|
|
__opal_attribute_noinline__;
|
2013-07-20 02:13:58 +04:00
|
|
|
|
|
|
|
#endif /* BTL_USNIC_SEND_H */
|