All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: luca.boccassi@gmail.com
Cc: dev@dpdk.org, david.marchand@redhat.com, roretzla@linux.microsoft.com
Subject: Re: [PATCH] Revert "eal/unix: fix thread creation"
Date: Wed, 30 Oct 2024 12:52:14 -0700	[thread overview]
Message-ID: <20241030125214.0274b37b@hermes.local> (raw)
In-Reply-To: <20241030190945.409721-1-luca.boccassi@gmail.com>

On Wed, 30 Oct 2024 19:08:41 +0000
luca.boccassi@gmail.com wrote:

> From: Luca Boccassi <luca.boccassi@gmail.com>
> 
> This commit introduced a regression on arm64, causing a deadlock.
> lcores_autotest gets stuck and never terminates:
> 
> [ 1077s] EAL: Detected CPU lcores: 4
> [ 1077s] EAL: Detected NUMA nodes: 1
> [ 1077s] EAL: Detected shared linkage of DPDK
> [ 1077s] EAL: Multi-process socket /tmp/dpdk/rte/mp_socket
> [ 1077s] EAL: Selected IOVA mode 'VA'
> [ 1077s] APP: HPET is not enabled, using TSC as default timer
> [ 1077s] RTE>>lcores_autotest
> [ 1127s] DPDK:fast-tests / lcores_autotest time out (After 50.0 seconds)
> 
> This is 100% reproducible when running the fast tests suite
> after a package build on OBS. Reverting it reliably fixes the
> issue.
> 
> This reverts commit b28c6196b132d1f25cb8c1bf781520fc41556b3a.
> ---
> I have bisected this long standing issue and identified the commit
> that introduced it. If anybody can provide a different fix that would
> be better, but if it's not possible to find another solution, it would
> be good to revert it until it can be found, to resolve the regression.
> 
>  lib/eal/unix/rte_thread.c | 73 +++++++++++++++------------------------
>  1 file changed, 28 insertions(+), 45 deletions(-)

Missing DCO (no Signed-off-by) which is required even for a Revert.

Also Luca usually uses either Debian or Microsoft email address
getting one from gmail is different and not in mailmap.

  reply	other threads:[~2024-10-30 19:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-30 19:08 [PATCH] Revert "eal/unix: fix thread creation" luca.boccassi
2024-10-30 19:52 ` Stephen Hemminger [this message]
2024-10-30 20:31   ` Luca Boccassi
2024-10-30 20:30 ` [PATCH v2] " luca.boccassi
2024-10-31 12:47   ` David Marchand
2024-10-31 12:52     ` David Marchand
2024-10-31 12:58       ` Luca Boccassi
2024-10-31 13:03         ` David Marchand
2024-10-31 14:05           ` Luca Boccassi
2024-10-31 20:46             ` Stephen Hemminger
2024-11-02 10:09               ` David Marchand
2024-11-04 17:59                 ` 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=20241030125214.0274b37b@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=luca.boccassi@gmail.com \
    --cc=roretzla@linux.microsoft.com \
    /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.