From: Patrick Robb <probb@iol.unh.edu>
To: "mannywang(王永峰)" <mannywang@tencent.com>
Cc: Konstantin Ananyev <konstantin.ananyev@huawei.com>, dev@dpdk.org
Subject: Re: [PATCH v4] acl: support custom memory allocators in rte_acl_build
Date: Mon, 1 Dec 2025 10:59:30 -0500 [thread overview]
Message-ID: <CAJvnSUBrCiEYqjTTC5My8pb1f3wQ_H+rV82iLxV9Yd3XY=kR2A@mail.gmail.com> (raw)
In-Reply-To: <F28176920A8AE2E0+20251201120508.120236-1-mannywang@tencent.com>
[-- Attachment #1: Type: text/plain, Size: 122 bytes --]
Recheck-request: iol-intel-Performance
Putting in a retest due to an infra fail at UNH. No action on your end is
needed.
[-- Attachment #2: Type: text/html, Size: 149 bytes --]
next prev parent reply other threads:[~2025-12-01 16:07 UTC|newest]
Thread overview: 20+ 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 [this message]
2025-12-01 16:42 ` Stephen Hemminger
2025-12-01 12:45 ` [PATCH v5] " =?gb18030?B?bWFubnl3YW5nKM3108C35Sk=?=
2025-12-02 2:47 ` fengchengwen
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='CAJvnSUBrCiEYqjTTC5My8pb1f3wQ_H+rV82iLxV9Yd3XY=kR2A@mail.gmail.com' \
--to=probb@iol.unh.edu \
--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 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).