| /Documentation/networking/ |
| D | kcm.txt | 12 | KCM socket | | KCM socket | | KCM socket | | KCM socket |
43 written on a KCM socket are sent atomically on an appropriate TCP socket.
44 Similarly, in the receive path, messages are constructed on each TCP socket
45 (Psock) and complete messages are steered to a KCM socket.
51 for each bound TCP socket, this structure holds the state for constructing
60 can be used to send and receive messages from the KCM socket.
62 Socket types
65 KCM supports SOCK_DGRAM and SOCK_SEQPACKET socket types.
76 Filter (BPF) is used for this. When attaching a TCP socket to a multiplexor a
81 to a KCM socket.
[all …]
|
| D | l2tp.txt | 49 Each L2TP tunnel is implemented using a UDP or L2TPIP socket; L2TPIP
51 new l2tpip socket family. The tunnel socket is typically created by
52 userspace, though for unmanaged L2TPv3 tunnels, the socket can also be
55 indirectly by pppd using a pppol2tp socket. In the case of ethernet,
85 socket. The session context holds data that lets the driver interface
94 1. Use a UDP socket per tunnel.
96 2. Create a single PPPoL2TP socket per tunnel bound to a special null
99 management socket causes the driver to mark the tunnel socket as an
100 L2TP UDP encapsulation socket and flags it for use by the
103 in this special PPPoX socket.
[all …]
|
| D | strparser.txt | 17 callback of a TCP socket. Messages are parsed and delivered as they are
18 received on the socket.
42 socket associated with the stream parser for use with receive
81 the lower socket for strparser to process. This should be called
82 from a data_ready callback that is set on the socket. Note that
83 maximum messages size is the limit of the receive socket
84 buffer and message timeout is the receive timeout for the socket.
88 strp_check_rcv is called to check for new messages on the socket.
113 kernel, return control of the socket to userspace which
117 is unrecoverable (application expected to close TCP socket)
[all …]
|
| D | phonet.txt | 8 and RPC. With the Linux Phonet socket family, Linux host processes can
75 The Phonet socket address family maps the Phonet packet header:
92 Applications can send Phonet messages using the Phonet datagram socket
93 protocol from the PF_PHONET family. Each socket is bound to one of the
102 fd = socket(PF_PHONET, SOCK_DGRAM, 0);
118 A Phonet datagram socket can be subscribed to any number of 8-bits
125 control request, or when the socket is closed.
127 Note that no more than one socket can be subcribed to any given
136 socket paradigm. The listening socket is bound to an unique free object
137 ID. Each listening socket can handle up to 255 simultaneous
[all …]
|
| D | rds.txt | 16 applications to use a single socket to talk to any other process in the
18 to N*N if you use a connection-oriented socket transport like TCP.
28 the end point of a connection. All socket operations that involve
40 * Socket interface
42 socket. The next section will cover the details. At any rate,
43 all I/O is performed through the standard BSD socket API.
50 attaches it to the socket. Once bound, the transport assignment
59 Socket Interface
63 AF_RDS and PF_RDS are the domain type to be used with socket(2)
64 to create RDS sockets. SOL_RDS is the socket-level to be used
[all …]
|
| D | rxrpc.txt | 20 (*) Socket options.
175 connections are handled transparently. One client socket may be used to
176 make multiple simultaneous calls to the same service. One server socket
186 (*) Each internal UDP socket is retained [tunable] for a certain amount of
207 Interaction with the user of the RxRPC socket:
209 (*) A socket is made into a server socket by binding an address with a
220 socket. This may be overridden by supplying an alternate address to the
226 (*) A server socket may also be used to make client calls. To do this, the
272 (*) The server application has to provide the server socket with a keyring of
280 nominated by a socket option.
[all …]
|
| D | msg_zerocopy.rst | 9 The MSG_ZEROCOPY flag enables copy avoidance for socket send calls.
19 underlying copy avoidance mechanism to common socket send calls.
52 [PATCH net-next v4 0/9] socket sendmsg MSG_ZEROCOPY
62 Socket Setup
68 this flag, a process must first signal intent by setting a socket option:
86 the socket option was not set, the socket exceeds its optmem limit or
104 socket error queue, akin to the transmit timestamping interface.
106 The notification itself is a simple scalar value. Each socket
143 the socket. A socket that has an error queued would normally block
166 may arrive out of order on retransmission and socket teardown.
[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
110 An AF_XDP is socket linked to a single UMEM, but one UMEM can have
111 multiple AF_XDP sockets. To share an UMEM created via one socket A,
112 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
|
| 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 | tproxy.txt | 5 To use it, enable the socket match and the TPROXY target in your kernel config.
14 socket on your box, set the packet mark to a certain value:
17 # iptables -t mangle -A PREROUTING -p tcp -m socket -j DIVERT
25 # nft add rule filter divert meta l4proto tcp socket transparent 1 meta mark set 1 accept
35 addresses. All you have to do is enable the (SOL_IP, IP_TRANSPARENT) socket
38 fd = socket(AF_INET, SOCK_STREAM, 0);
74 IP_TRANSPARENT) for the listening socket.
|
| 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
347 TCP socket is in LISTEN state, and kernel need to drop a packet,
358 stack will keep the socket in the TCP half-open queue. As it is in the
361 queue is still full, if it is not full, moves the socket to the accept
362 queue, if it is full, keeps the socket in the half-open queue, at next
363 time client replies ACK, this socket will get another chance to move
400 The socket receives a RST packet in Establish or CloseWait state.
[all …]
|
| D | j1939.rst | 116 J1939 defines white list filters per socket that a user can set in order to
123 When multiple filters are in place for a single socket, and a packet comes in
125 that socket.
133 On CAN, you first need to open a socket for communicating over a CAN network.
135 included too. To open a socket, use:
139 s = socket(PF_CAN, SOCK_DGRAM, CAN_J1939);
146 After the successful creation of the socket, you would normally use the bind(2)
147 and/or connect(2) system call to bind the socket to a CAN interface. After
148 binding and/or connecting the socket, you can read(2) and write(2) from/to the
149 socket or use send(2), sendto(2), sendmsg(2) and the recv*() counterpart
[all …]
|
| D | timestamping.txt | 37 This socket option enables timestamping of datagrams on the reception
38 path. Because the destination socket, if any, is not known early in
42 For interface details, see `man 7 socket`.
65 socket option takes a bitmap of flags, not a boolean. In
72 The socket option configures timestamp generation for individual
73 sk_buffs (1.3.1), timestamp reporting to the socket's error
87 requested by a particular socket, such as when receive timestamping is
100 can be enabled via both socket options and control messages.
107 This flag can be enabled via both socket options and control messages.
122 via both socket options and control messages.
[all …]
|
| D | udplite.txt | 11 This file briefly describes the existing kernel support and the socket API.
32 Porting applications to UDP-Lite is straightforward: only socket level and
40 uses the same socket type as UDP. In fact, porting from UDP to UDP-Lite is
41 very easy: simply add `IPPROTO_UDPLITE' as the last argument of the socket(2)
44 s = socket(PF_INET, SOCK_DGRAM, IPPROTO_UDPLITE);
48 s = socket(PF_INET6, SOCK_DGRAM, IPPROTO_UDPLITE);
55 single socket option, which takes an integer specifying the coverage length:
83 alone protocol, all socket options known from UDP can be used in exactly the
91 The socket API requires support through header files in /usr/include:
109 IV) KERNEL BEHAVIOUR WITH REGARD TO THE VARIOUS SOCKET OPTIONS
[all …]
|
| D | dccp.txt | 9 - Socket options
48 Socket options
71 service codes (RFC 4340, sec. 8.1.2); if this socket option is not set,
72 the socket will fall back to 0 (which means that no meaningful service code
88 time, combining the operation of the next two socket options. This option is
91 understood. This socket option takes as argument at least one uint8_t value, or
93 must be registered on the socket before calling connect() or listen().
101 DCCP_SOCKOPT_SERVER_TIMEWAIT enables the server (listening socket) to hold
104 state. When this boolean socket option is on, the server sends a Close instead
122 settings are inherited to the child socket after accept().
[all …]
|
| D | packet_mmap.txt | 6 socket interface on 2.4/2.6/3.x kernels. This type of sockets is used for
62 [setup] socket() -------> creation of the capture socket
70 [shutdown] close() --------> destruction of the capture socket and
75 socket creation and destruction is straight forward, and is done
78 int fd = socket(PF_PACKET, mode, htons(ETH_P_ALL));
86 The destruction of the socket and all associated resources
89 Similarly as without PACKET_MMAP, it is possible to use one socket
103 [setup] socket() -------> creation of the transmission socket
106 bind() ---------> bind transmission socket with a network interface
116 [shutdown] close() --------> destruction of the transmission socket and
[all …]
|
| D | nfc.txt | 25 The low-level data exchange interface is provided by the new socket family
39 | socket +-----------+
98 All polling operations requested through one netlink socket are stopped when
114 NFC_SOCKPROTO_RAW socket and call the 'connect' syscall with the sockaddr_nfc
120 When the socket is closed, the target is deactivated.
|
| /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 | 77 addresses on a socket.
83 on an SCTP socket using multiple
115 Called whenever a new socket is created by **accept**\(2)
116 (i.e. a TCP style socket) or when a socket is 'peeled off' e.g userspace
176 | socket security_sctp_sk_clone() is
177 | called to clone the new socket.
218 Set the sctp ``@ep sid`` to socket's sid (from ``ep->base.sk``) with
220 TCP style sockets and peeled off connections as they cause a new socket
224 options are set on the socket.
259 Called whenever a new socket is created by **accept**\(2) (i.e. a TCP style
[all …]
|
| /Documentation/admin-guide/perf/ |
| 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.
|
| D | thunderx2-pmu.rst | 5 The ThunderX2 SoC PMU consists of independent, system-wide, per-socket
19 The thunderx2_pmu driver registers per-socket perf PMUs for the DMC and
23 /sys/devices/uncore_<l3c_S/dmc_S/>; S is the socket id.
|
| /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
|
| /Documentation/devicetree/bindings/cpu/ |
| D | cpu-topology.txt | 12 - socket
63 - one or more socket nodes in a multi-socket system
69 - socket node
76 The nodes describing the CPU topology (socket/cluster/core/thread) can
87 (ie socket/cluster/core/thread) (where N = {0, 1, ...} is the node number; nodes
95 3 - socket/cluster/core/thread node bindings
98 Bindings for socket/cluster/cpu/thread nodes are defined as follows:
100 - socket node
103 per physical socket in the system. A system can
104 contain single or multiple physical socket.
[all …]
|
| /Documentation/driver-api/ |
| D | connector.rst | 17 - socket();
110 2.6.14 has a new netlink socket implementation, which by default does not
112 So, if you wish to use a netlink socket (for example using connector)
116 s = socket(PF_NETLINK, SOCK_DGRAM, NETLINK_CONNECTOR);
133 Where 270 above is SOL_NETLINK, and 1 is a NETLINK_ADD_MEMBERSHIP socket
134 option. To drop a multicast subscription, one should call the above socket
|