[lwip-devel] [bug #3031] Implement a new fully pool-based pbuf implementation.

[Simon Goldschmidt]

Follow-up Comment #9, bug #3031 (project lwip):

[I'm working on a mem to memp implementation (that is written in ANSI C; and
I'm short of time at the moment so it could take a while).]

>If an application sends and receives a lot of small packets (text-based
communication, for example) with an occasional large packet, the pools can be
configured to be small and pbuf chaining takes care of the large packets.

That would imply that PBUF_RAM packets are not guaranteed any more to be one
piece of memory. That would be a good option for low memory targets, though.
But I think the stack is not yet ready to handle pbuf chains everywhere...

Also, we might need some kind of algorithm when to use a bigger buffer and
waste memory and when to use 2 smaller ones. And we would need some kind of
configuration options to use the 'one-piece' or chained method.

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?3031>

_______________________________________________
  Nachricht geschickt von/durch Savannah
  http://savannah.nongnu.org/