Closed yintao707 closed 8 months ago
Seems similar to https://github.com/OpenAMP/open-amp/pull/508, could you have a look?
Seems similar to #508, could you have a look?
Thank you for your review, this has little interaction with #508
Seems similar to #508, could you have a look?
Thank you for your review, this has little interaction with #508
Please could you explain what do you mean by "little interaction" ?
The ns_unbind_cb
is used to inform that the other side destroys it endpoint. Using it for the deinit can introduce side effect in the existing code. The ept release introduced in #508 seems more appropriate. Is it an issue to use it?
Seems similar to #508, could you have a look?
Thank you for your review, this has little interaction with #508
Please could you explain what do you mean by "little interaction" ? The
ns_unbind_cb
is used to inform that the other side destroys it endpoint. Using it for the deinit can introduce side effect in the existing code. The ept release introduced in #508 seems more appropriate. Is it an issue to use it?
yes, you're right, sorry for my inaccurate expression. But the main reason for this modification is that master cannt received NS_DESTORY message, when remote is powered down or exits abnormally. at that time, master needs to actively call ns_unbind_cb to release resources
@arnopo does this change make sense now?
@arnopo does this change make sense now?
As we go to integrate the ept->release
ops, look to me that is should also address the need described here. But perhaps I miss something?
could we close this one as we merge #508?
I close it as no news Please reopen it if needed
When remote cannot send destroy messages, master cannot call ns_unbind_cb, this will cause the master to be unable to release resources