From aadc13adc0dd9e7f81c20680dc23ec09fd1b91c9 Mon Sep 17 00:00:00 2001
From: Jan Tattermusch <jtattermusch@users.noreply.github.com>
Date: Mon, 22 Jun 2015 12:25:55 -0700
Subject: [PATCH] clarify grpc_call_start_batch thread safety.
---
include/grpc/grpc.h | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/include/grpc/grpc.h b/include/grpc/grpc.h
index 71ffaa4a01..e07376fa78 100644
--- a/include/grpc/grpc.h
+++ b/include/grpc/grpc.h
@@ -387,7 +387,10 @@ grpc_call *grpc_channel_create_registered_call(
The order of ops specified in the batch has no significance.
Only one operation of each type can be active at once in any given
batch.
- THREAD SAFETY: grpc_call_start_batch is thread-compatible */
+ THREAD SAFETY: access to grpc_call_start_batch in multi-threaded environment
+ needs to be synchronized. As an optimization, you may synchronize batches
+ containing just send operations independently from batches containing just
+ receive operations. */
grpc_call_error grpc_call_start_batch(grpc_call *call, const grpc_op *ops,
size_t nops, void *tag);
--
GitLab