| /freebsd/crypto/openssl/doc/man7/ |
| H A D | provider-object.pod | 5 provider-object - A specification for a provider-native object abstraction
16 The provider-native object abstraction is a set of L<OSSL_PARAM(3)> keys and
68 same provider as the one originating the object abstraction in question (X).
72 For example, when the OpenSSL library receives an object abstraction with the
92 A provider-native object abstraction is an L<OSSL_PARAM(3)> with a selection
131 receive this object abstraction are expected to convert the data to a
140 receive this object abstraction are expected to convert the data to a
167 When a provider-native object abstraction is used, it I<must> contain object
|
| H A D | provider-storemgmt.pod | 37 to the OpenSSL library in provider-native object abstraction form (see
39 passing on that abstraction to suitable provided functions.
41 Examples of functions that the OpenSSL library can pass the abstraction to
95 OSSL_FUNC_store_open(), creates an object abstraction for it (see
97 I<object_cbarg>. I<object_cb> will then interpret the object abstraction
|
| H A D | bio.pod | 5 bio - Basic I/O abstraction
15 A BIO is an I/O abstraction, it hides many of the underlying I/O
|
| /freebsd/secure/lib/libcrypto/man/man7/ |
| H A D | provider-object.7 | 140 provider\-object \- A specification for a provider\-native object abstraction
149 The provider-native object abstraction is a set of \s-1\fBOSSL_PARAM\s0\fR\|(3) keys and
186 same provider as the one originating the object abstraction in question (X).
190 For example, when the OpenSSL library receives an object abstraction with the
205 A provider-native object abstraction is an \s-1\fBOSSL_PARAM\s0\fR\|(3) with a selection
238 receive this object abstraction are expected to convert the data to a
246 receive this object abstraction are expected to convert the data to a
268 When a provider-native object abstraction is used, it \fImust\fR contain object
|
| H A D | provider-storemgmt.7 | 172 to the OpenSSL library in provider-native object abstraction form (see
174 passing on that abstraction to suitable provided functions.
176 Examples of functions that the OpenSSL library can pass the abstraction to
233 \&\fBOSSL_FUNC_store_open()\fR, creates an object abstraction for it (see
235 \&\fIobject_cbarg\fR. \fIobject_cb\fR will then interpret the object abstraction
|
| H A D | bio.7 | 140 bio \- Basic I/O abstraction
148 A \s-1BIO\s0 is an I/O abstraction, it hides many of the underlying I/O
|
| /freebsd/share/doc/psd/18.gprof/ |
| H A D | profiling.me | 64 of an abstraction completely replaces a previous one.
72 If a routine implements an abstraction by invoking other abstractions,
74 time required by the abstraction it implements.
75 Similarly, if an abstraction is implemented by several
76 routines the time required by the abstraction will be distributed
|
| H A D | intro.me | 49 of abstraction implementations
66 abstraction is collected and charged
67 to that abstraction.
|
| H A D | present.me | 169 a set of routines that implement an abstraction.
210 If the data abstraction function cannot easily be speeded up,
233 As in the symbol table abstraction that is placed
|
| /freebsd/contrib/llvm-project/clang/include/clang/Tooling/Transformer/ |
| H A D | MatchConsumer.h | 1 //===--- MatchConsumer.h - MatchConsumer abstraction ------------*- C++ -*-===//
9 /// \file This file defines the *MatchConsumer* abstraction: a computation over
32 /// This is a central abstraction of the Transformer framework.
62 /// This is a central abstraction of the Transformer framework. It is a
|
| /freebsd/share/man/man9/ |
| H A D | buf.9 | 35 The kernel implements a KVM abstraction of the buffer cache which allows it
38 This abstraction supports
43 VM Buffer abstraction is mostly concentrated in
79 abstraction is considered a bad hack and it would be nice if we could get rid
|
| /freebsd/share/man/man4/ |
| H A D | intro.4 | 36 .Ss The device abstraction
50 The device abstraction generally provides a common set of system
66 Aspects of the device abstraction have changed significantly in
|
| H A D | sctp.4 | 68 abstraction.
69 In this abstraction sockets utilizing the
94 The other abstraction
104 This abstraction is the only one capable of sending data on the
|
| /freebsd/contrib/bmake/unit-tests/ |
| H A D | directive-for-empty.mk | 29 # named 'i', this condition makes for a leaky abstraction. If the .for
35 . error # not reached, due to the leaky abstraction
98 # This might be regarded another leaky abstraction, but it is in fact useful
|
| /freebsd/contrib/llvm-project/llvm/lib/Target/Mips/ |
| H A D | MipsOptionRecord.h | 1 //===- MipsOptionRecord.h - Abstraction for storing information -*- C++ -*-===//
9 // MipsOptionRecord - Abstraction for storing arbitrary information in
|
| /freebsd/contrib/ntp/sntp/libevent/include/event2/ |
| H A D | bufferevent_compat.h | 42 Libevent provides an abstraction on top of the regular event callbacks.
43 This abstraction is called a buffered event. A buffered event provides
|
| /freebsd/contrib/libevent/include/event2/ |
| H A D | bufferevent_compat.h | 42 Libevent provides an abstraction on top of the regular event callbacks.
43 This abstraction is called a buffered event. A buffered event provides
|
| /freebsd/contrib/llvm-project/llvm/lib/Target/Mips/MCTargetDesc/ |
| H A D | MipsOptionRecord.cpp | 1 //===- MipsOptionRecord.cpp - Abstraction for storing information ---------===//
31 // we can use the same abstraction (MipsRegInfoRecord class) to handle both. in EmitMipsOptionRecord()
|
| /freebsd/contrib/llvm-project/llvm/lib/Analysis/ |
| H A D | TensorSpec.cpp | 1 //===- TensorSpec.cpp - tensor type abstraction ---------------------------===//
9 // Implementation file for the abstraction of a tensor type, and JSON loading
|
| /freebsd/contrib/llvm-project/lldb/docs/design/ |
| H A D | overview.rst | |
| /freebsd/contrib/llvm-project/clang/lib/CodeGen/ |
| H A D | Address.h | 36 /// IR-level abstraction, carrying just the information necessary to perform IR
113 /// This is designed to be an IR-level abstraction, carrying just the
122 /// this abstraction allows the authentication to be delayed as long as possible
|
| /freebsd/sys/dev/isci/ |
| H A D | README | 6 This driver uses an OS-agnostic abstraction layer library named SCIL that is
|
| /freebsd/contrib/lutok/ |
| H A D | README | 13 library, Lutok adds several layers or abstraction and error checking
|
| /freebsd/contrib/ofed/libibverbs/man/ |
| H A D | ibv_create_comp_channel.3 | 32 A "completion channel" is an abstraction introduced by libibverbs that
|
| /freebsd/sys/contrib/openzfs/cmd/zed/agents/ |
| H A D | zfs_agents.h | 30 * Agent abstraction presented to ZED
|