From: Linzhe Lee <slayercat.subscription@gmail.com>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, "Xueming(Steven) Li" <xuemingl@nvidia.com>
Subject: Re: memory_hotplug_lock deadlock during initialization in Multi-process Mode on DPDK Version 22.11.3 LTS
Date: Thu, 28 Dec 2023 13:40:03 +0800 [thread overview]
Message-ID: <CAK_yBkNTT0gXi+EvuTOsVQd=T+2Xdh+Jy6MbkRP6dfnraTcbdw@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8xDKt73Y8bNnYTqLv2jf5HsqPT4MgBhbRiMRzEnA+fM+Q@mail.gmail.com>
Hi,
Testing on 22.11.4-rc3 confirms that this issue has been resolved.
Thank you very much.
David Marchand <david.marchand@redhat.com> 于2023年12月27日周三 18:14写道：
>
> Hello,
>
> Cc: 22.11 stable maintainer for info
>
> On Wed, Dec 27, 2023 at 4:14 AM Linzhe Lee
> <slayercat.subscription@gmail.com> wrote:
> >
> > Dear Team,
> >
> > I hope this message finds you well.
> >
> > We have encountered a recurring deadlock issue within the function
> > rte_rwlock_write_lock in the DPDK version 22.11.3 LTS.
> >
> > It appears to be related to a known matter addressed in
> > https://bugs.dpdk.org/show_bug.cgi?id=1277 and subsequently resolved
> > in version 23.11.
> >
> > I kindly propose the backporting of this fix to the 22.11 branch,
> > considering its status as a long-term support (LTS) version.
>
> As far as I can see, this fix is part of the 22.11.4-rc1 tag.
>
> A 22.11.4-rc3 tag was recently released.
> https://git.dpdk.org/dpdk-stable/tag/?h=v22.11.4-rc3
> Could you have a try with it?
>
>
> Thanks.
>
> --
> David Marchand
>
prev parent reply other threads:[~2023-12-28 5:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-27 3:13 Linzhe Lee
2023-12-27 10:14 ` David Marchand
2023-12-28 5:40 ` Linzhe Lee [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='CAK_yBkNTT0gXi+EvuTOsVQd=T+2Xdh+Jy6MbkRP6dfnraTcbdw@mail.gmail.com' \
--to=slayercat.subscription@gmail.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=xuemingl@nvidia.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 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).