From: =?gb18030?B?bWFubnl3YW5nKM3108C35Sk=?= <mannywang@tencent.com>
To: Konstantin Ananyev <konstantin.ananyev@huawei.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [Internet]RE: [PATCH v7] acl: support custom memory allocators
Date: Tue, 9 Dec 2025 20:56:11 +0800 [thread overview]
Message-ID: <DF324D1D0FA61EA8+07c5be16-e072-482e-a443-a1c424464ce2@tencent.com> (raw)
In-Reply-To: <0887b8f3045744199342bcb94e33f65b@huawei.com>
Thanks for the clarification, and sorry for misunderstanding your
intention earlier.
I’ve updated the implementation to use malloc/aligned_alloc() directly
in running_alloc()
as you suggested. Please check whether the new version matches your
expectation.
On 12/9/2025 6:59 PM, Konstantin Ananyev wrote:
> Sorry, I didn't express myself clear enough.
> My thought was to use malloc/aligned_alloc() directly in running_alloc() function.
> To be more specific here:
> static void *running_alloc(char *name, size_t size, size_t align, int32_t socket_id, void *udata)
> {
> ...
> /* just for the API correctness check */
> If (udata != <expected_value>) {
> /* report error */
> return NULL;
> }
>
> addr = aligned_alloc(align, size);
> if (addr == NULL) {
> /* report error*/
> }
> return addr;
> }
next prev parent reply other threads:[~2025-12-09 12:56 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 2:51 [RFC] rte_acl_build memory fragmentation concern and proposal for external memory support mannywang(王永峰)
2025-11-17 12:51 ` Konstantin Ananyev
2025-11-25 9:40 ` [PATCH] acl: support custom memory allocator =?gb18030?B?bWFubnl3YW5nKM3108C35Sk=?=
2025-11-25 12:06 ` [PATCH v2] " =?gb18030?B?bWFubnl3YW5nKM3108C35Sk=?=
2025-11-25 12:14 ` [PATCH v3] " =?gb18030?B?bWFubnl3YW5nKM3108C35Sk=?=
2025-11-25 14:59 ` Stephen Hemminger
2025-11-26 2:37 ` [Internet]Re: " =?gb18030?B?bWFubnl3YW5nKM3108C35Sk=?=
2025-11-25 18:01 ` Dmitry Kozlyuk
2025-11-26 2:44 ` [Internet]Re: " =?gb18030?B?bWFubnl3YW5nKM3108C35Sk=?=
2025-11-26 7:57 ` Dmitry Kozlyuk
2025-11-26 8:09 ` =?gb18030?B?bWFubnl3YW5nKM3108C35Sk=?=
2025-11-26 21:28 ` Stephen Hemminger
2025-11-27 2:05 ` [Internet]Re: " =?gb18030?B?bWFubnl3YW5nKM3108C35Sk=?=
2025-11-28 13:26 ` Konstantin Ananyev
2025-11-28 15:07 ` =?gb18030?B?bWFubnl3YW5nKM3108C35Sk=?=
2025-12-01 12:05 ` [PATCH v4] acl: support custom memory allocators in rte_acl_build =?gb18030?B?bWFubnl3YW5nKM3108C35Sk=?=
2025-12-01 15:59 ` Patrick Robb
2025-12-01 16:42 ` Stephen Hemminger
2025-12-02 9:33 ` [Internet]Re: " =?gb18030?B?bWFubnl3YW5nKM3108C35Sk=?=
2025-12-01 12:45 ` [PATCH v5] " =?gb18030?B?bWFubnl3YW5nKM3108C35Sk=?=
2025-12-02 2:47 ` fengchengwen
2025-12-02 9:25 ` [PATCH v6] acl: support custom memory allocators =?gb18030?B?bWFubnl3YW5nKM3108C35Sk=?=
2025-12-08 9:43 ` Konstantin Ananyev
2025-12-08 12:48 ` =?gb18030?B?bWFubnl3YW5nKM3108C35Sk=?=
2025-12-08 19:29 ` Stephen Hemminger
2025-12-09 2:30 ` [Internet]Re: " =?gb18030?B?bWFubnl3YW5nKM3108C35Sk=?=
2025-12-09 11:06 ` Konstantin Ananyev
2025-12-10 4:09 ` fengchengwen
2025-12-08 12:57 ` [PATCH v7] " =?gb18030?B?bWFubnl3YW5nKM3108C35Sk=?=
2025-12-09 10:59 ` Konstantin Ananyev
2025-12-09 12:56 ` =?gb18030?B?bWFubnl3YW5nKM3108C35Sk=?= [this message]
2025-12-09 12:52 ` [PATCH v8] " =?gb18030?B?bWFubnl3YW5nKM3108C35Sk=?=
2025-12-02 9:31 ` [Internet]Re: [PATCH v5] acl: support custom memory allocators in rte_acl_build =?gb18030?B?bWFubnl3YW5nKM3108C35Sk=?=
2025-12-11 1:46 ` [PATCH v3] acl: support custom memory allocator Stephen Hemminger
2025-12-11 2:22 ` [Internet]Re: " =?gb18030?B?bWFubnl3YW5nKM3108C35Sk=?=
2025-12-11 2:29 ` =?gb18030?B?bWFubnl3YW5nKM3108C35Sk=?=
2025-12-11 13:04 ` =?gb18030?B?bWFubnl3YW5nKM3108C35Sk=?=
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=DF324D1D0FA61EA8+07c5be16-e072-482e-a443-a1c424464ce2@tencent.com \
--to=mannywang@tencent.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@huawei.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).