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

[Simon Goldschmidt]

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

... and it _is_ a problem! At least for TCP, the other parts have such low
requirements that small PBUF_POOL pbufs are big enough.

tcp_enqueue wants to copy the whole data (a segment) using memcpy an that
fails for a pbuf chain. I don't know yet if it is the only point, since a
segment has a dataptr and a len value, I'll study that.

In the meantime, I'll add assertions in places where a PBUF_RAM type that is
chained can be dangerous.

By the way, in _my_ sources, in pbuf_alloc, I am allocating PBUF_POOLs
instead of PBUF_RAMs and fail if the pool has fallen below a low-water-mark.
PBUF_RAMs are effectively removed from the binary (and so is mem.c for me,
aside from dhcp, snmp & loopif but I don't use them ;-) ).

    _______________________________________________________

Reply to this item at:

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

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