From: David Marchand <david.marchand@redhat.com>
To: Dengdui Huang <huangdengdui@huawei.com>
Cc: dev@dpdk.org, honest.jiang@foxmail.com, fengchengwen@huawei.com,
roretzla@linux.microsoft.com, lihuisong@huawei.com,
haijie1@huawei.com, liuyonglong@huawei.com,
stephen@networkplumber.org
Subject: Re: [PATCH 0/2] fix the problem of dma-perf infinite loop
Date: Fri, 21 Mar 2025 08:49:06 +0100 [thread overview]
Message-ID: <CAJFAV8ygEGSfwb0Pc4hf-QM8dHTYNyD64craGxu0ptamvHqBKg@mail.gmail.com> (raw)
In-Reply-To: <20250321040316.104126-1-huangdengdui@huawei.com>
On Fri, Mar 21, 2025 at 5:03 AM Dengdui Huang <huangdengdui@huawei.com> wrote:
>
> After CPU isolation is configured, an infinite loop occurs when
> dma-perf is executed using the default config file.
>
> This patchset fix it.
>
> Dengdui Huang (2):
> eal: fix wake a incorrect lcore
> app/dma-perf: fix infinite loop
>
> app/test-dma-perf/benchmark.c | 5 ++++-
> lib/eal/unix/eal_unix_thread.c | 3 +++
> lib/eal/windows/eal_thread.c | 3 +++
> 3 files changed, 10 insertions(+), 1 deletion(-)
We can make EAL launch API more resilient, but the dma-perf
application should not post jobs on non sense lcore id, in the first
place.
parse_lcore() should be validating that the requested lcore_id is valid.
--
David Marchand
prev parent reply other threads:[~2025-03-21 7:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 4:03 Dengdui Huang
2025-03-21 4:03 ` [PATCH 1/2] eal: fix wake a incorrect lcore Dengdui Huang
2025-03-21 4:03 ` [PATCH 2/2] app/dma-perf: fix infinite loop Dengdui Huang
2025-03-21 15:58 ` Stephen Hemminger
2025-03-21 7:49 ` David Marchand [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=CAJFAV8ygEGSfwb0Pc4hf-QM8dHTYNyD64craGxu0ptamvHqBKg@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=haijie1@huawei.com \
--cc=honest.jiang@foxmail.com \
--cc=huangdengdui@huawei.com \
--cc=lihuisong@huawei.com \
--cc=liuyonglong@huawei.com \
--cc=roretzla@linux.microsoft.com \
--cc=stephen@networkplumber.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).