| /freebsd/crypto/openssl/doc/man7/ |
| H A D | ossl-guide-quic-multi-stream.pod | 6 demos/guide/quic-multi-stream.c
12 ossl-guide-quic-multi-stream
13 - OpenSSL Guide: Writing a simple multi-stream QUIC client
18 QUIC multi-stream application. It assumes a basic understanding of QUIC and how
19 it is used in OpenSSL. See L<ossl-guide-quic-introduction(7)> and
20 L<ossl-guide-quic-client-block(7)>.
24 In a QUIC multi-stream application we separate out the concepts of a QUIC
48 (see L<ossl-guide-libraries-introduction(7)>). In particular most OpenSSL
64 (by default) the default stream will be a client-initiated bi-directional
67 stream (whether it is bi-directional or uni-directional).
[all …]
|
| H A D | ossl-guide-libssl-introduction.pod | 5 ossl-guide-libssl-introduction, ssl
6 - OpenSSL Guide: An introduction to libssl
14 operations (see L<ossl-guide-libcrypto-introduction(7)>).
36 can be uni- or bi-directional.
39 bi-directional. In this case the B<SSL> object used for the connection also
40 represents that stream. See L<ossl-guide-tls-introduction(7)> for more
44 uni- or bi-directional. In this case an B<SSL> object can represent the
47 L<ossl-guide-quic-introduction(7)> for more information.
96 See L<ossl-guide-tls-introduction(7)> for an introduction to the SSL/TLS
97 protocol and L<ossl-guide-quic-introduction(7)> for an introduction to QUIC.
[all …]
|
| H A D | ossl-guide-quic-introduction.pod | 5 ossl-guide-quic-introduction
6 - OpenSSL Guide: An introduction to QUIC in OpenSSL
13 some OpenSSL and TLS fundamentals (see L<ossl-guide-libraries-introduction(7)>
14 and L<ossl-guide-tls-introduction(7)>).
23 integrity and authentication (see L<ossl-guide-tls-introduction(7)>).
36 "head-of-line blocking"). It also enables an application to open additional
37 logical streams without requiring a round-trip exchange of packets between the
44 to use HTTP/3 using a suitable third-party library.
48 Future versions of OpenSSL will offer support for 0-RTT connection initiation,
50 transmitted without any waiting time. This is similar to TLS 1.3's 0-RTT
[all …]
|
| /freebsd/secure/lib/libcrypto/man/man7/ |
| H A D | ossl-guide-quic-multi-stream.7 | 1 .\" -*- mode: troff; coding: utf-8 -*-
57 .IX Title "OSSL-GUIDE-QUIC-MULTI-STREAM 7ossl"
58 .TH OSSL-GUIDE-QUIC-MULTI-STREAM 7ossl 2025-09-30 3.5.4 OpenSSL
64 ossl\-guide\-quic\-multi\-stream
65 \&\- OpenSSL Guide: Writing a simple multi\-stream QUIC client
69 QUIC multi-stream application. It assumes a basic understanding of QUIC and how
70 it is used in OpenSSL. See \fBossl\-guide\-quic\-introduction\fR\|(7) and
71 \&\fBossl\-guide\-quic\-client\-block\fR\|(7).
74 In a QUIC multi-stream application we separate out the concepts of a QUIC
98 (see \fBossl\-guide\-libraries\-introduction\fR\|(7)). In particular most OpenSSL
[all …]
|
| H A D | ossl-guide-libssl-introduction.7 | 1 .\" -*- mode: troff; coding: utf-8 -*-
57 .IX Title "OSSL-GUIDE-LIBSSL-INTRODUCTION 7ossl"
58 .TH OSSL-GUIDE-LIBSSL-INTRODUCTION 7ossl 2025-09-30 3.5.4 OpenSSL
64 ossl\-guide\-libssl\-introduction, ssl
65 \&\- OpenSSL Guide: An introduction to libssl
72 operations (see \fBossl\-guide\-libcrypto\-introduction\fR\|(7)).
94 can be uni\- or bi-directional.
97 bi-directional. In this case the \fBSSL\fR object used for the connection also
98 represents that stream. See \fBossl\-guide\-tls\-introduction\fR\|(7) for more
102 uni\- or bi-directional. In this case an \fBSSL\fR object can represent the
[all …]
|
| H A D | ossl-guide-quic-introduction.7 | 1 .\" -*- mode: troff; coding: utf-8 -*-
57 .IX Title "OSSL-GUIDE-QUIC-INTRODUCTION 7ossl"
58 .TH OSSL-GUIDE-QUIC-INTRODUCTION 7ossl 2025-09-30 3.5.4 OpenSSL
64 ossl\-guide\-quic\-introduction
65 \&\- OpenSSL Guide: An introduction to QUIC in OpenSSL
71 some OpenSSL and TLS fundamentals (see \fBossl\-guide\-libraries\-introduction\fR\|(7)
72 and \fBossl\-guide\-tls\-introduction\fR\|(7)).
80 integrity and authentication (see \fBossl\-guide\-tls\-introduction\fR\|(7)).
90 "head-of-line blocking"). It also enables an application to open additional
91 logical streams without requiring a round-trip exchange of packets between the
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/pinctrl/ |
| H A D | renesas,rza1-ports.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pinctrl/renesas,rza1-port
[all...] |
| H A D | renesas,rza1-pinctrl.txt | 5 Pin multiplexing and GPIO configuration is performed on a per-pin basis
6 writing configuration values to per-port register sets.
12 -------------------
15 - compatible: should be:
16 - "renesas,r7s72100-ports": for RZ/A1H
17 - "renesas,r7s72101-ports", "renesas,r7s72100-ports": for RZ/A1M
18 - "renesas,r7s72102-ports": for RZ/A1L
20 - reg
27 pinctrl: pin-controller@fcfe3000 {
28 compatible = "renesas,r7s72100-ports";
[all …]
|
| /freebsd/contrib/unbound/dnstap/ |
| H A D | dnstap_fstrm.h | 2 * dnstap/dnstap_fstrm.h - Frame Streams protocol for dnstap
54 * The Frame Streams can be unidirectional or bi-directional.
55 * bi-directional streams use control frame types READY, ACCEPT and FINISH.
56 * uni-directional streams use control frame types START and STOP.
60 * bi-directional control frames implement a simple handshake protocol
63 * The uni-directional control frames have one start and one stop frame,
79 * 4byte bigendian, the control-field-type, currently only content-type.
84 * control frame max frame length 512 (excludes the 0-escape and control
185 * Like 'start content-type(protobuf:dnstap.Dnstap)' or 'stop'.
|
| /freebsd/sys/contrib/device-tree/Bindings/iio/adc/ |
| H A D | richtek,rtq6056.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: RTQ6056 Bi-Directional Current and Power Monitor with 16-bit ADC
10 - ChiYuan Huang <cy_huang@richtek.com>
13 The RTQ6056 is a high accuracy current-sense monitor with I2C and SMBus
19 internal analog-to-digital converter ADC. The programmable calibration,
24 https://www.richtek.com/assets/product_file/RTQ6056/DSQ6056-00.pdf
29 - enum:
30 - richtek,rtq6056
[all …]
|
| /freebsd/contrib/llvm-project/llvm/lib/Transforms/Vectorize/ |
| H A D | VPlanVerifier.h | 1 //===-- VPlanVerifier.h -----------------------------------------*- C++ -*-===//
5 // SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
7 //===----------------------------------------------------------------------===//
15 /// - Region's entry/exit block must have no predecessors/successors,
17 /// - Block's parent must be the region immediately containing the block.
18 /// - Linked blocks must have a bi-directional link (successor/predecessor).
19 /// - All predecessors/successors of a block must belong to the same region.
20 /// - Blocks must have no duplicated successor/predecessor.
22 //===----------------------------------------------------------------------===//
32 /// invariants for every region in the H-CFG.
[all …]
|
| H A D | VPlanVerifier.cpp | 1 //===-- VPlanVerifier.cpp -------------------------------------------------===//
5 // SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
7 //===----------------------------------------------------------------------===//
13 //===----------------------------------------------------------------------===//
23 #define DEBUG_TYPE "loop-vectorize"
33 // Verify that phi-like recipes are at the beginning of \p VPBB, with no
64 auto RecipeI = VPBB->begin(); in verifyPhiRecipes()
65 auto End = VPBB->end(); in verifyPhiRecipes()
67 const VPRegionBlock *ParentR = VPBB->getParent(); in verifyPhiRecipes()
68 bool IsHeaderVPBB = ParentR && !ParentR->isReplicator() && in verifyPhiRecipes()
[all …]
|
| /freebsd/share/man/man4/ |
| H A D | hv_vmbus.4 | 31 .Nd Hyper-V Virtual Machine Bus (VMBus) Driver
35 .Bd -ragged -offset indent
43 guest and root partitions in Hyper-V.
44 Hyper-V is a hypervisor-based virtualization technology from Microsoft.
45 Hyper-V supports isolation in terms of a partition.
64 The VMBus is a logical inter-partition communication channel.
71 The Hyper-V VMBus driver defines and implements
72 the interface that facilitate high performance bi-directional communication
87 .An -nosplit
|
| H A D | ng_pred1.4 | 32 .Nd Predictor-1 PPP compression (RFC 1978) netgraph node type
39 node type implements the Predictor-1 sub-protocols of the Compression Control
55 .Bl -tag -compact -width ".Va decomp"
74 .Bl -tag -width foo
81 .Bd -literal -offset 0n
90 This message contains no arguments, and is bi-directional.
95 The receiver should respond by sending a PPP CCP Reset-Request to the peer.
97 This message may also be received by this node type when a CCP Reset-Request
98 or Reset-Ack is received by the local PPP entity.
105 .Bd -literal
[all …]
|
| H A D | ng_deflate.4 | 41 node type implements the Deflate sub-protocols of the Compression Control
62 .Bl -tag -compact -width ".Va decomp"
82 .Bl -tag -width foo
89 .Bd -literal -offset 0n
103 This message contains no arguments, and is bi-directional.
108 The receiver should respond by sending a PPP CCP Reset-Request to the peer.
110 This message may also be received by this node type when a CCP Reset-Request
111 or Reset-Ack is received by the local PPP entity.
118 .Bd -literal
148 .%T "The Point-to-Point Protocol (PPP)"
|
| H A D | spigen.4 | 36 .Bd -ragged -offset indent
45 .Bd -literal -offset indent
54 device is associated with a single chip-select
56 with that chip-select line asserted.
58 SPI data transfers are inherently bi-directional; there are no separate
75 .Bl -tag -width indent
83 .Bd -literal
91 The buffers for the transfer are a previously-mmap'd region.
100 is non-zero, the data appears in the memory region immediately
104 .Bd -literal
[all …]
|
| H A D | ng_mppc.4 | 1 .\" Copyright (c) 1996-2000 Whistle Communications, Inc.
19 .\" MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
49 node type implements the Microsoft Point-to-Point Compression (MPPC)
50 and Microsoft Point-to-Point Encryption (MPPE) sub-protocols of
52 These protocols are often used in conjunction with the Point-to-Point
66 .Bl -tag -width ".Va decomp"
84 .Bl -tag -width foo
91 .Bd -literal -offset 0n
123 This key is based on the MS-CHAP credentials used at link authentication time.
131 This message contains no arguments, and is bi-directional.
[all …]
|
| H A D | ng_vjc.4 | 1 .\" Copyright (c) 1996-1999 Whistle Communications, Inc.
19 .\" MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
53 over PPP, SLIP, and other point-to-point IP connections to
82 Other non-TCP IP packets are forwarded unchanged to
104 .Bl -tag -width ".Va vjuncomp"
116 .Bl -tag -width foo
123 .Bd -literal -offset 4n
127 u_char maxChannel; /* Number of outgoing channels - 1 */
152 therefore operating in bi-directional
|
| /freebsd/sys/contrib/device-tree/Bindings/sound/ |
| H A D | nvidia,tegra210-i2s.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/sound/nvidia,tegra210-i2s.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 The Inter-IC Sound (I2S) controller implements full-duplex,
11 bi-directional and single direction point-to-point serial
16 - Jon Hunter <jonathanh@nvidia.com>
17 - Sameer Pujar <spujar@nvidia.com>
20 - $ref: dai-common.yaml#
24 pattern: "^i2s@[0-9a-f]*$"
[all …]
|
| /freebsd/sys/ofed/include/rdma/ |
| H A D | ib.h | 1 /*-
2 * SPDX-License-Identifier: BSD-2-Clause OR GPL-2.0
16 * - Redistributions of source code must retain the above
20 * - Redistributions in binary form must reproduce the above
66 return ((a->sib_addr64[0] | a->sib_addr64[1]) == 0); in ib_addr_any()
71 return ((a->sib_addr32[0] | a->sib_addr32[1] | in ib_addr_loopback()
72 a->sib_addr32[2] | (a->sib_addr32[3] ^ htonl(1))) == 0); in ib_addr_loopback()
78 addr->sib_addr32[0] = w1; in ib_addr_set()
79 addr->sib_addr32[1] = w2; in ib_addr_set()
80 addr->sib_addr32[2] = w3; in ib_addr_set()
[all …]
|
| /freebsd/crypto/openssl/demos/guide/ |
| H A D | quic-multi-stream.c | 2 * Copyright 2023-2024 The OpenSSL Project Authors. All Rights Reserved.
12 * doc/man7/ossl-guide-quic-multi-stream.pod
32 int sock = -1; in create_socket_bio()
50 * Create a UDP socket. We could equally use non-OpenSSL calls such in create_socket_bio()
57 if (sock == -1) in create_socket_bio()
63 sock = -1; in create_socket_bio()
70 sock = -1; in create_socket_bio()
77 if (sock != -1) { in create_socket_bio()
88 /* If sock is -1 then we've been unable to connect to the server */ in create_socket_bio()
89 if (sock == -1) in create_socket_bio()
[all …]
|
| /freebsd/sys/dev/usb/serial/ |
| H A D | ulpt.c | 3 /*-
4 * SPDX-License-Identifier: BSD-2-Clause
174 USETW(req.wIndex, sc->sc_iface_no); in ulpt_reset()
184 mtx_lock(&sc->sc_mtx); in ulpt_reset()
186 if (usbd_do_request_flags(sc->sc_udev, &sc->sc_mtx, in ulpt_reset()
189 if (usbd_do_request_flags(sc->sc_udev, &sc->sc_mtx, in ulpt_reset()
194 mtx_unlock(&sc->sc_mtx); in ulpt_reset()
201 struct usb_fifo *f = sc->sc_fifo_open[USB_FIFO_TX]; in ulpt_write_callback()
240 struct usb_fifo *f = sc->sc_fifo_open[USB_FIFO_RX]; in ulpt_read_callback()
257 if (sc->sc_zlps == 4) { in ulpt_read_callback()
[all …]
|
| /freebsd/sys/sys/ |
| H A D | pipe.h | 1 /*-
87 #define PIPE_WANT 0x020 /* Pipe is wanted to be run-down. */
101 * Per-pipe data structure.
102 * Two of these are linked together to produce bi-directional pipes.
142 #define PIPE_MTX(pipe) (&(pipe)->pipe_pair->pp_mtx)
|
| /freebsd/sys/contrib/device-tree/Bindings/remoteproc/ |
| H A D | st,stm32-rproc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/remoteproc/st,stm32-rproc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
14 - Fabien Dessenne <fabien.dessenne@foss.st.com>
15 - Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>
19 const: st,stm32mp1-m4
31 reset-names:
33 - const: mcu_rst
34 - const: hold_boot
[all …]
|
| /freebsd/lib/libsys/ |
| H A D | getrlimit.2 | 56 .Bl -tag -width RLIMIT_FSIZEAA
86 The maximum number of pseudo-terminals this user id is allowed to create.
88 The maximum total size of in-kernel buffers for bi-directional pipes/fifos
126 The limit of the number of process-shared posix thread library objects
145 .Bd -literal -offset indent
152 Only the super-user may raise the maximum limits.
166 Because this information is stored in the per-process information,
170 is thus a built-in command to
211 .Rv -std
219 .Bl -tag -width Er
[all …]
|