As the comments of co_post_reply (in cart’s api.h):
/**
* Collective RPC post-reply callback.
* This is an optional callback. If specified, it will execute after
* reply is sent to parent (after co_aggregate executes).
*/
For example, bcast traverse a sub-tree like node_a (parent) -> node_b (self) -> node_c and node_d (children).
At request forward phase -- node_b gets request from node_a and forward to node_c+node_d.
At reply aggregate phase – node_b will send reply to node_a, but the reply will be delayed until gets and aggregates replies from its children (co_aggregate is for this purpose). When the aggregated
reply sent to parent, it will call the co_post_reply to do some cleanup work if it is provided (free memory or whatever else).
Thanks,
Xuezhao
From:
<daos@daos.groups.io> on behalf of Colin Ngam <colin.ngam@...> Reply-To: "daos@daos.groups.io" <daos@daos.groups.io> Date: Thursday, May 7, 2020 at 8:26 AM To: "daos@daos.groups.io" <daos@daos.groups.io> Subject: [daos] Cart corp operations
Greetings,
Is “co_aggeregate” operation called before or after “ca_post_reply” operation?