HP IO manual Advanced configuration example

Page 68

Advanced configuration example

This example server has four NUMA nodes with eight hyper-threaded cores per node (16 logical processors per node, a total of 64 logical processors in the system). This system also uses the expansion configuration and has 11 PCIe expansion slots. During system boot, the system BIOS assigns PCIe slots 1-6 to NUMA node 2 and PCIe slots 7-11 to NUMA node 0. NUMA nodes 1 and 3 have no assigned PCIe slots. This configuration creates a load balancing problem in the system when IO Accelerator devices are under heavy traffic. During these periods of high use, half of the processors in the system sit idle while the other half of the processors are 100% utilized, thus limiting the throughput of the IO Accelerator devices.

To avoid this situation, you must manually configure the affinity of the IO Accelerator devices using the FIO_AFFINITY configuration parameter to distribute the work load across all NUMA nodes. This parameter overrides the default behavior of the IO Accelerator driver. For more information about the FIO_AFFINITY configuration parameter, refer to the syntax explanation below.

Syntax:

The following is an example of how to configure 10 HP IO Accelerator ioDrive Duo devices (each with two IO Accelerator devices) in a HP DL580 G7 system manually as described in the preceding paragraphs. Slot 1 is a Generation 1 PCIe slot, so it is not compatible with an ioDrive Duo device. Therefore you can fill slots 2-11 with ioDrive Duo devices. Because each ioDrive Duo device has two IO Accelerator devices, each ioDrive Duo devices has two device numbers (one for each IO Accelerator device). Each slot has two device numbers.

The following tables list the default BIOS NUMA node assignments.

BIOS assigned

PCIe slots

FCT device numbers

Processor Affinity

NUMA node

 

 

 

 

 

 

 

0

7-11

8,9,13,14,18,19,23,24,28,29

All processors in the node

 

 

 

 

1

None

None

None

2

2-6

135,136,140,141,145,146,150,151,

All processors in the node

 

 

155,156

 

3

None

None

None

Assigned

PCIe slots

FCT device numbers

Processor Affinity

NUMA node

 

 

 

 

 

 

 

0

7-9

8,9,13,14,18,19

All processors in the node (no hex mask)

1

10-11

23,24,28,29

All processors in the node (no hex mask)

2

2-3

135,136,140,141

All processors in the node (no hex mask)

3

4-6

145,146,150,151,155,156

All processors in the node (no hex mask)

In this example, the BIOS creates a load imbalance by assigning the cards to only two NUMA nodes in the system. To balance the work load, enter the following settings:

To configure the IO Accelerator driver with these override settings, run fio-configwith the following string:

fio-config -p FIO_AFFINITY 8,n0;9,n0;13,n0;14,n0;18,n0;19,n0;23,n1;24,n1;28,n1;29,n1;135,n2;136,n2;140, n2;141,n2;145,n3;146,n3;150,n3;151,n3;155,n3;156,n3

No <hex mask> was stipulated for any of the devices in this example (making each <affinity specification> a couplet rather than a triplet). Therefore, each device is shared among all of the

NUMA configuration 68

Image 68
Contents HP IO Accelerator Version 3.2.3 Windows User Guide Page Contents Maintenance Resources Contents summary About this guideProduct naming IntroductionOverview Performance attributes IO Accelerator capacity 320GB 640GB Models AJ878B BK836ASupported hardware Required operating environmentSupported firmware revisions Page Introduction Windows Server environments Installation overviewUninstalling a previously-installed driver Installing software on a Windows operating system Using the Setup Wizard Windows Server environments Windows Server environments Windows Server environments Windows Server environments Upgrading device firmware from VSL 1.x.x or 2.x.x to Upgrading procedure Fio-bugreportManual installation on Windows Server Fio-update-iodrive iodriveversion.fffManually installing on Windows Server Upgrading the device firmware using Windows Manually installing on Windows Server 2008Performing the upgrade Viewing the firmware versionUpgrading driver software using Windows Fio-detach /dev/fct0Windows Server environments Outdated firmware check Silent install optionDefragmentation Enabling PCIe power IO Accelerator namingWindows Server environments Creating a RAID configuration Setting up Snmp for Windows operating systemsFio-config -p Fiopreallocatememory 1072,4997,6710,10345 Snmp details for Windows operating systemsUsing test mode registry values Via garbage collectionSnmp MIB fields supporting Windows Server Snmp test registry entry DescriptionWindows Server environments Msiexec /i C\MyPackage\Example.msi /L*V C\log\example.log Using installation logsWindows Installer logging options Creating a patch install log Creating an installation logCreating an uninstall log Automated logging with the Windows Installer Logging Policy Troubleshooting event log messagesError ioDrivex Maintenance Maintenance toolsCommon maintenance tasks Uninstalling the IO Accelerator driver packageEnabling Autoattach Enabling PCIe power overrideUnmanaged shutdown issues Enabling the override parameter Fio-config /dev/fctx -p PCIeGLOBALSLOTPOWERLIMIT Fio-config /dev/fct2 -p PCIeGLOBALSLOTPOWERLIMITFio-attach UtilitiesUtilities reference Fio-beacon Fio-bugreportFio-attach device options Fio-beacon device optionsCompressing Fio-configFio-config device options Fio-config options FioexternalpoweroverrideFio-detach Fio-detach device optionsFio-format Fio-format device options deviceFio-pci-check Fio-statusFio-pci-check options Options Fio-status device optionsFfield Geometry and capacity information not available. appears Fio-sure-erase Fio-sure-erase options deviceFio-trim-config Fio-update-iodrive iodriveversion.fff options Fio-update-iodriveFio-trim-config options Options Format domainbusslot.func Monitoring IO Accelerator health Nand flash and component failureHealth metrics Health monitoring techniquesFlashback substitution events Software RAID and health monitoringMonitoring IO Accelerator health Using Trim Trim supportIntroduction to Trim Trim platformsControlling Trim aggressiveness Starting and stopping TrimEnabling Trim Trim configurations Using Windows page files with the IO Accelerator Configuring IO Accelerator paging supportIntroduction to Windows page files RAM consumptionFio-config -p Fiopreallocatememory 1234,17834 Fio-config -p FiopreallocatememoryFio-config -g Fiopreallocatememory Non-paged memory poolSetting up page files Windows page file managementSystem drive paging file configuration Guaranteeing minimum committable memoryDir c /ah Virtual Memory performanceVerifying page file operation Performance and tuning Introduction to performance and tuningDisabling Dvfs Limiting Apci C-statesSetting Numa affinity Setting the interrupt handler affinityNuma configuration Fio-config -p Fioaffinity 4,n1,0xf5,n07,g19,g2,0xff0Introduction to Numa architecture Fioaffinity parameterAdvanced configuration example Checking the log for errors Fio-config -p Fioaffinity 5,g0,0xf6,0xfFor more information Subscription serviceResources Support and other resources Before you contact HPHP contact information Customer Self RepairRéparation par le client CSR Riparazione da parte del cliente Reparaciones del propio cliente Reparo feito pelo cliente Support and other resources Support and other resources Support and other resources Regulatory information Safety and regulatory complianceWarranty information Acronyms and abbreviations NumaSMI-S Documentation feedback Index Using the IO Accelerator as a swap