DPDK patches and discussions
 help / color / mirror / Atom feed
From: fengchengwen <fengchengwen@huawei.com>
To: Bruce Richardson <bruce.richardson@intel.com>, <dev@dpdk.org>
Cc: <stable@dpdk.org>
Subject: Re: [PATCH v3] test: improve resiliency of malloc autotest
Date: Fri, 24 Jan 2025 15:18:11 +0800	[thread overview]
Message-ID: <0e91d822-ed10-4dae-8f0a-7169e7819517@huawei.com> (raw)
In-Reply-To: <20250117144112.2544963-1-bruce.richardson@intel.com>

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;
}

On 2025/1/17 22:40, Bruce Richardson wrote:
> The test case "test_multi_alloc_statistics" was brittle in that it did
> some allocations and frees and then checked statistics without
> considering the initial state of the malloc heaps. This meant that,
> depending on what allocations/frees were done beforehand, the test can
> sometimes fail.
> 
> We can improve resiliency by running the test using a new malloc heap,
> which means it is unaffected by any previous allocations.
> 
> Bugzilla ID: 1579
> Fixes: a40a1f8231b4 ("app: various tests update")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> ---
> v3:
> * switched allocation from mmap to malloc allowing it work on windows
> * use explicit alignment of the malloc return value to ensure memory
>   added to heap is page-aligned.
> 
> v2:
> * removed unnecessary extra include
> * only added new code for non-windows, since using mmap for allocation.
> ---
>  app/test/test_malloc.c | 35 +++++++++++++++++++++++++++++++++++
>  1 file changed, 35 insertions(+)
> 
> diff --git a/app/test/test_malloc.c b/app/test/test_malloc.c
> index 02a7d8ef20..9e73c0da09 100644
> --- a/app/test/test_malloc.c
> +++ b/app/test/test_malloc.c
> @@ -25,6 +25,7 @@
>  #include <rte_malloc.h>
>  #include <rte_cycles.h>
>  #include <rte_random.h>
> +#include <rte_eal_paging.h>
>  #include <rte_string_fns.h>
>  
>  #define N 10000
> @@ -272,6 +273,34 @@ test_multi_alloc_statistics(void)
>  	size_t size = 2048;
>  	int align = 1024;
>  	int overhead = 0;
> +	const size_t pgsz = rte_mem_page_size();
> +	const size_t heap_size = (1 << 21);
> +
> +	if (pgsz < heap_size) {
> +		printf("Page size is smaller than heap size\n");
> +		return TEST_SKIPPED;
> +	}
> +
> +	if (rte_malloc_heap_create(__func__) != 0) {
> +		printf("Failed to create test malloc heap\n");
> +		return -1;
> +	}
> +	/* Allocate some memory using malloc and add it to our test heap. */
> +	void *unaligned_memory = malloc(heap_size + pgsz);
> +	if (unaligned_memory == NULL) {
> +		printf("Failed to allocate memory\n");
> +		return -1;
> +	}
> +	void *memory = RTE_PTR_ALIGN(unaligned_memory, pgsz);
> +	if (rte_malloc_heap_memory_add(__func__, memory, heap_size, NULL, 1, heap_size) != 0) {
> +		printf("Failed to add memory to heap\n");
> +		return -1;
> +	}
> +	socket = rte_malloc_heap_get_socket(__func__);
> +	if (socket < 0) {
> +		printf("Failed to get socket for test malloc heap.\n");
> +		return -1;
> +	}
>  
>  	/* Dynamically calculate the overhead by allocating one cacheline and
>  	 * then comparing what was allocated from the heap.
> @@ -371,6 +400,12 @@ test_multi_alloc_statistics(void)
>  		printf("Malloc statistics are incorrect - freed alloc\n");
>  		return -1;
>  	}
> +
> +	/* cleanup */
> +	rte_malloc_heap_memory_remove(__func__, memory, heap_size);
> +	rte_malloc_heap_destroy(__func__);
> +	free(unaligned_memory);
> +
>  	return 0;
>  }
>  


      reply	other threads:[~2025-01-24  7:18 UTC|newest]

Thread overview: 7+ 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 [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=0e91d822-ed10-4dae-8f0a-7169e7819517@huawei.com \
    --to=fengchengwen@huawei.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --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).