Re: [lwip-members] Pbufs

[Jani Monoses]

Maybe such situations can be predicted and the pool sizes chosen so they are
pools proportional to the items they'll hold or find some good heuristics.
And they'll mostly be application allocated pools so the app might have some
ideas about how they should be used.
Inside lwip core just separate payload and header pools might be enough.
Another idea:if pool sizes would be multiples of the smallest pool than 
larger pools can be 'borrowed' by the smaller pool allocator and vice versa.

> The only drawback with fragmenting into many pools like this (it will make
> it easier in terms of locking that's for sure) is the situation where one
> pool runs out of memory but another has loads free.  It's a change in
> philosophy away from the "lwIP is a really low memory usage stack".  This
> doesn't bother me particularly, but it might others.
> 
> Kieran
> 
> 
> 
> _______________________________________________
> lwip-members mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/lwip-members