HP B- Accelerators Linux manual 13,14,18,19

Page 58

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:

Manually configure the VSL driver with these override settings, and then set the numa_node_override parameter with the following string:

numa_node_override=fct8:0,fct9:0,fct13:0,fct14:0,fct18:0,fct19:0,fct23:1,fct 24:1,fct28:1,fct29:1,fct135:2,fct136:2,fct140:2,fct141:2,fct145:3,fct146:3,f ct150:3,fct151:3,fct155:3,fct156:3

NUMA configuration 58

Image 58
Contents HP IO Accelerator Version 3.2.3 Linux User Guide Page Contents Maintenance Resources Contents summary About this guideOverview IntroductionProduct naming Performance attributes IO Accelerator capacity 320GB 640GB Models AJ878B BK836ASupported firmware revisions Required operating environmentSupported hardware Introduction Introduction Installing RPM packages on SUSE, RHEL, and OEL Software installationInstallation overview $ uname -rRpm -Uvh iomemory-vsl-kernel-version-VSL-version.x8664.rpm Rpm -Uvh fio*.rpmBuilding the IO Accelerator driver from source Building an RPM installation package$ rpmbuild --rebuild iomemory-vsl-VSL-version.src.rpm Upgrading device firmware from VSL 1.x.x or 2.x.x to Fio-bugreport Upgrading procedure$ rpm -qa grep -i iomemory $ rpm -e iomemory-vsl-2.6.18-194.el5-2.2.0.82-1.0 Fio-update-iodrive iodriveversion.fff$ modprobe iomemory-vsl Controlling IO Accelerator driver loading # Provides iomemory-vsl # Required-Start boot.udevLoading the IO Accelerator driver Fio-attach /dev/fct$ chkconfig --add iomemory-vsl Using the init script$ chkconfig --del iomemory-vsl # blacklist iomemory-vslMounting filesystems Setting the IO Accelerator driver optionsUsing module parameters Handling IO Accelerator driver unloadsUpgrading the firmware One-time configurationPersistent configuration $ modprobe iomemory-vsl auto-attach=0Using the Logical Volume Manager Enabling PCIe powerUsing the device as swap Options iomemoryvsl preallocatememory=1072,4997,6710,10345Device /dev/fio Configuring RAIDDevice partitions Etc/mdadm.conf$ mdadm --detail --scan Chkconfig boot.md on Chkconfig mdadmd on$ mdadm --assemble --scan Building a RAID 10 across multiple devices Fio-statusUnderstanding Discard Trim support Discard Trim on LinuxFiles and directories Setting up Snmp for LinuxSnmp details for Linux Snmp master agentYum install net-snmp rsync Configuring the Snmp master agentInstalling the Snmp subagent Snmp agentX subagentManually running the Snmp subagent Running and configuring the Snmp subagentSubagent log file Using the Snmp sample config files Enabling Snmp test modePCI0100.0 Setting up Snmp for Linux Troubleshooting Snmp Supported Snmp MIB fieldsSnmp MIB Device LED indicators MaintenanceMaintenance tools Command-line utilitiesEnabling PCIe power override Fio-update-iodriveOptions iomemory-vsl externalpoweroverride=value Common maintenance tasksEnabling the override parameter Unloading the IO Accelerator driver Uninstalling the IO Accelerator driver RPM packageDisabling auto attach Etc/modprobe.d/iomemory-vsl.conf Unmanaged shutdown issuesDisabling the driver Options iomemoryvsl autoattach=0Fio-attach UtilitiesUtilities reference Fio-attach device optionsFio-beacon device options Fio-beaconFio-bugreport Tmp/fio-bugreport-20100121.173256-sdv9ko.tar.bz2Fio-detach Fio-detach device options Fio-formatFio-format options device Fio-pci-check Fio-pci-check optionsFio-snmp-agentx options Fio-snmp-agentxFio-status Fio-status device optionsUtilities Fio-sure-erase Fio-sure-erase options device Fio-update-iodrive Fio-update-iodrive options iodriveversion.fff Domainbusslot.func Nand flash and component failure Monitoring IO Accelerator healthHealth metrics Health monitoring techniques About flashback protection technology Software RAID and health monitoringDisabling Dvfs Performance and tuningIntroduction to performance and tuning Limiting Apci C-statesSetting Numa affinity Setting the interrupt handler affinityIntroduction to Numa architecture Numa configurationAdvanced configuration example Numa node override parameter13,14,18,19 Resources Subscription serviceFor more information Warranty information Safety and regulatory complianceRegulatory information HP contact information Support and other resourcesBefore you contact HP 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 Acronyms and abbreviations SMH Documentation feedback Index Uninstalling utilities