* [dpdk-dev] Issues on FDIR and multi-processes
@ 2014-04-02 15:01 Mauro Annarumma
2014-04-02 15:33 ` Richardson, Bruce
0 siblings, 1 reply; 3+ messages in thread
From: Mauro Annarumma @ 2014-04-02 15:01 UTC (permalink / raw)
To: dev
Hi everyone,
we are working with Flow DIRector on a multiprocess application. This application consists of N secondary processes, each one receiving packets directly from its own queue on the NIC. It works fine when each secondary process runs on a different CPU core; instead, if we try to run two secondary processes on the same CPU core, these processes aren't able to read from their respectively queue.
Moreover we observe that one process initially receives same packet; then all the processes no longer receive anything.
Do you have any suggestion about these strange behaviour? Is it a DPDK limitation or a FDIR limitation?
Best regards.
Mauro
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [dpdk-dev] Issues on FDIR and multi-processes
2014-04-02 15:01 [dpdk-dev] Issues on FDIR and multi-processes Mauro Annarumma
@ 2014-04-02 15:33 ` Richardson, Bruce
[not found] ` <DUB111-W115C60A139CF692652B5FD5B16F0@phx.gbl>
0 siblings, 1 reply; 3+ messages in thread
From: Richardson, Bruce @ 2014-04-02 15:33 UTC (permalink / raw)
To: Mauro Annarumma, dev
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Mauro Annarumma
> Sent: Wednesday, April 02, 2014 4:02 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] Issues on FDIR and multi-processes
>
> Hi everyone,
> we are working with Flow DIRector on a multiprocess application. This application consists of N secondary processes,
> each one receiving packets directly from its own queue on the NIC. It works fine when each secondary process runs on
> a different CPU core; instead, if we try to run two secondary processes on the same CPU core, these processes aren't
> able to read from their respectively queue.
Running two co-operating Intel DPDK processes on the same lcore is not a supported configuration of Intel DPDK multiprocess. [Please see section 20.3 of the Intel DPDK Programmer's Guide document, which lists out some limitations of multi-process support]. Basically, each process in a multiprocess configuration is equivalent to a thread in a normal application deployment, so just as having two threads on the same core causes problems with mempools and other objects which use an "lcore_id" value unique in each thread to work correctly, so running two processes on the same lcore can cause exactly the same issues.
If you really do want to use this model and have multiple threads on the same lcore, at minimum you need to ensure that each thread/process has a unique lcore_id value <= RTE_MAX_LCORE.
/Bruce
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-04-04 17:33 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-04-02 15:01 [dpdk-dev] Issues on FDIR and multi-processes Mauro Annarumma
2014-04-02 15:33 ` Richardson, Bruce
[not found] ` <DUB111-W115C60A139CF692652B5FD5B16F0@phx.gbl>
2014-04-04 17:34 ` [dpdk-dev] FW: " Mauro Annarumma
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).