From: Kai Zhang <zhang.4522@osu.edu>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Problem in multi-queue receiving
Date: Sun, 10 Aug 2014 23:31:04 -0400 [thread overview]
Message-ID: <CACKSPmeuq+9X6iwDcsfgK1hgkrwaLq51G7KY2RaJKLkhfwp3DQ@mail.gmail.com> (raw)
In-Reply-To: <20140810111127.3638a395@haswell.linuxnetplumber.net>
Thanks, Stephen. That's the problem.
On Sun, Aug 10, 2014 at 2:11 PM, Stephen Hemminger <
stephen@networkplumber.org> wrote:
> On Sat, 9 Aug 2014 11:59:24 -0400
> Kai Zhang <zhang.4522@osu.edu> wrote:
>
> > 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
>
> You aren't rxmode.mq_mode therefore you are getting the default value
> of 0 == ETH_MQ_RX_NONE. You should set it to ETH_MQ_RX_RSS to enable
> RSS mode.
>
prev parent reply other threads:[~2014-08-11 3:28 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
2014-08-10 18:11 ` Stephen Hemminger
2014-08-11 3:31 ` Kai Zhang [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=CACKSPmeuq+9X6iwDcsfgK1hgkrwaLq51G7KY2RaJKLkhfwp3DQ@mail.gmail.com \
--to=zhang.4522@osu.edu \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).