HP IO Accelerator Driver and Management Software Version 3.2.3 Release Notes

Change log 17
• Due to a known issue, Windows Server 2003 is not supported with this release of the IO Accelerator
VSL.
• Changes to the firmware archive filename and distribution.
o When using the Windows and Solaris operating systems, the firmware archive file is now
distributed as a separate file, and no longer embedded within the IO Accelerator VSL installation
package.
o When using the Linux operating system, the firmware is still distributed as a package, but is now
also distributed as a separate firmware archive file.
o The firmware archive filename convention is now fusion_<version>-<date>.fff.
• New Virtual Controller feature available for Windows and Linux operating systems.
o For complete information on using the feature, see the Windows or Linux HP IO Accelerator VSL user
guide.
o With Virtual Controller technology each physical IO Accelerator device is split into two (virtual)
logical devices. Splitting the IO Accelerator device into two virtual devices has the following
implications:
— Latency: There is no effect on latency.
— Throughput: The total peak I/O bandwidth of the device is approximately the same.
— IOPS: Depending on the use of the virtual devices (especially the average I/O size), the peak
IOPS for each virtual device is about the same for a non-split device. The combined peak IOPS
of the two virtual devices can be nearly double that of a non-split device. For more information,
see the HP IO Accelerator VSL user guide for your platform.
— Capacity: Due to virtualization overhead, the combined capacity of the two virtual devices is
slightly less than that of a single-controller device. For a list of compatible devices and their
Virtual Controller capacities, see "Virtual Controller technology support (on page 10)."
• Added WIN_LOG_VERBOSE parameter to the Windows IO Accelerator VSL software. This parameter
expands the extent of the IO Accelerator VSL error log messages in the event log and provides
additional crucial information for troubleshooting any issues.
• Change to the device numbering in when using the Windows OS. The /dev/fctx device number
used in the command-line utilities is now assigned as the IO Accelerator VSL software initially loads.
• The NUMA affinity parameters in the Windows and Linux operating systems now use the PCI bus
number to set the affinity, and you must update any existing affinity configuration. For more information,
see the user guide for your platform.
• Separate management software releases. Starting with this IO Accelerator VSL software release, the
following management software is no longer included as part of the IO Accelerator VSL release:
o Management SDK, including:
— libfio-dev
— libfio-doc
— libvsl-dev
— libvsl-doc
o SMI-S, including:
— fio-remote-util
— fio-SMIS