From: Antoine POLLENUS <a.pollenus@deltacast.tv>
To: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Running a second DPDK process that prints the NIC's link status/speed causes the first DPDK process to stop transmitting.
Date: Fri, 7 Sep 2018 10:38:32 +0000 [thread overview]
Message-ID: <5b2991fd3fd341bfa8b09a414f5f54f6@deltacast.tv> (raw)
Francis
You should read these 2 resources on how DPDK multi process works:
https://doc.dpdk.org/guides/prog_guide/multi_proc_support.html
https://doc.dpdk.org/guides/sample_app_ug/multi_process.html
and most specifically this one :
https://doc.dpdk.org/guides/prog_guide/multi_proc_support.html#multi-process-limitations
The delivery of interrupts, such as Ethernet* device link status interrupts, do not work in secondary processes. All interrupts are triggered inside the primary process only. Any application needing interrupt notification in multiple processes should provide its own mechanism to transfer the interrupt information from the primary process to any secondary process that needs the information.
Regards
Antoine
next reply other threads:[~2018-09-07 10:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 10:38 Antoine POLLENUS [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-09-07 8:26 Francis Rammeloo
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=5b2991fd3fd341bfa8b09a414f5f54f6@deltacast.tv \
--to=a.pollenus@deltacast.tv \
--cc=users@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).