From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Newman Poborsky <newman555p@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] one worker reading multiple ports
Date: Thu, 20 Nov 2014 08:56:58 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8972684D317@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <CAHW=9PuErCQW=PDFzMoQLyUhzif6xNsU_28UmiJC=895t8+62w@mail.gmail.com>
Hi Newman,
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Newman Poborsky
> Sent: Thursday, November 20, 2014 8:34 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] one worker reading multiple ports
>
> Hi,
>
> is it possible to use one worker thread (one lcore) to read packets from
> multiple ports?
>
> When I start 2 workers and assign each one to read from different ports
> (with rte_eth_rx_burst()) everything works fine, but if I assign one
> worker to read packets from 2 ports, rte_eth_rx_burst() returns 0 as if no
> packets are read.
Yes, it is totally possible. The only problem would be if you try to use multiple threads
to read/write on one port, in which case you should use multiple queues.
Look at l3fwd app for instance. You can use just a single core to handle packets on multiple ports.
Pablo
>
> Is there any reason for this kind of behaviour?
>
> Thanks!
>
> Br,
> Newman P.
next prev parent reply other threads:[~2014-11-20 8:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 8:33 Newman Poborsky
2014-11-20 8:56 ` De Lara Guarch, Pablo [this message]
2014-11-20 16:10 ` Newman Poborsky
2014-11-20 21:52 ` Matthew Hall
2014-11-21 14:03 ` Newman Poborsky
2014-11-21 14:44 ` Bruce Richardson
2014-11-21 22:55 ` Newman Poborsky
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=E115CCD9D858EF4F90C690B0DCB4D8972684D317@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--cc=newman555p@gmail.com \
/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).