From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Czesnowicz, Przemyslaw" Subject: Re: [PATCH] vhost: add interface name to virtio-net struct Date: Thu, 18 Dec 2014 17:20:38 +0000 Message-ID: References: <1418914523-24530-1-git-send-email-ciara.loftus@intel.com> <2861628.6qtiPmT13X@xps13> <74F120C019F4A64C9B78E802F6AD4CC212578FCB@IRSMSX106.ger.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Cc: "dev-VfR2kkLFssw@public.gmane.org" To: "Loftus, Ciara" , Thomas Monjalon Return-path: In-Reply-To: <74F120C019F4A64C9B78E802F6AD4CC212578FCB-kPTMFJFq+rFT4JjzTwqWc7fspsVTdybXVpNB7YpNyf8@public.gmane.org> Content-Language: en-US List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" > Hi Thomas, >=20 > A basic vHost use case will work, for example a single Virtual Machine wi= th a > vHost port. However normal vSwitching use cases will require the use of m= ultiple > 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 p= ackets > from. This patch resolves this issue by exposing the tap device name of t= he > 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 >=20 > Thanks, > Ciara >=20