[Top][All Lists]

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

[lwip-devel] [bug #21433] Calling mem_free/pbuf_free from interrupt cont

From: Simon Goldschmidt
Subject: [lwip-devel] [bug #21433] Calling mem_free/pbuf_free from interrupt context isn't safe
Date: Fri, 28 Mar 2008 14:04:12 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv: Gecko/20080311 Firefox/

Follow-up Comment #21, bug #21433 (project lwip):

> Well, the point was to allow mem_free from other contexts such as 
> interrupts. Allowing mem_alloc as well would indeed be a different kettle
of fish.

Of course. Maybe I don't fully understand your approach. I try to summarize
the changes:

- The change is only valid if the heap is protected by SYS_ARCH_PROTECT, not
if it is protected using a semaphore
- In mem_malloc, in the big for loop, we include the
SYS_ARCH_UNPROTECT/SYS_ARCH_PROTECT/check like you stated in comment #10 to
allow mem_free to run in that case and keep the max time interrupts are
disabled low (short: "blip phase" :)

But in this case, how do you keep mem_malloc from running again while another
thread is in the "blip phase"?


Reply to this item at:


  Nachricht geschickt von/durch Savannah

reply via email to

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