openmpi/ompi/mca/mtl/psm2/help-mtl-psm2.txt

# -*- text -*-
#
# Copyright (C) 2009. QLogic Corporation.  All rights reserved.
# Copyright (c) 2013-2017 Intel, Inc. All rights reserved.
# $COPYRIGHT$
#
# Additional copyrights may follow
#
# $HEADER$
#
[psm2 init]
Initialization of PSM2 library failed.

  Error: %s
#
[debug level]
Unable to set PSM2 debug level.

  Error: %s
#
[unable to open endpoint]
PSM2 was unable to open an endpoint. Please make sure that the network link is
active on the node and the hardware is functioning.

  Error: %s
#
[no uuid present]
Error obtaining unique transport key from ORTE (orte_precondition_transports %s
the environment).

  Local host: %s
#
[error polling network]
Error %s occurred in attempting to make network progress (psm2_mq_ipeek).
#
[error posting receive]
Unable to post application receive buffer (psm2_mq_irecv or psm2_mq_imrecv).

  Error:      %s
  Buffer:     %p
  Length:     %llu
#
[path query mechanism unknown]
Unknown path record query mechanism %s. Supported mechanisms are %s.
#
[message too big]
Message size %llu bigger than supported by PSM2 API. Max = %llu
#
[no psm2 cuda env]
Warning: Open MPI has detected that you are running in an environment with CUDA
devices present and that you are using Intel(r) Ompi-Path networking. However,
the environment variable PSM2_CUDA was not set, meaning that the PSM2 Omni-Path
networking library was not told how to handle CUDA support.

If your application uses CUDA buffers, you should set the environment variable
PSM2_CUDA to 1; otherwise, set it to 0. Setting the variable to the wrong value
can have performance implications on your application, or even cause it to
crash.

Since it was not set, Open MPI has defaulted to setting the PSM2_CUDA
environment variable to 1.

Local hostname: %s
Revert "Update to sync with OMPI master and cleanup to build" This reverts commit cb55c88a8b7817d5891ff06a447ea190b0e77479. 2016-11-22 15:03:20 -08:00			`# -- text --`
			`#`
			`# Copyright (C) 2009. QLogic Corporation. All rights reserved.`
Move help text output regarding PSM2_CUDA envvar to component init phase The messages should be printed only in the event of CUDA builds and in the presence of supporting hardware and when PSM2 MTL has actually been selected for use. To this end, move help text output to component init phase. Also use opal_setenv/unsetenv() for safer setting, unsetting of the environment variable and sanitize the help text message. Signed-off-by: Aravind Gopalakrishnan <Aravind.Gopalakrishnan@intel.com> 2017-10-10 12:14:09 -07:00			`# Copyright (c) 2013-2017 Intel, Inc. All rights reserved.`
Revert "Update to sync with OMPI master and cleanup to build" This reverts commit cb55c88a8b7817d5891ff06a447ea190b0e77479. 2016-11-22 15:03:20 -08:00			`# $COPYRIGHT$`
			`#`
			`# Additional copyrights may follow`
			`#`
			`# $HEADER$`
			`#`
			`[psm2 init]`
			`Initialization of PSM2 library failed.`

			`Error: %s`
			`#`
			`[debug level]`
			`Unable to set PSM2 debug level.`

			`Error: %s`
			`#`
			`[unable to open endpoint]`
			`PSM2 was unable to open an endpoint. Please make sure that the network link is`
			`active on the node and the hardware is functioning.`

			`Error: %s`
			`#`
			`[no uuid present]`
			`Error obtaining unique transport key from ORTE (orte_precondition_transports %s`
			`the environment).`

			`Local host: %s`
			`#`
			`[error polling network]`
			`Error %s occurred in attempting to make network progress (psm2_mq_ipeek).`
			`#`
			`[error posting receive]`
			`Unable to post application receive buffer (psm2_mq_irecv or psm2_mq_imrecv).`

			`Error: %s`
			`Buffer: %p`
PSM and PSM2 MTLs check on the max message size allowed by API. OMPI send and receive mesages use size_t for the lenght while PSM and PSM2 psm(2)mq_send/receive use uint32_t. Type size_t is 64 bits in 64 bits arch. Therefore, this patch adds a sanity check on the lenght of the message and fails gracefully. Signed-off-by: Matias Cabral <matias.a.cabral@intel.com> 2017-05-10 12:45:11 -07:00			`Length: %llu`
Revert "Update to sync with OMPI master and cleanup to build" This reverts commit cb55c88a8b7817d5891ff06a447ea190b0e77479. 2016-11-22 15:03:20 -08:00			`#`
			`[path query mechanism unknown]`
			`Unknown path record query mechanism %s. Supported mechanisms are %s.`
PSM and PSM2 MTLs check on the max message size allowed by API. OMPI send and receive mesages use size_t for the lenght while PSM and PSM2 psm(2)mq_send/receive use uint32_t. Type size_t is 64 bits in 64 bits arch. Therefore, this patch adds a sanity check on the lenght of the message and fails gracefully. Signed-off-by: Matias Cabral <matias.a.cabral@intel.com> 2017-05-10 12:45:11 -07:00			`#`
			`[message too big]`
			`Message size %llu bigger than supported by PSM2 API. Max = %llu`
Use opal_show_help to warn about PSM2_CUDA envvar setting If Open MPI is configured with CUDA, then user also should be using a CUDA build of PSM2 and therefore be setting PSM2_CUDA environment variable to 1 while using CUDA buffers for transfers. If we detect this setting to be missing, force set it. If user wants to use this build for regular (Host buffer) transfers, we allow the option of setting PSM2_CUDA=0, but print a warning message to user that it is not a recommended usage scenario. Signed-off-by: Aravind Gopalakrishnan <Aravind.Gopalakrishnan@intel.com> 2017-09-29 17:04:10 -07:00			`#`
			`[no psm2 cuda env]`
Move help text output regarding PSM2_CUDA envvar to component init phase The messages should be printed only in the event of CUDA builds and in the presence of supporting hardware and when PSM2 MTL has actually been selected for use. To this end, move help text output to component init phase. Also use opal_setenv/unsetenv() for safer setting, unsetting of the environment variable and sanitize the help text message. Signed-off-by: Aravind Gopalakrishnan <Aravind.Gopalakrishnan@intel.com> 2017-10-10 12:14:09 -07:00			`Warning: Open MPI has detected that you are running in an environment with CUDA`
			`devices present and that you are using Intel(r) Ompi-Path networking. However,`
			`the environment variable PSM2_CUDA was not set, meaning that the PSM2 Omni-Path`
			`networking library was not told how to handle CUDA support.`

			`If your application uses CUDA buffers, you should set the environment variable`
			`PSM2_CUDA to 1; otherwise, set it to 0. Setting the variable to the wrong value`
			`can have performance implications on your application, or even cause it to`
			`crash.`

			`Since it was not set, Open MPI has defaulted to setting the PSM2_CUDA`
			`environment variable to 1.`

			`Local hostname: %s`