DPDK patches and discussions
 help / color / mirror / Atom feed
From: Julien Hascoet <jhascoet@kalrayinc.com>
To: dev@dpdk.org
Subject: [TEST] dpdk/app/test/test_mbuf.c test_refcnt_mbuf instability + fix proposal
Date: Mon, 7 Aug 2023 06:18:43 +0000	[thread overview]
Message-ID: <MR1P264MB172997D1815F2F49AA6AB6A7D00CA@MR1P264MB1729.FRAP264.PROD.OUTLOOK.COM> (raw)

[-- Attachment #1: Type: text/plain, Size: 1514 bytes --]

Hello,

from my understanding after debugging, in test_refcnt_iter the return value of rte_ring_enqueue is not checked; leading to lack of expected mbufs at the end checks.

Here is some fix proposal that seems to work after running endurance tests for several days:

diff --git a/app/test/test_mbuf.c b/app/test/test_mbuf.c
index b4f436b5e2..8a5d26e4f6 100644
--- a/app/test/test_mbuf.c
+++ b/app/test/test_mbuf.c
@@ -1033,12 +1033,17 @@ test_refcnt_iter(unsigned int lcore, unsigned int iter,
                tref += ref;
                if ((ref & 1) != 0) {
                        rte_pktmbuf_refcnt_update(m, ref);
-                       while (ref-- != 0)
-                               rte_ring_enqueue(refcnt_mbuf_ring, m);
+                       while (ref-- != 0) {
+                               /* retry in case of failure */
+                               while (rte_ring_enqueue(refcnt_mbuf_ring, m) != 0)
+                                       ;
+                       }
                } else {
                        while (ref-- != 0) {
                                rte_pktmbuf_refcnt_update(m, 1);
-                               rte_ring_enqueue(refcnt_mbuf_ring, m);
+                               /* retry in case of failure */
+                               while (rte_ring_enqueue(refcnt_mbuf_ring, m) != 0)
+                                       ;
                        }
                }
                rte_pktmbuf_free(m);

Can you confirm ?

Thank,

Julien Hascoet



[-- Attachment #2: Type: text/html, Size: 6035 bytes --]

             reply	other threads:[~2023-08-07  6:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-07  6:18 Julien Hascoet [this message]
2023-08-07  7:26 ` David Marchand
2023-08-07  8:02   ` Julien Hascoet
2023-08-08  7:03     ` David Marchand

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=MR1P264MB172997D1815F2F49AA6AB6A7D00CA@MR1P264MB1729.FRAP264.PROD.OUTLOOK.COM \
    --to=jhascoet@kalrayinc.com \
    --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).