In ds_gspace.c, I add ds_comp flag to structure sync_op. This flag holds the data process status, client-side ds_put request won't complete until this flag become true. The client sent this flag address with object data to the server. Once the server has completed processing the object data, from obj_put_complete() send rpc request along with that flag address back to the client side. Then dcgrpc_server_completion() modify the flag and release client sync lock.
PS: my ds_comp flag is similar to the opid flag in structure sync_op. I feel there must be some bugs on current opid flag implementation. It is better to find out what cause it fail, since my implementation brings an extra RPC communication.
In ds_gspace.c, I add ds_comp flag to structure sync_op. This flag holds the data process status, client-side ds_put request won't complete until this flag become true. The client sent this flag address with object data to the server. Once the server has completed processing the object data, from obj_put_complete() send rpc request along with that flag address back to the client side. Then dcgrpc_server_completion() modify the flag and release client sync lock.
PS: my ds_comp flag is similar to the opid flag in structure sync_op. I feel there must be some bugs on current opid flag implementation. It is better to find out what cause it fail, since my implementation brings an extra RPC communication.