From: Thomas Monjalon <thomas@monjalon.net>
To: Yongfeng Wang <mannywang@tencent.com>
Cc: "Konstantin Ananyev" <konstantin.ananyev@huawei.com>,
dev@dpdk.org, "mannywang(王永峰)" <mannywang@tencent.com>
Subject: Re: [PATCH v12] acl: support custom memory allocators
Date: Tue, 17 Feb 2026 13:04:34 +0100 [thread overview]
Message-ID: <5452560.l3KDuRtF6b@thomas> (raw)
In-Reply-To: <8C1540E8503F0A1B+20251217130637.19309-1-mannywang@tencent.com>
17/12/2025 14:06, mannywang(王永峰):
> Allow users to provide custom
> memory allocation hooks for runtime memory in rte_acl_ctx, via
> struct rte_acl_mem_hook.
>
> Key changes:
> - Added struct rte_acl_mem_hook with zalloc, free, and udata.
> - Added rte_acl_set_mem_hook / rte_acl_get_mem_hook to set/get callbacks.
> - Default allocation uses existing rte_zmalloc_socket/rte_free.
> - Modified ACL code to call callbacks for runtime allocations instead
> of rte_zmalloc_socket/rte_free directly.
I've simplified the doc to avoid copying what is already in doxygen
and may become outdated.
Applied, thanks.
next prev parent reply other threads:[~2026-02-17 12:04 UTC|newest]
Thread overview: 46+ 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 ` [Internet]RE: " =?gb18030?B?bWFubnl3YW5nKM3108C35Sk=?=
2025-12-09 12:52 ` [PATCH v8] " =?gb18030?B?bWFubnl3YW5nKM3108C35Sk=?=
2025-12-12 15:00 ` Konstantin Ananyev
2025-12-12 16:41 ` =?gb18030?B?bWFubnl3YW5nKM3108C35Sk=?=
2025-12-12 16:37 ` [PATCH v9] " =?gb18030?B?bWFubnl3YW5nKM3108C35Sk=?=
2025-12-13 1:27 ` [PATCH v10] " =?gb18030?B?bWFubnl3YW5nKM3108C35Sk=?=
2025-12-15 9:48 ` Konstantin Ananyev
2025-12-15 14:43 ` =?gb18030?B?bWFubnl3YW5nKM3108C35Sk=?=
2025-12-15 14:38 ` [PATCH v11] " =?gb18030?B?bWFubnl3YW5nKM3108C35Sk=?=
2025-12-17 13:06 ` [PATCH v12] " =?gb18030?B?bWFubnl3YW5nKM3108C35Sk=?=
2026-02-17 12:04 ` Thomas Monjalon [this message]
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=5452560.l3KDuRtF6b@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@huawei.com \
--cc=mannywang@tencent.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.