From: Mauro Annarumma <mauroannarumma@hotmail.it>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Issues on FDIR and multi-processes
Date: Wed, 2 Apr 2014 17:01:48 +0200 [thread overview]
Message-ID: <DUB111-W579008AE9E67DB1C94BCF8B16D0@phx.gbl> (raw)
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
next reply other threads:[~2014-04-02 15:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 15:01 Mauro Annarumma [this message]
2014-04-02 15:33 ` Richardson, Bruce
[not found] ` <DUB111-W115C60A139CF692652B5FD5B16F0@phx.gbl>
2014-04-04 17:34 ` [dpdk-dev] FW: " Mauro Annarumma
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=DUB111-W579008AE9E67DB1C94BCF8B16D0@phx.gbl \
--to=mauroannarumma@hotmail.it \
--cc=dev@dpdk.org \
/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).