All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/core Bug 1527] Running ring_stress_autotest with > 112 CPUs hangs test
Date: Mon, 26 Aug 2024 22:08:16 +0000	[thread overview]
Message-ID: <bug-1527-3@http.bugs.dpdk.org/> (raw)

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

https://bugs.dpdk.org/show_bug.cgi?id=1527

            Bug ID: 1527
           Summary: Running ring_stress_autotest with > 112 CPUs hangs
                    test
           Product: DPDK
           Version: 24.07
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: drc@linux.ibm.com
  Target Milestone: ---

System: IBM POWER9 system (PowerNV) with 128 CPUs (2 NUMA nodes), 256GB RAM
** Unverified on x86_64 system with similar size **
OS: RHEL 8.10 (gcc 8.5.0 & gcc 13.2.1)
DPDK: 24.07 (& all prior releases as far back as 21.05)

Running the ring stress autotest causes the test to hang as follows:

~/src/dpdk/build/app/test/dpdk-test --log-level=debug -l 2-127 --no-pci
--no-huge ring_stress_autotest
EAL: Detected CPU lcores: 128
EAL: Detected NUMA nodes: 2
EAL: Static memory layout is selected, amount of reserved memory can be
adjusted with -m or --socket-mem
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /run/user/1000/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
APP: HPET is not enabled, using TSC as default timer
RTE>>ring_stress_autotest
TEST-CASE MP/MC MT-WRK_ENQ_DEQ-MST_NONE-PRCS START
lcore_stat_dump(AGGREGATE)={
        nb_cycle=30720070618(60000137.93 usec),
        DEQ+ENQ={
                nb_call=24261400,
                nb_obj=861278043,
                nb_cycle=3701862086301,
                obj/call(avg): 35.50
                cycles/obj(avg): 4298.10
                cycles/call(avg): 152582.38
                max cycles/call=16721609(32659.39 usec),
                min cycles/call=346(0.68 usec),
        },
};
TEST-CASE MP/MC MT-WRK_ENQ_DEQ-MST_NONE-PRCS OK
TEST-CASE MP/MC MT-WRK_ENQ_DEQ-MST_NONE-AVG START
lcore_stat_dump(AGGREGATE)={
        nb_cycle=30720078841(60000153.99 usec),
        DEQ+ENQ={
                nb_call=24328571,
                nb_obj=863669930,
                nb_cycle=3840005487992,
                obj/call(avg): 35.50
                cycles/obj(avg): 4446.15
                cycles/call(avg): 157839.34
        },
};
TEST-CASE MP/MC MT-WRK_ENQ_DEQ-MST_NONE-AVG OK
TEST-CASE MT_RTS MT-WRK_ENQ_DEQ-MST_NONE-PRCS START
<<< Test hangs at this point, have waited up to 24 hours to complete >>>

-- 
You are receiving this mail because:
You are the assignee for the bug.

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

                 reply	other threads:[~2024-08-26 22:08 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-1527-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 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.