From: huangdengdui <huangdengdui@huawei.com>
To: David Marchand <david.marchand@redhat.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: Mon, 24 Mar 2025 11:42:51 +0800 [thread overview]
Message-ID: <1190b231-dfb3-4553-89d5-dd86bd2d964e@huawei.com> (raw)
In-Reply-To: <CAJFAV8ygEGSfwb0Pc4hf-QM8dHTYNyD64craGxu0ptamvHqBKg@mail.gmail.com>
On 2025/3/21 15:49, David Marchand wrote:
> 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.
>
>
OK, I'll add a check to make sure dma-perf uses the correct lcore.
next prev parent reply other threads:[~2025-03-24 3:42 UTC|newest]
Thread overview: 14+ 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-24 3:42 ` huangdengdui
2025-03-21 7:49 ` [PATCH 0/2] fix the problem of dma-perf " David Marchand
2025-03-24 3:42 ` huangdengdui [this message]
2025-03-27 8:58 ` [PATCH] app/dma-perf: fix " Dengdui Huang
2025-03-27 8:58 ` [PATCH 1/2] eal: fix uncheck worker ID Dengdui Huang
2025-03-27 8:58 ` [PATCH 2/2] app/dma-perf: fix infinite loop Dengdui Huang
2025-03-27 9:01 ` [PATCH v2 0/2] fix the problem of dma-perf " Dengdui Huang
2025-03-27 9:01 ` [PATCH v2 1/2] eal: fix uncheck worker ID Dengdui Huang
2025-03-27 9:32 ` Morten Brørup
2025-03-27 9:01 ` [PATCH v2 2/2] app/dma-perf: fix infinite loop Dengdui Huang
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=1190b231-dfb3-4553-89d5-dd86bd2d964e@huawei.com \
--to=huangdengdui@huawei.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=haijie1@huawei.com \
--cc=honest.jiang@foxmail.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).