HomeSort by relevance Sort by last modified time
    Searched refs:responsible (Results 1 - 25 of 36) sorted by null

1 2

  /external/syzkaller/vendor/google.golang.org/api/gensupport/
params.go 35 // so the caller is responsible for making a copy if necessary.
  /external/grpc-grpc/src/csharp/Grpc.Core/Logging/
TextWriterLogger.cs 39 /// User is responsible for providing an instance of TextWriter that is thread-safe.
48 /// User is responsible for providing an instance of TextWriter that is thread-safe.
  /external/autotest/site_utils/deployment/
cmdvalidate.py 309 `default_board` isn't checked; the caller is responsible for
363 `default_model` isn't checked; the caller is responsible for
  /external/tensorflow/tensorflow/contrib/verbs/
README.md 23 The design is based on TensorFlow r1.0. An RDMA path is added between servers for tensor transfer (weights, gradients, etc). The existing GRPC path remains and is responsible for "administrative" tasks, such as setting up the RDMA path, exchanging computation graphs, etc.
62 In order to allocate the result and proxy tensors, we need to know the tensor's meta-data, i.e. shape and data-type for DMAable tensors, and proto-size for serialized tensors. Unfortunately, this information is only available on the sender side which complicates manners. In order to avoid sending extra messages for querying the meta-data at each step, we store a local meta-data cache per tensor, which will only be update upon changes. Based on the assumption that the meta-data of a tensor rarely changes between steps, we expect that on most times the cache will only be updated once. The sender is responsible to detect changes in the meta-data, and update the receiver. In order for the sender to know that the meta-data had changed, each **RDMA_MESSAGE_TENSOR_REQUEST** will contain the meta-data that the receiver had grabbed from the local cache. The sender will then compare the meta-data from the message to the tensor's new meta-data.
131 * **class RdmaAdapter** - The base for RDMA communications. It may contain multiple channels and buffers. It is responsible for handling various incoming RDMA messages.
132 * **class RdmaChannel** - Responsible for RDMA connection to a particular node. It manages messagee buffers. A channel has a request table which stores all the pending tensor requests.
133 * **class RdmaMessageBuffer** - Responsible for sending or receiving messages. It has a fixed size memory to store the data. It has a queue to store the pending jobs. A channel has two message buffers one for tx and one for rx.
  /build/soong/
doc.go 17 // Soong itself is responsible for converting the modules read by Blueprint
  /external/u-boot/drivers/gpio/
Kconfig 48 responsible for the general-purpose I/O.
  /build/blueprint/
doc.go 64 // documentation as the "primary builder". This command is responsible for
module_ctx.go 54 // For example, consider a Module that is responsible for generating a library
  /device/linaro/bootloader/edk2/MdeModulePkg/Universal/EbcDxe/X64/
EbcLowLevel.asm 60 ; "The caller is responsible for allocating space for parameters to the
  /external/tensorflow/tensorflow/core/profiler/g3doc/
advise.md 79 it runs through a list of `Checkers`, each one responsible for checking one
  /external/llvm/test/CodeGen/PowerPC/
hello-reloc.s 2 ; which is responsible for writing mach-o relocation entries for (PIC)
  /external/swiftshader/third_party/llvm-7.0/llvm/test/CodeGen/PowerPC/
hello-reloc.s 2 ; which is responsible for writing mach-o relocation entries for (PIC)
  /device/linaro/bootloader/edk2/EdkCompatibilityPkg/Foundation/Library/EdkIIGlueLib/Library/BaseLib/Ia32/
Thunk16.asm 35 ; Here is the layout of the real mode stack. _ToUserCode() is responsible for
  /device/linaro/bootloader/edk2/MdePkg/Library/BaseLib/Ia32/
Thunk16.asm 36 ; Here is the layout of the real mode stack. _ToUserCode() is responsible for
  /external/llvm/bindings/go/llvm/
target.go 259 // responsible for disposing of it by calling the TargetData.Dispose method.
  /external/protobuf/csharp/src/Google.Protobuf/
CodedOutputStream.ComputeSize.cs 174 /// enum field, including the tag. The caller is responsible for
  /external/swiftshader/third_party/llvm-7.0/llvm/bindings/go/llvm/
target.go 259 // responsible for disposing of it by calling the TargetData.Dispose method.
  /bionic/docs/
fdsan.md 43 fdsan attempts to detect and/or prevent file descriptor mismanagement by enforcing file descriptor ownership. Like how most memory allocations can have their ownership handled by types such as `std::unique_ptr`, almost all file descriptors can be associated with a unique owner which is responsible for their closure. fdsan provides functions to associate a file descriptor with an owner; if someone tries to close a file descriptor that they don't own, depending on configuration, either a warning is emitted, or the process aborts.
  /external/syzkaller/vendor/golang.org/x/net/internal/timeseries/
timeseries.go 115 // Keeps a sequence of levels. Each level is responsible for storing data at
  /external/kotlinc/
LICENSE 223 PARTICULAR PURPOSE. You are solely responsible for determining the
479 PARTICULAR PURPOSE. You are solely responsible for determining the
    [all...]
NOTICE 223 PARTICULAR PURPOSE. You are solely responsible for determining the
479 PARTICULAR PURPOSE. You are solely responsible for determining the
    [all...]
  /external/syzkaller/vendor/google.golang.org/appengine/internal/
api.go 116 // Start goroutine responsible for flushing app logs.
api_pre17.go 120 // Start goroutine responsible for flushing app logs.
  /external/python/cpython2/Lib/plat-mac/
pimp.py 362 "responsible" for the contents."""
    [all...]
  /external/fonttools/Lib/fontTools/ufoLib/
__init__.py 371 Note: The caller is responsible for closing the open file.
925 # the user is responsible for closing the FS object
    [all...]

Completed in 2094 milliseconds

1 2