From: Lilijun <jerry.lilijun@huawei.com>
To: "Zhang, Helin" <helin.zhang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Problems when testing l2fwd with ixgbevf pmd dirver
Date: Thu, 23 Oct 2014 13:51:13 +0800 [thread overview]
Message-ID: <54489751.7030906@huawei.com> (raw)
In-Reply-To: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A7AA5D3@SHSMSX104.ccr.corp.intel.com>
On 2014/10/23 12:56, Zhang, Helin wrote:
>
>
>> -----Original Message-----
>> From: Lilijun [mailto:jerry.lilijun@huawei.com]
>> Sent: Thursday, October 23, 2014 12:31 PM
>> To: Zhang, Helin; dev@dpdk.org
>> Subject: Re: [dpdk-dev] Problems when testing l2fwd with ixgbevf pmd dirver
>>
>> On 2014/10/23 11:44, Zhang, Helin wrote:
>>> Hi
>>>
>>>> -----Original Message-----
>>>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Lilijun
>>>> Sent: Thursday, October 23, 2014 11:36 AM
>>>> To: dev@dpdk.org
>>>> Subject: [dpdk-dev] Problems when testing l2fwd with ixgbevf pmd dirver
>>>>
>>>> Hi all,
>>>>
>>>> I am testing the example l2fwd of dpdk-1.7.0 using intel 82599 VF NICs.
>>>> But the VF can't be used when doing probe pmd driver with following error:
>>>>
>>>> EAL: PCI device 0000:02:10.0 on NUMA socket -1
>>>> EAL: probe driver: 8086:10ed rte_ixgbevf_pmd
>>>> EAL: PCI memory mapped at 0x7f78b181f000
>>>> EAL: PCI memory mapped at 0x7f78b181b000
>>>> EAL: Error - exiting with code: 1
>>>> Cause: Requested device 0000:02:10.0 cannot be used
>>>>
>>>> Any suggestions?
>>> Did you launch DPDK host application?
>>
>> My test steps:
>> 1) rmmod ixgbe; modprobe ixgbe max_vfs=3,3
>> 2) insmod dpdk-1.7.0/x86_64-native-linuxapp-gcc/kmod/igb_uio.ko
>> 3) dpdk_nic_bind.py -b igb_uio 02:10.0 02:10.1
>> 4) ./build/l2fwd -c 0xf -n 3 -- -p 3 -q 1
>>
>> Then l2fwd run failed with error messages shown as above email.
> All done in guest, right?
> If yes, you need to check if host runs in host. It could be standard Linux host driver, or DPDK host driver.
Thanks for the reply.
The example application runs in host. Now the problem has been fixed for that I haven't make my PF NIC up yet.
>
>>
>> Is my test steps correctly?
>>
>>>
>>>>
>>>> Thanks,
>>>> Jerry
>>>
>>> Regards,
>>> Helin
>>>
>>>
>>
>
> Regards,
> Helin
>
>
>
next prev parent reply other threads:[~2014-10-23 5:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-23 3:36 Lilijun
2014-10-23 3:44 ` Zhang, Helin
2014-10-23 4:31 ` Lilijun
2014-10-23 4:56 ` Zhang, Helin
2014-10-23 5:51 ` Lilijun [this message]
2014-10-23 5:52 ` Dong, Binghua
2014-10-23 7:02 ` Lilijun
2014-10-23 5:37 ` Dong, Binghua
2014-10-23 5:54 ` Lilijun
2014-10-23 5:56 ` Zhang, Jerry
2014-10-23 7:03 ` Lilijun
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=54489751.7030906@huawei.com \
--to=jerry.lilijun@huawei.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@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).