From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 8795DA04DD; Tue, 31 Dec 2019 23:20:00 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id ACB881BFBF; Tue, 31 Dec 2019 23:19:59 +0100 (CET) Received: from mail-qt1-f196.google.com (mail-qt1-f196.google.com [209.85.160.196]) by dpdk.org (Postfix) with ESMTP id 318B51BFBD for ; Tue, 31 Dec 2019 23:19:58 +0100 (CET) Received: by mail-qt1-f196.google.com with SMTP id e12so32356496qto.2 for ; Tue, 31 Dec 2019 14:19:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=GEND04Q43gKS4zRxmnCvD5dp47i05wO7vLD4kAt3kik=; b=AL7nXj5sxygpkN93nisxom+8Iorh6h4u+3fZsw8AvROKya5V9+NpxR4eBUqvZMqrXA ER3heD/Tco/ReqG/GO3wNBqU/paUNj3kepd0gSN32S4q7+it3jkqbIJssygDAOqaoLuf xJ/MCakitW/wsAInnVMOJ1Wehrww34rgS1gLtaym+BXqQ8PF1knEJRpm2wJkx9TQ08sl FcVvgu7E+/a0wDVZhdfdYhR83YFNfyg9Rvq2MiJaTuaIaXMK/fG2GvN5vRE5brc4cQrK Iq9rz2VhwCZlzYny7oozKZIDUPhXD4rX1FXtLMrrWmwtSNXSpn4PKTHUdWgSnYfY+y67 pGRw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=GEND04Q43gKS4zRxmnCvD5dp47i05wO7vLD4kAt3kik=; b=PAZLaByaOEyxWHlGtWA8gb6okkRmQBgUw+pQyhkVfaUMliMRDPceUG09pmp+2VFkn7 qI9Psm0XChBroaQsNPQ3r55ODeS+PhEZ5hhXRp9sggJKO0bt4ihJTl94TcTV+KJITGNz 9b/gh99g0K8beZHjB6GFgbdIyz1cO2Zqz4iYznTcDuHNpn/fZMWlB7dY5ERyCb0IU3YM Mpgjwd9Q/k+e/M4lXrtA0WKsXp0msxnV+6NIqMo6skJjGYMTtzpgikprhhN2LSN5IH9i 1Sx9gSiNqQ0FT3W24tQMpUGAXEtYWJB5TvDYbKPw38nMCsAC/8jtJkCRT5UeWzb/moSc sZhA== X-Gm-Message-State: APjAAAWujIH4EXayBm0ecZ64sEscdYFwAQ5o/ab00NUUUmvYe9aFHibt c6tMjrQKZaOMRiODPN45t5Qu75O5oiXZvFdVqtg= X-Google-Smtp-Source: APXvYqxiAavx3vg0f33EZKXFd+n4g+Tj8WDT1B8Uq+c6i5qFP7Q1x+0FSai9pXLyRaR1r7lNfniQnn7cql8SDPfsB3Y= X-Received: by 2002:ac8:7586:: with SMTP id s6mr53094344qtq.309.1577830797379; Tue, 31 Dec 2019 14:19:57 -0800 (PST) MIME-Version: 1.0 From: William Tu Date: Tue, 31 Dec 2019 14:19:20 -0800 Message-ID: To: "" , dev@dpdk.org Cc: Jianfeng Tan Content-Type: text/plain; charset="UTF-8" Subject: [dpdk-dev] Question about using virtio_user in OVS-DPDK X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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