From: Alireza Sanaee <sarsanaee@gmail.com>
To: users@dpdk.org
Subject: Primary and secondary processes polling on two queues
Date: Tue, 31 Oct 2023 19:58:03 +0000 [thread overview]
Message-ID: <CAL=0pobcSyUoKvKqL7n-jMRKEg3Yu_+wJAm4m2B3dipYUa5ahw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 450 bytes --]
Hi everyone,
I have a NIC and I would like to receive packets on my primary process and
secondary process. I wonder if I can have primary process poll on queue = 0
and secondary one poll on queue = 1.
I tried to do this and observed packet loss. That made me wonder if I am
configuring something wrong.
Two questions:
1) Is this possible from practicality perspective?
2) If yes, what can potentially go wrong in this scenario.
Thanks,
Alireza
[-- Attachment #2: Type: text/html, Size: 770 bytes --]
next reply other threads:[~2023-10-31 19:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 19:58 Alireza Sanaee [this message]
2023-11-01 1:31 ` 答复: " jiangheng (G)
2023-11-01 10:15 ` Alireza Sanaee
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='CAL=0pobcSyUoKvKqL7n-jMRKEg3Yu_+wJAm4m2B3dipYUa5ahw@mail.gmail.com' \
--to=sarsanaee@gmail.com \
--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).