lwip-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-users] Correct way to free pbufs after tcp_recv callback finished


From: Gabriel Harrison
Subject: [lwip-users] Correct way to free pbufs after tcp_recv callback finished
Date: Mon, 27 Jun 2016 10:41:39 +0000

Hi,

 

We’ve started our first lwIP project, following the instructions on http://lwip.wikia.com/wiki/Raw/TCP to create our high level functions and taking the device level IRQ functions and ethernetif.c from the SDK for our chip (Freescale Kinetis K60)

 

Although we appear to have set things up correctly – we can send & receive requests – the TCP pbufs pool is not running out and it looks like they are not being freed after the receive has been processed.

 

I can see in tcp_recv_null in tcp.c that pbuf_free(p); is called after tcp_recved(pcb, p->tot_len); but I can’t find any info about freeing the pbufs in the wiki via either pbuf_free or pbuf_free_callback.

 

Should I be calling pbuf_free/ pbuf_free_callback in our receive callback or is this supposed to be handled elsewhere?

 

Thanks,

 

Gabriel


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

reply via email to

[Prev in Thread] Current Thread [Next in Thread]