[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-users] lwIP freeing up resources
From: |
Mahavir Jain |
Subject: |
[lwip-users] lwIP freeing up resources |
Date: |
Thu, 8 Aug 2013 14:32:58 +0530 |
User-agent: |
Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130311 Thunderbird/17.0.4 |
Hi All,
We are using lwIP 1.4.1 release and I have below question related to lwIP stack
or rather in general about networking stack usage in low level embedded systems:
How do we make sure to release all allocated resources like connections or
sockets for particular thread/task in case we have to delete that particular
thread/task ?
For example, consider a scenario where a thread acting as web server, is blocked
in accepted tcp connection on recv() call, and for some reason interface goes
down (or any other reason) and we have to re-start web server task. Another
thread deletes web-server task but what about socket/connection that is blocked
on recv(), and relevant resources in use ?
For systems where there is no such separation like user <--> kernel space how
this should be handled, i.e. to free up all resources once process is
deleted/killed ?
Any response in general or relevant to lwIP stack would be really helpful.
Mahavir
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [lwip-users] lwIP freeing up resources,
Mahavir Jain <=