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 19:37:53 +0000 [thread overview]
Message-ID: <bug-1667-3-kF6KOTINuv@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-1667-3@http.bugs.dpdk.org/>
[-- Attachment #1: Type: text/plain, Size: 704 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1667
fgiordano@riverbed.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #4 from fgiordano@riverbed.com ---
Never mind, the problem seems to be with the scheduling policy (and its
priority) that I use for the poller. With non-realtime scheduling policies, I
can run the poller in busy loop at 100% and not drop a single packet. The bug
is invalid.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 2707 bytes --]
prev parent reply other threads:[~2025-03-04 19:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 12:03 [DPDK/core Bug 1667] Can't configure DPDK poller in busy loop to fix drops bugzilla
2025-03-04 19:37 ` bugzilla [this message]
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-kF6KOTINuv@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.