DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Matthew Hall <mhall@mhcomputing.net>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Sending and receiving on the same port at the same time, from different threads
Date: Fri, 15 Jan 2016 10:15:42 -0800	[thread overview]
Message-ID: <20160115101542.28cfa5d9@xeon-e3> (raw)
In-Reply-To: <20160115173314.GA29578@mhcomputing.net>

On Fri, 15 Jan 2016 12:33:14 -0500
Matthew Hall <mhall@mhcomputing.net> 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.

      reply	other threads:[~2016-01-15 18:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-15 16:54 Zoltan Kiss
2016-01-15 17:33 ` Matthew Hall
2016-01-15 18:15   ` Stephen Hemminger [this message]

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=20160115101542.28cfa5d9@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=mhall@mhcomputing.net \
    /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).