Increase limits and remove restrictions for NVMe over Fiber Channel

Increase the limit of "NVMe over Fiber Channel hosts per I/O group = 16", (maybe to double that) and

REMOVE the Volume Mobility restrictions #5:  "SCSI only. Fibre Channel and iSCSI supported. NVMe not supported."

IBM has been touting the usefulness of moving to end-to-end NVMeoF connectivity for years.  And because of improvements to SCSI protocol over the past couple years (interrupt coalescing or something like that?), has "lowered the usefulness bar" of this.  Consequentially, further development in this area has been lagging - specifically the above limitations (It was also mentioned to me that there is a limit on the number of NVMe volume mappings - but I could not find this limit specified in the configurations limits and restrictions document.  Any limit to an insufficient number of supported NVMe-mapped volumes should be increased to be more on par with supported SCSI volume mappings - or at least to a few hundred volumes).

Problem is, the SCSI improvements still do NOT give a large improvement the one biggest advantage that was always touted for end-to-end NVMe connectivity:  Reduced CPU utilization.  VMware 7 adds support for NVMeo over Fiber Channel, and uses a "High-Performance Plug-in (HPP)" multipathing driver to support it.  This end-to-end NVMe protocol reduces the CPU consumption of VMware that results from SCSI interrupt requests.  Another VMWare storage improvement is available with this HPP:  You can set all IO's to bypass VMware's I/O Scheduler, which can suffer performance resulting from ESX-internal IO queueing.   Additionally, this plugin detects new NVMe-mapped volumes, and size changes of these volumes, without a need to 'rescan the bus' like you need to do with SCSI.

Our environment will, according to testing performed, benefit significantly from reduced CPU utilization on our ESX hosts as a result of implementing end-to-end NVMe over FC connectivity.  The limits, however, are concerning and making us hesitant to do so.  Please do necessary development to remove the limits as noted above.