From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: Sending and receiving on the same port at the same time, from different threads Date: Fri, 15 Jan 2016 10:15:42 -0800 Message-ID: <20160115101542.28cfa5d9@xeon-e3> References: <56992433.7060206@linaro.org> <20160115173314.GA29578@mhcomputing.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org To: Matthew Hall Return-path: Received: from mail-pf0-f181.google.com (mail-pf0-f181.google.com [209.85.192.181]) by dpdk.org (Postfix) with ESMTP id 307FF568D for ; Fri, 15 Jan 2016 19:15:34 +0100 (CET) Received: by mail-pf0-f181.google.com with SMTP id n128so121251288pfn.3 for ; Fri, 15 Jan 2016 10:15:34 -0800 (PST) In-Reply-To: <20160115173314.GA29578@mhcomputing.net> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Fri, 15 Jan 2016 12:33:14 -0500 Matthew Hall wrote: > On Fri, Jan 15, 2016 at 04:54:11PM +0000, Zoltan Kiss wrote: > > Can you call rte_eth_tx_burst() and rte_eth_tx_burst() on the same port at > > the same time from different threads? > > In general, yes you can. I did this before in an L4-L7 performance tester, so > cores could concentrate on RX or TX to keep the speeds high. > > > Have anyone seen a device where it wasn't true? > > Not specifically. But I didn't go looking for one either. > > Matthew. Same port is OK, as long as each thread uses different queues. The device queues are not thread safe; ie two threads can't be pulling/pushing to the same queue.