Re: [lwip-users] Allocating and deallocating an mbox in different threads

[Kieran Mansley]

On Wed, 2007-04-18 at 04:04 -0700, Andrew Lentvorski wrote:
> Kieran Mansley wrote:
> > On Wed, 2007-04-18 at 03:19 -0700, Andrew Lentvorski wrote:
> > 
> >> In this instance, though, the freeing of the mbox is being used as a 
> >> reverse message between the API layers.  That's uncool and makes all 
> >> kinds of assumptions about the implementation of mbox.
> >>
> >> Is there any way to change this to an actual explicit reverse message 
> >> and let the original thread do the deallocation?
> > 
> > Can you give a bit more detail about what problem this is causing?
> 
> The problem this is causing is that I have two mbox types of which only 
> one is "memory-based".

So if I understand correctly I think this is specific to the
modifications that you've made?  I can't see a functional problem with
changing this as you suggest to post a message that would then result in
the freeing of the mbox, but I haven't looked at it in detail.  I think
though that as it is specific to your modifications, it's not
appropriate to make this change in the general code base.

Kieran