> Hi Thomas, > > A basic vHost use case will work, for example a single Virtual Machine with a > vHost port. However normal vSwitching use cases will require the use of > multiple > vHost ports and multiple VMs. With that in mind, it is essential that the > vSwitch > has some way of knowing which vHost port it is sending to and receiving > packets > from. This patch resolves this issue by exposing the tap device name of the > vHost device. Without that information we cannot determine the particular > vHost port to send/receive from, which in the context of switching, is a > critical > problem.
Exactly. The vSwitch uses tap name to associate the virtio device with ovs port. Without this change the vhost library cannot be used in vSwitch. Regards Przemek > > Thanks, > Ciara >
