[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [patch #7658] Make pbuf_free() send PBUF_POOL pbufs to Ethe
[lwip-devel] [patch #7658] Make pbuf_free() send PBUF_POOL pbufs to Ethernet driver directly.
Wed, 04 Jul 2012 10:50:32 +0000
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:18.104.22.168) Gecko/20111108 Fedora/3.6.24-1.fc14 Firefox/3.6.24
Follow-up Comment #3, patch #7658 (project lwip):
Just found task#11472 which this patch is "sort-of" related to.
The issue of supporting "fixed location RX" buffers can easily be achieved by
using the lwIP support for MEMP_SEPARATE_POOLS to allow the specific driver to
provide the location for the actual memp_memory_PBUF_POOL_base vector... and
in-conjunction with a free hook as provided by this patch allows drivers to
control RX buffers from fixed locations.
Admittedly at the moment it is for the complete PBUF_POOL space (and not
specifically RX-only buffers). If a completely stand-alone RX space is
required for a target then ideally the CUSTOM PBUF support could be improved
(exported) to allow drivers to easily implement a separate RX "custom" PBUF
pool. i.e. allow LWIP_SUPPORT_CUSTOM_PBUF to be a lwipopts.h->opt.h option
(and not just in pbuf.h), with suitable exported API support so that drivers
can use the CUSTOM support for fixed location, DMA-ring-buffer, etc. So this
patch would not strictly be needed, especially if the LWIP_SUPPORT_CUSTOM_PBUF
support allowed for "buffer re-use" (as this patch does).
Reply to this item at:
Message sent via/by Savannah
|[Prev in Thread]
||[Next in Thread]|
- [lwip-devel] [patch #7658] Make pbuf_free() send PBUF_POOL pbufs to Ethernet driver directly.,
James Smith <=