Searched full:socket (Results 1 – 25 of 179) sorted by relevance
12345678
| /Documentation/networking/ |
| D | kcm.rst | 15 | KCM socket | | KCM socket | | KCM socket | | KCM socket |
46 written on a KCM socket are sent atomically on an appropriate TCP socket.
47 Similarly, in the receive path, messages are constructed on each TCP socket
48 (Psock) and complete messages are steered to a KCM socket.
54 for each bound TCP socket, this structure holds the state for constructing
63 can be used to send and receive messages from the KCM socket.
65 Socket types
68 KCM supports SOCK_DGRAM and SOCK_SEQPACKET socket types.
79 Filter (BPF) is used for this. When attaching a TCP socket to a multiplexor a
84 to a KCM socket.
[all …]
|
| D | l2tp.rst | 28 associated with a socket. Each session is associated with a virtual
40 1) Create a tunnel socket. Exchange L2TP control protocol messages
41 with the peer over that socket in order to establish a tunnel.
47 tunnel socket in order to establish a session.
62 To create a tunnel socket for use by L2TP, the standard POSIX
63 socket API is used.
67 int sockfd = socket(AF_INET, SOCK_DGRAM, IPPROTO_UDP);
71 int sockfd = socket(AF_INET6, SOCK_DGRAM, IPPROTO_L2TP);
73 UDP socket programming doesn't need to be covered here.
76 subsystem. The L2TPIP socket address is defined in struct
[all …]
|
| D | phonet.rst | 12 and RPC. With the Linux Phonet socket family, Linux host processes can
80 The Phonet socket address family maps the Phonet packet header::
97 Applications can send Phonet messages using the Phonet datagram socket
98 protocol from the PF_PHONET family. Each socket is bound to one of the
109 fd = socket(PF_PHONET, SOCK_DGRAM, 0);
125 A Phonet datagram socket can be subscribed to any number of 8-bits
132 control request, or when the socket is closed.
134 Note that no more than one socket can be subscribed to any given
143 socket paradigm. The listening socket is bound to an unique free object
144 ID. Each listening socket can handle up to 255 simultaneous
[all …]
|
| D | strparser.rst | 21 callback of a TCP socket. Messages are parsed and delivered as they are
22 received on the socket.
48 socket associated with the stream parser for use with receive
99 the lower socket for strparser to process. This should be called
100 from a data_ready callback that is set on the socket. Note that
101 maximum messages size is the limit of the receive socket
102 buffer and message timeout is the receive timeout for the socket.
108 strp_check_rcv is called to check for new messages on the socket.
136 kernel, return control of the socket to userspace which
140 is unrecoverable (application expected to close TCP socket)
[all …]
|
| D | rds.rst | 21 applications to use a single socket to talk to any other process in the
23 to N*N if you use a connection-oriented socket transport like TCP.
34 the end point of a connection. All socket operations that involve
46 * Socket interface
49 socket. The next section will cover the details. At any rate,
50 all I/O is performed through the standard BSD socket API.
57 attaches it to the socket. Once bound, the transport assignment
67 Socket Interface
71 AF_RDS and PF_RDS are the domain type to be used with socket(2)
72 to create RDS sockets. SOL_RDS is the socket-level to be used
[all …]
|
| D | msg_zerocopy.rst | 9 The MSG_ZEROCOPY flag enables copy avoidance for socket send calls.
20 underlying copy avoidance mechanism to common socket send calls.
53 [PATCH net-next v4 0/9] socket sendmsg MSG_ZEROCOPY
63 Socket Setup
69 this flag, a process must first signal intent by setting a socket option:
87 the socket exceeds its optmem limit or the user exceeds their ulimit on
105 socket error queue, akin to the transmit timestamping interface.
107 The notification itself is a simple scalar value. Each socket
144 the socket. A socket that has an error queued would normally block
167 may arrive out of order on retransmission and socket teardown.
[all …]
|
| D | rxrpc.rst | 22 (#) Socket options.
174 connections are handled transparently. One client socket may be used to
175 make multiple simultaneous calls to the same service. One server socket
185 (#) Each internal UDP socket is retained [tunable] for a certain amount of
206 Interaction with the user of the RxRPC socket:
208 (#) A socket is made into a server socket by binding an address with a
219 socket. This may be overridden by supplying an alternate address to the
225 (#) A server socket may also be used to make client calls. To do this, the
271 (#) The server application has to provide the server socket with a keyring of
279 nominated by a socket option.
[all …]
|
| D | tls-handshake.rst | 35 An open socket is passed to a handshake agent via a netlink operation,
36 which creates a socket descriptor in the agent's file descriptor table.
38 the socket to use the TLS ULP and sets the session information using the
39 SOL_TLS socket options. The handshake agent returns the socket to the
47 socket by invoking one of the tls_client_hello() functions. First, it
53 struct socket *ta_sock;
65 The @ta_sock field references an open and connected socket. The consumer
66 must hold a reference on the socket to prevent it from being destroyed
81 socket to be fully closed once both the kernel and the handshake agent
102 for this socket. The function returns a negative errno if the handshake
[all …]
|
| D | af_xdp.rst | 23 An AF_XDP socket (XSK) is created with the normal socket()
25 TX ring. A socket can receive packets on the RX ring and it can send
28 to have at least one of these rings for each socket. An RX or TX
53 The socket is then finally bound with a bind() call to a device and a
61 with as well as its own newly created XSK socket. The new process will
65 process has to create its own socket with associated RX and TX rings,
93 In order to use an AF_XDP socket, a number of associated objects need
115 An AF_XDP is socket linked to a single UMEM, but one UMEM can have
116 multiple AF_XDP sockets. To share an UMEM created via one socket A,
117 the next socket B can do this by setting the XDP_SHARED_UMEM flag in
[all …]
|
| D | tls.rst | 19 First create a new TCP socket and set the TLS ULP.
23 sock = socket(AF_INET, SOCK_STREAM, 0);
26 Setting the TLS ULP allows us to set/get TLS socket options. Currently
29 data-path to the kernel. There is a separate socket option for moving
67 After setting the TLS_TX socket option all application data sent over this
68 socket is encrypted using TLS and the parameters provided in the socket option.
96 -ENOMEM and some data was left on the socket buffer from a previous
97 call using MSG_MORE, the MSG_MORE data is left on the socket buffer.
102 After setting the TLS_RX socket option, all recv family socket calls
128 These messages can be sent over the socket by providing the TLS record type
[all …]
|
| D | can.rst | 13 socket API, the Linux network stack and implements the CAN device
14 drivers as network interfaces. The CAN socket API has been designed
22 Motivation / Why Using the Socket API
41 protocol family has been implemented which provides a socket interface
58 selects that protocol when opening the socket, and then can read and
67 socket(2) and using bind(2) to select a CAN interface and CAN ID, an
109 provide a socket interface to user space applications which builds
129 application opens a CAN RAW socket, the raw protocol module itself
176 separate socket. See sockopts from the CAN RAW sockets in :ref:`socketcan-raw-sockets`.
209 Like TCP/IP, you first need to open a socket for communicating over a
[all …]
|
| D | mctp.rst | 11 The core code provides a socket-based interface to send and receive MCTP
12 messages, through an AF_MCTP, SOCK_DGRAM socket.
46 int sd = socket(AF_MCTP, SOCK_DGRAM, 0);
50 As with all socket address families, source and destination addresses are
77 socket system calls. These behaviours have been chosen to map closely to the
80 ``bind()`` : set local socket address
98 This establishes the local address of the socket. Incoming MCTP messages that
99 match the network, address, and message type will be received by this socket.
100 The reference to 'incoming' is important here; a bound socket will only receive
105 this socket. Given the above, the only valid value is ``MCTP_TAG_OWNER``, which
[all …]
|
| D | snmp_counter.rst | 33 ICMP and so on. If no one listens on a raw socket, only kernel
35 socket, all valid IP packets will be delivered.
95 raw socket, kernel will always deliver the packet to the raw socket
138 ICMP output path will check the header of a raw socket, so the
345 TCP socket is in LISTEN state, and kernel need to drop a packet,
356 stack will keep the socket in the TCP half-open queue. As it is in the
359 queue is still full, if it is not full, moves the socket to the accept
360 queue, if it is full, keeps the socket in the half-open queue, at next
361 time client replies ACK, this socket will get another chance to move
398 The socket receives a RST packet in Establish or CloseWait state.
[all …]
|
| D | tproxy.rst | 8 To use it, enable the socket match and the TPROXY target in your kernel config.
17 socket on your box, set the packet mark to a certain value::
20 # iptables -t mangle -A PREROUTING -p tcp -m socket --transparent -j DIVERT
28 # nft add rule filter divert meta l4proto tcp socket transparent 1 meta mark set 1 accept
38 addresses. All you have to do is enable the (SOL_IP, IP_TRANSPARENT) socket
41 fd = socket(AF_INET, SOCK_STREAM, 0);
77 IP_TRANSPARENT) for the listening socket.
|
| D | mptcp.rst | 40 Technically, when a new socket is created with the ``IPPROTO_MPTCP`` protocol
95 ``socket``:
99 int sd = socket(AF_INET(6), SOCK_STREAM, IPPROTO_MPTCP);
119 Socket options
122 MPTCP supports most socket options handled by TCP. It is possible some less
129 There are some MPTCP specific socket options at the ``SOL_MPTCP`` (284) level to
143 Note that at the TCP level, ``TCP_IS_MPTCP`` socket option can be used to know
150 A new socket type has been added for MPTCP for the userspace-facing socket. The
|
| D | dccp.rst | 11 - Socket options
51 Socket options
75 service codes (RFC 4340, sec. 8.1.2); if this socket option is not set,
76 the socket will fall back to 0 (which means that no meaningful service code
92 time, combining the operation of the next two socket options. This option is
95 understood. This socket option takes as argument at least one uint8_t value, or
97 must be registered on the socket before calling connect() or listen().
105 DCCP_SOCKOPT_SERVER_TIMEWAIT enables the server (listening socket) to hold
108 state. When this boolean socket option is on, the server sends a Close instead
127 settings are inherited to the child socket after accept().
[all …]
|
| /Documentation/bpf/ |
| D | map_sk_storage.rst | 11 ``BPF_MAP_TYPE_SK_STORAGE`` is used to provide socket-local storage for BPF
13 to be provided and acts as the handle for accessing the socket-local
15 locally with each socket instead of with the map. The kernel is responsible for
16 allocating storage for a socket when requested and for freeing the storage when
17 either the map or the socket is deleted.
22 socket-local storage.
37 Socket-local storage for ``map`` can be retrieved from socket ``sk`` using the
56 Socket-local storage for ``map`` can be deleted from socket ``sk`` using the
70 Socket-local storage for map ``map_fd`` can be added or updated locally to a
71 socket using the ``bpf_map_update_elem()`` libbpf function. The socket is
[all …]
|
| D | prog_sk_lookup.rst | 8 into the socket lookup performed by the transport layer when a packet is to be
11 When invoked BPF sk_lookup program can select a socket that will receive the
20 binding sockets to an address with ``bind()`` socket call is impractical, such
29 Such setups would require creating and ``bind()``'ing one socket to each of the
31 latency spikes during socket lookup.
47 find a listening (TCP) or an unconnected (UDP) socket for an incoming packet.
54 ``SK_PASS`` signifies that the socket lookup should continue on to regular
58 A BPF sk_lookup program can also select a socket to receive the packet by
59 calling ``bpf_sk_assign()`` BPF helper. Typically, the program looks up a socket
62 selection. Selecting a socket only takes effect if the program has terminated
[all …]
|
| D | map_sockmap.rst | 13 redirect skbs between sockets or to apply policy at the socket level based on
19 index to look up a reference to a ``struct sock``. The map values are socket
21 holds references to sockets via their socket descriptors.
25 returning socket cookies to userspace. Returning the ``struct sock *`` that
34 When a socket is inserted into one of these maps, its socket callbacks are
89 This helper is used in programs implementing policies at the socket level. If
91 returns ``SK_PASS``), redirect it to the socket referenced by ``map`` (of type
105 Redirect the packet to the socket referenced by ``map`` (of type
119 socket entries of type ``struct sock *`` can be retrieved using the
137 by the socket being added. If the socket is already attached to BPF programs,
[all …]
|
| D | prog_cgroup_sockopt.rst | 15 The context (``struct bpf_sockopt``) has associated socket (``sk``) and
24 and socket local storage.
50 This hook has access to the cgroup and socket local storage.
115 /* Custom socket option. */
123 /* Modify kernel's socket option. */
141 /* Custom socket option. */
148 /* Modify kernel's socket option. */
162 of BPF program that handles socket options.
|
| /Documentation/admin-guide/perf/ |
| D | nvidia-pmu.rst | 37 see /sys/bus/event_sources/devices/nvidia_scf_pmu_<socket-id>.
41 * Count event id 0x0 in socket 0::
45 * Count event id 0x0 in socket 1::
69 see /sys/bus/event_sources/devices/nvidia_nvlink_c2c0_pmu_<socket-id>.
73 * Count event id 0x0 from the GPU/CPU connected with socket 0::
77 * Count event id 0x0 from the GPU/CPU connected with socket 1::
81 * Count event id 0x0 from the GPU/CPU connected with socket 2::
85 * Count event id 0x0 from the GPU/CPU connected with socket 3::
99 see /sys/bus/event_sources/devices/nvidia_nvlink_c2c1_pmu_<socket-id>.
103 * Count event id 0x0 from the GPU connected with socket 0::
[all …]
|
| D | qcom_l3_pmu.rst | 7 by all cores within a socket. Each slice is exposed as a separate uncore perf
8 PMU with device name l3cache_<socket>_<instance>. User space is responsible
14 consisting of one CPU per socket which will be used to handle all the PMU
15 events on that socket.
|
| /Documentation/netlabel/ |
| D | cipso_ipv4.rst | 23 adding the CIPSO label to the socket. This causes all packets leaving the
24 system through the socket to have the CIPSO IP option applied. The socket's
26 that it is set upon the socket's creation. The LSM can set the socket's CIPSO
29 generated and attached to the socket.
38 This is typically done at the socket layer using the 'socket_sock_rcv_skb()'
|
| /Documentation/security/ |
| D | SCTP.rst | 74 addresses on a socket.
80 on an SCTP socket using multiple
112 Called whenever a new socket is created by **accept**\(2)
113 (i.e. a TCP style socket) or when a socket is 'peeled off' e.g userspace
177 | socket security_sctp_sk_clone() is
178 | called to clone the new socket.
219 Set the sctp ``@asoc sid`` to socket's sid (from ``asoc->base.sk``) with
221 TCP style sockets and peeled off connections as they cause a new socket
225 options are set on the socket.
260 Called whenever a new socket is created by **accept**\(2) (i.e. a TCP style
[all …]
|
| /Documentation/hwmon/ |
| D | k10temp.rst | 8 Socket F: Quad-Core/Six-Core/Embedded Opteron (but see below)
10 Socket AM2+: Quad-Core Opteron, Phenom (II) X3/X4, Athlon X2 (but see below)
12 Socket AM3: Quad-Core Opteron, Athlon/Phenom II X2/X3/X4, Sempron II
14 Socket S1G3: Athlon II, Sempron, Turion II
18 Socket S1G2: Athlon (X2), Sempron (X2), Turion X2 (Ultra)
93 All these processors have a sensor, but on those for Socket F or AM2+,
99 socket type, not the processor's actual capabilities. Therefore, if you
|
12345678