dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.org>
To: Sambath Kumar Balasubramanian
	<sambath.balasubramanian-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "dev-VfR2kkLFssw@public.gmane.org" <dev-VfR2kkLFssw@public.gmane.org>
Subject: Re: 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-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Wed, 16 Oct 2013 13:32:33 -0700
Sambath Kumar Balasubramanian <sambath.balasubramanian-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 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.

  parent reply	other threads:[~2013-10-16 21:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-16 20:32 Multiple LCore receiving from same port/queue Sambath Kumar Balasubramanian
     [not found] ` <CAPrcauMkHjNkOxGK7nn55iicJ6R7=hduOPnM+e5ut1EoL6dYBQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-10-16 21:06   ` Stephen Hemminger [this message]
2013-10-16 21:12   ` Vladimir Medvedkin
     [not found]     ` <CANDrEH=CJKEKhFP0mivZMfX-3f5UHVUcbss=KWhuw=LL0Ecoxg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
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-otpzqlsittunbdjkjebofr2eb7je58tq@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.org \
    --cc=sambath.balasubramanian-Re5JQEeQqe8AvxtiuMwx3w@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 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).