|  | @@ -50,6 +50,8 @@
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  |  /* grpc_workqueue is forward declared in exec_ctx.h */
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  | +/* Deprecated: do not use.
 | 
	
		
			
				|  |  | +   This has *already* been removed in a future commit. */
 | 
	
		
			
				|  |  |  void grpc_workqueue_flush(grpc_exec_ctx *exec_ctx, grpc_workqueue *workqueue);
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  |  //#define GRPC_WORKQUEUE_REFCOUNT_DEBUG
 | 
	
	
		
			
				|  | @@ -69,7 +71,16 @@ void grpc_workqueue_ref(grpc_workqueue *workqueue);
 | 
	
		
			
				|  |  |  void grpc_workqueue_unref(grpc_exec_ctx *exec_ctx, grpc_workqueue *workqueue);
 | 
	
		
			
				|  |  |  #endif
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  | -/** Add a work item to a workqueue */
 | 
	
		
			
				|  |  | +/** Add a work item to a workqueue. Items added to a work queue will be started
 | 
	
		
			
				|  |  | +    in approximately the order they were enqueued, on some thread that may or
 | 
	
		
			
				|  |  | +    may not be the current thread. Successive closures enqueued onto a workqueue
 | 
	
		
			
				|  |  | +    MAY be executed concurrently.
 | 
	
		
			
				|  |  | +
 | 
	
		
			
				|  |  | +    It is generally more expensive to add a closure to a workqueue than to the
 | 
	
		
			
				|  |  | +    execution context, both in terms of CPU work and in execution latency.
 | 
	
		
			
				|  |  | +
 | 
	
		
			
				|  |  | +    Use work queues when it's important that other threads be given a chance to
 | 
	
		
			
				|  |  | +    tackle some workload. */
 | 
	
		
			
				|  |  |  void grpc_workqueue_enqueue(grpc_exec_ctx *exec_ctx, grpc_workqueue *workqueue,
 | 
	
		
			
				|  |  |                              grpc_closure *closure, grpc_error *error);
 | 
	
		
			
				|  |  |  
 |