With more and more storage controller hardware supporting SR-IOV in next couple of years it seems to make sense at this point to discuss, from a storage stack perspective, managing how we instantiate and manage SR-IOV virtual functions (VFs). Currently for hardware that does support SR-IOV, the management of that functionality is managed entirely by the hardware device driver. However, a more dynamic management to how VFs are created and destroyed (assuming the hardware supports it) may be more desirable since the most common use case, assigning VFs to virtual guests, also tends to be very dynamic and fluid. We also need to consider how VFs interact with complimentary technology such as NPIV in Fibre Channel. I'd like to propose that we discuss the following issues to see if a consensus can be reached about how to deal with them: * VF instantiation * VF/NPIV port pairing * Namespace management * LUN presentation Any other subtopics to add to this discussion are obviously welcomed. Thanks, Chad This message and any attached documents contain information from QLogic Corporation or its wholly-owned subsidiaries that may be confidential. If you are not the intended recipient, you may not read, copy, distribute, or use this information. If you have received this transmission in error, please notify the sender immediately by reply e-mail and then delete this message. -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
