DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Xie, Huawei" <huawei.xie@intel.com>
To: Franck BAUDIN <Franck.BAUDIN@qosmos.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] user space vhost driver library
Date: Thu, 24 Jul 2014 15:16:12 +0000	[thread overview]
Message-ID: <C37D651A908B024F974696C65296B57B0F24517F@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <D84D5A6C1B26E448A0F35B539111D0E720F5D6@CAROUBIER.jungle.qosmos.com>

Hi Franck:
The natural wrapper for vhost library would be like port in OVDK, which you can receive from or send to. In DPDK, we have a vhost example, which demonstrates simple switching functionality between guest virtual machines.

BR
-huawei
> -----Original Message-----
> From: Franck BAUDIN [mailto:Franck.BAUDIN@qosmos.com]
> Sent: Thursday, July 24, 2014 5:23 PM
> To: Xie, Huawei; dev@dpdk.org
> Subject: RE: [dpdk-dev] [PATCH v2] user space vhost driver library
> 
> Hello,
> 
> My understanding is that this is a helper library, but not a PMD driver. Is my
> understanding correct? If so, do you plan to write a vhost PMD driver?
> 
> Regards,
> Franck.
> 
> 
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Xie, Huawei
> > Sent: vendredi 18 juillet 2014 12:03
> > To: Xie, Huawei; dev@dpdk.org
> > Subject: Re: [dpdk-dev] [PATCH v2] user space vhost driver library
> >
> > Merged two patches in previous patch set into 1.
> >
> > > -----Original Message-----
> > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Huawei Xie
> > > Sent: Friday, July 18, 2014 5:56 PM
> > > To: dev@dpdk.org
> > > Subject: [dpdk-dev] [PATCH v2] user space vhost driver library
> > >
> > > This user space vhost library is based off user space vhost example
> > > and aims to provide same API for different vhost implementations. This
> > > implementation includes user space vhost cuse driver, kernel module
> > > for eventfd proxy and vhost enqueue/dequeue functionalities.
> > >
> > > Huawei Xie (1):
> > >   vhost library support to facilitate integration with vswitch.
> > >
> > >  config/common_linuxapp                       |    7 +
> > >  lib/Makefile                                 |    1 +
> > >  lib/librte_vhost/Makefile                    |   48 ++
> > >  lib/librte_vhost/eventfd_link/Makefile       |   39 +
> > >  lib/librte_vhost/eventfd_link/eventfd_link.c |  205 ++++++
> > >  lib/librte_vhost/eventfd_link/eventfd_link.h |   79 ++
> > >  lib/librte_vhost/rte_virtio_net.h            |  192 +++++
> > >  lib/librte_vhost/vhost-net-cdev.c            |  363 ++++++++++
> > >  lib/librte_vhost/vhost-net-cdev.h            |  112 +++
> > >  lib/librte_vhost/vhost_rxtx.c                |  292 ++++++++
> > >  lib/librte_vhost/virtio-net.c                | 1002
> > ++++++++++++++++++++++++++
> > >  11 files changed, 2340 insertions(+)
> > >  create mode 100644 lib/librte_vhost/Makefile  create mode 100644
> > > lib/librte_vhost/eventfd_link/Makefile
> > >  create mode 100644 lib/librte_vhost/eventfd_link/eventfd_link.c
> > >  create mode 100644 lib/librte_vhost/eventfd_link/eventfd_link.h
> > >  create mode 100644 lib/librte_vhost/rte_virtio_net.h  create mode
> > > 100644 lib/librte_vhost/vhost-net-cdev.c  create mode 100644
> > > lib/librte_vhost/vhost-net-cdev.h  create mode 100644
> > > lib/librte_vhost/vhost_rxtx.c  create mode 100644
> > > lib/librte_vhost/virtio-net.c
> > >
> > > --
> > > 1.8.1.4
> 
> This message and any attachments (the "message") are confidential, intended
> solely for the addressees. If you are not the intended recipient, please notify the
> sender immediately by e-mail and delete this message from your system. In this
> case, you are not authorized to use, copy this message and/or disclose the
> content to any other person. E-mails are susceptible to alteration. Neither
> Qosmos nor any of its subsidiaries or affiliates shall be liable for the message if
> altered, changed or falsified.
> 
> Ce message et toutes ses pièces jointes (ci-après le "message")sont confidentiels
> et établis à l'intention exclusive de ses destinataires. Si vous avez reçu ce
> message par erreur, merci d’en informer immédiatement son émetteur par
> courrier électronique et d’effacer ce message de votre système. Dans cette
> hypothèse, vous n’êtes pas autorisé à utiliser, copier ce message et/ou en
> divulguer le contenu à un tiers. Tout message électronique est susceptible
> d'altération. Qosmos et ses filiales déclinent toute responsabilité au titre de ce
> message s'il a été altéré, déformé ou falsifié.

      reply	other threads:[~2014-07-24 15:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18  9:56 Huawei Xie
2014-07-18  9:56 ` [dpdk-dev] [PATCH v2] lib/librte_vhost: vhost library support to facilitate integration with vswitch Huawei Xie
2014-07-25 13:31   ` Long, Thomas
     [not found]   ` <C37D651A908B024F974696C65296B57B0F2487B2@SHSMSX101.ccr.corp.intel.com>
2014-07-30 10:39     ` Ananyev, Konstantin
2014-07-18 10:02 ` [dpdk-dev] [PATCH v2] user space vhost driver library Xie, Huawei
2014-07-24  9:23   ` Franck BAUDIN
2014-07-24 15:16     ` Xie, Huawei [this message]

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=C37D651A908B024F974696C65296B57B0F24517F@SHSMSX101.ccr.corp.intel.com \
    --to=huawei.xie@intel.com \
    --cc=Franck.BAUDIN@qosmos.com \
    --cc=dev@dpdk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).