Home
last modified time | relevance | path

Searched refs:control (Results 1 – 25 of 130) sorted by relevance

123456

/openssl/doc/designs/quic-design/
H A Dquic-fc.md7 QUIC flow control acts at both connection and stream levels. At any time,
9 by stream-level flow control, or both. Flow control uses a credit-based model in
10 which the relevant flow control limit is expressed as the maximum number of
27 advancing us more flow control credit.)
32 Connection-level flow control is controlled by the `MAX_DATA` frame;
44 to flow control.
46 Note that flow control and congestion control are completely separate
159 control for the TX side.
219 flow control. There are a few differences:
238 control to determine if flow control limits are violated by the peer.
[all …]
H A Dcongestion-control.md1 Congestion control API design
6 based on interfaces suggested by RFC 9002 and MSQUIC's congestion control APIs.
35 congestion control algorithm requires access to the statistics manager, but such
38 QUIC congestion control state is per-path, per-connection. Currently we support
39 only a single path per connection, so there is one congestion control instance
42 While the congestion control API is roughly based around the arrangement of
43 functions as described by the congestion control pseudocode in RFC 9002, there
45 loss detection and congestion control functions. Where a literal option of RFC
53 The congestion control API may be revised to allow pluggable congestion
H A Dstream-receive-buffers.md20 more data. Without the flow control limit a rogue peer could trigger
23 data can be released and flow control limit can be raised.
47 This function adjusts the current data flow control limit on the `stream`
124 effectively raise the stream data flow control limit quadratically.
127 more data than what is allowed by the stream data flow control limit
130 Although intuitively the MAX_DATA flow control limit might be used to
144 any data will be supported, the MAX_DATA flow control limit should be equal
H A Drx-depacketizer.md48 - Flow control, which is currently unspecified. In the [overview], it's
117 | 0x10 | [max_data] | Flow control [^5] | ✔ | | |…
118 | 0x11 | [max_stream_data] | Flow control [^5] | ✔ | | |…
121 | 0x14 | [data_blocked] | Flow control [^5] | ✔ | | |…
122 | 0x15 | [stream_data_blocked] | Flow control [^5] | ✔ | | |…
160 [^5]: The details of what flow control will need are yet to be determined
H A Dtx-packetiser.md86 - CFQ: queried for generic control frames
119 Many control frames do not require special handling and are handled by the
170 control frames, and with TXFC instances to know how much stream data it is
176 future. Currently, congestion control is a no-op.
254 - Active Stream: A stream which has data or flow control frames ready for
415 flow control window. Thus there is a performance reason to include them in
421 connection-level flow control, but controls rate at which new streams are
502 stream-level flow control frames, RESET_STREAM and STOP_SENDING frames to
561 or `STOP_SENDING` frames, followed by stream-level flow control frames if
683 * Congestion control
[all …]
H A Dquic-fifm.md82 - Need for a generic control queue which can store encoded control frames.
83 This control queue will handle both initial transmission and retransmission of
84 most control frames which do not have special requirements.
103 - What control frames using the **GCR** strategy were sent in the packet
162 * TXPIM in keeping a list of GCR control frames which were sent in a
208 * priority determines the relative ordering of control frames in a packet.
287 - Keeping track of all GCR control frames which were transmitted
290 - Keeping track of all REGEN-strategy control frame types, via a flag
481 - TX Packetiser queries the CFQ to determine what control frames it places
/openssl/doc/man3/
H A DOSSL_CRMF_MSG_set1_regCtrl_regToken.pod58 returns the respective control X in the given I<msg>, if present.
60 OSSL_CRMF_MSG_set1_regCtrl_regToken() sets the regToken control in the given
63 OSSL_CRMF_MSG_set1_regCtrl_authenticator() sets the authenticator control in
86 control in the given I<msg> copying the given I<tok> as value. See RFC 4211,
89 OSSL_CRMF_MSG_set1_regCtrl_protocolEncrKey() sets the protocolEncrKey control in
92 OSSL_CRMF_MSG_set1_regCtrl_oldCertID() sets the B<oldCertID> regToken control in
H A DOPENSSL_config.pod38 control over their configuration functionality should use the configuration
46 However, very few applications currently support the control interface and so
48 ENGINEs will require certain control operations to customize them. If an
50 ENGINE control operations because they can be performed by editing a
H A DENGINE_add.pod280 of state to control which implementations are available for a given
335 is something for the application to control. Some applications
413 available "control commands", providing a more flexible configuration
422 control commands; the first is to provide the necessary details to the
436 I<Issuing control commands to an ENGINE>
441 the string-pairs used for control commands consist of a command "name"
495 I<Discovering supported control commands>
507 It is using these "core" control commands that one can discover the control
534 if a ctrl() handler was supplied but no array of control commands;
537 if a ctrl() handler and array of control commands was supplied;
[all …]
H A DX509_LOOKUP.pod95 a B<X509_LOOKUP> structure using any control function in the
97 The arguments of the control command are passed via I<argc> and I<argl>,
101 control command. In general, this function is not called directly, but
103 The control I<cmd>s known to OpenSSL are discussed in more depth
203 doesn't have a control function.
204 Otherwise, it returns what the control function in the
H A DSSL_new_stream.pod44 The creation of new streams is subject to flow control by the QUIC protocol. If
56 object even if a new QUIC stream cannot yet be opened due to flow control. The
59 regarding the stream) will be sent until QUIC flow control allows it. Any queued
H A DERR_GET_LIB.pod47 Applications should not make control flow decisions based on specific error
49 OpenSSL). A particular error code can only be considered meaningful for control
H A DSSL_alloc_buffers.pod21 control when buffers are freed and allocated.
27 to control where and how buffers are allocated.
H A DBIO_push.pod21 It then makes a control call on I<b> and returns I<b>.
25 Otherwise it makes a control call on I<b> and
41 consequences (a control call is made to the affected BIOs).
H A DEVP_CIPHER_meth_new.pod128 will be called with the control code B<EVP_CTRL_SET_KEY_LENGTH> and
139 control code B<EVP_CTRL_RAND_KEY> and the pointer to the key memory
148 The destination B<EVP_CIPHER_CTX> is passed to the control with the
174 The EVP routines will simply give them control and do nothing more.
223 EVP_CIPHER_meth_set_ctrl() sets the control function for B<cipher>.
H A DPEM_read_bio_ex.pod31 and control characters from the end of each line, so as to be compatible with
37 If neither PEM_FLAG_EAY_COMPATIBLE or PEM_FLAG_ONLY_B64 is set, control characters
H A DBIO_s_datagram.pod117 This control does not affect the operation of L<BIO_sendmmsg(3)> or
154 connected. Other BIOs may also implement this control if they are capable of
193 the underlying network socket, and returns that Path MTU in bytes. This control
201 This control requests that Path MTU discovery be enabled on the underlying
232 L<BIO_recvmmsg(3)> is not affected by this control.
H A DX509_LOOKUP_meth_new.pod134 function to be used to handle arbitrary control commands issued by
135 X509_LOOKUP_ctrl(). The control function is given the X509_LOOKUP
140 B<argc> and B<argl> are used depends entirely on the control function.
H A DASYNC_start_job.pod40 that point the code can be paused and control returns to user code until some
112 then ASYNC_pause_job() will immediately return control to the calling
151 invokes ASYNC_pause_job(). This returns control back to the code that created
196 application developer is likely to require control over when the latter
274 * Return control back to main just before calling a blocking
276 * for reading before returning control to this thread.
H A DOSSL_PARAM_print_to_bio.pod22 I<print_values> is a control parameter, indicating that key values should be
H A DOSSL_QUIC_client_method.pod22 mode of operation and avoid the need to return control to the
/openssl/
H A DREADME-ENGINES.md51 form of "control commands". These allow an application to expose to the
59 in planning) for supporting these control commands from the CONF (or
164 automatically fails. All it does provide are a few "control commands"
165 that can be used to control how it will load an external ENGINE
166 implementation from a shared-library. To see these control commands,
171 The "SO_PATH" control command should be used to identify the
186 that has been loaded from the shared-library. As such, any control
217 "control commands" mechanism, will provide some way for you to pass
230 a control command you can issue afterwards to "forget" the smart-card
305 commands marked as "SUCCESS" and the list of control commands
[all …]
H A DAUTHORS.md8 source control.
/openssl/crypto/ec/curve448/
H A Dcurve448.c553 static int recode_wnaf(struct smvt_control *control, in recode_wnaf() argument
567 control[position].power = -1; in recode_wnaf()
568 control[position].addend = 0; in recode_wnaf()
600 control[position].power = pos + 16 * (w - 1); in recode_wnaf()
601 control[position].addend = delta; in recode_wnaf()
611 control[i] = control[i + position]; in recode_wnaf()
/openssl/crypto/bio/
H A Dbss_dgram.c1066 mh->Control.buf = control; in translate_msg_win()
1100 mh->msg_control = msg->local != NULL ? control : NULL; in translate_msg()
1335 unsigned char control[BIO_CMSG_ALLOC_LEN]; in dgram_sendmmsg() local
1343 unsigned char control[BIO_CMSG_ALLOC_LEN]; in dgram_sendmmsg() local
1374 control[i], &BIO_MSG_N(msg, stride, i)); in dgram_sendmmsg()
1413 translate_msg(b, &mh, &iov, control, msg); in dgram_sendmmsg()
1445 translate_msg_win(b, &wmsg, &wbuf, control, msg); in dgram_sendmmsg()
1536 unsigned char control[BIO_CMSG_ALLOC_LEN]; in dgram_recvmmsg() local
1544 unsigned char control[BIO_CMSG_ALLOC_LEN]; in dgram_recvmmsg() local
1620 translate_msg(b, &mh, &iov, control, msg); in dgram_recvmmsg()
[all …]

Completed in 47 milliseconds

123456