From: Jose Gavine Cueto <pepedocs@gmail.com>
To: yuxuan zhang <zhangyuxuanxd@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Cannot run l3fwd with the problem of " nb_tx_queues"
Date: Thu, 14 Nov 2013 16:31:00 +0800 [thread overview]
Message-ID: <CAJ5bv6FaOB4JGe_CfD6C74V6DJAvd1dTDjr4yExVnmp4uJDu-g@mail.gmail.com> (raw)
In-Reply-To: <CADsvVhmQ3VeXVCpF-XXVCpvdGvaivtYxbRR4o7qkqLSW4tW6fA@mail.gmail.com>
Hi,
Your nic (port 0) is capable of 1 txq only see error:
" port_id=0 nb_tx_queues=2 > 1"
I think that caused the error.
Cheers,
Pepe
On Thu, Nov 14, 2013 at 1:21 PM, yuxuan zhang <zhangyuxuanxd@gmail.com>wrote:
> Hi Everyone:
>
> I meet a problem with running the DPDK1.3 example l3fwd in the VMware. I
> have two 82545EM NIC to run the l3fwd and the OS is Cent6.4. But l3fwd
> cannot be configured port correctly .I start the l3fwd with following
> command:
>
> ./build/l3fwd -c 0x3 -n 2 -- -p 0x3 --config="(0,0,0),(1,0,1)"
>
> However, I get following errors with debug info:
>
> Initializing port 0 ... Creating queues: nb_rxq=1 nb_txq=2... PMD:
> rte_eth_dev_configure: ethdev port_id=0 nb_tx_queues=2 > 1
> EAL: Error - exiting with code: 1
> Cause: Cannot configure device: err=-22, port=0
>
> And I have known that the reason for this problem produced in the
> **rte_eth_dev_configure function**. However, I do not kown how to fix it.
>
> I would really appreciate If someone could provide some help to solve this
> issue.
>
--
To stop learning is like to stop loving.
next prev parent reply other threads:[~2013-11-14 8:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 5:21 yuxuan zhang
2013-11-14 8:31 ` Jose Gavine Cueto [this message]
2013-11-27 10:58 ` 6305
2013-11-27 11:04 ` Thomas Monjalon
2013-11-27 11:05 ` Jose Gavine Cueto
2013-11-27 12:49 ` yuxuan zhang
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=CAJ5bv6FaOB4JGe_CfD6C74V6DJAvd1dTDjr4yExVnmp4uJDu-g@mail.gmail.com \
--to=pepedocs@gmail.com \
--cc=dev@dpdk.org \
--cc=zhangyuxuanxd@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).