| /freebsd/lib/libpmc/pmu-events/arch/x86/cascadelakex/ |
| H A D | uncore-other.json | 10 …"BriefDescription": "LLC misses - Uncacheable reads (from cpu) . Derived from unc_cha_tor_inserts.…
20 "BriefDescription": "LLC misses - Uncacheable reads (from cpu) ",
164 "ScaleUnit": "7.11E-06Bytes",
174 "ScaleUnit": "7.11E-06Bytes",
355 "BriefDescription": "Multi-socket cacheline Directory state lookups; Snoop Not Needed",
360 …"PublicDescription": "Counts transactions that looked into the multi-socket cacheline Directory st…
365 "BriefDescription": "Multi-socket cacheline Directory state lookups; Snoop Needed",
370 …"PublicDescription": "Counts transactions that looked into the multi-socket cacheline Directory s…
375 …"BriefDescription": "Multi-socket cacheline Directory state updates; Directory Updated memory writ…
380 …"PublicDescription": "Counts only multi-socket cacheline Directory state updates memory writes iss…
[all …]
|
| /freebsd/lib/libpmc/pmu-events/arch/x86/skylakex/ |
| H A D | uncore-other.json | 10 …"BriefDescription": "LLC misses - Uncacheable reads (from cpu) . Derived from unc_cha_tor_inserts.…
20 "BriefDescription": "LLC misses - Uncacheable reads (from cpu) ",
164 "ScaleUnit": "7.11E-06Bytes",
174 "ScaleUnit": "7.11E-06Bytes",
355 "BriefDescription": "Multi-socket cacheline Directory state lookups; Snoop Not Needed",
360 …"PublicDescription": "Counts transactions that looked into the multi-socket cacheline Directory st…
365 "BriefDescription": "Multi-socket cacheline Directory state lookups; Snoop Needed",
370 …"PublicDescription": "Counts transactions that looked into the multi-socket cacheline Directory s…
375 …"BriefDescription": "Multi-socket cacheline Directory state updates; Directory Updated memory writ…
380 …"PublicDescription": "Counts only multi-socket cacheline Directory state updates memory writes iss…
[all …]
|
| /freebsd/secure/lib/libcrypto/man/man7/ |
| H A D | openssl-quic-concurrency.7 | 1 .\" -*- mode: troff; coding: utf-8 -*-
57 .IX Title "OPENSSL-QUIC-CONCURRENCY 7ossl"
58 .TH OPENSSL-QUIC-CONCURRENCY 7ossl 2025-09-30 3.5.4 OpenSSL
64 openssl\-quic\-concurrency \- OpenSSL QUIC Concurrency Model
103 The \fBSingle-Threaded Concurrency Model (SCM)\fR, which supports only
104 application-synchronised single-threaded usage.
106 The \fBContentive Concurrency Model (CCM)\fR, which supports multi-threaded usage.
108 The \fBThread-Assisted Concurrency Model (TACM)\fR, which also supports
109 multi-threaded usage and provides assistance to an application for handling QUIC
114 The \fBSingle-Threaded Concurrency Model (SCM)\fR performs no locking or
[all …]
|
| H A D | openssl-quic.7 | 1 .\" -*- mode: troff; coding: utf-8 -*-
57 .IX Title "OPENSSL-QUIC 7ossl"
58 .TH OPENSSL-QUIC 7ossl 2025-09-30 3.5.4 OpenSSL
64 openssl\-quic \- OpenSSL QUIC
82 Default stream mode versus multi-stream mode for clients;
84 The changes to existing libssl APIs which are driven by QUIC-related
92 New, QUIC-specific APIs.
96 stream mode, which is intended to provide compatibility with existing non-QUIC
100 client-initiated or server-initiated from a QUIC perspective depends on whether
105 instead adopt the multi-stream API. See the RECOMMENDATIONS FOR NEW APPLICATIONS
[all …]
|
| H A D | ossl-guide-quic-client-block.7 | 1 .\" -*- mode: troff; coding: utf-8 -*-
57 .IX Title "OSSL-GUIDE-QUIC-CLIENT-BLOCK 7ossl"
58 .TH OSSL-GUIDE-QUIC-CLIENT-BLOCK 7ossl 2025-09-30 3.5.4 OpenSSL
64 ossl\-guide\-quic\-client\-block
65 \&\- OpenSSL Guide: Writing a simple blocking QUIC client
71 QUIC is non-standard and will not be supported by real world servers. This is
76 (see \fBossl\-guide\-libraries\-introduction\fR\|(7), \fBossl\-guide\-tls\-introduction\fR\|(7)
77 and \fBossl\-guide\-quic\-introduction\fR\|(7)); and that you know how to
82 \&\fBossl\-guide\-tls\-client\-block\fR\|(7). Only the differences between that client and
87 tutorial will discuss how to write a multi-stream client (see
[all …]
|
| H A D | ossl-guide-quic-client-non-block.7 | 1 .\" -*- mode: troff; coding: utf-8 -*-
57 .IX Title "OSSL-GUIDE-QUIC-CLIENT-NON-BLOCK 7ossl"
58 .TH OSSL-GUIDE-QUIC-CLIENT-NON-BLOCK 7ossl 2025-09-30 3.5.4 OpenSSL
64 ossl\-guide\-quic\-client\-non\-block
65 \&\- OpenSSL Guide: Writing a simple nonblocking QUIC client
69 \&\fBossl\-guide\-quic\-client\-block\fR\|(7) page which demonstrates how to write a simple
75 \&\fBquic\-client\-non\-block.c\fR. It is also available online at
76 <https://github.com/openssl/openssl/blob/master/demos/guide/quic\-client\-non\-block.c>.
79 nonblocking socket. However, despite this, the \fBSSL\fR object still has blocking
93 \&\fBSSL_read_ex\fR\|(3) or \fBSSL_write_ex\fR\|(3) will return immediately with a non-fatal
[all …]
|
| /freebsd/tools/tools/netrate/httpd/ |
| H A D | httpd.c | 1 /*-
2 * Copyright (c) 2005-2006 Robert N. M. Watson
29 #include <sys/socket.h>
53 * Simple, multi-threaded/multi-process HTTP server. Very dumb.
66 #define HTTP_CONTENT "Content-Type: text/html\n\n"
69 * In order to support both multi-threaded and multi-process operation but
70 * use a single shared memory statistics model, we create a page-aligned
72 * threading; for multi-process operation, we mark it as INHERIT_SHARE, so we
73 * must put it in page-aligned memory that isn't shared with other memory, or
78 pthread_t hts_thread; /* Multi-thread. */
[all …]
|
| /freebsd/crypto/openssl/doc/man7/ |
| H A D | openssl-quic-concurrency.pod | 5 openssl-quic-concurrency - OpenSSL QUIC Concurrency Model
59 The B<Single-Threaded Concurrency Model (SCM)>, which supports only
60 application-synchronised single-threaded usage.
64 The B<Contentive Concurrency Model (CCM)>, which supports multi-threaded usage.
68 The B<Thread-Assisted Concurrency Model (TACM)>, which also supports
69 multi-threaded usage and provides assistance to an application for handling QUIC
80 The B<Single-Threaded Concurrency Model (SCM)> performs no locking or
91 synchronisation for multi-threaded usage of QUIC objects. For example, different
95 This concurrency model adds the overhead of locking over the Single-Threaded
96 Concurrency Model in order to support multi-threaded usage, but provides limited
[all …]
|
| H A D | openssl-quic.pod | 5 openssl-quic - OpenSSL QUIC
28 Default stream mode versus multi-stream mode for clients;
32 The changes to existing libssl APIs which are driven by QUIC-related
46 New, QUIC-specific APIs.
53 stream mode, which is intended to provide compatibility with existing non-QUIC
57 client-initiated or server-initiated from a QUIC perspective depends on whether
62 instead adopt the multi-stream API. See the RECOMMENDATIONS FOR NEW APPLICATIONS
68 multi-stream mode. By default, a newly created QUIC connection SSL object uses
80 whether a stream is client-initiated or server-initiated. In default stream
83 is using a server-initiated stream, and the L<SSL_read(3)> call will not
[all …]
|
| H A D | ossl-guide-quic-client-block.pod | 6 demos/guide/quic-client-block.c
12 ossl-guide-quic-client-block
13 - OpenSSL Guide: Writing a simple blocking QUIC client
20 QUIC is non-standard and will not be supported by real world servers. This is
25 (see L<ossl-guide-libraries-introduction(7)>, L<ossl-guide-tls-introduction(7)>
26 and L<ossl-guide-quic-introduction(7)>); and that you know how to
31 L<ossl-guide-tls-client-block(7)>. Only the differences between that client and
36 tutorial will discuss how to write a multi-stream client (see
37 L<ossl-guide-quic-multi-stream(7)>).
41 C<quic-client-block.c>. It is also available online at
[all …]
|
| H A D | ossl-guide-quic-client-non-block.pod | 6 demos/guide/quic-client-non-block.c
12 ossl-guide-quic-client-non-block
13 - OpenSSL Guide: Writing a simple nonblocking QUIC client
18 L<ossl-guide-quic-client-block(7)> page which demonstrates how to write a simple
24 B<quic-client-non-block.c>. It is also available online at
25 L<https://github.com/openssl/openssl/blob/master/demos/guide/quic-client-non-block.c>.
28 nonblocking socket. However, despite this, the B<SSL> object still has blocking
42 L<SSL_read_ex(3)> or L<SSL_write_ex(3)> will return immediately with a non-fatal
46 L<ossl-guide-quic-client-block(7)> page we assume that you are familiar with it
49 =head2 Performing work while waiting for the socket
[all …]
|
| /freebsd/contrib/wpa/src/drivers/ |
| H A D | driver_wired_common.c | 3 * Copyright (c) 2005-2009, Jouni Malinen <j@w1.fi>
38 s = socket(PF_INET, SOCK_DGRAM, 0); in driver_wired_get_ifflags()
40 wpa_printf(MSG_ERROR, "socket: %s", strerror(errno)); in driver_wired_get_ifflags()
41 return -1; in driver_wired_get_ifflags()
50 return -1; in driver_wired_get_ifflags()
63 s = socket(PF_INET, SOCK_DGRAM, 0); in driver_wired_set_ifflags()
65 wpa_printf(MSG_ERROR, "socket: %s", strerror(errno)); in driver_wired_set_ifflags()
66 return -1; in driver_wired_set_ifflags()
76 return -1; in driver_wired_set_ifflags()
89 return -1; in driver_wired_multi()
[all …]
|
| /freebsd/share/doc/smm/18.net/ |
| H A D | 7.t | 31 .\".ds RH "Socket/protocol interface
33 \s+2Socket/protocol interface\s0
35 The interface between the socket routines and the communication
43 #define PRU_BIND 2 /* bind socket to address */
56 #define PRU_SOCKADDR 15 /* fetch socket's address */
69 int error; struct socket *so; int req; struct mbuf *m, *addr, *rights;
73 The address \fIaddr\fP is supplied for address-oriented requests
76 chain containing user-specified capabilities (see the \fIsendmsg\fP
79 A non-zero return value gives a
85 When a protocol is bound to a socket (with the \fIsocket\fP
[all …]
|
| /freebsd/share/man/man4/ |
| H A D | sctp.4 | 41 .Fn socket AF_INET SOCK_STREAM IPPROTO_SCTP
43 .Fn socket AF_INET SOCK_SEQPACKET IPPROTO_SCTP
47 protocol provides reliable, flow-controlled, two-way
57 Internet address format and, in addition, provides a per-host
80 passive socket, the
82 system call must be used after binding the socket with the
100 socket address) and an association will be setup
105 third leg of the four-way handshake.
108 to allow the socket to accept connections.
116 protocol directly supports multi-homing.
[all …]
|
| /freebsd/crypto/openssh/ |
| H A D | PROTOCOL.mux | 2 ControlMaster connection-sharing.
5 master. This will cause ssh(1) to listen on a Unix domain socket for
6 requests from clients. Clients communicate over this socket using a
27 Unix domain control socket. The passenger client then waits until it is
36 this mode, the mux client/server connection socket will stop speaking
86 descriptors (in that order) using Unix domain socket control messages.
109 non-multiplexed ssh(1) connection. Two additional cases that the
120 3. Requesting passenger-mode stdio forwarding
131 (in that order) using Unix domain socket control messages.
174 If listen port is (unsigned int) -2, then the listen host is treated as
[all …]
|
| /freebsd/usr.sbin/inetd/ |
| H A D | inetd.8 | 34 .Dq super-server
55 of its sockets, it decides what service the socket
57 The server program is invoked with the service socket
62 continues to listen on the socket (except in some cases which
70 .Bl -tag -width indent
92 a TCP-based service would need two entries,
106 May be overridden on a per-service basis with the
107 "max-connections-per-ip-per-minute" parameter.
112 May be overridden on a per-service basis with the "max-child"
128 May be overridden on a per-service basis with the "max-child-per-ip"
[all …]
|
| /freebsd/usr.sbin/rpcbind/ |
| H A D | rpcbind.8 | 55 is started, it checks that certain name-to-address
56 translation-calls function correctly.
66 utility can only be started by the super-user.
68 .Bl -tag -width indent
83 With this option, the name-to-address translation consistency
89 on a multi-homed host.
96 which could lead to problems on a multi-homed host due to
128 Allow old-style local connections over the loopback interface.
129 Without this flag, local connections are only allowed over a local socket,
148 to use non-privileged ports for outgoing connections, preventing non-privileged
[all …]
|
| /freebsd/usr.bin/finger/ |
| H A D | net.c | 1 /*-
2 * SPDX-License-Identifier: BSD-3-Clause
36 #include <sys/socket.h>
58 int error, multi; in netfinger() local
80 multi = (ai0->ai_next) != 0; in netfinger()
83 if (ai0->ai_canonname == 0) in netfinger()
86 printf("[%s]\n", ai0->ai_canonname); in netfinger()
88 for (ai = ai0; ai != NULL; ai = ai->ai_next) { in netfinger()
89 if (multi) in netfinger()
111 s = socket(ai->ai_family, ai->ai_socktype, ai->ai_protocol); in do_protocol()
[all …]
|
| /freebsd/lib/libc/net/ |
| H A D | sctp_opt_info.3 | 33 .Nd get SCTP socket information
45 call provides a multi-os compatible method for getting
64 socket options.
100 The call returns 0 on success and -1 upon error.
105 .Bl -tag -width Er
113 was not one of the above listed SCTP socket
122 is not a socket.
132 socket option has changed in FreeBSD 9.0 and higher,
|
| /freebsd/crypto/openssl/doc/designs/quic-design/ |
| H A D | glossary.md | 52 **DISPATCH:** Refers to the QUIC-specific dispatch code in `ssl_lib.c`. This
59 **Event Leader:** The QSO which is is the top-level QSO in a hierarchy of QSOs,
62 design](server/quic-server-api.md).
66 **FIFD:** Frame-in-flight dispatcher. Ties together the CFQ and TXPIM to handle
69 **FIFM:** Frame-in-flight manager. Tracks frames in flight until their
77 **Key epoch:** Non-negative number designating a generation of QUIC keys used to
99 **Locally-initiated:** Refers to a QUIC stream which was initiated by the local
131 **MSMT:** Multi-stream multi-thread. Refers to a type of multi-stream QUIC usage
134 **MSST:** Multi-stream single-thread. Refers to a type of multi-stream QUIC
152 **Port Leader:** The QSO which is responsible for servicing a given UDP socket.
[all …]
|
| /freebsd/usr.sbin/ppp/ |
| H A D | ppp.8 | 31 .Nd Point to Point Protocol (a.k.a. user-ppp)
99 .Bl -tag -width XXX -offset XXX
141 exits with a non-zero result.
161 .Dq force-scripts
176 As pipes are not bi-directional, ppp will redirect all writes to descriptor
186 .Dq force-scripts
195 This is a no-op, and gives the same behaviour as if none of the above
213 .Bl -diag
231 .It Supports on-demand dialup capability.
243 mode (direct-dial mode) also automatically dials and establishes the
[all …]
|
| /freebsd/contrib/llvm-project/llvm/include/llvm/Support/ |
| H A D | Threading.h | 1 //===-- llvm/Support/Threading.h - Control multithreading mode --*- C++ -*-===//
5 // SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
7 //===----------------------------------------------------------------------===//
9 // This file declares helper functions for running LLVM in a multi-threaded
12 //===----------------------------------------------------------------------===//
19 #include "llvm/Config/llvm-config.h" // for LLVM_ON_UNIX
51 /// Returns true if LLVM is compiled with support for multi-threading, and
137 /// multi-socket system, this ensures threads are assigned to all CPU
142 /// Finds the CPU socket where a thread should go. Returns 'std::nullopt' if
143 /// the thread shall remain on the actual CPU socket.
[all …]
|
| /freebsd/lib/libpmc/pmu-events/arch/arm64/ |
| H A D | common-and-microarch.json | 129 "PublicDescription": "Attributable Level 1 data cache write-back",
132 "BriefDescription": "Attributable Level 1 data cache write-back"
147 "PublicDescription": "Attributable Level 2 data cache write-back",
150 "BriefDescription": "Attributable Level 2 data cache write-back"
273 "PublicDescription": "Access to another socket in a multi-socket system",
276 "BriefDescription": "Access to another socket in a multi-socket system"
303 … "PublicDescription": "Attributable memory read access to another socket in a multi-socket system",
306 … "BriefDescription": "Attributable memory read access to another socket in a multi-socket system"
309 …"PublicDescription": "Level 1 data cache long-latency read miss. The counter counts each memory r…
312 "BriefDescription": "Level 1 data cache long-latency read miss"
[all …]
|
| /freebsd/tools/test/netfibs/ |
| H A D | README | 3 exercising multi-IP FIBs. At this time only IPv6 test cases are provided.
9 socket in very simplistic ways. It has a couple of options to provide
22 interface in the same broadcast domain (be it cross-over or on a
40 unrelated to multi-FIB test leading to a panic(9). "delay" calls
|
| /freebsd/sys/contrib/device-tree/Bindings/cpu/ |
| H A D | cpu-topology.txt | 6 1 - Introduction
12 - socket
13 - cluster
14 - core
15 - thread
18 symmetric multi-threading (SMT) is supported or not.
29 Currently, only ARM/RISC-V intend to use this cpu topology binding but it may be
39 2 - cpu-map node
42 The ARM/RISC-V CPU topology is defined within the cpu-map node, which is a direct
46 - cpu-map node
[all …]
|