Re: [PATCH v3 0/7] allocate cache entries from memory pool
- From
Stefan Beller <sbeller@google.com>
- Date
- May 25, 2018, 22:53 UTC
- Message-ID
- <CAGZ79kbZcqzRAqip_CbEmxxhXr_UcAfO-siRgoVjqdd7XsH8sg@mail.gmail.com>
- In-Reply-To
- <BL0PR2101MB11068051AD589871D4D707CBCE6A0@BL0PR2101MB1106.namprd21.prod.outlook.com>
Show 6 quoted lines
> > The memory pool design makes some tradeoffs. It is not meant to > be completely replace malloc / free as a general purpose > allocator, but rather used in scenarios where the benefit (faster > allocations, lower bookkeeping overhead) is worth the > tradeoffs (not able to free individual allocations).
So this is the actual stated design goal of this memory pool? Fast&cheap allocation with little overhead for giving up individual frees?
> We debated several approaches for what to do here
it would be awesome if the list could participate in the discussion even if only read-only.