diff options
| author |  Sanjoy Das <sanjoy@google.com> | 2018-04-26 15:33:38 -0700 |
|---|---|---|
| committer |  TensorFlower Gardener <gardener@tensorflow.org> | 2018-04-26 15:36:18 -0700 |
| commit | ab5de487813b4849dfb5415ee60595654dff06be (patch) | |
| tree | 47ec64e0e02eea2e5fe0fae67e056f343dc905f7 /tensorflow/compiler/xla/executable_run_options.cc | |
| parent | 2808c3f05f7713ff1ab20f365e986a4651180376 (diff) | |
Remove the inter-op thread pool
Forgot about this in cl/194299356. However, when I checked cl/194299356, I
found that we actually (incorrectly?) used the *intra* op thread pool in the
parallel CPU executable? Does that mean the inter op thread pool was always
unused?
PiperOrigin-RevId: 194464734
Diffstat (limited to 'tensorflow/compiler/xla/executable_run_options.cc')
| -rw-r--r-- | tensorflow/compiler/xla/executable_run_options.cc | 11 |
1 files changed, 0 insertions, 11 deletions
diff --git a/tensorflow/compiler/xla/executable_run_options.cc b/tensorflow/compiler/xla/executable_run_options.cc index 99b8f0558e..a472747bd1 100644 --- a/tensorflow/compiler/xla/executable_run_options.cc +++ b/tensorflow/compiler/xla/executable_run_options.cc @@ -45,17 +45,6 @@ stream_executor::Stream* ExecutableRunOptions::stream() const { return stream_; } -ExecutableRunOptions& ExecutableRunOptions::set_inter_op_thread_pool( - tensorflow::thread::ThreadPool* inter_op_thread_pool) { - inter_op_thread_pool_ = inter_op_thread_pool; - return *this; -} - -tensorflow::thread::ThreadPool* ExecutableRunOptions::inter_op_thread_pool() - const { - return inter_op_thread_pool_; -} - ExecutableRunOptions& ExecutableRunOptions::set_intra_op_thread_pool( const Eigen::ThreadPoolDevice* intra_op_thread_pool) { intra_op_thread_pool_ = intra_op_thread_pool; |