[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #28064] pbuf_alloc(PBUF_POOL) is not thread-safe
From: |
Simon Goldschmidt |
Subject: |
[lwip-devel] [bug #28064] pbuf_alloc(PBUF_POOL) is not thread-safe |
Date: |
Fri, 27 Nov 2009 06:24:53 +0000 |
User-agent: |
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; de; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 |
Follow-up Comment #3, bug #28064 (project lwip):
The code in question has been added on jan 28th, 2009 after a discussion on
lwip-users (without a bugtracker entry): Jonathan came up with a calculation
of how long it takes to free ooseq pbufs.
Having that calculation in mind, the most simple solution probably is to call
tcpip_callback (non-blocking) to free the ooseq pbufs in the correct thread
context. Of course, that doesn't work when allocating from an ISR with
NO_SYS=1.
The downside is of course that we still loose some packets until the
ooseq-freeing code runs in tcpip_thread, but that's the best I can currently
think of.
Any comments on this before I make the canges?
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?28064>
_______________________________________________
Nachricht geschickt von/durch Savannah
http://savannah.nongnu.org/