[lwip-devel] [task #6735] Provide new pbuf type: PBUF_RAM_NOCOPY

[Jonathan Larmour]

Follow-up Comment #21, task #6735 (project lwip):

> Why can't PBUF_RAM_NOCOPY be freed by the allocating code as
> well, making the driver reference the pbuf before enqueueing it
> for sending?

But if the user is unable to reuse the pbuf or payload, what would be the
point? It would just waste code.

> I don't see any indication for letting the stack (or driver) free
> the pbuf when looking at the name (NOCOPY)... And it would 
> certainly be more straightforward like the other pbuf types that 
> way... 

Do you mean you haven't seen that in the patch? If so, yes you're right -
that patch is only the first part of the work. As per comment #7 there's more
to come, but that will wait till after 1.3.

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/task/?6735>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/