RE: [lwip-devel] Best method to allocate space for external packets

[Grubb, Jared]

Just like I am proposing for user-defined pools, we could create
user-defined pbuf pools. This would require a few changes, but the total
size of the changes would not be that large. We have a lot of
flexibility with the memp_std.h file, and in the latest version I posted
a few days ago, there is a separate LWIP_PBUF_POOL macro to simplify the
declaration of the two pbuf pools used in lwIP right now.

I can create a mock-up of what this would require in pbuf.c later today
for you all to review, if you think this would be useful.

I feel it would be useful because currently we say that PBUF_POOL is
useful for, among other things, hardware receive buffers, but the
PBUF_POOL is used a bit in lwIP too (SNMP and PPP come to mind).
Allowing these to be separate pools would be useful. To preserve
backwards compatibility, we can make it so there is only one pbuf
mempool.

-----Original Message-----
From: address@hidden
[mailto:address@hidden On Behalf Of
Jonathan Larmour
Sent: Thursday, August 16, 2007 4:34 PM
To: lwip-devel
Subject: Re: [lwip-devel] Best method to allocate space for external
packets

Thomas Taranowski wrote:

I don't think we can try and fit anything into the existing memp
allocator 
system, since it's inherent in the design of that that all the pools are

contiguous and sequential.

The simplification here is that _all_ pool pbufs would then be allocated

like that. This is fine most of the time but could be more complicated
if 
there are multiple devices, not all of which need this system. Should we

be worried about that? I don't know but from my thinking about it, it 
would be a very hard problem to solve without breaking abstractions
and/or 
lots of APIs. Maybe we should leave it to the port and driver.

Thoughts?


_______________________________________________
lwip-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/lwip-devel