首页 > 其他分享 >btl参数完整列表

btl参数完整列表

时间:2024-11-25 15:21:53浏览次数:5  
标签:level default value 列表 参数 MCA btl data

~]# ompi_info --param btl all --level 9
             MCA btl: self (MCA v2.1.0, API v3.3.0, Component v5.0.5)
             MCA btl: sm (MCA v2.1.0, API v3.3.0, Component v5.0.5)
             MCA btl: tcp (MCA v2.1.0, API v3.3.0, Component v5.0.5)
        MCA btl base: ---------------------------------------------------
        MCA btl base: parameter "btl" (current value: "", data source: default, level: 2 user/detail, type: string)
                      Default selection set of components for the btl framework (<none> means use all components that can be found)
        MCA btl base: ---------------------------------------------------
        MCA btl base: parameter "btl_base_verbose" (current value: "error", data source: default, level: 8 dev/detail, type: int)
                      Verbosity level for the btl framework (default: 0)
                      Valid values: -1|none, 0|error, 10|component, 20|warn, 40|info, 60|trace, 80|debug, 100|max, 0-100
        MCA btl base: parameter "btl_base_include" (current value: "", data source: default, level: 9 dev/all, type: string)
        MCA btl base: parameter "btl_base_exclude" (current value: "", data source: default, level: 9 dev/all, type: string)
        MCA btl base: parameter "btl_base_warn_peer_error" (current value: "true", data source: default, level: 9 dev/all, type: bool)
                      This parameter is used to turn on warning messages when peers disconnect unexpectedly
                      Valid values: 0|f|false|disabled|no|n, 1|t|true|enabled|yes|y
        MCA btl base: parameter "btl_base_warn_component_unused" (current value: "1", data source: default, level: 9 dev/all, type: int)
                      This parameter is used to turn on warning messages when certain NICs are not used
        MCA btl self: ---------------------------------------------------
        MCA btl self: parameter "btl_self_free_list_num" (current value: "0", data source: default, level: 9 dev/all, type: int)
                      Number of fragments by default
        MCA btl self: parameter "btl_self_free_list_max" (current value: "64", data source: default, level: 9 dev/all, type: int)
                      Maximum number of fragments
        MCA btl self: parameter "btl_self_free_list_inc" (current value: "8", data source: default, level: 9 dev/all, type: int)
                      Increment by this number of fragments
        MCA btl self: parameter "btl_self_exclusivity" (current value: "65536", data source: default, level: 7 dev/basic, type: unsigned_int)
                      BTL exclusivity (must be >= 0)
        MCA btl self: informational "btl_self_atomic_flags" (current value: "", data source: default, level: 5 tuner/detail, type: unsigned_int)
                      BTL atomic support flags
                      Valid values: Comma-delimited list of:  0x1|add, 0x200|and, 0x400|or, 0x800|xor, 0x1000|land, 0x2000|lor, 0x4000|lxor, 0x10000|swap, 0x100000|min, 0x200000|max, 0x10000000|compare-and-swap, 0x20000000|global
        MCA btl self: parameter "btl_self_rndv_eager_limit" (current value: "131072", data source: default, level: 4 tuner/basic, type: size_t)
                      Size (in bytes, including header) of "phase 1" fragment sent for all large messages (must be >= 0 and <= eager_limit)
        MCA btl self: parameter "btl_self_eager_limit" (current value: "1024", data source: default, level: 4 tuner/basic, type: size_t)
                      Maximum size (in bytes, including header) of "short" messages (must be >= 1).
        MCA btl self: parameter "btl_self_get_limit" (current value: "18446744073709551615", data source: default, level: 4 tuner/basic, type: size_t)
                      Maximum size (in bytes) for btl get
        MCA btl self: parameter "btl_self_get_alignment" (current value: "0", data source: default, level: 6 tuner/all, type: size_t)
                      Alignment required for btl get
        MCA btl self: parameter "btl_self_put_limit" (current value: "18446744073709551615", data source: default, level: 4 tuner/basic, type: size_t)
                      Maximum size (in bytes) for btl put
        MCA btl self: parameter "btl_self_put_alignment" (current value: "0", data source: default, level: 6 tuner/all, type: size_t)
                      Alignment required for btl put
        MCA btl self: parameter "btl_self_accelerator_max_send_size" (current value: "0", data source: default, level: 4 tuner/basic, type: size_t)
                      Maximum size (in bytes) of a single GPU "phase 2" fragment of a long message when using the pipeline protocol (must be >= 1) (only valid on smcuda btl)
        MCA btl self: parameter "btl_self_max_send_size" (current value: "16384", data source: default, level: 4 tuner/basic, type: size_t)
                      Maximum size (in bytes) of a single "phase 2" fragment of a long message when using the pipeline protocol (must be >= 1)
        MCA btl self: parameter "btl_self_rdma_pipeline_send_length" (current value: "2147483647", data source: default, level: 4 tuner/basic, type: size_t)
                      Length of the "phase 2" portion of a large message (in bytes) when using the pipeline protocol.  This part of the message will be split into fragments of size max_send_size and sent using send/receive semantics (must be >= 0; only relevant when the PUT flag is set)
        MCA btl self: parameter "btl_self_rdma_pipeline_frag_size" (current value: "2147483647", data source: default, level: 4 tuner/basic, type: size_t)
                      Maximum size (in bytes) of a single "phase 3" fragment from a long message when using the pipeline protocol.  These fragments will be sent using RDMA semantics (must be >= 1; only relevant when the PUT flag is set)
        MCA btl self: parameter "btl_self_min_rdma_pipeline_size" (current value: "2147484671", data source: default, level: 4 tuner/basic, type: size_t)
                      Messages smaller than this size (in bytes) will not use the RDMA pipeline protocol.  Instead, they will be split into fragments of max_send_size and sent using send/receive semantics (must be >=0, and is automatically adjusted up to at least (eager_limit+btl_rdma_pipeline_send_length); only relevant when the PUT flag is set)
        MCA btl self: parameter "btl_self_latency" (current value: "0", data source: default, level: 5 tuner/detail, type: unsigned_int)
                      Approximate latency of interconnect (0 = auto-detect value at run-time [not supported in all BTL modules], >= 1 = latency in microseconds)
        MCA btl self: parameter "btl_self_bandwidth" (current value: "100", data source: default, level: 5 tuner/detail, type: unsigned_int)
                      Approximate maximum bandwidth of interconnect (0 = auto-detect value at run-time [not supported in all BTL modules], >= 1 = bandwidth in Mbps)
          MCA btl sm: ---------------------------------------------------
          MCA btl sm: parameter "btl_sm_free_list_num" (current value: "8", data source: default, level: 9 dev/all, type: int, synonyms: btl_vader_free_list_num)
                      Initial number of fragments to allocate for shared memory communication.
          MCA btl sm: parameter "btl_sm_free_list_max" (current value: "512", data source: default, level: 9 dev/all, type: int, synonyms: btl_vader_free_list_max)
                      Maximum number of fragments to allocate for shared memory communication.
          MCA btl sm: parameter "btl_sm_free_list_inc" (current value: "64", data source: default, level: 9 dev/all, type: int, synonyms: btl_vader_free_list_inc)
                      Number of fragments to create on each allocation.
          MCA btl sm: parameter "btl_sm_memcpy_limit" (current value: "524288", data source: default, level: 5 tuner/detail, type: int, synonyms: btl_vader_memcpy_limit)
                      Message size to switch from using memmove to memcpy. The relative speed of these two routines can vary by size.
          MCA btl sm: parameter "btl_sm_segment_size" (current value: "16777216", data source: default, level: 5 tuner/detail, type: int, synonyms: btl_vader_segment_size)
                      Maximum size of all shared memory buffers (default: 16M)
          MCA btl sm: parameter "btl_sm_max_inline_send" (current value: "256", data source: default, level: 5 tuner/detail, type: unsigned_int, synonyms: btl_vader_max_inline_send)
                      Maximum size to transfer using copy-in copy-out semantics
          MCA btl sm: parameter "btl_sm_fbox_threshold" (current value: "16", data source: default, level: 5 tuner/detail, type: unsigned_int, synonyms: btl_vader_fbox_threshold)
                      Number of sends required before an eager send buffer is setup for a peer (default: 16)
          MCA btl sm: parameter "btl_sm_fbox_max" (current value: "32", data source: default, level: 5 tuner/detail, type: unsigned_int, synonyms: btl_vader_fbox_max)
                      Maximum number of eager send buffers to allocate (default: 32)
          MCA btl sm: parameter "btl_sm_fbox_size" (current value: "4096", data source: default, level: 5 tuner/detail, type: unsigned_int, synonyms: btl_vader_fbox_size)
                      Size of per-peer fast transfer buffers (default: 4k)
          MCA btl sm: parameter "btl_sm_backing_directory" (current value: "/dev/shm", data source: default, level: 3 user/all, type: string, synonyms: btl_vader_backing_directory)
                      Directory to place backing files for shared memory communication. This directory should be on a local filesystem such as /tmp or /dev/shm (default: (linux) /dev/shm, (others) session directory)
          MCA btl sm: parameter "btl_sm_exclusivity" (current value: "65536", data source: default, level: 7 dev/basic, type: unsigned_int, synonyms: btl_vader_exclusivity)
                      BTL exclusivity (must be >= 0)
          MCA btl sm: parameter "btl_sm_flags" (current value: "send,inplace", data source: default, level: 5 tuner/detail, type: unsigned_int, synonyms: btl_vader_flags)
                      BTL bit flags (general flags: send, put, get, in-place, hetero-rdma, atomics, fetching-atomics)
                      Valid values: Comma-delimited list of:  0x1|send, 0x2|put, 0x4|get, 0x8|inplace, 0x4000|signaled, 0x8000|atomics, 0x10000|fetching-atomics, 0x20000|static, 0x400|accelerator-put, 0x800|accelerator-get, 0x1000|accelerator-async-send, 0x2000|accelerator-async-recv, 0x200|failover, 0x10|need-ack, 0x20|need-csum, 0x100|hetero-rdma, 0x80000|rdma-flush, 0x100000|put-am, 0x200000|get_am, 0x400000|atomic-am
          MCA btl sm: informational "btl_sm_atomic_flags" (current value: "", data source: default, level: 5 tuner/detail, type: unsigned_int, synonyms: btl_vader_atomic_flags)
                      BTL atomic support flags
                      Valid values: Comma-delimited list of:  0x1|add, 0x200|and, 0x400|or, 0x800|xor, 0x1000|land, 0x2000|lor, 0x4000|lxor, 0x10000|swap, 0x100000|min, 0x200000|max, 0x10000000|compare-and-swap, 0x20000000|global
          MCA btl sm: parameter "btl_sm_rndv_eager_limit" (current value: "32768", data source: default, level: 4 tuner/basic, type: size_t, synonyms: btl_vader_rndv_eager_limit)
                      Size (in bytes, including header) of "phase 1" fragment sent for all large messages (must be >= 0 and <= eager_limit)
          MCA btl sm: parameter "btl_sm_eager_limit" (current value: "4096", data source: default, level: 4 tuner/basic, type: size_t, synonyms: btl_vader_eager_limit)
                      Maximum size (in bytes, including header) of "short" messages (must be >= 1).
          MCA btl sm: parameter "btl_sm_accelerator_max_send_size" (current value: "0", data source: default, level: 4 tuner/basic, type: size_t, synonyms: btl_vader_accelerator_max_send_size)
                      Maximum size (in bytes) of a single GPU "phase 2" fragment of a long message when using the pipeline protocol (must be >= 1) (only valid on smcuda btl)
          MCA btl sm: parameter "btl_sm_max_send_size" (current value: "32768", data source: default, level: 4 tuner/basic, type: size_t, synonyms: btl_vader_max_send_size)
                      Maximum size (in bytes) of a single "phase 2" fragment of a long message when using the pipeline protocol (must be >= 1)
       MCA btl vader: ---------------------------------------------------
       MCA btl vader: parameter "btl_vader_free_list_num" (current value: "8", data source: default, level: 9 dev/all, type: int, synonym of: btl_sm_free_list_num)
                      Initial number of fragments to allocate for shared memory communication.
       MCA btl vader: parameter "btl_vader_free_list_max" (current value: "512", data source: default, level: 9 dev/all, type: int, synonym of: btl_sm_free_list_max)
                      Maximum number of fragments to allocate for shared memory communication.
       MCA btl vader: parameter "btl_vader_free_list_inc" (current value: "64", data source: default, level: 9 dev/all, type: int, synonym of: btl_sm_free_list_inc)
                      Number of fragments to create on each allocation.
       MCA btl vader: parameter "btl_vader_memcpy_limit" (current value: "524288", data source: default, level: 5 tuner/detail, type: int, synonym of: btl_sm_memcpy_limit)
                      Message size to switch from using memmove to memcpy. The relative speed of these two routines can vary by size.
       MCA btl vader: parameter "btl_vader_segment_size" (current value: "16777216", data source: default, level: 5 tuner/detail, type: int, synonym of: btl_sm_segment_size)
                      Maximum size of all shared memory buffers (default: 16M)
       MCA btl vader: parameter "btl_vader_max_inline_send" (current value: "256", data source: default, level: 5 tuner/detail, type: unsigned_int, synonym of: btl_sm_max_inline_send)
                      Maximum size to transfer using copy-in copy-out semantics
       MCA btl vader: parameter "btl_vader_fbox_threshold" (current value: "16", data source: default, level: 5 tuner/detail, type: unsigned_int, synonym of: btl_sm_fbox_threshold)
                      Number of sends required before an eager send buffer is setup for a peer (default: 16)
       MCA btl vader: parameter "btl_vader_fbox_max" (current value: "32", data source: default, level: 5 tuner/detail, type: unsigned_int, synonym of: btl_sm_fbox_max)
                      Maximum number of eager send buffers to allocate (default: 32)
       MCA btl vader: parameter "btl_vader_fbox_size" (current value: "4096", data source: default, level: 5 tuner/detail, type: unsigned_int, synonym of: btl_sm_fbox_size)
                      Size of per-peer fast transfer buffers (default: 4k)
       MCA btl vader: parameter "btl_vader_backing_directory" (current value: "/dev/shm", data source: default, level: 3 user/all, type: string, synonym of: btl_sm_backing_directory)
                      Directory to place backing files for shared memory communication. This directory should be on a local filesystem such as /tmp or /dev/shm (default: (linux) /dev/shm, (others) session directory)
       MCA btl vader: parameter "btl_vader_exclusivity" (current value: "65536", data source: default, level: 7 dev/basic, type: unsigned_int, synonym of: btl_sm_exclusivity)
                      BTL exclusivity (must be >= 0)
       MCA btl vader: parameter "btl_vader_flags" (current value: "send,inplace", data source: default, level: 5 tuner/detail, type: unsigned_int, synonym of: btl_sm_flags)
                      BTL bit flags (general flags: send, put, get, in-place, hetero-rdma, atomics, fetching-atomics)
                      Valid values: Comma-delimited list of:  0x1|send, 0x2|put, 0x4|get, 0x8|inplace, 0x4000|signaled, 0x8000|atomics, 0x10000|fetching-atomics, 0x20000|static, 0x400|accelerator-put, 0x800|accelerator-get, 0x1000|accelerator-async-send, 0x2000|accelerator-async-recv, 0x200|failover, 0x10|need-ack, 0x20|need-csum, 0x100|hetero-rdma, 0x80000|rdma-flush, 0x100000|put-am, 0x200000|get_am, 0x400000|atomic-am
       MCA btl vader: parameter "btl_vader_atomic_flags" (current value: "", data source: default, level: 5 tuner/detail, type: unsigned_int, synonym of: btl_sm_atomic_flags)
                      BTL atomic support flags
                      Valid values: Comma-delimited list of:  0x1|add, 0x200|and, 0x400|or, 0x800|xor, 0x1000|land, 0x2000|lor, 0x4000|lxor, 0x10000|swap, 0x100000|min, 0x200000|max, 0x10000000|compare-and-swap, 0x20000000|global
       MCA btl vader: parameter "btl_vader_rndv_eager_limit" (current value: "32768", data source: default, level: 4 tuner/basic, type: size_t, synonym of: btl_sm_rndv_eager_limit)
                      Size (in bytes, including header) of "phase 1" fragment sent for all large messages (must be >= 0 and <= eager_limit)
       MCA btl vader: parameter "btl_vader_eager_limit" (current value: "4096", data source: default, level: 4 tuner/basic, type: size_t, synonym of: btl_sm_eager_limit)
                      Maximum size (in bytes, including header) of "short" messages (must be >= 1).
       MCA btl vader: parameter "btl_vader_accelerator_max_send_size" (current value: "0", data source: default, level: 4 tuner/basic, type: size_t, synonym of: btl_sm_accelerator_max_send_size)
                      Maximum size (in bytes) of a single GPU "phase 2" fragment of a long message when using the pipeline protocol (must be >= 1) (only valid on smcuda btl)
       MCA btl vader: parameter "btl_vader_max_send_size" (current value: "32768", data source: default, level: 4 tuner/basic, type: size_t, synonym of: btl_sm_max_send_size)
                      Maximum size (in bytes) of a single "phase 2" fragment of a long message when using the pipeline protocol (must be >= 1)
       MCA btl vader: parameter "btl_vader_major_version" (current value: "5", data source: default, level: 9 dev/all, type: int, synonym of: btl_sm_major_version)
       MCA btl vader: parameter "btl_vader_minor_version" (current value: "0", data source: default, level: 9 dev/all, type: int, synonym of: btl_sm_minor_version)
       MCA btl vader: parameter "btl_vader_release_version" (current value: "5", data source: default, level: 9 dev/all, type: int, synonym of: btl_sm_release_version)
         MCA btl tcp: ---------------------------------------------------
         MCA btl tcp: parameter "btl_tcp_links" (current value: "1", data source: default, level: 4 tuner/basic, type: unsigned_int)
         MCA btl tcp: parameter "btl_tcp_if_include" (current value: "", data source: default, level: 1 user/basic, type: string)
                      Comma-delimited list of devices and/or CIDR notation of networks to use for MPI communication (e.g., "eth0,192.168.0.0/16").  Mutually exclusive with btl_tcp_if_exclude.
         MCA btl tcp: parameter "btl_tcp_if_exclude" (current value: "127.0.0.1/8,sppp", data source: default, level: 1 user/basic, type: string)
                      Comma-delimited list of devices and/or CIDR notation of networks to NOT use for MPI communication -- all devices not matching these specifications will be used (e.g., "eth0,192.168.0.0/16").  If set to a non-default value, it is mutually exclusive with btl_tcp_if_include.
         MCA btl tcp: parameter "btl_tcp_free_list_num" (current value: "8", data source: default, level: 5 tuner/detail, type: int)
         MCA btl tcp: parameter "btl_tcp_free_list_max" (current value: "-1", data source: default, level: 5 tuner/detail, type: int)
         MCA btl tcp: parameter "btl_tcp_free_list_inc" (current value: "32", data source: default, level: 5 tuner/detail, type: int)
         MCA btl tcp: parameter "btl_tcp_sndbuf" (current value: "0", data source: default, level: 4 tuner/basic, type: int)
                      The size of the send buffer socket option for each connection.  Modern TCP stacks generally are smarter than a fixed size and in some situations setting a buffer size explicitly can actually lower performance.  0 means the tcp btl will not try to set a send buffer size.
         MCA btl tcp: parameter "btl_tcp_rcvbuf" (current value: "0", data source: default, level: 4 tuner/basic, type: int)
                      The size of the receive buffer socket option for each connection.  Modern TCP stacks generally are smarter than a fixed size and in some situations setting a buffer size explicitly can actually lower performance.  0 means the tcp btl will not try to set a receive buffer size.
         MCA btl tcp: parameter "btl_tcp_endpoint_cache" (current value: "30720", data source: default, level: 4 tuner/basic, type: int)
                      The size of the internal cache for each TCP connection. This cache is used to reduce the number of syscalls, by replacing them with memcpy. Every read will read the expected data plus the amount of the endpoint_cache
         MCA btl tcp: parameter "btl_tcp_use_nagle" (current value: "0", data source: default, level: 4 tuner/basic, type: int)
                      Whether to use Nagle's algorithm or not (using Nagle's algorithm may increase short message latency)
         MCA btl tcp: parameter "btl_tcp_port_min_v4" (current value: "1024", data source: default, level: 2 user/detail, type: int)
                      The minimum port where the TCP BTL will try to bind (default 1024)
         MCA btl tcp: parameter "btl_tcp_port_range_v4" (current value: "64511", data source: default, level: 2 user/detail, type: int)
                      The number of ports where the TCP BTL will try to bind (default 64511). This parameter together with the port min, define a range of ports where Open MPI will open sockets.
         MCA btl tcp: parameter "btl_tcp_progress_thread" (current value: "0", data source: default, level: 1 user/basic, type: int)
         MCA btl tcp: parameter "btl_tcp_warn_all_unfound_interfaces" (current value: "false", data source: default, level: 2 user/detail, type: bool)
                      Issue a warning for all unfound interfaces included in if_exclude
                      Valid values: 0|f|false|disabled|no|n, 1|t|true|enabled|yes|y
         MCA btl tcp: parameter "btl_tcp_exclusivity" (current value: "100", data source: default, level: 7 dev/basic, type: unsigned_int)
                      BTL exclusivity (must be >= 0)
         MCA btl tcp: parameter "btl_tcp_flags" (current value: "send,put,inplace,need-ack,need-csum,hetero-rdma", data source: default, level: 5 tuner/detail, type: unsigned_int)
                      BTL bit flags (general flags: send, put, get, in-place, hetero-rdma, atomics, fetching-atomics)
                      Valid values: Comma-delimited list of:  0x1|send, 0x2|put, 0x4|get, 0x8|inplace, 0x4000|signaled, 0x8000|atomics, 0x10000|fetching-atomics, 0x20000|static, 0x400|accelerator-put, 0x800|accelerator-get, 0x1000|accelerator-async-send, 0x2000|accelerator-async-recv, 0x200|failover, 0x10|need-ack, 0x20|need-csum, 0x100|hetero-rdma, 0x80000|rdma-flush, 0x100000|put-am, 0x200000|get_am, 0x400000|atomic-am
         MCA btl tcp: informational "btl_tcp_atomic_flags" (current value: "", data source: default, level: 5 tuner/detail, type: unsigned_int)
                      BTL atomic support flags
                      Valid values: Comma-delimited list of:  0x1|add, 0x200|and, 0x400|or, 0x800|xor, 0x1000|land, 0x2000|lor, 0x4000|lxor, 0x10000|swap, 0x100000|min, 0x200000|max, 0x10000000|compare-and-swap, 0x20000000|global
         MCA btl tcp: parameter "btl_tcp_rndv_eager_limit" (current value: "65536", data source: default, level: 4 tuner/basic, type: size_t)
                      Size (in bytes, including header) of "phase 1" fragment sent for all large messages (must be >= 0 and <= eager_limit)
         MCA btl tcp: parameter "btl_tcp_eager_limit" (current value: "65536", data source: default, level: 4 tuner/basic, type: size_t)
                      Maximum size (in bytes, including header) of "short" messages (must be >= 1).
         MCA btl tcp: parameter "btl_tcp_put_limit" (current value: "18446744073709551615", data source: default, level: 4 tuner/basic, type: size_t)
                      Maximum size (in bytes) for btl put
         MCA btl tcp: parameter "btl_tcp_put_alignment" (current value: "0", data source: default, level: 6 tuner/all, type: size_t)
                      Alignment required for btl put
         MCA btl tcp: parameter "btl_tcp_accelerator_max_send_size" (current value: "0", data source: default, level: 4 tuner/basic, type: size_t)
                      Maximum size (in bytes) of a single GPU "phase 2" fragment of a long message when using the pipeline protocol (must be >= 1) (only valid on smcuda btl)
         MCA btl tcp: parameter "btl_tcp_max_send_size" (current value: "131072", data source: default, level: 4 tuner/basic, type: size_t)
                      Maximum size (in bytes) of a single "phase 2" fragment of a long message when using the pipeline protocol (must be >= 1)
         MCA btl tcp: parameter "btl_tcp_rdma_pipeline_send_length" (current value: "131072", data source: default, level: 4 tuner/basic, type: size_t)
                      Length of the "phase 2" portion of a large message (in bytes) when using the pipeline protocol.  This part of the message will be split into fragments of size max_send_size and sent using send/receive semantics (must be >= 0; only relevant when the PUT flag is set)
         MCA btl tcp: parameter "btl_tcp_rdma_pipeline_frag_size" (current value: "2147482624", data source: default, level: 4 tuner/basic, type: size_t)
                      Maximum size (in bytes) of a single "phase 3" fragment from a long message when using the pipeline protocol.  These fragments will be sent using RDMA semantics (must be >= 1; only relevant when the PUT flag is set)
         MCA btl tcp: parameter "btl_tcp_min_rdma_pipeline_size" (current value: "196608", data source: default, level: 4 tuner/basic, type: size_t)
                      Messages smaller than this size (in bytes) will not use the RDMA pipeline protocol.  Instead, they will be split into fragments of max_send_size and sent using send/receive semantics (must be >=0, and is automatically adjusted up to at least (eager_limit+btl_rdma_pipeline_send_length); only relevant when the PUT flag is set)
         MCA btl tcp: parameter "btl_tcp_latency" (current value: "0", data source: default, level: 5 tuner/detail, type: unsigned_int)
                      Approximate latency of interconnect (0 = auto-detect value at run-time [not supported in all BTL modules], >= 1 = latency in microseconds)
         MCA btl tcp: parameter "btl_tcp_bandwidth" (current value: "0", data source: default, level: 5 tuner/detail, type: unsigned_int)
                      Approximate maximum bandwidth of interconnect (0 = auto-detect value at run-time [not supported in all BTL modules], >= 1 = bandwidth in Mbps)
         MCA btl tcp: parameter "btl_tcp_disable_family" (current value: "0", data source: default, level: 2 user/detail, type: int)

