> 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.
The sender side stays of course the same, no modifications needed. > 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. That's what I meant: We would have to insert sys_mbox_msg_free() or something throughout the code where sys_(arch_)mbox_get() is used after we are finished with the messages. I don't know for sure this would be the only necessary modification for multiprocessing, but I guess so. Simon -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger _______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users
