[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: |
Thu, 26 Nov 2009 16:59:12 +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 |
Update of bug #28064 (project lwip):
Severity: 3 - Normal => 5 - Blocker
Status: None => In Progress
Assigned to: None => goldsimon
Summary: pbuf_alloc(PBUF_POOL) cannot be used from ISR any
more => pbuf_alloc(PBUF_POOL) is not thread-safe
_______________________________________________________
Follow-up Comment #2:
Updated summary and status:
This is a blocker: if the pbuf-pool is empty, pbuf_alloc_pool iterates the
tcp_active_pcbs list from every thread. This has been introduced with 1.3.1.
As nice as this feature (reclaiming ooseq pbufs) is, it doesn't work as it
is.
If we still want this, we have to implement it in another way so that the
ooseq-freeing code runs in the tcpip-thread.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?28064>
_______________________________________________
Nachricht geschickt von/durch Savannah
http://savannah.nongnu.org/