From: Bruce Richardson <bruce.richardson@intel.com>
To: fengchengwen <fengchengwen@huawei.com>
Cc: <dev@dpdk.org>, <stable@dpdk.org>
Subject: Re: [PATCH v3] test: improve resiliency of malloc autotest
Date: Thu, 6 Feb 2025 11:40:04 +0000 [thread overview]
Message-ID: <Z6SflKJyTbxMRD9g@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <0e91d822-ed10-4dae-8f0a-7169e7819517@huawei.com>
On Fri, Jan 24, 2025 at 03:18:11PM +0800, fengchengwen wrote:
> The new impl don't support re-test, how about add a wrap:
> 1. rename test_multi_alloc_statistics with do_test_multi_alloc_statistics, and make it take socket as parameter
> 2. create a new function test_multi_alloc_statistics {
> // prepare a new malloc heap
> ret = do_test_multi_alloc_statistics(socket);
> // free the heap
> return ret;
> }
>
Can you clarify the issues being seen on re-test? I have just run
malloc_autotest multiple times within the same dpdk-test instance and not
seen any issues.
/Bruce
prev parent reply other threads:[~2025-02-06 11:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 12:59 [PATCH] " Bruce Richardson
2025-01-17 13:52 ` [PATCH v2] " Bruce Richardson
2025-01-17 14:20 ` Dmitry Kozlyuk
2025-01-17 14:26 ` Bruce Richardson
2025-01-17 16:57 ` Stephen Hemminger
2025-01-17 14:40 ` [PATCH v3] " Bruce Richardson
2025-01-24 7:18 ` fengchengwen
2025-02-06 11:40 ` Bruce Richardson [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=Z6SflKJyTbxMRD9g@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=stable@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 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).