From: jinag <15720603159@163.com>
To: matan@nvidia.com, thomas@monjalon.net, users@dpdk.org
Subject: Can dpdk rx interrupts work in secondary process
Date: Mon, 28 Aug 2023 09:10:05 +0800 (CST) [thread overview]
Message-ID: <7753c1c6.1e45.18a39b0d67e.Coremail.15720603159@163.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 277 bytes --]
Hi matan and thomas:
When I call rte_eth_dev_rx_intr_ctl_q in secondary process, I found dev->intr_handle->intr_vec is NULL.
https://github.com/DPDK/dpdk/blob/v19.11/lib/librte_ethdev/rte_ethdev.c#L4120
I wonder if this is a bug or rx interrupts can't work in secondary prcess.
[-- Attachment #2: Type: text/html, Size: 656 bytes --]
reply other threads:[~2023-08-28 8:07 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=7753c1c6.1e45.18a39b0d67e.Coremail.15720603159@163.com \
--to=15720603159@163.com \
--cc=matan@nvidia.com \
--cc=thomas@monjalon.net \
--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).