标签:level,default,value,列表,参数,MCA,btl,data
From: https://www.cnblogs.com/honghu0420/p/18567621

相关文章

  • mybatis的拓展-----mybatis的内置参数和OGNL表达式的使用
    mybatis的两个内置参数1,_parameter代表整个参数单个参数,_parameter就是这个参数多个参数会被封装成一个map,_parameter就是代表这个map例如接口中有一个方法 publicList<Employee>getEmpsTestInnerParameter(Employeeemployee);_parameter就代表employee对象2,_database......
  • Qt托盘消息通知(③托盘消息列表)
    实现思路创建消息窗口:使用 QWidget 或 QDialog 来创建一个显示消息的窗口。使用 QListWidget:在消息窗口中使用 QListWidget 来动态显示消息。添加滑块:如果消息数量超过5条,使用 QScrollArea 来实现滑动功能。更新消息列表:每次接收到新的消息时更新消息列表。完整代......
  • [转]Docker/DockerHub 国内镜像源/加速列表(11月23日更新-长期维护)
    原文地址:Docker/DockerHub国内镜像源/加速列表(11月23日更新-长期维护)-轩辕博客文章目录 [隐藏]1 前言2 更新日志3 使用教程3.0.0.1 为了加速镜像拉取,使用以下命令设置registrymirror3.0.0.2 使用DockerHub代理,以下以docker.linkedbus.com 为例:可以根......
  • 【C++语法】构造函数初始化列表
    初始化列表相较于在构造函数体中赋值,有以下几个优势:1.避免多次构造对于某些类型的成员变量(如const或引用类型),它们必须在初始化列表中进行初始化,不能在构造函数体中赋值。例如:classExample{  private:    constinta;//常量成员    int&ref;......
  • Python内置数据结构:列表篇:【】,list函数创建。列表创建常见遇到问题,索引,列表增删改查,常
    介绍:列表元组字典集合列表: 方括号【】和list函数是列表最常用的两种定义方式。我们暂且称列表内的东西为元素,列表内的元素以逗号分隔开。列表的初始化:空列表,有数值是列表的两种初始化情况。使用方括号创建列表:【】a=[]#创建了一个空列表并将其赋值给了a我们可以称a为一......
  • gateway拦截器获取请求参数
    packagecom.dp.config;importorg.springframework.cloud.gateway.filter.GatewayFilterChain;importorg.springframework.cloud.gateway.filter.GlobalFilter;importorg.springframework.cloud.gateway.filter.factory.rewrite.CachedBodyOutputMessage;importorg.s......
  • Java学习笔记--对象数组,方法参数,命令行参数,快速生成方法
    目录一,对象数组Personp=newPerson();二,方法参数1.基本数据类型做方法参数传递2.引用数据类型做方法参数传递三,命令行参数四,快速生成方法1.快速生成方法2.快速将一段代码抽取到一个方法中 一,对象数组Person[]arr=newPerson[3];Personp=newPerson();......
  • 【淘汰9成NLP面试者的高频面题】RNN是如何基于时间进行参数学习(BPTT)的?
    【淘汰9成NLP面试者的高频面题】RNN是如何基于时间进行参数学习(BPTT)的?重要性:★★本题主要考察面试者有有以下几点:①理解RNN循环的概念,认识到截断的BPTT的必要性②理解深度学习框架在处理反向传播时需要在保存各个时刻的中间(前向计算)数据,会消耗大量的显存这是我常用......
  • 使用 JavaScript 的 XMLHttpRequest 或 Fetch API 发送 HTTP 请求时,GET 请求和 POST
    使用JavaScript的XMLHttpRequest或FetchAPI发送HTTP请求时,GET请求和POST请求处理参数的方式不同,这与HTTP协议的设计有关GET请求的参数特点:GET请求的参数通过URL传递。原因:URL表现方式:GET请求的主要目的是从服务器获取资源。URL是资源的唯一标识,因此GET......
  • windows C#-取消任务列表(上)
    如果不想等待异步控制台应用程序完成,可以取消该应用程序。通过遵循本文的示例,可将取消添加到下载网站内容的应用程序。可通过将CancellationTokenSource实例与每个任务进行关联来取消多个任务。如果选择Enter键,则将取消所有尚未完成的任务。创建示例应用程序创建新的......