From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: "Zachary.Jen (簡汶翰) : 6305"
<Zachary.Jen-hquedaq+nxtWk0Htik3J/w@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: Cannot run l3fwd with the problem of " nb_tx_queues"
Date: Wed, 27 Nov 2013 12:04:09 +0100 [thread overview]
Message-ID: <201311271204.09531.thomas.monjalon@6wind.com> (raw)
In-Reply-To: <5295CFA4.1060100-hquedaq+nxtWk0Htik3J/w@public.gmane.org>
Hello,
27/11/2013 11:58, Zachary.Jen (簡汶翰) : 6305 :
> I also have the same question in l3fwd example.
> I guess may DPDK don't support the chip-set so that we got this error msg.
>
> In my system, I have 2 kinds of chip-set, 82580 & 82574L.
> If I use l3fwd -c 3 -n 1 -- -p 3 --config '(0,0,0),(1,0,1)' in 82574L,
> it will get the error msg.
> But when I change my card with 82580 and use the same command to execute
> DPDK l3fwd.
> It's working.
>
> So, maybe the root cause is the DPDK does not support your chip-set and
> send out this error msg.
No, it's only a problem of hardware queues availability.
82574 has only 1 queue.
--
Thomas
next prev parent reply other threads:[~2013-11-27 11:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 5:21 Cannot run l3fwd with the problem of " nb_tx_queues" yuxuan zhang
[not found] ` <CADsvVhmQ3VeXVCpF-XXVCpvdGvaivtYxbRR4o7qkqLSW4tW6fA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-14 8:31 ` Jose Gavine Cueto
[not found] ` <CAJ5bv6FaOB4JGe_CfD6C74V6DJAvd1dTDjr4yExVnmp4uJDu-g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-27 10:58 ` Zachary.Jen (簡汶翰) : 6305
[not found] ` <5295CFA4.1060100-hquedaq+nxtWk0Htik3J/w@public.gmane.org>
2013-11-27 11:04 ` Thomas Monjalon [this message]
2013-11-27 11:05 ` Jose Gavine Cueto
[not found] ` <CAJ5bv6FHW3UAtNDsQ_JGgOnCPjahXvFfsws4R=v_ObRxDBXqDA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
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=201311271204.09531.thomas.monjalon@6wind.com \
--to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
--cc=Zachary.Jen-hquedaq+nxtWk0Htik3J/w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.