Wireshark-dev: Re: [Wireshark-dev] RFD: The Future of Memory Management in Wireshark
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Guy Harris <guy@xxxxxxxxxxxx>
Date: Tue, 23 Oct 2012 20:10:57 -0700
On Oct 18, 2012, at 6:01 PM, Evan Huus <eapache@xxxxxxxxx> wrote:

> I have linked a tarball [2] containing the following files:
> - wmem_allocator.h - the definition of the allocator interface
> - wmem_allocator_glib.* - a simple implementation of the allocator
> interface backed by g_malloc and a singly-linked list.

Presumably an implementation of the allocator could, instead of calling a lower-level memory allocator (malloc(), g_malloc(), etc.) for each allocation call, allocate larger chunks and parcel out memory from the larger chunks (as the current emem allocator does), if that ends up saving enough CPU, by making fewer allocate and free calls to the underlying memory allocator, so as to make it worth whatever wasted memory we have at the ends of chunks?