From mboxrd@z Thu Jan 1 00:00:00 1970 From: chintu hetam Subject: Re: DPDK 2.2 build failing with vhost-kni Date: Mon, 11 Apr 2016 10:09:02 -0400 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "dev@dpdk.org" To: "Xie, Huawei" Return-path: Received: from mail-wm0-f45.google.com (mail-wm0-f45.google.com [74.125.82.45]) by dpdk.org (Postfix) with ESMTP id 8A28D137D for ; Mon, 11 Apr 2016 16:09:02 +0200 (CEST) Received: by mail-wm0-f45.google.com with SMTP id a140so14552148wma.0 for ; Mon, 11 Apr 2016 07:09:02 -0700 (PDT) In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Thanks Xie. I am trying to test FreeBSD-9.3-virtio as guest. Somewhere in the forum i found virtio-kni combination reaching around 2.7 Gbps performance, which is enough for my test, though i dint find equivalent driver performance characterization for qemu-vhost user space combination. Also, as per nics-2.2 user guide, "Linux kernel with KVM module; vhost module loaded and ioeventfd supported. Qemu standard backend without vhost support isn=E2=80=99t tested, and probably isn=E2=80=99t supported",which i= s bit different from vhost user space support,but still.. Just to be sure vhost user space =3D qemu virtio backend- tap-linux-bridge configuration, as per nics guide, right? Thanking in advance, again. On Mon, Apr 11, 2016 at 4:25 AM, Xie, Huawei wrote: > On 4/10/2016 7:26 AM, chintu hetam wrote: > > I am compiling DPDK 2.2 on Fedora 23 and i am seeing following build > error > > > /home/vcr/devel/dpdk/dpdk-2.2.0/build/build/lib/librte_eal/linuxapp/kni/k= ni_vhost.c: > > In function =E2=80=98kni_sock_poll=E2=80=99: > > > /home/vcr/devel/dpdk/dpdk-2.2.0/build/build/lib/librte_eal/linuxapp/kni/k= ni_vhost.c:254:25: > > error: =E2=80=98SOCK_ASYNC_NOSPACE=E2=80=99 undeclared (first use in th= is function) > > (!test_and_set_bit(SOCK_ASYNC_NOSPACE, &q->sock->flags) && > > ^ > > Hi, besides the issue, now user space vhost is the preferred way to > switch packets with the virtual machine, and we have plans to remove kni > vhost support. Do you have any reason to use kni vhost? >