From mboxrd@z Thu Jan 1 00:00:00 1970 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) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; bh=PUetmr+bizpGIaqWvPHsaOQwC4kpU9gGt6GpIQZ9woM=; b=yOSFIX2Xtsq1kgCg5aTCCWjDIyHGWw5NNfCqQzcoiWnMvBmx1XO35sJa1Ba2H3QlmR mcgiXwPf84rrvfM+vpwFvB7x2UTGDx+pAKRPwpDMt3h/+UB40QdHoU41XI8gIJjvVkNY eix8GK3njaVV390BCC5uUp4OjgHCsz1RVYF3qLJhU9UVV1FR8ro5d/No8gtfXL44BrtL JdGwdlkfSfX9YuYlFf9xyA2VfckB0x6oUGSpBiXIWfQ2ZtF2LmpZ3PPCzkGTPZq/ynie +v1ubZuZknonz1CxvuCpdovt86z/BDM8GacaEk8BWE394EkfFq2MVKvKSW4L7IjGnd3e x2Sw== 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=PUetmr+bizpGIaqWvPHsaOQwC4kpU9gGt6GpIQZ9woM=; b=i/CL7WrIvwxjlB9J596HuOAMXWz+fAVHPTRxn845J5MPbZpVd+MuLwPODlfBD/jSUA yCd9kIOVYKfIaJrSMZ+FLHgUg95KjBuCsu8D3DxwAuSfgnDm5KYqcSb19vTghrY8vsiT pmi5HYOC/i/6dDmYNx2lHwKTn9864Yrv5llMZQQEOARA1z5iUWHnszZjoXkgDrxEWz7f GKKzYXF9TumI+LQfaDIsz6Q01iNKCyanxxQlc7t0/ZjN6yXFAJGzvoE3RSxcP2UGoSWR QbN43rmsixqKxYXsfvPW88/XIPtkBKhoFif5GGdyvWOdf7VDJL5MKXvmpEYtPv0EbnEg uvVA== X-Gm-Message-State: ALoCoQlyVJ2ta95R/wHnipRznPWZs2z5cB6bzsZDLq7m/yfhub83jcM1wPn548PqDqJh83PjGZOMF9juo1yw/IgbtlKa+zwwjA== X-Received: by 10.98.72.132 with SMTP id q4mr16671026pfi.53.1452881733631; Fri, 15 Jan 2016 10:15:33 -0800 (PST) Received: from xeon-e3 (static-50-53-82-155.bvtn.or.frontiernet.net. [50.53.82.155]) by smtp.gmail.com with ESMTPSA id 68sm16857549pfa.78.2016.01.15.10.15.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 15 Jan 2016 10:15:33 -0800 (PST) Date: Fri, 15 Jan 2016 10:15:42 -0800 From: Stephen Hemminger To: Matthew Hall Message-ID: <20160115101542.28cfa5d9@xeon-e3> In-Reply-To: <20160115173314.GA29578@mhcomputing.net> 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 Subject: Re: [dpdk-dev] Sending and receiving on the same port at the same time, from different threads X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jan 2016 18:15:34 -0000 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.