Searched full:tcp (Results 1 – 25 of 120) sorted by relevance
12345
| /Documentation/networking/ |
| D | tcp_ao.rst | 4 TCP Authentication Option Linux implementation (RFC5925)
7 TCP Authentication Option (TCP-AO) provides a TCP extension aimed at verifying
8 segments between trusted peers. It adds a new TCP header option with
10 of a TCP segment using a hashing function with a password known to both peers.
11 The intent of TCP-AO is to deprecate TCP-MD5 providing better security,
17 .. table:: Short and Limited Comparison of TCP-AO and TCP-MD5
20 | | TCP-MD5 | TCP-AO |
31 | | |TCP header permitted. |
34 |TCP connection | | |
45 |traffic-crossing | |includes TCP ports. |
[all …]
|
| D | kcm.rst | 8 interface over TCP for generic application protocols. With KCM an application
9 can efficiently send and receive application protocol messages over TCP using
31 | TCP sock | | TCP sock | | TCP sock | | TCP sock | | TCP sock |
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
50 TCP sockets & Psocks
53 TCP sockets may be bound to a KCM multiplexor. A Psock structure is allocated
54 for each bound TCP socket, this structure holds the state for constructing
60 Each multiplexor assumes that all attached TCP connections are to the same
73 Messages are sent over a TCP stream with some application protocol message
[all …]
|
| D | snmp_counter.rst | 32 The number of packets delivers to the upper layer protocols. E.g. TCP, UDP,
249 General TCP counters
257 The number of packets received by the TCP layer. As mentioned in
259 error, invalid TCP header and so on. Only one error won't be included:
263 packets would be delivered to the TCP layer, but the TCP layer will discard
274 The number of packets sent by the TCP layer. As mentioned in RFC1213,
286 It means the TCP layer sends a SYN, and come into the SYN-SENT
296 It means the TCP layer receives a SYN, replies a SYN+ACK, come into
301 When packets are received by the TCP layer and are not be read by the
302 application, the TCP layer will try to merge them. This counter
[all …]
|
| D | mptcp.rst | 4 Multipath TCP (MPTCP)
10 Multipath TCP or MPTCP is an extension to the standard TCP and is described in
12 device to make use of multiple interfaces at once to send and receive TCP
18 For more details about Multipath TCP in the Linux kernel, please see the
26 brings new use-cases, compared to TCP:
42 a regular TCP connection that is used to transmit data through one interface.
44 host to be able to detect the use of MPTCP, a new field is added to the TCP
45 *option* field of the underlying TCP *subflow*. This field contains, amongst
48 it, the returned ``SYN+ACK`` packet will not contain MPTCP options in the TCP
49 *option* field. In that case, the connection will be "downgraded" to plain TCP,
[all …]
|
| D | devmem.rst | 4 Device Memory TCP
11 Device memory TCP (devmem TCP) enables receiving data directly into device
12 memory (dmabuf). The feature is currently implemented for TCP sockets.
36 Devmem TCP optimizes this use case by implementing socket APIs that enable
41 Packet headers go to host memory and are processed by the TCP/IP stack
58 https://netdevconf.org/0x17/sessions/talk/device-memory-tcp.html
61 [PATCH net-next v24 00/13] Device Memory TCP
79 Header split, flow steering, & RSS are required features for devmem TCP.
90 ethtool -G eth1 tcp-data-split on
134 devmem TCP, even if the dmabuf is not actually backed by devmem. An example of
[all …]
|
| D | proc_net_tcp.rst | 4 The proc/net/tcp and proc/net/tcp6 variables
7 This document describes the interfaces /proc/net/tcp and /proc/net/tcp6.
10 These /proc interfaces provide information about currently active TCP
14 It will first list all listening TCP sockets, and next list all established
15 TCP connections. A typical entry of /proc/net/tcp would look like this (split
20 | | | | |------> remote TCP port number
22 | | |--------------------> local TCP port number
|
| D | tls-offload.rst | 10 Linux kernel provides TLS connection offload infrastructure. Once a TCP
29 * Full TCP NIC offload mode (``TLS_HW_RECORD``) - mode of operation where
31 with its own TCP handling, it is not usable in production environments
43 mode) and then hands the modified scatter list to the TCP layer. From this
44 point on the TCP stack proceeds as normal.
56 :c:type:`struct sk_buff <sk_buff>`. The packets reach the TCP stack and
101 which TCP sequence number corresponds to the beginning of the record with
112 number, simplifying TCP sequence number matching.
124 so the initial records' TCP sequence number may be anywhere inside the segment.
135 * expected TCP sequence number
[all …]
|
| D | openvswitch.rst | 79 e.g. source and destination addresses from Ethernet, IP, or TCP
86 corresponding to a TCP packet that arrived on vport 1::
90 frag=no), tcp(src=49163, dst=80)
94 in_port(1), eth(...), eth_type(0x0800), ipv4(...), tcp(...)
177 definitions. With this change, a TCP packet in VLAN 10 would have a
180 eth(...), vlan(vid=10, pcp=0), eth_type(0x0800), ip(proto=6, ...), tcp(...)
192 example, why 802.1Q support uses nested attributes. A TCP packet in
196 ip(proto=6, ...), tcp(...)))
198 Notice how the "eth_type", "ip", and "tcp" flow key attributes are
218 indicates protocol 6 for TCP, but which is truncated just after the IP
[all …]
|
| D | ip-sysctl.rst | 40 protocols for which pmtu events will be honored are TCP, SCTP
44 TCP path mtu must still work but path MTU information of other
74 associated with a socket for example, TCP RSTs or ICMP echo replies).
321 TCP variables
327 See also tcp_max_syn_backlog for additional tuning for TCP sockets.
363 Enable TCP auto corking :
390 TCP SYN and SYNACK messages usually advertise an ADVMSS option,
409 Allows TCP to send "duplicate" SACKs.
424 Control use of Explicit Congestion Notification (ECN) by TCP.
425 ECN is used only when both ends of the TCP connection indicate
[all …]
|
| D | segmentation-offloads.rst | 15 * TCP Segmentation Offload - TSO
24 TCP Segmentation Offload
27 TCP segmentation allows a device to segment a single frame into multiple
29 When TCP segmentation requested the bit for either SKB_GSO_TCPV4 or
33 TCP segmentation is dependent on support for the use of partial checksum
37 In order to support TCP segmentation offload it is necessary to populate
40 TCP header. In addition as CHECKSUM_PARTIAL is required csum_start should
41 also point to the TCP header of the packet.
137 it effectively does is take advantage of certain traits of TCP and tunnels
|
| D | strparser.rst | 21 callback of a TCP socket. Messages are parsed and delivered as they are
47 strparser that is allocated by the upper layer. sk is the TCP
140 is unrecoverable (application expected to close TCP socket)
145 the error on TCP socket and wake it up. If parse_msg returned
197 the TCP socket in receive callback mode. The stream parser may
229 associated TCP socket. In general mode, the timeout is passed as an
231 the stream parser is aborted and the ETIMEDOUT error is set on the TCP
235 buffer size of the associated TCP socket. If the length returned by
237 is aborted with EMSGSIZE error set on the TCP socket. Note that this
239 parser to be 2*sk_rcvbuf of the TCP socket.
|
| D | dctcp.rst | 4 DCTCP (DataCenter TCP)
7 DCTCP is an enhancement to the TCP congestion control algorithm for data
32 "Data Center TCP (DCTCP)", Data Center Networks session"
|
| D | tproxy.rst | 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
63 be able to find out the original destination address. Even in case of TCP
69 # iptables -t mangle -A PREROUTING -p tcp --dport 80 -j TPROXY \
74 # nft add rule filter divert tcp dport 80 tproxy to :50080 meta mark set 1 accept
|
| D | rds.rst | 23 to N*N if you use a connection-oriented socket transport like TCP.
26 transports. The current implementation used to support RDS over TCP as well
43 The port space is entirely independent of UDP, TCP or any other
395 Mprds is multipathed-RDS, primarily intended for RDS-over-TCP
397 implementation of RDS-over-TCP is implemented by demultiplexing multiple
399 port]) over a single TCP socket between the 2 IP addresses involved. This
401 single TCP flow, thus it is
406 by having multiple TCP/IP flows per rds/tcp connection, i.e., multipathed
407 RDS (mprds). Each such TCP/IP flow constitutes a path for the rds/tcp
410 socket will be sent over the attached path using TCP to segment/reassemble
[all …]
|
| D | tcp-thin.rst | 4 Thin-streams and TCP
14 the service quality. Extreme latencies are caused by TCP's
23 streams provoke high latencies when using TCP is unfortunate.
|
| D | nf_flowtable.rst | 10 IPv4 and IPv6 and the layer 4 TCP and UDP protocols.
77 TCP RST and FIN packets are also passed up to the classic IP forwarding path to
93 ip protocol tcp flow add @f
106 flowtable for the TCP syn-ack packet coming in the reply direction. Once the
117 …tcp 6 src=10.141.10.2 dst=192.168.10.2 sport=52728 dport=5201 src=192.168.10.2 dst=192.168.10…
|
| /Documentation/netlink/specs/ |
| D | tcp_metrics.yaml | 8 Management interface for TCP metrics.
10 c-family-name: tcp-metrics-genl-name
11 c-version-name: tcp-metrics-genl-version
17 name: tcp-fastopen-cookie-max
23 name: tcp-metrics
24 name-prefix: tcp-metrics-attr-
66 min-len: tcp-fastopen-cookie-max
134 attribute-set: tcp-metrics
163 attribute-set: tcp-metrics
|
| /Documentation/admin-guide/nfs/ |
| D | nfsd-admin-interfaces.rst | 18 bound (and listening, for tcp) socket, or
20 "udp", "tcp", or "rdma".
23 udp and one tcp listener at port 2049 (see nfsd_init_socks).
|
| /Documentation/networking/device_drivers/ethernet/freescale/ |
| D | gianfar.rst | 15 the 8548) has the ability to perform TCP, UDP, and IP checksums
16 in hardware. The Linux kernel only offloads the TCP and UDP
18 the driver only supports checksumming for TCP/IP and UDP/IP
|
| /Documentation/networking/device_drivers/ethernet/microsoft/ |
| D | netvsc.rst | 20 support checksum offload for TCP and UDP for both IPv4 and
21 IPv6. Windows Server 2012 only supports checksum offload for TCP.
25 Hyper-V supports receive side scaling. For TCP & UDP, packets can
29 For TCP & UDP, we can switch hash level between L3 and L4 by ethtool
30 command. TCP/UDP over IPv4 and v6 can be set differently. The default
60 processing overhead by coalescing multiple TCP segments when possible. The
|
| /Documentation/networking/device_drivers/ethernet/chelsio/ |
| D | cxgb.rst | 77 TCP Segmentation Offloading (TSO) Support
81 to offload portions of outbound TCP processing to a network interface card
125 Disabling TCP timestamp::
165 Setting TCP read buffers (min/default/max)::
169 Setting TCP write buffers (min/pressure/max)::
173 Setting TCP buffer space (min/pressure/max)::
177 TCP window size for single connections:
183 "TCP/IP Illustrated, Volume 1, The Protocols" by W. Richard Stevens.
196 TCP window size for multiple connections:
240 1. Large number of TCP retransmits on a multiprocessor (SMP) system.
[all …]
|
| /Documentation/scsi/ |
| D | cxgb3i.rst | 34 the PDU into multiple TCP segments if necessary, and transmit all
35 the TCP segments onto the wire. It handles TCP retransmission if
38 On receiving, S3 h/w recovers the iSCSI PDU by reassembling TCP
|
| /Documentation/gpu/amdgpu/ |
| D | debugging.rst | 29 Faulty UTCL2 client ID: TCP (0x8)
55 - TCP/SQC/SQG: Shaders
69 In the example above, a shader (cliend id = TCP) generated a read (RW = 0x0) to
|
| /Documentation/admin-guide/blockdev/ |
| D | nbd.rst | 2 Network Block Device (TCP version)
11 request over TCP to the server, which will reply with the data read.
|
| /Documentation/bpf/ |
| D | prog_sk_lookup.rst | 14 Hooks for a common attach point (``BPF_SK_LOOKUP``) exist for both TCP and UDP.
47 find a listening (TCP) or an unconnected (UDP) socket for an incoming packet.
49 Incoming traffic to established (TCP) and connected (UDP) sockets is delivered
|
12345