<?xml version="1.0"?>
<help>

<InterruptModeration>
{\rtf1\ansi\ansicpg1255\deff0\deflang1037{\fonttbl{\f0\fswiss\fcharset0 Arial;}{\f1\fnil\fcharset0 Arial;}{\f2\froman\fcharset0 Times New Roman;}{\f3\fnil\fcharset2 Symbol;}}
{\colortbl ;\red0\green0\blue0;}
{\*\generator Msftedit 5.41.21.2509;}\viewkind4\uc1\pard\fi90\lang1033\b\f0\fs20 Interrupt Moderation\b0\par
\pard\li90\cf1\f1\fs16 Moderates or delays the interrupts\rquote  generation. Hence, optimizes network throughput and CPU utilization (default Enabled).\par
\pard{\pntext\f3\'B7\tab}{\*\pn\pnlvlblt\pnf3\pnindent0{\pntxtb\'B7}}\li90 When the interrupt moderation is enabled, the system accumulates interrupts and sends a sin-gle interrupt rather than a series of interrupts. An interrupt is generated after receiving 5 pack-ets or passed 10 micro seconds from receiving the first packet. \fs22\par
\fs16{\pntext\f3\'B7\tab}When the interrupt moderation is disabled, the system generates an interrupt each time a packet is received or sent. In this mode, the CPU utilization data rates increase, as the system handles a larger number of interrupts. However, the latency decreases as the packet is handled faster. \f2\fs22\par
\pard\cf0\f0\fs20\par
}
</InterruptModeration>

<RxIntModeration>
{\rtf1\ansi\ansicpg1255\deff0\deflang1037{\fonttbl{\f0\fswiss\fcharset0 Arial;}{\f1\fnil\fcharset0 Arial;}}
{\colortbl ;\red0\green0\blue0;}
{\*\generator Msftedit 5.41.21.2509;}\viewkind4\uc1\pard\li90\lang1033\b\f0\fs20 Rx Interrupt Moderation Type\b0\par
\cf1\f1\fs16 Sets the rate at which the controller moderates or delays the generation of interrupts making it possible to optimize network throughput and CPU utilization. The default setting (Adaptive) adjusts the interrupt rates dynamically depending on the traffic type and network usage. Choosing a different setting may improve network and system performance in certain configurations. \cf0\f0\par
\par
}
</RxIntModeration>


   <SendIntModCount>
{\rtf1\ansi\deff0{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\lang1033\b\f0\fs20 Interrupt Moderation TX Packet Count\par
\b0\fs16 Number of packets that need to be sent before an interrupt is generated on the send side (default
0). \par
(Default: 0)\fs20\par
}
   </SendIntModCount>
   
   <SendIntModTime>
{\rtf1\ansi\deff0{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\lang1033\b\f0\fs20 Interrupt Moderation TX Packet Time\par
\b0\fs16 Maximum elapsed time (in usec) between the sending of a packet and the generation of an interrupt even if the moderation count has not been reached (default 0)
}
   </SendIntModTime>

   <RecvIntModCount>
{\rtf1\ansi\deff0{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\lang1033\b\f0\fs20 Interrupt Moderation RX Packet Count\par
\b0\fs16 Number of packets that need to be received before an interrupt is generated on the receive side. \par
(Default: 5)\fs20\par
}
   </RecvIntModCount>
   
   <RecvIntModTime>
{\rtf1\ansi\deff0{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\lang1033\b\f0\fs20 Interrupt Moderation RX Packet Time\par
\b0\fs16 Maximum elapsed time (in usec) between the receiving of a packet and the generation of an interrupt, even if the moderation count has not been reached (Default: 0)
}
   </RecvIntModTime>

   <LargeSendOffload>
{\rtf1\ansi\ansicpg1252\deff0{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\nowidctlpar\li90\lang1033\b\f0\fs20 Large Send Offload (LSO)\par
\b0\fs16 The TCP large send offload (LSO) option allows the TCP stack to build a TCP message up to 64KB long and send it in one call down the stack. The adapter then re-segments the message into multiple TCP packets for transmission on the wire, with each pack sized according to MTU. This option offloads a large amount of kernel processing time from the host CPU to the adapter.\par
\pard\li90\fs20\par
}   </LargeSendOffload>
                            
   <JumboPacket_ETH>
{\rtf1\ansi\ansicpg1252\deff0{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\lang1033\b\f0\fs20 Maximum Frame Size (MTU)\par
\pard\nowidctlpar\li90\b0\fs16 Set the maximum size of a frame (or packet) that can be sent over the wire. This is also known as the maximum transmission unit (MTU). The MTU of a network can have a large impact on performance. The range of valid MTU values is 600 through 9600.\par
\par
\b NOTE: \b0 All devices on the same physical network, or on the same logical network if using VLAN tagging, must have the same MTU.\par
\pard\li90\fs20\par
}   </JumboPacket_ETH>

   <JumboPacket_IPoIB>
{\rtf1\ansi\ansicpg1252\deff0{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\lang1033\b\f0\fs20 Maximum Frame Size (MTU)\par
\pard\nowidctlpar\li90\b0\fs16 Set the maximum size of a frame (or packet) that can be sent over the wire. This is also known as the maximum transmission unit (MTU). The MTU of a network can have a large impact on performance. The range of valid MTU values is 1500 through 4092.\par
\par
\b NOTE: \b0 All devices on the same physical network, or on the same logical network if using VLAN tagging, must have the same MTU.\par
\pard\li90\fs20\par
}   </JumboPacket_IPoIB>
						
    <SendPollingModCount> 
{\rtf1\ansi\deff0{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\lang1033\b\f0\fs20 Polling Moderation Send Packet Count\par
\b0\fs16 Number of packets that need to be sent before a polling event on the send side. This parameter is effective only if polling mode is set.\par
(Default: 1)\fs20\par
}
    </SendPollingModCount> 

    <SendPollingModTime> 
{\rtf1\ansi\deff0{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\lang1033\b\f0\fs20 Polling Moderation Send Packet Time\par
\b0\fs16 Maximum elapsed time (in msec) between the sending of a packet and a polling event on the send side is initiated. This parameter is effective only if polling mode is set.\par
(Default: 20)\fs20\par
}
    </SendPollingModTime> 

    <IPChecksumOffloadIPv4 >
{\rtf1\ansi\ansicpg1252\deff0{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\lang1033\b\f0\fs20 IPv4 checksums Offload\par
\pard\nowidctlpar\li90\b0\fs16 This option enables the adapter to compute IPV4 checksum upon transmit and/or receive instead of the CPU. \par
By default, this parameter is enabled for transmit and receive IPv4 checksum offloading.\par
\pard\li90\fs20\par
}    </IPChecksumOffloadIPv4 >

    <TCPUDPChecksumOffloadIPv4>
{\rtf1\ansi\ansicpg1252\deff0{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\lang1033\b\f0\fs20 TCP/UDP Checksum Offload over IPv4 packets \par
\pard\nowidctlpar\li90\b0\fs16 This option enables the adapter to compute TCP/UDP checksum over IPv4 packets upon transmit and/or receive instead of the CPU.\par
By default, this parameter is enabled for transmit and receive TCP/UDP over IPv4 checksum offloading.\par
\pard\li90\fs20\par
}    </TCPUDPChecksumOffloadIPv4>

    <TCPUDPChecksumOffloadIPv6>
{\rtf1\ansi\ansicpg1252\deff0{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\lang1033\b\f0\fs20 TCP/UDP Checksum Offload over IPv6 packets \par
\pard\nowidctlpar\li90\b0\fs16 This option enables the adapter to compute TCP/UDP checksum over IPv6 packets upon transmit and/or receive instead of the CPU. \par
By default, this parameter is enabled for transmit and receive TCP/UDP over IPv6 checksum offloading.\par
\pard\li90\fs20\par
}    </TCPUDPChecksumOffloadIPv6>

    <RecvCompletionMethod>
{\rtf1\fbidis\ansi\ansicpg1252\deff0{\fonttbl{\f0\fswiss\fcharset0 Arial;}{\f1\fnil\fcharset0 Arial;}{\f2\fswiss\fcharset0 Wingdings;}{\f3\froman\fcharset0 Times New Roman;}{\f4\fnil\fcharset2 Symbol;}}
{\colortbl ;\red0\green0\blue0;}
{\*\generator Msftedit 5.41.21.2510;}\viewkind4\uc1\pard\ltrpar\li90\lang1033\b\f0\fs20 Receive completion method\par
\cf1\b0\f1\fs16 Sets the completion methods of the received packets, and can affect network throughput and CPU utilization. \f2\fs20\par
\pard{\pntext\f4\'B7\tab}{\*\pn\pnlvlblt\pnf4\pnindent0{\pntxtb\'B7}}\ltrpar\fi-360\li810\b\f1\fs16 Polling Method\f3\fs22  \b0\f1\fs16 Increases the CPU utilization as the system polls the received rings for the incoming packets. However, it may increase the network bandwidth as the incoming packet is handled faster. \cf0\f0\fs20\par
\cf1\b\f1\fs16{\pntext\f4\'B7\tab}Adaptive (Default Settings)\f3\fs22  \b0\f1\fs16 A combination of the interrupt and polling methods dynamically, depending on traffic type and network usage. Choosing a different setting may improve network and/or system performance in certain config-urations. \cf0\f0\fs20\par
}
    </RecvCompletionMethod>
    
    <ReceiveBuffers>
{\rtf1\ansi\deff0{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\lang1033\b\f0\fs20 Receive Ring Size\par
\b0\fs16 The number of packets in each receive ring.\par
(Default: 1024)\fs20\par
}
    </ReceiveBuffers>

    <SendCompletionMethod>
{\rtf1\fbidis\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fswiss\fcharset0 Arial;}{\f1\fnil\fcharset0 Arial;}}
{\colortbl ;\red0\green0\blue0;}
{\*\generator Msftedit 5.41.21.2510;}\viewkind4\uc1\pard\ltrpar\li90\b\f0\fs20 Send completion method\par
\cf1\b0\f1\fs16 Sets the completion methods of the Send packets and it may affect network throughput and CPU utilization. \cf0\f0\fs20\par
}
    </SendCompletionMethod>

    <RxRingNum>
{\rtf1\ansi\ansicpg1252\deff0{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\lang1033\b\f0\fs20 Number of Receive Rings\par
\b0\fs16 This parameter sets the number of receive rings that are used while using Receive Side Scaling (RSS). While using RSS, each ring is mapped to a CPU. Using more receive rings means more CPUs are used for receiving packets. Setting this parameter affects network throughput and CPU utilization.\par
1 queue is used when low CPU utilization is required. \par
2 queues are used when good throughput and low CPU utilization are required (Default). \par
4 or more\~queues are used for applications that demand maximum throughput and maximum transactions per second.\fs20\par
}    </RxRingNum>

    <TransmitBuffers>
{\rtf1\ansi\deff0{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\lang1033\b\f0\fs20 Send Ring Size\par
\b0\fs16 The number of packets in each send ring.\par
(Default: 2048)\fs20\par
}
    </TransmitBuffers>

    <RSS>
{\rtf1\ansi\ansicpg1252\deff0{\fonttbl{\f0\fswiss\fcharset0 Arial;}{\f1\fswiss\fprq2\fcharset0 Arial;}{\f2\fnil\fcharset2 Symbol;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\lang1033\b\f0\fs20 RSS Mode\par
\pard\nowidctlpar\li90\b0\fs16 Use RSS mode to improve the performance of handling incoming packets. This mode allows the adapter port to utilize the multiple CPUs in a multi-core system for receiving incoming packets and steering them to the destination. RSS can significantly improve the number of transactions per second, the number of connections per second, and the network throughput.\par
This parameter can be set to one of two values:\par
\pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent0{\pntxtb\'B7}}\nowidctlpar\fi-720\li810 Enabled (default): Set RSS Mode.\f1\par
\f0{\pntext\f2\'B7\tab}Disabled: In this mode, the hardware is configured once to use the Toeplitz hash function and the indirection table is never changed. Note that IOAT is not functional in this mode.\f1\par
}	</RSS>

	<VlanHelp>
{\rtf1\ansi\ansicpg1252\deff0{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\nowidctlpar\li90\lang1033\f0\fs16 This dialog allows you to configure Virtual LANs (VLANs) for the adapter.\par
\par
\b NOTE:\b0  After configuring a VLAN, the adapter associated with the VLAN may experience a momentary loss of connectivity.\par
\par
The list view has four columns: \par
\b VLAN Name:\tab\b0 Displays the assigned VLAN name.\par
\b ID: \b0\tab\tab Displays the assigned VLAN ID.\par
\b Priority:\tab\b0 Displays the assigned VLAN priority.\par
\b Status:\tab\b0\tab Displays the status of the VLAN: Up or Down.\par
\par
The dialog shows three buttons:\par
\b New:\b0\tab\tab Opens a dialog to define a new VLAN.\par
\b Remove:\b0\tab Removes the selected VLAN.\par
\b Modify:\b0\tab\tab Opens a dialog to change the selected VLAN\rquote s settings.\par
\pard\li90\fs20\par
}	</VlanHelp>

	<VlanNewHelp>
{\rtf1\ansi\ansicpg1252\deff0{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\nowidctlpar\li90\lang1033\f0\fs16 This dialog allows you to enter or modify the following VLAN properties:\par
\b VLAN Name:\b0\tab The name can be any unique alphanumeric string.\par
\b VLAN ID:\b0\tab The ID is a number between 1 and 4095.\par
\b VLAN Priority:\b0\tab The priority is a number between 0 and 7 (0- lowest; 7\endash  highest). \par
\b\par
NOTE: \b0 After creating a new VLAN, the adapter associated with the VLAN may experience a momentary loss of connectivity.\par
\pard\li90\fs20\par
}	</VlanNewHelp>

	<Flow_Control_Options>
{\rtf1\ansi\ansicpg1252\deff0{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\lang1033\b\f0\fs20 Flow Control Options\fs16\par
\b0 Allows you to control the TCP/IP traffic by pausing frame transmit and/or receive operations.\tab\par
Example: Assume that Adapter A transmits frames at a rate higher than what Adapter B can process (i.e., Adapter B runs out of buffer space before receiving all frames from Adapter A). As a result, Adapter B discards the incoming frames that it cannot buffer until the overload condition ends, and data is lost.\par
By enabling the flow control mechanism, the adapters can overcome this problem and eliminate the risk of data loss. Adapter B will generate a flow control frame when it enters the overload condition. Upon receiving the flow control frame, Adapter A will suspend further frame transmission until a specified time period has elapsed. This will allow Adapter B time to recover from the overloaded state. At the end of the specified time period, Adapter A will resume the transmission of frames. \fs20\par
}    </Flow_Control_Options>

	<FlowControl>
{\rtf1\ansi\ansicpg1252\deff0{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\lang1033\b\f0\fs20 Flow Control\par
\b0\fs16 When Rx Pause is enabled, the receiving adapter generates a flow control frame when its receive queue reaches a pre-defined limit. It sends to the sending adapter\par
\b\par
\b0\fs16 When Tx Pause is enabled, the sending adapter pauses transmission if it receives a flow control frame from a link partner.\par
\pard\li90\sb100\sa100\b NOTE:\b0  For adapters to benefit from this feature, link partners must support flow control frames.\par
\pard\li90\fs20\par
}	</FlowControl>

<HeaderDataSplit>
{\rtf1\ansi\ansicpg1252\deff0{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\lang1033\b\f0\fs20 Header Data Split\par
\b0\fs16Header-data split allows to improve network performance by splitting the header and data in received Ethernet frames into separate buffers. \par
\b0\fs16By separating the headers and the data, these services enable the headers to be collected together into smaller regions of memory. Therefore, more headers fit into a single memory page and more headers fit into the system caches, so the overhead for memory accesses in the driver stack is reduced.\par
(Default: Enabled)\fs20\par
} </HeaderDataSplit>

    <Offload_Options>
{\rtf1\ansi\ansicpg1252\deff0{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\lang1033\b\f0\fs20 Offload Options\par
\b0\fs16 Allows you to specify which TCP/IP offload settings are handled by the adapter rather than the operating system.\par
Enabling offloading services increases transmission performance. The performance increases because offload tasks (such as checksum calculations) are performed by adapter hardware rather than the operating system (and therefore with lower latency), and also CPU resources become more available for other tasks.\par
\fs20\par
}    </Offload_Options>

	<Performance_Options>
{\rtf1\ansi\deff0{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\lang1033\b\f0\fs20 Performance Options\par
\b0\fs16 Configures parameters that can improve adapter performance.\par
\fs20\par
}
  </Performance_Options>

    <LBFOHelp>
{\rtf1\ansi\ansicpg1252\deff0{\fonttbl{\f0\fswiss\fcharset0 Arial;}{\f1\fnil\fcharset2 Symbol;}}
{\colortbl ;\red127\green0\blue0;}
{\stylesheet{ Normal;}{\s1 heading 1;}{\s2 heading 2;}{\s3 heading 3;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\nowidctlpar\li90\lang1033\f0\fs16 LBFO stands for Load Balancing and Fail Over. The administrator can configure a bundle of adapters and associate up to 8 Mellanox ConnectX adapters to this bundle. LBFO should be used to increase the system reliability upon a link failure, and to balance the workload of packet transfers.\cf1\b\par
\pard\li90\cf0\b0 The following LBFO types are supported:\par
\pard\li90\sb100\sa100\b Fault Tolerance - \b0 provides redundancy through automatic fail-over from an active adapter to a standby adapter in case of switch port, cable, or adapter failure.\par
\b Send Load Balancing -\b0  provides transmit traffic load balancing and fault tolerance in the event of switch port, cable, or adapter failure. In this mode, the transmit traffic is balanced across member adapters based on the source and destination nodes. Note that only one adapter accepts all receive traffic.\par
\pard\lang1033\b\f0\fs16 Team attributes\par
\pard\li90\ul\b0 Primary\ulnone :\tab Sets the designated primary adapter of the team.\par
\ul Status\ulnone :\tab Shows the status of the specific adapter. Possible values are: Connected, Disconnected, Disabled.\par
\ul Role\ulnone :\tab Shows the current role of the adapter in the team. Possible values are: Active, Backup.\par
\pard\keepn\s3\li90\sb240\sa60\ul\b Notes\par
\pard{\pntext\f1\'B7\tab}{\*\pn\pnlvlblt\pnf1\pnindent0{\pntxtb\'B7}}\fi-720\li810\ulnone\b0 Only Mellanox ConnectX Mellanox adapters can be part of the bundle.\par
{\pntext\f1\'B7\tab}The bundle can contain up to 8 Mellanox ConnectX adapters.\par
\pard{\pntext\f1\'B7\tab}{\*\pn\pnlvlblt\pnf1\pnindent0{\pntxtb\'B7}}\fi-720\li810 All the adapters in the bundle must have the same RSS, MTU, Offloading options, and LBFO type. If you attempt to add or modify an adapter with non-compatible properties, this adapter will be removed from the bundle and an event log will be issued.\par
\pard{\pntext\f1\'B7\tab}{\*\pn\pnlvlblt\pnf1\pnindent0{\pntxtb\'B7}}\fi-720\li810 With Primary adapter disconnected, a different adapter may take Active role.\fs20\par
}    </LBFOHelp>

	<Performance_IPoIB>
{\rtf1\ansi\deff0{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\nowidctlpar\li90\lang1033\f0\fs16 In order to improve performance, you can use the performance tuning tool. You can activate the tool by choosing a scenario that you wish to tune the system for and by clicking the Run Tuning button. In this case, the tool will change several performance-related registry entries, consisting of general configurations and driver configurations, and will try to identify system services that may cause low performance. The tool will generate a log file that lists the changes it made. The\~log\~path is:\b\~\~\par
\b0 %windir%\\system32\\LogFiles\\PerformanceTuning.log \~\par
\par
\b Tuning scenarios:\b0\par\par
Single port traffic\tab\tab Improving performance for running\par\tab\tab\tab single port traffic each time.\par\par
Dual port traffic\tab\tab Improving performance for running\par\tab\tab\tab traffic on both ports simultaneously.\par\par
Forwarding traffic\tab\tab Improving performance for running\par\tab\tab\tab routing scenarios that involve both \par\tab\tab\tab ports (for example: via IXIA)\par\par
Multicast traffic\tab\tab Improving performance for running\par\tab\tab\tab multicast traffic on one of the ports\par\tab\tab\tab or both of them\par
\~\par
This tuning is needed only once after the installation, assuming that the modified entries remain unchanged. Since the modified registry entries are shared by all Mellanox NIC devices in your system, this tuning tool needs to be run for one Mellanox NIC device only.\par
\~\par
\b NOTE:\b0  You may be asked to reboot your machine in order for these changes to take effect.\par
\pard\li90\fs20\par
}}	</Performance_IPoIB>

	<Performance_ETH>
{\rtf1\ansi\deff0{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\nowidctlpar\li90\lang1033\f0\fs16 In order to improve performance, you can use the performance tuning tool. You can activate the tool by choosing a scenario that you wish to tune the system for and by clicking the Run Tuning button. In this case, the tool will change several performance-related registry entries, consisting of general configurations and driver configurations, and will try to identify system services that may cause low performance. The tool will generate a log file that lists the changes it made. The\~log\~path is:\b\~\~\par
\b0 %windir%\\system32\\LogFiles\\PerformanceTuning.log \~\par
\par
\b Tuning scenarios:\b0\par\par
Single port traffic\tab\tab Improving performance for running\par\tab\tab\tab single port traffic each time.\par\par
Single stream traffic\tab Improving performance for running\par\tab\tab\tab single stream traffic each time.\par\par
Dual port traffic\tab\tab Improving performance for running\par\tab\tab\tab traffic on both ports simultaneously.\par\par
Forwarding traffic\tab\tab Improving performance for running\par\tab\tab\tab routing scenarios that involve both \par\tab\tab\tab ports (for example: via IXIA)\par\par
Multicast traffic\tab\tab Improving performance for running\par\tab\tab\tab multicast traffic on one of the ports\par\tab\tab\tab or both of them\par
\~\par
This tuning is needed only once after the installation, assuming that the modified entries remain unchanged. Since the modified registry entries are shared by all Mellanox NIC devices in your system, this tuning tool needs to be run for one Mellanox NIC device only.\par
\~\par
\b NOTE:\b0  You may be asked to reboot your machine in order for these changes to take effect.\par
\pard\li90\fs20\par
}}	</Performance_ETH>

	<AddVlan>
{\rtf1\ansi\ansicpg1252\deff0\deflang1033\deflangfe1033{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\f0\fs20 Please wait until the VLAN installation completes...\par
}	
	</AddVlan>

	<RemoveVlan>
{\rtf1\ansi\ansicpg1252\deff0{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\lang1033\f0\fs20 Please wait until the VLAN removal completes...\par
}
	</RemoveVlan>

	<TeamConfig>
{\rtf1\ansi\ansicpg1252\deff0\deflang1033\deflangfe1033{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\f0\fs20 Please wait until the TEAM Configuration completes...\par
}	
	</TeamConfig>

	<T_CtrlReg>
{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\b\f0\fs16 Control Registers\b0\par
Tests registers the software uses to configure and send commands to the adapter controller.\par
This test includes all General Registers except the EEPROM Control/Data Register, all Receive Registers, and all Transmit Registers.\par
The test will validate the read-only bit(s) and read-write bit(s) of most control registers (MAC registers) used driver/software.\fs20\par
}	</T_CtrlReg>

	<T_FIFO>
{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\b\f0\fs16 FIFO\b0\par
Tests FIFO memory on the adapter by writing and reading patterns to and from FIFO memory.\par
}	
	</T_FIFO>

	<T_EEPROM>
{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\b\f0\fs16 EEPROM\b0\par
Reads the EEPROM contents and confirms that the checksum is correct. \par
This uses the EEPROM Control/Data Register\par
}	
	</T_EEPROM>

	<T_Interrupt>
{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\b\f0\fs16 Interrupt\b0\par
The test will validate if the hardware is capable of generating an interrupt and the driver is capable to catch the interrupt.\par
}	
	</T_Interrupt>

	<T_InternalLB>
{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\b\f0\fs16 Internal Loopback\b0\par
Tests the adapter's ability to send and receive packets by sending packets to itself. \par
This test uses both the MAC loopback and the Transceiver loopback modes.\par
}	
	</T_InternalLB>

	<T_ExternalLB>
{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\b\f0\fs16 External Full duplex Loopback\par
\b0 Tests the adapter's ability to send and receive packets by sending packets to itself.\par
}	
	</T_ExternalLB>

	<T_LED>
{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\b\f0\fs16 LED\par
\b0 The test will turn all MAC LEDs and copper PHY LEDs for a half second and off for half second for the \lquote BlinkDurationSec\rquote .\par
}	
	</T_LED>

	<T_Link>
{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\b\f0\fs16 Link\par
\b0 Tests that the adapter is linked to a valid link partner.\par
}	
	</T_Link>

	<T_Speed>
{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\b\f0\fs16 Speed\par
\b0 This tests that the adapter has auto-negotiated link speed correctly.\par
}	
	</T_Speed>

	<T_Cable>
{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\b\f0\fs16 Cable\par
\b0 Tests the cable connection and the adapter's send and receive functionality by sending proprietary packets out on the network and retrieving those same packets.  (a.k.a Ping)\par
}	
	</T_Cable>

	<PortType>
{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fswiss\fprq2\fcharset0 Arial;}{\f1\fnil\fcharset0 Calibri;}{\f2\fnil\fcharset2 Symbol;}}
{\*\generator Msftedit 5.41.21.2509;}\viewkind4\uc1\pard\li90\b\f0\fs20 Port Protocol Configuration\par
\b0\fs16This menu displays the adapter's port type and enables you to set the network protocols for the network adapter ports.\par
\par
\pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent0{\pntxtb\'B7}}\fi-360\li450 The network protocol is determined according to the NIC's Hardware Defaults port type. You can choose the protocol explicitly by selecting the port type to InfiniBand (IB)  or Ethernet (Eth). \par
{\pntext\f2\'B7\tab}To enable Auto Sensing, please choose AUTO. If the NIC supports Auto Sensing, the port protocol will be determined according to the link type. Otherwise it will start as IB.  \par
\pard
\par
\b NOTE:\b0 \par
\pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent0{\pntxtb\'B7}}\fi-360\li450
\b0When the adapter is a single port, only one port is displayed.\par
\b0When the NIC is InfiniBand or Ethernet only, the user cannot change the port type.\par
\b0RoCE is enabled by default when the port is started as Ethernet.\par
\b0Changing the port type will restart the drivers.\par
\pard
\fs20\par
}  
</PortType>
	

	<RoCE_Options>
{\rtf1\ansi\deff0{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\lang1033\b\f0\fs20 RoCE Options\par
\b0\fs16 Enables you to configure parameters related to RoCE functionality.\par
\fs20\par
}
	</RoCE_Options>

	<RoceMaxFrameSize>
{\rtf1\ansi\deff0{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\lang1033\b\f0\fs20 RoCE Max Frame Size\par
\b0\fs16 Enables you to set the maximum size of a frame (or packet) that can be sent by the RoCE protocol. This is also known as the maximum transmission unit (MTU).\par
\parValid RoCE MTU values are 256, 512, 1024, 2048. The default MTU is 1024.\par
\par
\b NOTE:\b0 \par
\b - \b0All devices that run the RoCE protocol must have the same RoCE MTU.\par
\b - \b0Ethernet packet will use the general MTU value whereas the RoCE packet will use the RoCE MTU.\par
\b - \b0When using MTU 2048 the administrator should configure the switches to support MTU 2048 or higher.\par
\fs20\par
}
	</RoceMaxFrameSize>

	<IB_Options>
{\rtf1\ansi\deff0{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\lang1033\b\f0\fs20 IB Options\par
\b0\fs16 Enables you to configure parameters related to IB functionality.\par
\fs20\par
}
	</IB_Options>

	<SaTimeout>
{\rtf1\ansi\deff0{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\lang1033\b\f0\fs20 SA Query Timeout\par
\b0\fs16 Enables you to set the  the waiting timeout in ms for a completion of one SA query\par
\parThe range of valid values is 500 through 60000. Default value is 1000 ms\par
\fs20\par
}
	</SaTimeout>

	<SaRetries>
{\rtf1\ansi\deff0{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\lang1033\b\f0\fs20 SA Query Retry Count\par
\b0\fs16 Enables you to set the  number of SA query retries when query is failed\par
\parThe range of valid values is 1 through 64. Default value is 10\par
\fs20\par
}
	</SaRetries>

<VMQ_Options>
{\rtf1\ansi\deff0{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\li90\lang1033\b\f0\fs20 VMQ Options\par
\b0\fs16 Allows you to enable or disable support for the virtual machine queue (VMQ) features of the network adapter.\par
\fs20\par
}
  </VMQ_Options>
  
	<VMQ>
{\rtf1\ansi\ansicpg1252\deff0{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2510;}\viewkind4\uc1\pard\li90\lang1033\b\f0\fs20 Virtual Machine Queues\par
\pard\nowidctlpar\li90\b0\fs16 A value that describes whether the device has enabled or disabled the VMQ feature.\par
}	
	</VMQ>

	<VMQLookaheadSplit>
{\rtf1\ansi\ansicpg1252\deff0{\fonttbl{\f0\fswiss\fprq2\fcharset0 Arial;}{\f1\fnil\fcharset0 Calibri;}}
{\*\generator Msftedit 5.41.21.2510;}\viewkind4\uc1\pard\li90\lang1033\b\f0\fs20 VMQ Lookahead Split\par
\pard\b0\fs16 A value that describes whether the device has enabled or disabled the ability to split receive buffers into lookahead and post-lookahead buffers.\lang9\f1\fs22\par
}
	</VMQLookaheadSplit>

	<VMQVlanFiltering>
{\rtf1\ansi\ansicpg1252\deff0{\fonttbl{\f0\fswiss\fprq2\fcharset0 Arial;}{\f1\fnil\fcharset0 Calibri;}}
{\*\generator Msftedit 5.41.21.2510;}\viewkind4\uc1\pard\li90\lang1033\b\f0\fs20 VMQ VLAN Filtering\par
\pard\b0\fs16 A value that describes whether the device has enabled or disabled the ability to filter network packets by using the VLAN identifier in the media access control (MAC) header.\lang9\f1\fs22\par
}
	</VMQVlanFiltering>	

</help>


