Steve's Power Systems BlogPower BlogContactLog inRegister
  • Power Blog
  • Contact

  • Register

IBM Power Systems Blog

Power Systems
  • Front Page
  • Categories
  • Archives
  • Latest comments
  • « AIX - What is IO Wait?
  • Script to recreate a volume group with new PVIDs »

VIO Server Virtual SCSI Adapter Limits

Posted by steve on 14 Jun 2012 in VIO Server Tips, AIX Tips

You have to be careful with the maximum number of disks per virtual adapter on VIO clients.
Use the following formula to evaluate this maximum number of disks per adapter.

 

Maximum disks per adapter = ( 512 – 2 ) / ( 3 + queue depth ).

 

Because virtual SCSI connections operate at memory speed, there is generally no performance gain from adding multiple adapters between a Virtual I/O Server and client.

For AIX virtual I/O client partitions, each adapter pair can handle up to 85 virtual devices with the default queue depth of 3.

Where the number of virtual devices per adapter are expected to exceed that number, or where the queue depth on some devices might be increased above the default, reserve additional adapter slots for the virtual I/O server and client partitions.

When tuning queue depths, the vSCSI adapters have a fixed queue depth of 512 command elements per adapter. The adapter itself uses 2 of these, 3 are reserved for each vSCSI LUN for error recovery and the rest are used for I/O requests.

So, with the default queue depth of 3 for vSCSI LUNs, that allows for up to 85 LUNs to use an adapter: (512 - 2) / (3 + 3) = 85 rounding down. If you need higher queue depths for the devices, then the number of LUNs per adapter is reduced.

Some examples:

A queue depth of 8 allows 510 / 11 = 46 LUNs per adapter.
A queue depth of 16 allows 510 / 19 = 26 LUNs per adapter.
A queue depth of 25 allows 510 / 28 = 18 LUNs per adapter.
A queue depth of 32 allows 510 / 35 = 14 LUNs per adapter.
A queue depth of 64 allows 510 / 67 = 7 LUNs per adapter.

Tags: AIXVIOVIO ServerVIOSqueue depthvSCSI

No feedback yet


Form is loading...

July 2026
Mon Tue Wed Thu Fri Sat Sun
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30 31    
 << <   > >>

IBM Power Systems Blog

IBM Power Systems - Administration, Tuning and Optimisation. These posts are my own personal opinions and comments only.

Search

Categories

  • All
  • AIX Tips
  • AIX Tuning
  • Command Line Tips
  • HMC Tips
  • LPM Information
  • NIM Tips
  • Performance Testing
  • Power System Affinity
  • PowerHA Tips
  • SRIOV and vNIC
  • Scripts and One Liners
  • VIO Server Tips

Recent Posts

  • AIX NIM Hints and Tips
  • Finding Multiple Install Sources for AIX
  • PowerHA and EMC Busy Devices
  • AIX Random Password Generation
  • VIO Server 3.1.0 and ssh host keys
  • VIO Server 3.1.0 Items to Review
  • Just when you thought you understood idle CPU time!!
  • 40Gbit Adapter Performance Testing
  • LPM Copy Time Statistics
  • IBM HMC Upgrades

Recent Comments

  • steve on How to configure IBM SRIOV Adapters
  • Howard Coles on How to configure IBM SRIOV Adapters
  • steve on AIX mpstat and lssrad part 1
  • Charin Kumjudpai on AIX mpstat and lssrad part 1
  • Gagandeep on LPM and multiple vSwitches
  • Fant Steele on VIO Server 3.1.0 and ssh host keys
  • steve on AIX NIM Hints and Tips
  • alan wilcox on AIX NIM Hints and Tips
  • steve on AIX buf_mode attribute for Virtual Ethernet Adapters
  • Bernhar on AIX buf_mode attribute for Virtual Ethernet Adapters
  • Gery on Reading VLANs from the SEA Adapter
  • steve on Reading VLANs from the SEA Adapter
  • patrice on Reading VLANs from the SEA Adapter
  • steve on Reading VLANs from the SEA Adapter
  • steve on AIX buf_mode attribute for Virtual Ethernet Adapters
  • Chris K. on AIX buf_mode attribute for Virtual Ethernet Adapters
  • jovi on AIX or VIOS Errors: 29FA8C20 and 7BFEEA1F
  • steve on AIX or VIOS Errors: 29FA8C20 and 7BFEEA1F
  • jovi on AIX or VIOS Errors: 29FA8C20 and 7BFEEA1F
  • steve on Creating EtherChannel Devices from Command Line

This collection ©2026 by Stephen Diwell • Contact • Help • CMS with Bootstrap

CMS software
Cookies are required to enable core site functionality.