[
https://issues.apache.org/jira/browse/TS-2581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15276958#comment-15276958
]
ASF GitHub Bot commented on TS-2581:
------------------------------------
Github user zwoop commented on a diff in the pull request:
https://github.com/apache/trafficserver/pull/622#discussion_r62565771
--- Diff: lib/ts/ink_memory.h ---
@@ -89,6 +89,11 @@ void *ats_free_null(void *ptr);
void ats_memalign_free(void *ptr);
int ats_mallopt(int param, int value);
+/* use IOBufs as the underlying allocation pool */
+void *ats_malloc_pool(size_t size);
+void *ats_realloc_pool(void *ptr, size_t size);
+void ats_free_pool(void *ptr);
--- End diff --
All the other memory declarations (like ats_malloc) are already in
ink_memory.h, no?
> Add / modify APIs to allow easy freelist allocation of iobuffer's from C/C++
> plugins
> ------------------------------------------------------------------------------------
>
> Key: TS-2581
> URL: https://issues.apache.org/jira/browse/TS-2581
> Project: Traffic Server
> Issue Type: New Feature
> Components: TS API
> Reporter: Leif Hedstrom
> Assignee: Jason Kenny
> Labels: api-addition, newbie
> Fix For: 7.0.0
>
>
> This would allow for efficient allocations in plugins, such that they can do
> an in-place new() on a chunk of memory (iobuffer).
> The API / features should make it easy and possible to asks for an iobuffer
> of at least size <x>. It can return a bigger one, at which point, you'd waste
> some. But this allows us to reuse / repurpose the existing iobuffer
> allocation.
> Phil points out that there are existing iobuffer allocation APIs, so maybe
> something in conjunction with that is appropriate. I would like for this to
> be easy on the plugin user though, such that it's as simple as "malloc/free"
> chains.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
