/freebsd/sys/netpfil/ipfilter/netinet/ |
H A D | ip_lookup.c | 75 static ipf_lookup_t *backends[MAX_BACKENDS] = { variable 107 for (i = 0, l = backends; i < MAX_BACKENDS; i++, l++) { in ipf_lookup_soft_create() 135 err = (*backends[i]->ipfl_init)(softc, softl->ipf_back[i]); in ipf_lookup_soft_init() 160 (*backends[i]->ipfl_fini)(softc, in ipf_lookup_soft_fini() 184 (*backends[i]->ipfl_expire)(softc, softl->ipf_back[i]); in ipf_lookup_expire() 207 (*backends[i]->ipfl_destroy)(softc, in ipf_lookup_soft_destroy() 332 for (i = 0, l = backends; i < MAX_BACKENDS; i++, l++) { in ipf_lookup_addnode() 382 for (i = 0, l = backends; i < MAX_BACKENDS; i++, l++) { in ipf_lookup_delnode() 429 for (i = 0, l = backends; i < MAX_BACKENDS; i++, l++) { in ipf_lookup_addtable() 490 for (i = 0, l = backends; i < MAX_BACKENDS; i++, l++) { in ipf_lookup_deltable() [all …]
|
/freebsd/contrib/wpa/src/utils/ |
H A D | ext_password.c | 19 static const struct ext_password_backend *backends[] = { variable 45 for (i = 0; backends[i]; i++) { in ext_password_init() 46 if (os_strcmp(backends[i]->name, backend) == 0) { in ext_password_init() 47 data->backend = backends[i]; in ext_password_init()
|
/freebsd/contrib/ntp/sntp/libevent/test/ |
H A D | test.sh | 152 -b - specify backends 160 backends=$BACKENDS 167 b) backends="$OPTARG";; 180 for i in $backends; do
|
/freebsd/contrib/libevent/test/ |
H A D | test.sh | 152 -b - specify backends 160 backends=$BACKENDS 167 b) backends="$OPTARG";; 180 for i in $backends; do
|
/freebsd/lib/libc++/ |
H A D | __config_site | 35 // PSTL backends
|
H A D | Makefile | 1022 PSBDIR= ${CXXINCLUDEDIR}/__pstl/backends 1028 PSB+= ${HDRDIR}/__pstl/backends/${hdr}
|
/freebsd/contrib/llvm-project/lld/ |
H A D | CODE_OWNERS.TXT | 14 D: COFF, ELF backends (COFF/* ELF/*)
|
/freebsd/etc/mtree/ |
H A D | BSD.include.dist | 76 backends
|
/freebsd/contrib/ntp/sntp/libevent/ |
H A D | whatsnew-2.0.txt | 156 systems' fast backends. Previously, programmers who cared about this 157 needed to know which backends supported what. This tended to get quite 160 There is now an API to choose backends, either by name or by feature. 249 2.9. Edge-triggered events on some backends. 251 With some backends, it's now possible to add the EV_ET flag to an event 284 3.1. Change-minimization on O(1) backends 323 testing the IOCP backends on the mailing list, it seems that there isn't 606 before. Right now, iterating over the different backends on various
|
H A D | ChangeLog-1.4 | 46 …o Activate fd events in a pseudorandom order with O(N) backends, so that we don't systematically f… 70 o event_add would not return error for some backends; from Dean McNamee 164 …o Make kqueue have the same behavior as other backends when a signal is caught between event_add()… 174 o move EV_PERSIST handling out of the event backends
|
H A D | CMakeLists.txt | 1204 # We run all tests with the different backends turned on one at a time. 1207 # Add event backends based on system introspection result. 1553 message(STATUS "Available event backends: ${BACKENDS}")
|
H A D | ChangeLog-2.0 | 497 o Reorder backends in test.sh to match preference order in event.c (ece974f) 582 o Fix an issue with forking and signal socketpairs in select/poll backends (d61b2f3) 1054 … as EV_WRITE, not EV_READ. This should bring it in line with the other backends, and improve port… 1116 …o Activate fd events in a pseudorandom order with O(N) backends, so that we don't systematically f… 1147 o move EV_PERSIST handling out of the event backends 1236 o support for edge-triggered events on epoll and kqueue backends: patch from Valery Kholodkov 1237 …o support for selecting event backends by their features, and for querying the features of a backe… 1265 …o Restructure the event backends so that they do not need to keep track of events themselves, as a…
|
H A D | whatsnew-2.1.txt | 161 On backends that support it (currently epoll), there is now an
|
/freebsd/contrib/libevent/ |
H A D | whatsnew-2.0.txt | 156 systems' fast backends. Previously, programmers who cared about this 157 needed to know which backends supported what. This tended to get quite 160 There is now an API to choose backends, either by name or by feature. 249 2.9. Edge-triggered events on some backends. 251 With some backends, it's now possible to add the EV_ET flag to an event 284 3.1. Change-minimization on O(1) backends 323 testing the IOCP backends on the mailing list, it seems that there isn't 606 before. Right now, iterating over the different backends on various
|
H A D | ChangeLog-1.4 | 46 …o Activate fd events in a pseudorandom order with O(N) backends, so that we don't systematically f… 70 o event_add would not return error for some backends; from Dean McNamee 164 …o Make kqueue have the same behavior as other backends when a signal is caught between event_add()… 174 o move EV_PERSIST handling out of the event backends
|
H A D | CMakeLists.txt | 1204 # We run all tests with the different backends turned on one at a time. 1207 # Add event backends based on system introspection result. 1553 message(STATUS "Available event backends: ${BACKENDS}")
|
H A D | ChangeLog-2.0 | 497 o Reorder backends in test.sh to match preference order in event.c (ece974f) 582 o Fix an issue with forking and signal socketpairs in select/poll backends (d61b2f3) 1054 … as EV_WRITE, not EV_READ. This should bring it in line with the other backends, and improve port… 1116 …o Activate fd events in a pseudorandom order with O(N) backends, so that we don't systematically f… 1147 o move EV_PERSIST handling out of the event backends 1236 o support for edge-triggered events on epoll and kqueue backends: patch from Valery Kholodkov 1237 …o support for selecting event backends by their features, and for querying the features of a backe… 1265 …o Restructure the event backends so that they do not need to keep track of events themselves, as a…
|
H A D | whatsnew-2.1.txt | 161 On backends that support it (currently epoll), there is now an
|
/freebsd/sys/cam/ctl/ |
H A D | README.ctl.txt | 97 - You can also see a list of LUNs and their backends like this: 202 - The block and ramdisk backends now support setting the LUN blocksize. 245 CTL has the concept of pluggable frontend ports and backends. All 246 frontends and backends can be active at the same time. You can have a
|
/freebsd/contrib/wpa/wpa_supplicant/doc/docbook/ |
H A D | wpa_priv.sgml | 115 supported <command>wpa_supplicant</command> driver backends is to be
|
H A D | wpa_supplicant.sgml | 246 <para>A summary of available driver backends is below. Support for each 247 of the driver backends is chosen at wpa_supplicant compile time. For a 248 list of supported driver backends that may be used with the -D option on
|
/freebsd/contrib/ntp/sntp/m4/ |
H A D | openldap.m4 | 518 AC_MSG_ERROR([BerkeleyDB version incompatible with BDB/HDB backends]) 532 [AC_CACHE_CHECK([if Berkeley DB version supported by BDB/HDB backends], [ol_cv_bdb_compat],[
|
/freebsd/crypto/openssl/doc/man3/ |
H A D | EVP_PKEY_new.pod | 66 backends, such as providers (through L<EVP_KEYMGMT(3)>) or B<ENGINE>s.
|
/freebsd/contrib/llvm-project/libcxx/include/ |
H A D | module.modulemap | 1604 header "__pstl/backends/default.h" 1608 header "__pstl/backends/libdispatch.h" 1612 header "__pstl/backends/serial.h" 1616 header "__pstl/backends/std_thread.h"
|
/freebsd/contrib/llvm-project/llvm/include/llvm/Target/ |
H A D | TargetInstrPredicate.td | 54 // Tablegen backends know how to expand MCInstPredicate definitions into actual
|