[dpdk-dev] DPDK 2.2 build failing with vhost-kni

[chintu hetam]

I tried vhost-user mode, and during init of ./vhost-switch it fails
with
PMD: eth_ixgbe_dev_init(): port 0 vendorID=0x8086 deviceID=0x1528
pf queue num: 0, configured vmdq pool num: 64, each vmdq pool has 2 queues
EAL: Error - exiting with code: 1
  Cause: Cannot initialize network ports

it's failing in port_init function, and it seems from
http://dpdk.org/doc/guides-1.8/rel_notes/resolved_issues.html

this has to with ixgbe checking for eeprom pba parameters. is that correct,
coz rebuilding ixgbe 4.3.13 by disabling those lines dint help either?

i tried enabling configure
CONFIG_RTE_LIBRTE_ETHDEV_DEBUG=y
 but still i don't see the log messages under /var/log nor on stdout?

just to keep ball rolling i'd like to see at least kni compiling and
working.

FYI, i am using X540-AT2

cheers

On Mon, Apr 11, 2016 at 10:09 AM, chintu hetam <rometoroam at gmail.com> wrote:

> 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’t tested, and probably isn’t supported",which is bit different
> from vhost user space support,but still..
>
> Just to be sure vhost user space = 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 <huawei.xie at intel.com> 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/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?
>>
>
>