From: chintu hetam <rometoroam@gmail.com>
To: "Xie, Huawei" <huawei.xie@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK 2.2 build failing with vhost-kni
Date: Mon, 11 Apr 2016 14:57:26 -0400 [thread overview]
Message-ID: <CAOH8HtpAfjvqLRAVvro00pSdVGe0NkGN=z8JWqqtG6oqZqNM9g@mail.gmail.com> (raw)
In-Reply-To: <CAOH8HtrEm0cWsQSZds3f3h_Dw-t+MOSUUTCBUcgPDtjUeHUyig@mail.gmail.com>
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@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@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?
>>
>
>
next prev parent reply other threads:[~2016-04-11 18:57 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
2016-04-11 14:09 ` chintu hetam
2016-04-11 18:57 ` chintu hetam [this message]
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='CAOH8HtpAfjvqLRAVvro00pSdVGe0NkGN=z8JWqqtG6oqZqNM9g@mail.gmail.com' \
--to=rometoroam@gmail.com \
--cc=dev@dpdk.org \
--cc=huawei.xie@intel.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).