[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lwip-devel] mem(p) allocator change request
From: |
christiaan . simons |
Subject: |
Re: [lwip-devel] mem(p) allocator change request |
Date: |
Tue, 30 Mar 2004 09:42:50 +0200 |
address@hidden wrote on 29-03-2004
17:10:48:
> but my question is what you mean with "externally
> allocated pools"?
To be more precise, pools defined outside the memp module.
> What I would like is to let the stack rely on another (extern)
> pool allocator taking care of allocations and freeing of memory
> for arbitrary sizes (I use a number of pools with different block
> sizes to minimize the waste of unused space per block).
This is a different approach. I would like to use the memp
allocator if there isn't another one available.
I think we should provide access to the external
allocator in the port/architecture file cc.h.
E.g. #define lwip_platform_pool_alloc() etc,
and let memp export lwip_pool_alloc() either as the
default implementation, or as the platform specific one.
> I don't get this part. Why would each module need to provide pools?
I want to remove the pool from the memp module,
and let memp (or another module) only do the (de)allocations.
> Sub allocate? feels like reimplementing yet another allocator here..?
Yes, I might want to be able to chop up things even further,
though it's probably silly.
Hope this clarifies things,
Christiaan
The information contained in this communication is confidential and is
intended solely for the use of the individual or entity to whom it is
addressed. Axon Digital Design Group is neither liable for the proper nor
for the complete transmission of the information contained in this
communication nor for any delay in its receipt. Axon Digital Design Group
does not guarantee that the integrity of this communication has been
maintained nor that the communication is free of viruses, interceptions or
interference. If you are not the intended recipient of this communication,
you are hereby notified that reading, disseminating, distributing or
copying this message is strictly prohibited. In that case please return the
communication to the sender and delete and destroy all copies. In carrying
out its engagements, Axon Digital Design Group applies general terms and
conditions, which contain a clause that limits its liability. A copy of
these terms and conditions is available on request free of charge.
Re: [lwip-devel] mem(p) allocator change request, lukem . lwip, 2004/03/29