-# InfiniBand Communication Management Assistant for clusters address file\r
-#\r
-# Use ib_acme utility with -G option to automatically generate a sample\r
-# acm_addr.cfg file for the current system.\r
-#\r
-# Entry format is:\r
-# address device port pkey\r
-#\r
-# The address may be one of the following:\r
-# host_name - ascii character string, up to 31 characters\r
-# address - IPv4 or IPv6 formatted address\r
-#\r
-# device name - struct ibv_device name\r
-# port number - valid port number on device (numbering starts at 1)\r
-# pkey - partition key in hex (can specify 'default' for pkey 0xFFFF)\r
-#\r
-# Up to 4 addresses can be associated with a given <device, port, pkey> tuple\r
-#\r
-# Samples:\r
-# node31 ibv_device0 1 default\r
-# node31-1 ibv_device0 1 0x00FF\r
-# node31-2 ibv_device0 2 0x00FF\r
-# 192.168.0.1 ibv_device0 1 0xFFFF\r
+# InfiniBand Communication Management Assistant for clusters address file
+#
+# Use ib_acme utility with -G option to automatically generate a sample
+# acm_addr.cfg file for the current system.
+#
+# Entry format is:
+# address device port pkey
+#
+# The address may be one of the following:
+# host_name - ascii character string, up to 31 characters
+# address - IPv4 or IPv6 formatted address
+#
+# device name - struct ibv_device name
+# port number - valid port number on device (numbering starts at 1)
+# pkey - partition key in hex (can specify 'default' for pkey 0xFFFF)
+#
+# Up to 4 addresses can be associated with a given <device, port, pkey> tuple
+#
+# Samples:
+# node31 ibv_device0 1 default
+# node31-1 ibv_device0 1 0x00FF
+# node31-2 ibv_device0 2 0x00FF
+# 192.168.0.1 ibv_device0 1 0xFFFF
# 192.168.0.2 ibv_device0 2 default
\ No newline at end of file
-# InfiniBand Multicast Communication Manager for clusters configuration file\r
-#\r
-# Use ib_acme utility with -O option to automatically generate a sample\r
-# acm_opts.cfg file for the current system.\r
-#\r
-# Entry format is:\r
-# name value\r
-\r
-# log_file:\r
-# Specifies the location of the ACM service output. The log file is used to\r
-# assist with ACM service debugging and troubleshooting. The log_file can\r
-# be set to 'stdout', 'stderr', or the name of a file.\r
-# Examples:\r
-# log_file stdout\r
-# log_file stderr\r
-# log_file /var/log/ibacm.log\r
-\r
-log_file /var/log/ibacm.log\r
-\r
-# log_level:\r
+# InfiniBand Multicast Communication Manager for clusters configuration file
+#
+# Use ib_acme utility with -O option to automatically generate a sample
+# acm_opts.cfg file for the current system.
+#
+# Entry format is:
+# name value
+
+# log_file:
+# Specifies the location of the ACM service output. The log file is used to
+# assist with ACM service debugging and troubleshooting. The log_file can
+# be set to 'stdout', 'stderr', or the name of a file.
+# Examples:
+# log_file stdout
+# log_file stderr
+# log_file /var/log/ibacm.log
+
+log_file /var/log/ibacm.log
+
+# log_level:
# Indicates the amount of detailed data written to the log file. Log levels
# should be one of the following values:
# 0 - basic configuration & errors
# 2 - verbose operation
log_level 0
-\r
-# lock_file:\r
-# Specifies the location of the ACM lock file used to ensure that only a\r
-# single instance of ACM is running.\r
-\r
-lock_file /var/lock/ibacm.pid\r
-\r
-# addr_prot:\r
-# Default resolution protocol to resolve IP addresses into IB GIDs.\r
-# Supported protocols are:\r
-# acm - Use ACM multicast protocol, which is similar to ARP.\r
-\r
-addr_prot acm\r
-\r
-# route_prot:\r
-# Default resolution protocol to resolve IB routing information.\r
-# Supported protocols are:\r
-# sa - Query SA for path record data and cache results.\r
-# acm - Use ACM multicast protocol.\r
-\r
-route_prot sa\r
-\r
-# loopback_prot:\r
-# Address and route resolution protocol to resolve local addresses\r
-# Supported protocols are:\r
-# none - Use same protocols defined for addr_prot and route_prot\r
-# local - Resolve information used locally available data\r
-\r
-loopback_prot local\r
-\r
-# server_port:\r
-# TCP port number that the server listens on.\r
-# If this value is changed, then a corresponding change is required for\r
-# client applications.\r
-\r
-server_port 6125\r
-\r
-# timeout:\r
-# Additional time, in milliseconds, that the ACM service will wait for a\r
-# response from a remote ACM service or the IB SA. The actual request\r
-# timeout is this value plus the subnet timeout.\r
-\r
-timeout 2000\r
-\r
-# retries:\r
-# Number of times that the ACM service will retry a request. This affects\r
-# both ACM multicast messages and and IB SA messages.\r
-\r
-retries 2\r
-\r
-# resolve_depth:\r
-# Specifies the maximum number of outstanding requests that can be in\r
-# progress simultaneously. A larger resolve depth allows for greater\r
-# parallelism, but increases system resource usage and subnet load.\r
-# If the number of pending requests is greater than the resolve_depth,\r
-# the additional requests will automatically be queued until some of\r
-# the previous requests complete.\r
-\r
-resolve_depth 1\r
-\r
-# sa_depth:\r
-# Specifies the maximum number of outstanding requests to the SA that\r
-# can be in progress simultaneously. A larger SA depth allows for greater\r
-# parallelism, but increases system resource usage and SA load.\r
-# If the number of pending SA requests is greater than the sa_depth,\r
-# the additional requests will automatically be queued until some of\r
-# the previous requests complete. The number of outstanding SA requests\r
-# is separate from the specified resolve_depth.\r
-\r
-sa_depth 1\r
-\r
-# send_depth:\r
-# Specifies the maximum number of outstanding requests that can be in\r
-# progress simultaneously. A larger send depth allows for greater\r
-# parallelism, but increases system resource usage and subnet load.\r
-# If the number of pending requests is greater than the send_depth,\r
-# the additional requests will automatically be queued until some of\r
-# the previous requests complete.\r
-\r
-send_depth 1\r
-\r
-# recv_depth:\r
-# Specifies the number of buffers allocated and ready to receive remote\r
-# requests. A larger receive depth consumes more system resources, but\r
-# can avoid dropping requests due to insufficient receive buffers.\r
-\r
-recv_depth 1024\r
-\r
-# min_mtu:\r
-# Indicates the minimum MTU supported by the ACM service. The ACM service\r
-# negotiates to use the largest MTU available between both sides of a\r
-# connection. It is most efficient and recommended that min_mtu be set\r
-# to the largest MTU value supported by all nodes in a cluster.\r
-\r
-min_mtu 2048\r
-\r
-# min_rate:\r
-# Indicates the minimum link rate, in Gbps, supported by the ACM service.\r
-# The ACM service negotiates to use the highest rate available between both\r
-# sides of a connection. It is most efficient and recommended that the\r
-# min_rate be set to the largest rate supported by all nodes in a cluster.\r
-\r
-min_rate 10\r
+
+# lock_file:
+# Specifies the location of the ACM lock file used to ensure that only a
+# single instance of ACM is running.
+
+lock_file /var/lock/ibacm.pid
+
+# addr_prot:
+# Default resolution protocol to resolve IP addresses into IB GIDs.
+# Supported protocols are:
+# acm - Use ACM multicast protocol, which is similar to ARP.
+
+addr_prot acm
+
+# route_prot:
+# Default resolution protocol to resolve IB routing information.
+# Supported protocols are:
+# sa - Query SA for path record data and cache results.
+# acm - Use ACM multicast protocol.
+
+route_prot sa
+
+# loopback_prot:
+# Address and route resolution protocol to resolve local addresses
+# Supported protocols are:
+# none - Use same protocols defined for addr_prot and route_prot
+# local - Resolve information used locally available data
+
+loopback_prot local
+
+# server_port:
+# TCP port number that the server listens on.
+# If this value is changed, then a corresponding change is required for
+# client applications.
+
+server_port 6125
+
+# timeout:
+# Additional time, in milliseconds, that the ACM service will wait for a
+# response from a remote ACM service or the IB SA. The actual request
+# timeout is this value plus the subnet timeout.
+
+timeout 2000
+
+# retries:
+# Number of times that the ACM service will retry a request. This affects
+# both ACM multicast messages and and IB SA messages.
+
+retries 2
+
+# resolve_depth:
+# Specifies the maximum number of outstanding requests that can be in
+# progress simultaneously. A larger resolve depth allows for greater
+# parallelism, but increases system resource usage and subnet load.
+# If the number of pending requests is greater than the resolve_depth,
+# the additional requests will automatically be queued until some of
+# the previous requests complete.
+
+resolve_depth 1
+
+# sa_depth:
+# Specifies the maximum number of outstanding requests to the SA that
+# can be in progress simultaneously. A larger SA depth allows for greater
+# parallelism, but increases system resource usage and SA load.
+# If the number of pending SA requests is greater than the sa_depth,
+# the additional requests will automatically be queued until some of
+# the previous requests complete. The number of outstanding SA requests
+# is separate from the specified resolve_depth.
+
+sa_depth 1
+
+# send_depth:
+# Specifies the maximum number of outstanding requests that can be in
+# progress simultaneously. A larger send depth allows for greater
+# parallelism, but increases system resource usage and subnet load.
+# If the number of pending requests is greater than the send_depth,
+# the additional requests will automatically be queued until some of
+# the previous requests complete.
+
+send_depth 1
+
+# recv_depth:
+# Specifies the number of buffers allocated and ready to receive remote
+# requests. A larger receive depth consumes more system resources, but
+# can avoid dropping requests due to insufficient receive buffers.
+
+recv_depth 1024
+
+# min_mtu:
+# Indicates the minimum MTU supported by the ACM service. The ACM service
+# negotiates to use the largest MTU available between both sides of a
+# connection. It is most efficient and recommended that min_mtu be set
+# to the largest MTU value supported by all nodes in a cluster.
+
+min_mtu 2048
+
+# min_rate:
+# Indicates the minimum link rate, in Gbps, supported by the ACM service.
+# The ACM service negotiates to use the highest rate available between both
+# sides of a connection. It is most efficient and recommended that the
+# min_rate be set to the largest rate supported by all nodes in a cluster.
+
+min_rate 10
projects / ~shefty / ibacm.git / commitdiff