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

[Jared Grubb]

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

> I'd like to know how other stacks (that are advertising zero-copy) solve
this... Although this seems a problem only for the sockets layer, a netconn
app can use the new pbuf type.

I was reading the KAME IPv6 (the BSD IPv6 code) implementation book, and I
remember it saying packets are copied upon coming into the socket API. 

For us, this would make sense too.... copy as early as possible (if
necessary) and make the stack itself 100% zero-copy. Then, we must only have
special checks along the interface to the application. Network layer and lower
(IP, ARP, driver, etc) would always assume zero-copy, whereas transport layer
makes the conversions.

    _______________________________________________________

Reply to this item at:

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

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