Lines Matching refs:support
5 eventual BIO_dgram_mem) to support APIs which allow multiple datagrams to be
23 on OSes which do not support `sendmmsg` or `sendmsg`.
29 we can support on all platforms (for example, arbitrary control messages).
35 - For OSes which do not support `sendmmsg`, we emulate it using repeated
36 calls to `sendmsg`. For OSes which do not support `sendmsg`, we emulate it
51 - The BIO methods are designed to support stateless operation in which they
56 The motivation for this is that these functions are intended to support
61 - We do not support iovecs. The motivations for this are:
63 - Not all platforms can support iovecs (e.g. Windows).
65 - The only way we could emulate iovecs on platforms which don't support
78 - Even if we did support iovecs, we would have to impose a limit
86 be used for a send operation. We support this, but require this functionality
150 support may not be available in all circumstances, in which case processing of
157 Local address support is enabled as follows:
165 `BIO_dgram_get_local_addr_cap()` returns 1 if local address support is
167 fails if support is not available.
195 The flags argument is defined by us. Initially we can support something like
211 - If we choose to support these functions when OS support is not available
220 msghdr`, *m\*v* iovecs, etc. Since we want to support multithreaded use
261 - We also need to decide what to do for OSes which don't support at least
267 - Not providing these functions on OSes that don't support
288 pitfall of buffer copying to emulate iovec support. There is a fair risk
303 The problem here is we want to support “single-copy” (where the data is only
362 This approach allows `BIO_dgram` to support myriad options via composition of
392 - Flexible support for single-copy (zero-copy).
398 QUIC implementation so probably not a big deal. We can always support
427 Since we will probably need to support platforms without
428 `sendmmsg`/`recvmmsg` support anyway, (b) seems like the better option.
469 intention to support multithreaded use of a single BIO at this time (unless I am
472 If we wanted to support multithreaded use of the same FD using the same BIO, we
