I don't think the core would have to free anything in the case of the
threaded code. If you are a one machine system, don't actually copy
the data in the mbox_post: Ignore the size.
If you are a multiprocess machine, you have to allocate the space in
the sys_mbox_post code on the other client machine (or process), and
it might be a little tricky. The sender's (or poster) side should be
easy. I have to think about the recv/fetch side.
On Dec 14, 2008, at 3:31 PM, [email protected] wrote:
Rishi Khan wrote:
Does it really need to know the 'type' of message, or does it
just need the size of the message.
Hmm, good idea, might be worth a try! But that would also mean that
data taken out of an mbox must be explicitly freed (since it is
duplicated by sending it through the mbox). This means there is
code to be added to the core files.
Still, this might be the simplest way to achieve multiprocess-
compatibility.
Simon
_______________________________________________
lwip-users mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/lwip-users
_______________________________________________
lwip-users mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/lwip-users
