Для этого сайта требуется поддержка JavaScript.
Обзор
Помощь
Вход
ports
/
openmpi
Следить
1
В избранное
1
Форкнуть
0
Вы уже форкнули openmpi
Код
Релизы
Активность
openmpi
/
orte
/
mca
/
oob
/
tcp
История
Ralph Castain
0c043dbdc9
Fix typo in var name
2015-04-02 02:32:42 -07:00
..
configure.m4
Remove the old configure option for disabling full rte support - we now use the OMPI rte framework for such purposes
2013-02-28 01:35:55 +00:00
help-oob-tcp.txt
ckpt
2015-03-28 07:59:20 -07:00
Makefile.am
Use the correct abstraction layer name for the data dirs
2014-05-08 14:32:24 +00:00
oob_tcp_common.c
We don't need to know about non-fatal errors from setting socket options
2015-03-20 07:16:31 -07:00
oob_tcp_common.h
Now that the BTLs are moving down to OPAL and becoming available to ORTE, there no longer is a need/desire to push performance in the OOB/TCP component. So we don't need multiple modules driving NICs in parallel, and can drop all the complicated distribution logic. Fall back to the simplified single module model, but retain the ability to run that module in its own progress thread if so directed.
2014-06-06 02:24:17 +00:00
oob_tcp_component.c
Fix typo in var name
2015-04-02 02:32:42 -07:00
oob_tcp_component.h
Support attempts to connect async processes by allowing the oob/tcp connection to retry the attempt to connect to a peer. Off by default, operates if someone specifies how long to wait between retry attempts.
2015-04-01 20:21:23 -07:00
oob_tcp_connection.c
Support attempts to connect async processes by allowing the oob/tcp connection to retry the attempt to connect to a peer. Off by default, operates if someone specifies how long to wait between retry attempts.
2015-04-01 20:21:23 -07:00
oob_tcp_connection.h
Now that the BTLs are moving down to OPAL and becoming available to ORTE, there no longer is a need/desire to push performance in the OOB/TCP component. So we don't need multiple modules driving NICs in parallel, and can drop all the complicated distribution logic. Fall back to the simplified single module model, but retain the ability to run that module in its own progress thread if so directed.
2014-06-06 02:24:17 +00:00
oob_tcp_hdr.h
Don't use "size_t" for the nbytes field in the header - use uint32_t to ensure that ntohl/htonl correctly match it
2013-12-23 21:39:49 +00:00
oob_tcp_listener.c
fix misc memory leaks
2015-03-05 13:58:05 +09:00
oob_tcp_listener.h
As per the RFC, bring in the ORTE async progress code and the rewrite of OOB:
2013-08-22 16:37:40 +00:00
oob_tcp_peer.h
Support attempts to connect async processes by allowing the oob/tcp connection to retry the attempt to connect to a peer. Off by default, operates if someone specifies how long to wait between retry attempts.
2015-04-01 20:21:23 -07:00
oob_tcp_ping.h
Now that the BTLs are moving down to OPAL and becoming available to ORTE, there no longer is a need/desire to push performance in the OOB/TCP component. So we don't need multiple modules driving NICs in parallel, and can drop all the complicated distribution logic. Fall back to the simplified single module model, but retain the ability to run that module in its own progress thread if so directed.
2014-06-06 02:24:17 +00:00
oob_tcp_sendrecv.c
Silence set-but-not-used warning when timing isn't enabled
2014-09-17 00:40:10 +00:00
oob_tcp_sendrecv.h
Now that the BTLs are moving down to OPAL and becoming available to ORTE, there no longer is a need/desire to push performance in the OOB/TCP component. So we don't need multiple modules driving NICs in parallel, and can drop all the complicated distribution logic. Fall back to the simplified single module model, but retain the ability to run that module in its own progress thread if so directed.
2014-06-06 02:24:17 +00:00
oob_tcp.c
Further reduce the RARP load by removing getaddrinfo for IPv6 connections. Correct typo when checking return on inet_pton. Don't consider the TCP component for apps that are launched via mpirun as it will never be used.
2015-03-16 19:42:05 -07:00
oob_tcp.h
Now that the BTLs are moving down to OPAL and becoming available to ORTE, there no longer is a need/desire to push performance in the OOB/TCP component. So we don't need multiple modules driving NICs in parallel, and can drop all the complicated distribution logic. Fall back to the simplified single module model, but retain the ability to run that module in its own progress thread if so directed.
2014-06-06 02:24:17 +00:00
owner.txt
add owner files to opa/ompi/orte mca directories
2015-02-22 15:10:23 -07:00