| /freebsd/sys/contrib/device-tree/Bindings/display/ |
| H A D | xylon,logicvc-display.yaml | 25 In version 3 of the controller, each layer has fixed memory offset and address
103 xylon,background-layer:
106 The last layer is used to display a black background (C_USE_BACKGROUND).
107 The layer must still be registered.
126 "^layer@[0-9]+$":
133 xylon,layer-depth:
135 description: Layer depth (C_LAYER_X_DATA_WIDTH).
137 xylon,layer-colorspace:
143 description: Layer colorspace (C_LAYER_X_TYPE).
145 xylon,layer-alpha-mode:
[all …]
|
| /freebsd/sbin/mount_nullfs/ |
| H A D | mount_nullfs.8 | 38 .Nd "mount a loopback file system sub-tree; demonstrate the use of a null file system layer"
49 layer, duplicating a sub-tree of the file system
81 all lower-layer vnodes, not just over directory vnodes.
95 Disable metadata caching in the null layer.
96 Some lower-layer file systems may force this option.
108 to the lower (mounted-from) filesystem layer.
113 Enable the bypass of unix socket file to lower filesystem layer.
121 layer path are performed on same unix socket.
124 is done on a socket in the lower layer, then
134 The null layer has two purposes.
[all …]
|
| /freebsd/sbin/mount_unionfs/ |
| H A D | mount_unionfs.8 | 55 layer and
59 layer.
77 becomes the lower layer and
79 becomes the upper layer.
84 Specifies the way to create a file or a directory in the upper layer
92 lower layer to the created file in the upper layer.
99 Specifies whether whiteouts should always be made in the upper layer
101 lower layer.
136 Filenames are looked up in the upper layer and then in the
137 lower layer.
[all …]
|
| /freebsd/crypto/openssl/doc/designs/quic-design/ |
| H A D | record-layer.md | 1 Design Problem: Abstract Record Layer
4 This document covers the design of an abstract record layer for use in (D)TLS.
5 The QUIC record layer is handled separately.
11 an individual record layer.
15 Libssl supports a number of different types of record layer, and record layer
18 - Standard TLS record layer
19 - Standard DTLS record layer
20 - Kernel TLS record layer
22 Within the TLS record layer there are options to handle "multiblock" and
24 writing of multiple records at the same time. All record layer variants also
[all …]
|
| H A D | quic-thread-assist.md | 8 Part of the QUIC state comprises the TLS handshake layer. However, synchronising
11 At first glance, one could synchronise handshake layer public APIs by locking a
13 the handshake layer. Since we forward a very large number of APIs to the
14 handshake layer, this would require a very large number of code changes to add
50 - **2. Handshake layer always belongs to the application thread.**
52 In this model, the handshake layer “belongs” to the application thread
60 future which would be processed by the handshake layer.
63 as the handshake layer, the only thing we actually need to worry about
85 - **3. Handshake layer belongs to the assist thread after connection begins.**
87 In this model, the application may make handshake layer calls freely prior to
|
| H A D | quic-tls.md | 5 the standard TLS record layer and instead assumes responsibility for the
105 * handshake layer is concerned, meaning that it should be immediately torn
146 * It registers itself as a custom TLS record layer
149 ### Custom TLS Record Layer
151 A TLS record layer is defined via an `OSSL_RECORD_METHOD` object. This object
153 record layer. Existing record layers include one for TLS, one for DTLS and one
156 `QUIC_TLS` registers itself as a custom TLS record layer. A new internal
171 The TLS record layer code is further modified to provide the following
174 The custom record layer will need a record layer specific argument (`rlarg`
187 Invoked every time a new record layer object is created by the TLS
[all …]
|
| /freebsd/usr.sbin/ppp/ |
| H A D | link.c | 43 #include "layer.h"
163 * the async layer record how much it's padded the packet in the mbuf's in link_PendingLowPriorityData()
251 int layer; in link_PushPacket() local
255 * ``push'' function in each layer starting at the top. in link_PushPacket()
263 bp->priv = 0; /* Adjusted by the async layer ! */ in link_PushPacket()
264 for (layer = l->nlayers; layer && bp; layer--) in link_PushPacket()
265 if (l->layer[layer - 1]->push != NULL) in link_PushPacket()
266 bp = (*l->layer[layer - 1]->push)(b, l, bp, pri, &proto); in link_PushPacket()
280 int layer; in link_PullPacket() local
284 * ``pull'' function in each layer starting at the bottom. in link_PullPacket()
[all …]
|
| /freebsd/contrib/llvm-project/lldb/source/Plugins/TraceExporter/common/ |
| H A D | TraceHTR.h | 71 /// Function calls are identified in the instruction layer by finding 'call'
93 /// Constructor for a block of an HTR layer.
96 /// The offset of the start of this block in the previous layer.
100 /// layer.
107 /// Get the offset of the start of this block in the previous layer.
114 /// previous layer.
127 /// Offset in the previous layer
130 /// layer
136 /// HTR layer interface
140 /// Construct new HTR layer.
[all …]
|
| /freebsd/contrib/libarchive/libarchive/ |
| H A D | libarchive_internals.3 | 54 layer, a format layer that understands the archive file format,
55 a compression layer, and an I/O layer.
56 The I/O layer is completely exposed to clients who can replace
76 The lowest layer is the I/O layer.
77 This layer can be overridden by clients, but most clients use
82 The compression layer calls the I/O layer t
[all...] |
| /freebsd/sys/contrib/ena-com/ |
| H A D | ena_com.h | 470 * @ena_dev: ENA communication layer struct
481 * @ena_dev: ENA communication layer struct
488 * @ena_dev: ENA communication layer struct
495 * @ena_dev: ENA communication layer struct
503 * @ena_dev: ENA communication layer struct
508 * @ena_dev: ENA communication layer struct
515 * @ena_dev: ENA communication layer struct
522 * @ena_dev: ENA communication layer struct
530 * @ena_dev: ENA communication layer struct
535 * @ena_dev: ENA communication layer struct
[all …]
|
| /freebsd/contrib/llvm-project/lldb/source/Plugins/TraceExporter/docs/ |
| H A D | htr.rst | 11 **Layer:** The representation of trace data between passes. For Intel PT there are two types of layers:
13 **Instruction Layer:** Composed of the load addresses of the instructions in the trace. In an effort to save space,
15 single instruction layer.
17 **Block Layer:** Composed of blocks - a block in *layer n* refers to a sequence of blocks in *layer n - 1*. A block in
18 *layer 1* refers to a sequence of instructions in *layer 0* (the instruction layer). Metadata is stored for each block in
19 a block layer
[all...] |
| /freebsd/sys/compat/linuxkpi/common/src/ |
| H A D | linux_idr.c | 162 idr_pos(int id, int layer) in idr_pos() argument
164 return (id >> (IDR_BITS * layer)) & IDR_MASK; in idr_pos()
199 idr_remove_layer(struct idr_layer *il, int layer) in idr_remove_layer() argument
205 if (layer == 0) { in idr_remove_layer()
211 idr_remove_layer(il->ary[i], layer - 1); in idr_remove_layer()
230 int layer; in idr_remove_locked() local
235 layer = idr->layers - 1; in idr_remove_locked()
242 while (layer && il) { in idr_remove_locked()
243 idx = idr_pos(id, layer); in idr_remove_locked()
246 layer--; in idr_remove_locked()
[all …]
|
| /freebsd/contrib/wpa/src/tls/ |
| H A D | tlsv1_record.c | 20 * tlsv1_record_set_cipher_suite - TLS record layer: Set cipher suite
21 * @rl: Pointer to TLS record layer data
25 * This function is used to prepare TLS record layer for cipher suite change.
68 * tlsv1_record_change_write_cipher - TLS record layer: Change write cipher
69 * @rl: Pointer to TLS record layer data
72 * This function changes TLS record layer to use the new cipher suite
77 wpa_printf(MSG_DEBUG, "TLSv1: Record Layer - New write cipher suite " in tlsv1_record_change_write_cipher()
102 * tlsv1_record_change_read_cipher - TLS record layer: Change read cipher
103 * @rl: Pointer to TLS record layer data
106 * This function changes TLS record layer to use the new cipher suite
[all …]
|
| /freebsd/crypto/openssl/crypto/slh_dsa/ |
| H A D | slh_hypertree.c | 19 * where the first signature uses the XMSS key at the lowest layer, and the last
20 * signature uses the XMSS key at the top layer.
40 uint32_t layer, mask; in ossl_slh_ht_sign() local
66 for (layer = 0; layer < d; ++layer) { in ossl_slh_ht_sign()
68 adrsf->set_layer_address(adrs, layer); in ossl_slh_ht_sign()
79 if (layer < d - 1) { in ossl_slh_ht_sign()
120 uint32_t layer; in ossl_slh_ht_verify() local
125 for (layer = 0; layer < d; ++layer) { in ossl_slh_ht_verify()
126 adrsf->set_layer_address(adrs, layer); in ossl_slh_ht_verify()
|
| /freebsd/share/man/man9/ |
| H A D | own.9 | 84 The network layer designates the next command as being either for all
86 The network layer also specifies the speed used by the link layer.
146 is the client device (the presentation layer device) sending the command.
161 presentation layer devices can use to coordinate access.
189 The lowest relevant layer, the link layer, defines the polling windows
191 The network layer is built on top of the link layer
193 The transport layer defines commands and responses from the devices.
194 The presentation layer is composed of the device specific commands and
200 Presentation layer devices (children of the newbus
|
| H A D | ifnet.9 | 382 describing the link layer implemented by the interface (if any)
386 (Some trivial interfaces do not provide any link layer addresses;
531 A pointer to the common data for the interface's layer 2 protocol.
577 layer:
580 Pass a packet to an appropriate upper layer as determined
581 from the link-layer header of the packet.
586 can be shared among multiple drivers utilizing the same link-layer
652 for validity, and if necessary compute a link-layer group which
736 Control flags for the link layer.
972 Length of a link-layer address on this device, or zero if there are
[all …]
|
| /freebsd/crypto/openssl/ssl/record/ |
| H A D | record.h | 15 * These structures should be considered PRIVATE to the record layer. No *
16 * non-record layer code should be using these structures in any way. *
66 * record layer. No non-record layer code should be accessing the members of *
75 /* Custom record layer: always selected if set */
77 /* Record layer specific argument */
79 /* Method to use for the read record layer*/
81 /* Method to use for the write record layer*/
83 /* The read record layer object itself */
85 /* The write record layer object itself */
87 /* BIO to store data destined for the next read record layer epoch */
[all …]
|
| /freebsd/sys/dev/isci/scil/ |
| H A D | scic_sds_phy_registers.h | 61 * to the SCU link layer registers.
71 //* SCU LINK LAYER REGISTER OPERATIONS
75 * Macro to read the transport layer register associated with this phy
85 * Macro to write the transport layer register associated with this phy
96 //* Transport Layer registers controlled by the phy object
100 * This macro reads the Transport layer control register
106 * This macro writes the Transport layer control register
112 * This macro reads the Transport layer address translation register
118 * This macro writes the Transport layer address translation register
124 * This macro writes the STP Transport Layer Direct Attached RNi register.
[all …]
|
| /freebsd/sys/fs/nullfs/ |
| H A D | null_vnops.c | 39 * Null Layer
43 * The null layer duplicates a portion of the filesystem
48 * all lower-layer vnodes, not just over directory vnodes.
50 * The null layer has two purposes. First, it serves as a demonstration
51 * of layering by proving a layer which does nothing. (It actually
53 * more than nothing.) Second, the null layer can serve as a prototype
54 * layer. Since it provides all necessary layer framework,
56 * with a null layer.
58 * The remainder of this man page examines the null layer as a basis
67 * layer will appear in the namespace (alias-pn). After
[all …]
|
| /freebsd/contrib/libpcap/ |
| H A D | pcap_datalink_val_to_name.3pcap | 24 name or description for a link-layer header type value
39 translates a link-layer header type value to the corresponding
40 link-layer header type name, which is the
42 name for the link-layer header type value with the
51 translates a link-layer header type value to a short description of that
52 link-layer header type.
59 translates a link-layer header type value to a short description of that
60 link-layer header type just like
|
| /freebsd/contrib/libpcap/pcap/ |
| H A D | sll.h | 53 * a 2-byte link-layer type;
55 * a 2-byte link-layer address length;
57 * an 8-byte source link-layer address, whose actual length is
60 * All fields except for the link-layer address are in network byte order.
63 * LINUX_SLL_ values below. If you must change the link-layer header
80 * A DLT_LINUX_SLL fake link-layer header.
87 uint16_t sll_hatype; /* link-layer address type */
88 uint16_t sll_halen; /* link-layer address length */
89 uint8_t sll_addr[SLL_ADDRLEN]; /* link-layer address */
94 * A DLT_LINUX_SLL2 fake link-layer header.
[all …]
|
| /freebsd/crypto/openssl/include/internal/ |
| H A D | recordmethod.h | 68 * There could be some complexity in finding suitable record layer implementations
91 * The BIO in |transport| is the BIO for the underlying transport layer.
105 * the record layer has failed because it is unsuitable, but an alternative
106 * record layer can be tried instead.
162 * Find out the maximum number of records that the record layer is prepared
171 * exit the record layer may update this to an alternative fragment size to
212 * Read a record and return the record layer version and record type in
214 * record layer buffer containing the record payload data and |*datalen|
218 * An opaque record layer handle for the record is returned in |*rechandle|
261 * Called immediately after creation of the record layer if we are in a
[all …]
|
| /freebsd/share/doc/smm/18.net/ |
| H A D | 2.t | 41 session layer (layer 3) and all of the transport and
44 The network layer provides possibly imperfect
52 layer the notions of reliable transfer, data sequencing,
58 each message handed to the network layer by a
64 The session layer facilities may provide forms of
66 by the transport layer, service authentication
73 the internal layering. The contents of each layer
|
| /freebsd/usr.sbin/fifolog/lib/ |
| H A D | fifolog.h | 36 * The outer timestamping and synchronization layer.
38 * The inner sequencing and identification layer.
40 * All three layers are synchronized at a subset of the outer layer
44 * The outer layer:
71 * These fields are immediately followed by the inner layer payload as
74 * If the inner layer payload is shorter than the available space in
85 * The gzip layer
92 * in outer layer (apart from a natural correlation with padding) since
96 * The inner layer:
98 * The inner layer contains data identification and to the second
[all …]
|
| /freebsd/sys/contrib/dev/iwlwifi/ |
| H A D | iwl-op-mode.h | 25 * The operational mode (a.k.a. op_mode) is the layer that implements
28 * underlying HW works, since the transport layer takes care of that.
39 * 1) The driver layer (iwl-drv.c) chooses the op_mode based on the
41 * 2) The driver layer starts the op_mode (ops->start)
44 * 5) The driver layer stops the op_mode
51 * interact with it. The driver layer typically calls the start and stop
52 * handlers, the transport layer calls the others.
57 * @start: start the op_mode. The transport layer is already allocated.
76 * @free_skb: allows the transport layer to free skbs that haven't been
78 * there are Tx packets pending in the transport layer
[all...] |