From: topperxin <topperxin@126.com>
To: dev@dpdk.org, user@dpdk.org
Subject: [dpdk-dev] Why secondary process can't receive the interrupt from NIC
Date: Wed, 22 Mar 2017 22:53:16 +0800 (CST) [thread overview]
Message-ID: <dd1168a.d55a.15af681f3a2.Coremail.topperxin@126.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=GBK, Size: 1483 bytes --]
HI list
I'm using two processes in our program.
The primary process to load config, init data
The secondary process to receive and forward the package from NIC
In order to reduce the cpu usage, we decide to use interrupt + poll mode.
But I find in the dpdk lib, the secondary process can not setup and receive the interrupt.
Who can tell me the reason, and if we want to let the secondary process receive the interrupt, what's the best practice?
Thanks a lot.
=========================================
/*
* map the PCI resources of a PCI device in virtual memory (VFIO version).
* primary and secondary processes follow almost exactly the same path
*/
int
pci_vfio_map_resource(struct rte_pci_device *dev)
{
..........................................
/* if secondary process, do not set up interrupts */
if (internal_config.process_type == RTE_PROC_PRIMARY) {
if (pci_vfio_setup_interrupts(dev, vfio_dev_fd) != 0) {
RTE_LOG(ERR, EAL, " %s error setting up interrupts!\n", pci_addr);
close(vfio_dev_fd);
rte_free(vfio_res);
return -1;
}
..........................................
}
\x16º&}êëº\x1c¢+b×¥ryÓ\x1a¯mµç¸×m5í\x17º¹ÏjØ_zºî( اµé\¢d^qè¯y×ë¢i kN"×¥r¦8{^Ê&×ݹçµÛFòvd¢¸\x0f¢Ë_\x1c"¶\x11\x1213ât\x0e»Ûmu\vwmj½´×½yç®4ûMtÐ!\x13\f¢\fJ('jÛ«z
reply other threads:[~2017-03-22 14:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=dd1168a.d55a.15af681f3a2.Coremail.topperxin@126.com \
--to=topperxin@126.com \
--cc=dev@dpdk.org \
--cc=user@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).