Searched refs:advance (Results 1 – 11 of 11) sorted by relevance
| /openssl/test/ |
| H A D | quic_ackm_test.c | 493 #define TX_OP_PKT(advance, pn, num_pn) \ argument
495 #define TX_OP_ACK(advance, pn, num_pn) \ argument
641 #define RX_OP_PKT(advance, pn, num_pn) \ argument
643 RX_OPK_PKT, (advance) * OSSL_TIME_MS, (pn), (num_pn), \
647 #define RX_OP_CHECK_UNPROC(advance, pn, num_pn) \ argument
649 RX_OPK_CHECK_UNPROC, (advance) * OSSL_TIME_MS, (pn), (num_pn),\
653 #define RX_OP_CHECK_PROC(advance, pn, num_pn) \ argument
655 RX_OPK_CHECK_PROC, (advance) * OSSL_TIME_MS, (pn), (num_pn), \
659 #define RX_OP_CHECK_STATE(advance, expect_desired, expect_deadline) \ argument
661 RX_OPK_CHECK_STATE, (advance) * OSSL_TIME_MS, 0, 0, \
[all …]
|
| /openssl/doc/man3/ |
| H A D | TS_VERIFY_CTX_set_certs.pod | 31 verifying a TST. B<ctx> is the verification context created in advance and
|
| H A D | SSL_set_connect_state.pod | 44 the handshake routines must be explicitly set in advance using either
|
| H A D | BN_mod_exp_mont.pod | 31 function, so you can save time on initialization if you provide it in advance.
|
| H A D | SSL_do_handshake.pod | 17 routines may have to be explicitly set in advance using either
|
| H A D | EVP_PKEY_get_size.pod | 61 the upper limit in advance.
|
| H A D | CMS_decrypt.pod | 63 in advance using the CMS utility functions such as CMS_set1_pkey(). In this
|
| H A D | RSA_get0_key.pod | 135 in advance and allocate sufficient buffer to store the return values before
|
| H A D | OSSL_HTTP_transfer.pod | 169 the length of the data in I<req> does not need to be determined in advance: the
|
| /openssl/doc/designs/quic-design/ |
| H A D | dgram-api.md | 98 available in advance.
482 `recvmmsg`, and thus how many buffers it allocates in advance.
|
| /openssl/ |
| H A D | CHANGES.md | 9777 So only messages with sequence numbers less than 10 in advance will be
15389 but for applications that know in advance when to expect data, it
|
Completed in 68 milliseconds
