DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Xie, Huawei" <huawei.xie@intel.com>
To: chintu hetam <rometoroam@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK 2.2 build failing with vhost-kni
Date: Mon, 11 Apr 2016 08:25:59 +0000	[thread overview]
Message-ID: <C37D651A908B024F974696C65296B57B4C6DEE0E@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <CAOH8HtoUOEddeciO9F0XFdz7B9OFZvwb22sc8Rc9GSs5WaQ=fg@mail.gmail.com>

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/kni_vhost.c:
> In function ‘kni_sock_poll’:
> /home/vcr/devel/dpdk/dpdk-2.2.0/build/build/lib/librte_eal/linuxapp/kni/kni_vhost.c:254:25:
> error: ‘SOCK_ASYNC_NOSPACE’ undeclared (first use in this 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?

  reply	other threads:[~2016-04-11  8:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-09 23:26 chintu hetam
2016-04-11  8:25 ` Xie, Huawei [this message]
2016-04-11 14:09   ` chintu hetam
2016-04-11 18:57     ` chintu hetam
2016-04-11 19:02       ` chintu hetam
2016-04-11 16:54 ` [dpdk-dev] [PATCH] kni: fix vhost-kni compile errors Ferruh Yigit
2016-04-11 17:04   ` Thomas Monjalon
2016-04-11 17:57     ` Ferruh Yigit
2016-04-11 18:30     ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2016-04-11 20:43       ` Thomas Monjalon

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=C37D651A908B024F974696C65296B57B4C6DEE0E@SHSMSX101.ccr.corp.intel.com \
    --to=huawei.xie@intel.com \
    --cc=dev@dpdk.org \
    --cc=rometoroam@gmail.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).