DPDK usage discussions
 help / color / mirror / Atom feed
From: "Avi Cohen (A)" <avi.cohen@huawei.com>
To: "Tan, Jianfeng" <jianfeng.tan@intel.com>,
	"dpdk-ovs@lists.01.org" <dpdk-ovs@lists.01.org>,
	"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] VIRTIO  for containers
Date: Mon, 26 Jun 2017 12:06:00 +0000	[thread overview]
Message-ID: <B84047ECBD981D4B93EAE5A6245AA361013C8E03@FRAEML521-MBX.china.huawei.com> (raw)
In-Reply-To: <ED26CBA2FAD1BF48A8719AEF02201E36512186DE@SHSMSX103.ccr.corp.intel.com>

Thank You Jianfeng

> We have developed virtio-user + vhost-kernel as the backend. In that
> scenario, you can add the tap interface into a container network namespace.
> And there's a vhost kthread to push the data out to user space.
> 
> And I cannot guarantee the performance as it has diametric model in VM
> (virtio) - OVS-DPDK (vhost).
> 
[Avi Cohen (A)] 
Can you refer to a document how to run this setup?
Best Regards
avi
> 
> > I've tested the performance of a container connected to OVS-DPDK  via
> > vdev-af_packet  and processed by virtual PMD, and its performance is
> > good [uses mmap'ed to userspace  - zero copy RX/TX ring buffer] but
> > not good as  the performance  of a  VM connected  to OVS-DPDK (@host)
> > via vhost-user virtio.
> > Best Regards
> > avi
> >
> > > -----Original Message-----
> > > From: Tan, Jianfeng [mailto:jianfeng.tan@intel.com]
> > > Sent: Monday, 26 June, 2017 6:15 AM
> > > To: Avi Cohen (A); dpdk-ovs@lists.01.org; users@dpdk.org
> > > Subject: RE: VIRTIO for containers
> > >
> > > Hi Avi,
> > >
> > > > -----Original Message-----
> > > > From: users [mailto:users-bounces@dpdk.org] On Behalf Of Avi Cohen
> > > > (A)
> > > > Sent: Sunday, June 25, 2017 11:13 PM
> > > > To: dpdk-ovs@lists.01.org; users@dpdk.org
> > > > Subject: [dpdk-users] VIRTIO for containers
> > > >
> > > > Hello,
> > > > Does  anyone know the status of this project
> > > > http://dpdk.org/ml/archives/dev/2015-November/027732.html  -
> > > > Implementing a virtio device for containers ?
> > >
> > > It has been upstreamed since v16.07. Here is a howto doc:
> > >
> > http://dpdk.org/doc/guides/howto/virtio_user_for_container_networking.
> > h
> > > tml
> > >
> > >
> > > Thanks,
> > > Jianfeng
> > >
> > > >
> > > > Best Regards
> > > > avi

  reply	other threads:[~2017-06-26 12:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-25 15:13 Avi Cohen (A)
2017-06-26  3:14 ` Tan, Jianfeng
2017-06-26  6:16   ` Avi Cohen (A)
2017-06-26 11:58     ` Tan, Jianfeng
2017-06-26 12:06       ` Avi Cohen (A) [this message]
2017-06-27 14:22         ` Tan, Jianfeng
2017-06-28  6:45           ` Avi Cohen (A)
2017-07-03  7:21             ` Tan, Jianfeng
2017-07-09 15:32               ` Avi Cohen (A)
2017-07-10  3:28                 ` Tan, Jianfeng
2017-07-10  6:49                   ` Avi Cohen (A)
2017-10-20  9:24 王志克
2017-10-20 16:54 ` Tan, Jianfeng
2017-10-24  3:15   ` 王志克
2017-10-24  9:45   ` 王志克
2017-10-25  7:34     ` Tan, Jianfeng
2017-10-25  9:58       ` 王志克
2017-10-26  8:53         ` Tan, Jianfeng
2017-10-26 12:53           ` 王志克
2017-10-27  1:58             ` Tan, Jianfeng
2017-10-31  4:25           ` 王志克
2017-11-01  2:58             ` Tan, Jianfeng

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=B84047ECBD981D4B93EAE5A6245AA361013C8E03@FRAEML521-MBX.china.huawei.com \
    --to=avi.cohen@huawei.com \
    --cc=dpdk-ovs@lists.01.org \
    --cc=jianfeng.tan@intel.com \
    --cc=users@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).