From: Stephen Hemminger <stephen@networkplumber.org>
To: Sambath Kumar Balasubramanian <sambath.balasubramanian@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Multiple LCore receiving from same port/queue
Date: Wed, 16 Oct 2013 14:06:26 -0700 [thread overview]
Message-ID: <20131016140626.41a07b0d@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <CAPrcauMkHjNkOxGK7nn55iicJ6R7=hduOPnM+e5ut1EoL6dYBQ@mail.gmail.com>
On Wed, 16 Oct 2013 13:32:33 -0700
Sambath Kumar Balasubramanian <sambath.balasubramanian@gmail.com> wrote:
> Hi,
>
> I have a test dpdk application with 2 lcores receiving packets
> using rte_eth_rx_burst API. Is this a supported packet processing model.
> The reason I am asking is I am running into some trouble with this model.
>
> Thanks,
> Sambath
For performance reasons, receive and transmit functions are not thread safe.
You need to have one queue per lcore, or use locking.
next prev parent reply other threads:[~2013-10-16 21:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 20:32 Sambath Kumar Balasubramanian
2013-10-16 21:06 ` Stephen Hemminger [this message]
2013-10-16 21:12 ` Vladimir Medvedkin
2013-10-16 21:37 ` Sambath Kumar Balasubramanian
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=20131016140626.41a07b0d@nehalam.linuxnetplumber.net \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=sambath.balasubramanian@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).