From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 532094633C; Tue, 4 Mar 2025 13:03:58 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 2519240156; Tue, 4 Mar 2025 13:03:57 +0100 (CET) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id 0A04440041 for ; Tue, 4 Mar 2025 13:03:56 +0100 (CET) Received: by inbox.dpdk.org (Postfix, from userid 33) id D4DF54633D; Tue, 4 Mar 2025 13:03:55 +0100 (CET) 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 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: core X-Bugzilla-Version: 24.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: fgiordano@riverbed.com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: multipart/alternative; boundary=17410898350.0d540d6.3916976 Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --17410898350.0d540d6.3916976 Date: Tue, 4 Mar 2025 13:03:55 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All https://bugs.dpdk.org/show_bug.cgi?id=3D1667 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 a= nd then I have a simple poller thread that copies packets out of the descripto= rs 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 c= an process 10Gbps/1.8Mpps. However, sometimes (like 3-4 times a day), the poller can't keep up and dro= ps a few packets. I have a sleep in my current configuration so I tried to remov= e 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 cr= azy. That's counter intuitive to me and I would like to know why that happens. --=20 You are receiving this mail because: You are the assignee for the bug.= --17410898350.0d540d6.3916976 Date: Tue, 4 Mar 2025 13:03:55 +0100 MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All
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 conf=
igure multiple NICs with different PMDs and
then I have a simple poller thread that copies packets out of the descripto=
rs
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 c=
an
process 10Gbps/1.8Mpps.

However, sometimes (like 3-4 times a day), the poller can't keep up and dro=
ps a
few packets. I have a sleep in my current configuration so I tried to remov=
e 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 cr=
azy.
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.
=20=20=20=20=20=20=20=20=20=20
= --17410898350.0d540d6.3916976--