From: czy12345@mail.ustc.edu.cn
To: "Pavel Shirshov" <pavel.shirshov@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] l3fwd rte_eth_dev_configure: err=-17
Date: Mon, 31 Jul 2017 20:55:24 +0800 (GMT+08:00) [thread overview]
Message-ID: <1dd40776.6167.15d98b7206d.Coremail.czy12345@mail.ustc.edu.cn> (raw)
In-Reply-To: <CALkUq2iFCgwDgJR1x3opo8cjddZdwMzU385XDpZJ9Maf+couKg@mail.gmail.com>
The DPDK version I used is 17.02.1 . Today I also tried 17.05 and 17.05.1, the result were the same except the return err which was -22.
Network devices using DPDK-compatible driver
============================================
0000:02:00.0 '82574L Gigabit Network Connection 10d3' drv=igb_uio unused=vfio-pci
0000:03:00.0 '82574L Gigabit Network Connection 10d3' drv=igb_uio unused=vfio-pci
Thanks.
At2017-07-31 13:47:41,Pavel Shirshov<pavel.shirshov@gmail.com>wrote:
> Hello,
>
> What version of DPDK?
> What NIC on port 0?
>
> Thanks
>
> On Sun, Jul 30, 2017 at 12:42 AM, <czy12345@mail.ustc.edu.cn> wrote:
> > Hello experts,
> >
> > I have successfully ran l2fwd example. But I'm having troubles running the l3fwd example. I find that in l2fwd the nb_tx_queue parameter of function rte_eth_dev_configure is equal to 1, but in l3fwd the parameter is set to the number of lcores. And then when I use more than one lcores, the function fails. Wondering what is related with the problem?
> >
> > Thanks in advance.
> >
> > #./l3fwd -l 1 -n 4 -- -p 0x3 --config="(0,0,1),(1,0,1)" --parse-ptype
> > success
> >
> > #./l3fwd -l 1,2 -n 4 -- -p 0x3 --config="(0,0,1),(1,0,2)" --parse-ptype
> > EAL: Detected 8 lcore(s)
> > EAL: Probing VFIO support...
> > EAL: VFIO support initialized
> > EAL: PCI device 0000:01:00.0 on NUMA socket -1
> > EAL: probe driver: 8086:10e6 net_e1000_igb
> > EAL: PCI device 0000:01:00.1 on NUMA socket -1
> > EAL: probe driver: 8086:10e6 net_e1000_igb
> > EAL: PCI device 0000:02:00.0 on NUMA socket -1
> > EAL: probe driver: 8086:10d3 net_e1000_em
> > EAL: PCI device 0000:03:00.0 on NUMA socket -1
> > EAL: probe driver: 8086:10d3 net_e1000_em
> > EAL: PCI device 0000:04:00.0 on NUMA socket -1
> > EAL: probe driver: 8086:10d3 net_e1000_em
> > EAL: PCI device 0000:05:00.0 on NUMA socket -1
> > EAL: probe driver: 8086:10d3 net_e1000_em
> > EAL: PCI device 0000:06:00.0 on NUMA socket -1
> > EAL: probe driver: 8086:10d3 net_e1000_em
> > EAL: PCI device 0000:07:00.0 on NUMA socket -1
> > EAL: probe driver: 8086:10d3 net_e1000_em
> > soft parse-ptype is enabled
> > L3FWD: LPM or EM none selected, default LPM on
> > Initializing port 0 ... Creating queues: nb_rxq=1 nb_txq=2... EAL: Error - exiting with code: 1
> > Cause: Cannot configure device: err=-17, port=0
prev parent reply other threads:[~2017-07-31 12:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-30 7:42 czy12345
2017-07-31 5:47 ` Pavel Shirshov
2017-07-31 12:55 ` czy12345 [this message]
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=1dd40776.6167.15d98b7206d.Coremail.czy12345@mail.ustc.edu.cn \
--to=czy12345@mail.ustc.edu.cn \
--cc=pavel.shirshov@gmail.com \
--cc=users@dpdk.org \
/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).