- Sort Score
- Result 10 results
- Languages All
Results 1 - 8 of 8 for custom (0.29 sec)
-
tensorflow/c/eager/custom_device_testutil.h
limitations under the License. ==============================================================================*/ #ifndef TENSORFLOW_C_EAGER_CUSTOM_DEVICE_TESTUTIL_H_ #define TENSORFLOW_C_EAGER_CUSTOM_DEVICE_TESTUTIL_H_ // A simple logging device to test custom device registration. #include <memory> #include "tensorflow/c/c_api.h" #include "tensorflow/c/eager/c_api.h" #include "tensorflow/c/eager/c_api_experimental.h"
C - Registered: Tue Apr 30 12:39:09 GMT 2024 - Last Modified: Thu Aug 27 23:39:24 GMT 2020 - 1.6K bytes - Viewed (0) -
tensorflow/c/eager/parallel_device/parallel_device.h
// on each underlying device. // // For example if `device_name` is // "/job:localhost/replica:0/task:0/device:CUSTOM:0" // and `underlying_devices` is // {"/job:localhost/replica:0/task:0/device:GPU:0", // "/job:localhost/replica:0/task:0/device:GPU:1"} // Then executing an operation on CUSTOM:0 will execute it on GPU:0 and GPU:1. // // Implicit copies onto `device_name` are allowed, replicating the value once
C - Registered: Tue Apr 30 12:39:09 GMT 2024 - Last Modified: Thu Jun 04 21:49:16 GMT 2020 - 2.9K bytes - Viewed (0) -
tensorflow/c/c_api.h
// Creates a new operation - see `TF_NewOperation` for more details. // // The lock for `graph` must be held when calling this function. // // Unless implementing advanced behavior, like custom gradient functions, you // most likely need to call `TF_NewOperation` instead. TF_CAPI_EXPORT extern TF_OperationDescription* TF_NewOperationLocked( TF_Graph* graph, const char* op_type, const char* oper_name);
C - Registered: Tue Apr 30 12:39:09 GMT 2024 - Last Modified: Thu Oct 26 21:08:15 GMT 2023 - 82.3K bytes - Viewed (3) -
tensorflow/c/eager/c_api_experimental.h
// be an empty string if no device was explicitly requested, but will // otherwise be the name of this custom device. Ops are placed onto a custom // device if any of their inputs are on that custom device, but custom devices // are free to set a bad status in order to require explicit placement. void (*execute)(const TFE_Op* op, int* num_outputs,
C - Registered: Tue Apr 30 12:39:09 GMT 2024 - Last Modified: Wed Feb 21 22:37:46 GMT 2024 - 39.5K bytes - Viewed (0) -
tensorflow/c/experimental/grappler/grappler_internal.h
#include "tensorflow/c/c_api.h" #include "tensorflow/c/experimental/grappler/grappler.h" #include "tensorflow/core/framework/graph.pb.h" #include "tensorflow/core/grappler/optimizers/custom_graph_optimizer.h" #include "tensorflow/core/grappler/optimizers/custom_graph_optimizer_registry.h" #include "tensorflow/core/platform/status.h" #include "tensorflow/core/protobuf/rewriter_config.pb.h" namespace tensorflow { namespace grappler {
C - Registered: Tue Feb 27 12:39:08 GMT 2024 - Last Modified: Wed Jun 08 08:58:23 GMT 2022 - 3.5K bytes - Viewed (1) -
tensorflow/c/eager/immediate_execution_operation.h
virtual ImmediateExecutionContext* GetContext() const = 0; // Following two methods are used to support custom device. // Return true if the inputs contain custom device tensor handle. It means // that the argument need to be handled by a custom device. virtual bool HasCustomDeviceInput() const = 0; virtual const tensorflow::OpDef* OpDef() const = 0;
C - Registered: Tue Apr 30 12:39:09 GMT 2024 - Last Modified: Mon Sep 26 22:40:32 GMT 2022 - 3.6K bytes - Viewed (0) -
tensorflow/c/eager/immediate_execution_context.h
// Experimental Custom Device. //===--------------------------------------------------------------------===// virtual CustomDeviceOpHandler& GetCustomDeviceOpHandler() = 0; // Returns whether `device_name` is registered as a custom device. virtual bool IsCustomDevice(const string& device_name) = 0; // Register a custom device. It will return error is the device name is
C - Registered: Tue Apr 30 12:39:09 GMT 2024 - Last Modified: Thu Jul 06 08:34:00 GMT 2023 - 12.3K bytes - Viewed (0) -
tensorflow/c/experimental/filesystem/filesystem_interface.h
/// tied with TensorFlow releases and should have their own versioning metadata /// in addition with the data discussed in this section. Each plugin author can /// use a custom scheme, but it should only relate to changes in plugin code. /// This section only touches metadata related to the versioning of this /// interface that is shared by all possible plugins. ///
C - Registered: Tue Apr 30 12:39:09 GMT 2024 - Last Modified: Fri May 27 17:36:54 GMT 2022 - 53.1K bytes - Viewed (0)