All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Czesnowicz, Przemyslaw" <przemyslaw.czesnowicz-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: "Loftus,
	Ciara" <ciara.loftus-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	Thomas Monjalon
	<thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
Cc: "dev-VfR2kkLFssw@public.gmane.org" <dev-VfR2kkLFssw@public.gmane.org>
Subject: Re: [PATCH] vhost: add interface name to virtio-net struct
Date: Thu, 18 Dec 2014 17:20:38 +0000	[thread overview]
Message-ID: <FD920D91FA434C4988D04BF2D401125919D001B3@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <74F120C019F4A64C9B78E802F6AD4CC212578FCB-kPTMFJFq+rFT4JjzTwqWc7fspsVTdybXVpNB7YpNyf8@public.gmane.org>


> 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
> 

  parent reply	other threads:[~2014-12-18 17:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-18 14:55 [PATCH] vhost: add interface name to virtio-net struct ciara.loftus-ral2JQCrhuEAvxtiuMwx3w
     [not found] ` <1418914523-24530-1-git-send-email-ciara.loftus-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-12-18 15:33   ` Thomas Monjalon
2014-12-18 17:01     ` Loftus, Ciara
     [not found]       ` <74F120C019F4A64C9B78E802F6AD4CC212578FCB-kPTMFJFq+rFT4JjzTwqWc7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-12-18 17:16         ` Xie, Huawei
2014-12-18 17:20         ` Czesnowicz, Przemyslaw [this message]
2014-12-18 16:20   ` Stephen Hemminger
2014-12-18 16:26     ` Vincent JARDIN
2014-12-18 17:03   ` Ananyev, Konstantin
     [not found]     ` <2601191342CEEE43887BDE71AB977258213C1FDC-kPTMFJFq+rEu0RiL9chJVbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-12-18 18:11       ` Loftus, Ciara

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=FD920D91FA434C4988D04BF2D401125919D001B3@IRSMSX108.ger.corp.intel.com \
    --to=przemyslaw.czesnowicz-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=ciara.loftus-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.org \
    --cc=thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.