From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stephen@networkplumber.org>
Received: from mail-pd0-f181.google.com (mail-pd0-f181.google.com
 [209.85.192.181]) by dpdk.org (Postfix) with ESMTP id 7CA64156
 for <dev@dpdk.org>; Wed, 16 Oct 2013 23:05:43 +0200 (CEST)
Received: by mail-pd0-f181.google.com with SMTP id y13so1537562pdi.40
 for <dev@dpdk.org>; Wed, 16 Oct 2013 14:06:30 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to
 :references:mime-version:content-type:content-transfer-encoding;
 bh=Al8H5GCbJZmftWpr7buSgXHI1bhfcLB/qp8gnYPe/F4=;
 b=CMTVbbNZbrMdKv5dXrElC8puI5+Dt+JjibjfqNUpWfMCqOlynvp3HdNPhEUTq2urRr
 dW0WFkgwEOfif7Rj0oOB0efpnEefOWIUqfch0YNJxSKk/npsoTLU66Gsg9xVIaNquyjI
 McUDm2YQasdt2LEpOwHhXRaml4EKx+rmcz9KxQYCedT0GZyjuVqKBZwt5ulo3UNsMZZZ
 kUwjQgmWfKMwc1vRS35mXtou4GqvU7mu78Dn3YKYWQJg9/99wGznE3nAhovKRH7+9V3k
 CfhEUK42SVKRsNrNK37TI8yIw97adhrPQU5OEe4N+gvY9vaLJpanQRwdCvV8owC5VvYy
 cjCg==
X-Gm-Message-State: ALoCoQmOwhrQyixquA00GO1JYNFsw85TkwCfSwoCbv7Xe2LlxKEIGD1UnlRJTLJw90BDt1wN4ES+
X-Received: by 10.66.147.230 with SMTP id tn6mr5473948pab.135.1381957590203;
 Wed, 16 Oct 2013 14:06:30 -0700 (PDT)
Received: from nehalam.linuxnetplumber.net
 (static-50-53-83-51.bvtn.or.frontiernet.net. [50.53.83.51])
 by mx.google.com with ESMTPSA id a6sm46543222pbr.17.1969.12.31.16.00.00
 (version=TLSv1.2 cipher=RC4-SHA bits=128/128);
 Wed, 16 Oct 2013 14:06:29 -0700 (PDT)
Date: Wed, 16 Oct 2013 14:06:26 -0700
From: Stephen Hemminger <stephen@networkplumber.org>
To: Sambath Kumar Balasubramanian <sambath.balasubramanian@gmail.com>
Message-ID: <20131016140626.41a07b0d@nehalam.linuxnetplumber.net>
In-Reply-To: <CAPrcauMkHjNkOxGK7nn55iicJ6R7=hduOPnM+e5ut1EoL6dYBQ@mail.gmail.com>
References: <CAPrcauMkHjNkOxGK7nn55iicJ6R7=hduOPnM+e5ut1EoL6dYBQ@mail.gmail.com>
X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.10; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Multiple LCore receiving from same port/queue
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Oct 2013 21:05:43 -0000

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.