OpenGrok
Home
Sort by relevance
Sort by last modified time
Full Search
Definition
Symbol
File Path
History
|
|
Help
Searched
refs:information
(Results
76 - 100
of
1092
) sorted by null
1
2
3
4
5
6
7
8
9
10
11
>>
/prebuilts/go/darwin-x86/src/cmd/vendor/github.com/ianlancetaylor/demangle/
c++filt.go
41
var help = flag.Bool("h", false, "Display help
information
")
42
var debug = flag.Bool("d", false, "Display debugging
information
for strings on command line")
48
// -V (print version
information
)
/prebuilts/go/darwin-x86/src/vendor/golang_org/x/net/idna/
trieval.go
12
// info holds
information
from the IDNA mapping table for a single rune. It is
13
// the value returned by a trie lookup. In most cases, all
information
fits in
82
// join types and additional rune
information
/prebuilts/go/linux-x86/src/cmd/vendor/github.com/google/pprof/internal/binutils/
addr2liner_nm.go
33
//
information
from a binary.
43
// newAddr2LinerNM starts the given nm command reporting
information
about the
94
// addrInfo returns the stack frame
information
for a specific program
/prebuilts/go/linux-x86/src/cmd/vendor/github.com/ianlancetaylor/demangle/
c++filt.go
41
var help = flag.Bool("h", false, "Display help
information
")
42
var debug = flag.Bool("d", false, "Display debugging
information
for strings on command line")
48
// -V (print version
information
)
/prebuilts/go/linux-x86/src/vendor/golang_org/x/net/idna/
trieval.go
12
// info holds
information
from the IDNA mapping table for a single rune. It is
13
// the value returned by a trie lookup. In most cases, all
information
fits in
82
// join types and additional rune
information
/external/icu/icu4c/source/samples/
defs.mk
9
# Load ICU
information
. You can copy this to other makefiles #######
/external/llvm/test/MC/Mips/
elf_reginfo.s
9
# Check for register
information
sections.
/external/mesa3d/docs/specs/
MESA_agp_offset.spec
39
information
.
/external/protobuf/examples/
list_people.go
41
//
information
inside.
/external/walt/docs/
PrivacyPolicy.md
6
WALT app processes all data locally on the Android device and does not transmit any
information
via the Internet,
/frameworks/rs/script_api/
rs_core.spec
31
For more
information
on how to develop with RenderScript and how the runtime and Android
/hardware/interfaces/camera/provider/
README.md
12
More complete
information
about the Android camera HAL and subsystem can be found at
/prebuilts/go/darwin-x86/src/syscall/
route_netbsd.go
30
// network interface arrival and departure
information
.
route_openbsd.go
30
// network interface arrival and departure
information
.
/prebuilts/go/linux-x86/src/syscall/
route_netbsd.go
30
// network interface arrival and departure
information
.
route_openbsd.go
30
// network interface arrival and departure
information
.
/toolchain/binutils/binutils-2.27/gas/testsuite/gas/i386/
debug1.d
3
#name: DWARF2 debugging
information
1
/external/libunwind/doc/
unw_flush_cache.tex
27
\Func{unw\_flush\_cache}() may flush more
information
than requested,
32
information
cached on behalf of address space \Var{as} is flushed.
unw_get_proc_info.tex
20
information
about the procedure that created the stack frame
23
return the
information
. The \Type{unw\_proc\_info\_t} has the
28
(e.g., due to lack of unwind
information
), the \Var{start\_ip}
32
cannot be determined (e.g., due to lack of unwind
information
),
36
language-specific
information
needed during exception handling. If
libunwind-setjmp.tex
47
correct unwind
information
. On newer platforms, this is rarely an
50
unwound during a \Func{longjmp}() have correct unwind
information
53
information
).
/prebuilts/go/darwin-x86/src/cmd/cgo/
main.go
32
// A Package collects
information
about the package we're going to write.
50
// A File collects
information
about a single Go input file.
94
// A Name collects
information
about C.xxx.
132
// A Type collects
information
about a type in both the C and Go worlds.
142
// A FuncType collects
information
about a function type in both the C and Go worlds.
192
var dynlinker = flag.Bool("dynlinker", false, "record dynamic linker
information
in -dynimport mode")
219
// and dumps
information
about the imported symbols and the
221
// appropriate executable and then use its import
information
/prebuilts/go/linux-x86/src/cmd/cgo/
main.go
32
// A Package collects
information
about the package we're going to write.
50
// A File collects
information
about a single Go input file.
94
// A Name collects
information
about C.xxx.
132
// A Type collects
information
about a type in both the C and Go worlds.
142
// A FuncType collects
information
about a function type in both the C and Go worlds.
192
var dynlinker = flag.Bool("dynlinker", false, "record dynamic linker
information
in -dynimport mode")
219
// and dumps
information
about the imported symbols and the
221
// appropriate executable and then use its import
information
/toolchain/binutils/binutils-2.27/gas/testsuite/gas/mips/
loc-swap.d
3
#name: MIPS DWARF-2 location
information
with branch swapping
7
# Verify that DWARF-2 location
information
for instructions reordered
mips16@loc-swap.d
3
#name: MIPS DWARF-2 location
information
with branch swapping
7
# Verify that DWARF-2 location
information
for instructions reordered
/external/tensorflow/tensorflow/contrib/verbs/
patch_notes_verbs_with_0_copies.md
27
2. The address of the destination Tensor needs to be sent to the sender side for writing, meaning that the result/proxy tensor should be pre-allocated on the receiver side, prior to sending the tensor request. In order to do that, we need to know its meta-data, i.e. shape and data-type for DMAble 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 on each step, we store a local meta-data cache per tensor. 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. When the sender receives a request for a tensor, if it is the first time this tensor is requested, or in the rare case that the meta-data did change, the sender will first send a meta-data response, on which the receiver will update the local cache, and reallocate the result/proxy tensors if required. When the receiver sends the tensor request, it will contain also the meta-data currently stored in its local cache, so the sender can compare it to see if there was a change.
30
5. With the addition of tensor pre-allocation, we noticed there is a large code similarity between sending the first tensor request and re-sending the request in case of meta-data changes. After implementing a common method for tensor pre-allocation, it turned out that implementation becomes much simpler by encapsulating the process of request sending/re-sending, meta-data response callback and content response callback, all in a single "Request" class. The request class holds all the relevant request
information
, which reduces excessive parameter passing and lambda capturing. This decision is purely for elegance and code simplicity, and we decided to implement it in first stage because it makes the implementation much easier.
37
* **class RemoteAddressContext** - Remote address
information
(address + mr). Will be passed as write context for tensor proto writes.
40
* **class RdmaTensorRequest** - Holds and manages
information
for a single tensor request throughout the entire receive cycle. API:
44
* **class RdmaTensorResponse** - Holds
information
for a single tensor response, such as destination address and rkey.
48
The protocol messages themselves will remain mostly unchanged at the first stage, but will be used differently, as described below. The current messages structures already have most of the required fields for the new implementation. The only change is the "buffer_size" field which is no longer used since we are no longer sending additional
information
with the tensor, and thus it is now always equal to the "tensor_bytes" field. Instead, we use that field to pass the "request_index".
62
* is_dead/data_type/tensor_shape/tensor_bytes - The current meta-data as stored in the receiver local cache. The sender will use that
information
to know if the receiver's cache requires updating.
Completed in 1666 milliseconds
1
2
3
4
5
6
7
8
9
10
11
>>