From: "Zhang, Helin" <helin.zhang@intel.com>
To: Kai Zhang <zhang.4522@osu.edu>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Problem in multi-queue receiving
Date: Sun, 10 Aug 2014 13:37:40 +0000 [thread overview]
Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A77A0CD@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <CACKSPmeriwphHnR=1kqOC6+5S0EqWDbK7VHMXEccca55iSDHFg@mail.gmail.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Kai Zhang
> Sent: Saturday, August 9, 2014 11:59 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] Problem in multi-queue receiving
>
> Hi there,
>
> I have a problem for multi-queue receiving.
>
> For a specific application, I am not using the lcore abstractions in DPDK.
> I launch rx and tx threads seperately. For one port with N queues, I launched N
> rx threads and N tx threads, with each thread in charge of receiving or sending
> only one queue.
>
> The tx threads work on their own queues well. However, all received packets
> only go to queue 0 rx thread, and other rx threads receive nothing.
>
> My code is at :
> https://github.com/kay21s/dpdk/blob/master/examples/pthread/main.c
> It has a default NUM_QUEUE=2, which means port 0 is configured with 2
> queues, and 2 rx threads and 2 tx threads are launched.
> Is there any problem in my implementation? or DPDK does not support it?
>
> Thanks a lot!
> Kai
Hi Kai
My suggestion is to try DPDK example applications (e.g. testpmd, l2fwd, l3fwd) first to see if it work fine on you board. Then check the difference between your application and the examples.
Regards,
Helin
next prev parent reply other threads:[~2014-08-10 13:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-09 15:59 Kai Zhang
2014-08-10 13:37 ` Zhang, Helin [this message]
2014-08-10 18:11 ` Stephen Hemminger
2014-08-11 3:31 ` Kai 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=F35DEAC7BCE34641BA9FAC6BCA4A12E70A77A0CD@SHSMSX104.ccr.corp.intel.com \
--to=helin.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=zhang.4522@osu.edu \
/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).