From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/core Bug 1667] Can't configure DPDK poller in busy loop to fix drops
Date: Tue, 04 Mar 2025 12:03:55 +0000 [thread overview]
Message-ID: <bug-1667-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1467 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1667
Bug ID: 1667
Summary: Can't configure DPDK poller in busy loop to fix drops
Product: DPDK
Version: 24.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: fgiordano@riverbed.com
Target Milestone: ---
I have an application where I configure multiple NICs with different PMDs and
then I have a simple poller thread that copies packets out of the descriptors
of configured NICs to dedicated rte_rings (one for each port) using
rte_eth_rx_burst. Other threads will then get packets out of the rings and
process packets on a per-port basis.
This poller is configured to run in realtime mode, with high priority on a
dedicated/isolated CPU. It works well and for example on an Intel X710 it can
process 10Gbps/1.8Mpps.
However, sometimes (like 3-4 times a day), the poller can't keep up and drops a
few packets. I have a sleep in my current configuration so I tried to remove it
and have the poller run in busy loop (since it runs in its own cpu and cpu
usage is not a problem). But if I do so, it starts dropping packets like crazy.
That's counter intuitive to me and I would like to know why that happens.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3348 bytes --]
reply other threads:[~2025-03-04 12:03 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=bug-1667-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--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).