Home
last modified time | relevance | path

Searched full:approach (Results 1 – 25 of 672) sorted by relevance

12345678910>>...27

/freebsd/share/doc/papers/diskperf/
H A Dmethodology.ms35 These might be termed the \fIindirect\fR and the \fIdirect\fR approach.
36 The approach used by DEC in producing most of the performance data
38 approach.
39 We chose to use the direct approach.
41 The indirect approach used by DEC involves two steps.
55 The problems encountered with this indirect approach often
81 The advantage of this approach is the implicit accuracy in
89 A more significant disadvantage to the direct approach
/freebsd/crypto/openssl/doc/designs/quic-design/
H A Drecord-layer.md72 ### Use a METHOD based approach
74 A METHOD based approach is simply a structure containing function pointers. It
84 In the MVP the METHOD approach would be private. However, once it has
89 based approach. However it could be used as a "stepping stone" for that, i.e.
90 the MVP could implement a METHOD based approach, and subsequent releases could
95 * Simple approach that has been used historically in OpenSSL
105 * Not consistent with the provider based approach we used for extensibility in
110 ### Use a provider based approach
112 This approach is very similar to the alternative METHOD based approach. The
117 This approach is more consistent with the approach adopted for extensibility in
[all …]
H A Dquic-io-arch.md153 This undermines our general approach of providing the application with control
178 Moreover, this does not appear to be a realistically implementable approach:
198 Even if this approach were successfully implemented, applications will still
212 our internal approach to I/O to be flexibly adapted in the future as
215 This is also the approach used by all other known QUIC implementations; it is
225 This approach in general requires that a network socket be configured in
232 fewest disadvantages and is the only approach which appears to actually be
H A Ddgram-api.md213 case (a “polyfill” approach).
362 This approach allows `BIO_dgram` to support myriad options via composition of
380 Pros of this approach:
394 Cons of this approach:
473 would need to revisit the set-call-then-execute-call API approach above
/freebsd/contrib/ntp/
H A DREADME.leapsmear61 but of course the smearing server approach also works.
64 The Leap Smear Approach
79 With this approach the time an NTP server sends to its clients still matches
92 Pros and Cons of the Smearing Approach
94 The disadvantages of this approach are:
107 better approach may be to slew the time in a well defined way, over a
155 Google's leap smear approach is a very efficient solution for this, for
165 the -x approach. The current leap second code in ntpd determines the point
/freebsd/lib/libsys/
H A Dffclock.251 approach radically different from the feedback alternative implemented by the
53 The feed-forward approach has demonstrated better performance and higher
54 robustness than a feedback approach when synchronising over the network.
82 The feed-forward approach does not require that the clock estimates be retrieved
H A Dsetcred.2256 This piecewise approach causes such a process to transiently hold high privilege
263 The necessity of an atomic, global approach to changing credentials clearly
/freebsd/contrib/googletest/googletest/
H A DREADME.md66 And a more robust and flexible approach is to build GoogleTest as part of that
76 location. This is the least flexible approach and can make it more difficult
79 source tree. This is often the simplest approach, but is also the hardest to
85 approach doesn't have the limitations of the other methods.
109 Note that this approach requires CMake 3.14 or later due to its use of the
/freebsd/contrib/llvm-project/llvm/include/llvm/CodeGen/GlobalISel/
H A DCSEMIRBuilder.h37 // TODO: Another approach for checking dominance is having two iterators and
39 // approach is better? Should this even change dynamically? For G_CONSTANTS
40 // most of which will be at the top of the BB, the top down approach would be
/freebsd/contrib/libarchive/libarchive/test/
H A Dtest_write_disk_hardlink.c63 * First, use a tar-like approach; a regular file, then in DEFINE_TEST()
93 * Repeat tar approach test, but use unset to mark the in DEFINE_TEST()
123 * Second, try an old-cpio-like approach; a regular file, then in DEFINE_TEST()
152 * Third, try a new-cpio-like approach, where the initial in DEFINE_TEST()
/freebsd/contrib/llvm-project/libcxx/include/__pstl/internal/omp/
H A Dparallel_for_each.h
/freebsd/crypto/openssl/doc/man7/
H A Dfips_module.pod14 with the FIPS module. Which is the correct approach to use will depend on your
50 One simple approach is to cause all applications that are using OpenSSL to only
53 This approach can be done purely via configuration. As long as applications are
114 This approach has the primary advantage that it is simple, and no code changes
116 some disadvantages to this approach:
152 A variation on the above approach is to do the same thing on an individual
/freebsd/secure/lib/libcrypto/man/man7/
H A Dfips_module.771 with the FIPS module. Which is the correct approach to use will depend on your
96 One simple approach is to cause all applications that are using OpenSSL to only
99 This approach can be done purely via configuration. As long as applications are
166 This approach has the primary advantage that it is simple, and no code changes
168 some disadvantages to this approach:
191 A variation on the above approach is to do the same thing on an individual
/freebsd/sys/dev/chromebook_platform/
H A Dchromebook_platform.c62 * A stopgap approach to preserve the status quo. in chromebook_i2c_identify()
63 * A more intelligent approach is required to correctly in chromebook_i2c_identify()
/freebsd/secure/lib/libcrypto/man/man3/
H A DSSL_shutdown.3176 If this approach is not used, the second call to \fBSSL_shutdown()\fR (to complete the
194 This alternative "fast shutdown" approach should only be done if it is known
201 This approach of a single \fBSSL_shutdown()\fR call without waiting is preferable to
206 The fast shutdown approach can only be used if there is no intention to reuse
244 An alternative approach is to simply avoid calling \fBSSL_read\fR\|(3) if it is known
/freebsd/lib/msun/man/
H A Dexp.3164 approach anything or nothing as x and y approach 0
/freebsd/crypto/openssl/doc/man3/
H A DSSL_shutdown.pod129 If this approach is not used, the second call to SSL_shutdown() (to complete the
148 This alternative "fast shutdown" approach should only be done if it is known
155 This approach of a single SSL_shutdown() call without waiting is preferable to
160 The fast shutdown approach can only be used if there is no intention to reuse
201 An alternative approach is to simply avoid calling L<SSL_read(3)> if it is known
/freebsd/sys/contrib/zstd/zlibWrapper/examples/
H A Dfitblk_original.c11 Add detailed description of approach
14 /* Approach to just fitting a requested compressed size:
43 two pass approach similar to the above. That shortfall is due to
/freebsd/share/man/man4/
H A Dtcp_rack.454 threshold approach, RACK-TLP detects losses more efficiently
59 DupAck threshold approach.
H A Dfdt.451 platform and architecture independent approach for resolving such problems.
83 embedded applications (eliminates hard-coded configuration approach, enforces
/freebsd/lib/libc/include/
H A Dreentrant.h49 * One approach for thread safety is to provide discrete versions of the
54 * Another approach is to provide a single thread safe library. However,
/freebsd/contrib/expat/
H A DREADME.md51 This approach leverages CMake's own [module `FindEXPAT`](https://cmake.org/cmake/help/latest/module/FindEXPAT.html).
71 This approach requires files from…
99 This approach — as demonstrated below — requires CMake >=3.18 for both the
/freebsd/crypto/krb5/src/util/support/
H A Dcache-addrinfo.h44 * Approach overview:
70 * We're taking a simpler approach: A system provides these routines or
/freebsd/crypto/krb5/src/include/krb5/
H A Dkadm5_hook_plugin.h39 * Allbery; it is likely that Heimdal will adopt an approach based on
43 * than the kdb interface, so this approach is more desirable than
/freebsd/sys/contrib/device-tree/Bindings/
H A Dxilinx.txt17 The new approach is to export the parameters into the device tree and
89 That covers the general approach to binding xilinx IP cores into the

12345678910>>...27