From: William Tu <u9012063@gmail.com>
To: "<dev@openvswitch.org>" <dev@openvswitch.org>, dev@dpdk.org
Cc: Jianfeng Tan <jianfeng.tan@linux.alibaba.com>
Subject: [dpdk-dev] Question about using virtio_user in OVS-DPDK
Date: Tue, 31 Dec 2019 14:19:20 -0800 [thread overview]
Message-ID: <CALDO+SZePcVEpxvMQ4s-7LC3fXJ0BEpEqssenfGgaME2MJTZjg@mail.gmail.com> (raw)
Hi,
I'm trying to find a faster way to communicate from userspace OVS to
kernel. So I create a virtio_user port at OVS-DPDK, and send packets
to kernel's tap device.
packets in OVS userspace -> virtio-user port -> vhost-net (kernel) ->
tap device (kernel)
As described in paper[1], figure 1 for legacy applications.
But there is no documentation about it. I tried:
1) load vhost-net
# lsmod | grep vhost
vhost_net 32768 0
vhost 57344 1 vhost_net
tap 28672 1 vhost_net
tun 57344 8 vhost_net
2) start OVS
3) create tap and attach to OVS
ip tuntap add mode tap tap0
ip link set dev tap0 up
ovs-vsctl add-port br0 tap0 -- set interface tap0 type=dpdk \
options:dpdk-devargs=vdev:net_virtio_user1,iface=tap0,path=/dev/vhost-net
So I thought this is a faster channel using virtio ring than
readv/writev to the tap fd.
But it doesn't work.
2019-12-31T22:06:39.956Z|00033|netdev|WARN|could not create netdev
tap0 of unknown type dpdk
2019-12-31T22:06:39.956Z|00034|bridge|WARN|could not open network
device tap0 (Address family not supported by protocol)
Any suggestions? Or do I understand the concept of virtio_user correctly?
[1] VIRTIO-USER: A New Versatile Channel for Kernel-Bypass Networks
Thanks
William
next reply other threads:[~2019-12-31 22:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <dd0cbd6a6fe97b43349226ba91b2e616@sslemail.net>
2019-12-31 22:19 ` William Tu [this message]
[not found] ` <e91d25eaa10b4228824f1d7c3cb949e5@inspur.com>
2020-01-02 20:01 ` [dpdk-dev] [dpdk.org代发] " William Tu
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=CALDO+SZePcVEpxvMQ4s-7LC3fXJ0BEpEqssenfGgaME2MJTZjg@mail.gmail.com \
--to=u9012063@gmail.com \
--cc=dev@dpdk.org \
--cc=dev@openvswitch.org \
--cc=jianfeng.tan@linux.alibaba.com \
/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).