TCP (reference) in projects: Linux-v5.10

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched refs:TCP (Results 1 – 25 of 131) sorted by relevance

12 3 4 5 6

/Linux-v5.10/Documentation/networking/
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	proc_net_tcp.rst	`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	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 190 the TCP socket in receive callback mode. The stream parser may 222 associated TCP socket. In general mode, the timeout is passed as an 224 the stream parser is aborted and the ETIMEDOUT error is set on the TCP 228 buffer size of the associated TCP socket. If the length returned by 230 is aborted with EMSGSIZE error set on the TCP socket. Note that this 232 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	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	ip-sysctl.rst	39 protocols for which pmtu events will be honored are TCP, SCTP 43 TCP path mtu must still work but path MTU information of other 72 associated with a socket for example, TCP RSTs or ICMP echo replies). 239 TCP variables 245 See also tcp_max_syn_backlog for additional tuning for TCP sockets. 278 Enable TCP auto corking : 305 TCP SYN and SYNACK messages usually advertise an ADVMSS option, 324 Allows TCP to send "duplicate" SACKs. 339 Control use of Explicit Congestion Notification (ECN) by TCP. 340 ECN is used only when both ends of the TCP connection indicate [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	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 …]
/Linux-v5.10/net/ipv4/
D	Kconfig	269 bool "IP: TCP syncookie support" 271 Normal TCP/IP networking is open to an attack known as "SYN 278 say Y here, the TCP/IP stack will use a cryptographic challenge 281 is no need for the legitimate users to change their TCP/IP software; 385 bool "IP: ESP in TCP encapsulation (RFC 8229)" 392 TCP/IPv4 sockets. 419 Support for INET (TCP, DCCP, etc) socket monitoring interface used by 461 bool "TCP: advanced congestion control" 463 Support for selection of various TCP congestion control 477 BIC-TCP is a sender-side only change that ensures a linear RTT [all …]
/Linux-v5.10/net/mptcp/
D	Kconfig	`3 bool "MPTCP: Multipath TCP" 9 Multipath TCP (MPTCP) connections send and receive data over multiple 11 uses the TCP protocol, and TCP options carry header information for 21 bool "MPTCP: IPv6 support for Multipath TCP"`
/Linux-v5.10/drivers/infiniband/sw/siw/
D	Kconfig	`2 tristate "Software RDMA over TCP/IP (iWARP) driver" 8 the Linux TCP/IP network stack. It enables a system with a 18 TCP/IP, the driver further interfaces with the Linux 19 in-kernel TCP socket layer.`
/Linux-v5.10/net/dccp/ccids/
D	Kconfig	`15 bool "CCID-3 (TCP-Friendly)" 18 CCID-3 denotes TCP-Friendly Rate Control (TFRC), an equation-based 20 be reasonably fair when competing for bandwidth with TCP-like flows, 22 within a factor of two of the sending rate of a TCP flow under the 24 throughput over time compared with TCP, which makes CCID-3 more`
/Linux-v5.10/net/rds/
D	Kconfig	`8 sequenced delivery of datagrams over Infiniband or TCP. 18 tristate "RDS over TCP" 22 Allow RDS to use TCP as a transport.`
/Linux-v5.10/tools/testing/selftests/bpf/prog_tests/
D	cls_redirect.c	`170 TCP, enumerator 239 { TCP, ACCEPT, UNKNOWN_CONN, NO_HOPS, SYN }, 240 { TCP, ACCEPT, UNKNOWN_CONN, NO_HOPS, ACK }, 241 { TCP, FORWARD, UNKNOWN_CONN, ONE_HOP, ACK }, 242 { TCP, ACCEPT, KNOWN_CONN, ONE_HOP, ACK }, 333 case TCP: in build_input() 391 &servers[TCP][i], &conns[TCP][i], in test_cls_redirect_common() 392 &tuples[TCP][i]))) in test_cls_redirect_common()`
/Linux-v5.10/drivers/net/ethernet/intel/ice/
D	ice_lan_tx_rx.h	637 ICE_PTT(26, IP, IPV4, NOF, NONE, NONE, NOF, TCP, PAY4), 646 ICE_PTT(33, IP, IPV4, NOF, IP_IP, IPV4, NOF, TCP, PAY4), 655 ICE_PTT(40, IP, IPV4, NOF, IP_IP, IPV6, NOF, TCP, PAY4), 667 ICE_PTT(48, IP, IPV4, NOF, IP_GRENAT, IPV4, NOF, TCP, PAY4), 676 ICE_PTT(55, IP, IPV4, NOF, IP_GRENAT, IPV6, NOF, TCP, PAY4), 688 ICE_PTT(63, IP, IPV4, NOF, IP_GRENAT_MAC, IPV4, NOF, TCP, PAY4), 697 ICE_PTT(70, IP, IPV4, NOF, IP_GRENAT_MAC, IPV6, NOF, TCP, PAY4), 709 ICE_PTT(78, IP, IPV4, NOF, IP_GRENAT_MAC_VLAN, IPV4, NOF, TCP, PAY4), 718 ICE_PTT(85, IP, IPV4, NOF, IP_GRENAT_MAC_VLAN, IPV6, NOF, TCP, PAY4), 727 ICE_PTT(92, IP, IPV6, NOF, NONE, NONE, NOF, TCP, PAY4), [all …]
/Linux-v5.10/drivers/net/ethernet/intel/iavf/
D	iavf_common.c	577 IAVF_PTT(26, IP, IPV4, NOF, NONE, NONE, NOF, TCP, PAY4), 586 IAVF_PTT(33, IP, IPV4, NOF, IP_IP, IPV4, NOF, TCP, PAY4), 595 IAVF_PTT(40, IP, IPV4, NOF, IP_IP, IPV6, NOF, TCP, PAY4), 607 IAVF_PTT(48, IP, IPV4, NOF, IP_GRENAT, IPV4, NOF, TCP, PAY4), 616 IAVF_PTT(55, IP, IPV4, NOF, IP_GRENAT, IPV6, NOF, TCP, PAY4), 628 IAVF_PTT(63, IP, IPV4, NOF, IP_GRENAT_MAC, IPV4, NOF, TCP, PAY4), 637 IAVF_PTT(70, IP, IPV4, NOF, IP_GRENAT_MAC, IPV6, NOF, TCP, PAY4), 649 IAVF_PTT(78, IP, IPV4, NOF, IP_GRENAT_MAC_VLAN, IPV4, NOF, TCP, PAY4), 658 IAVF_PTT(85, IP, IPV4, NOF, IP_GRENAT_MAC_VLAN, IPV6, NOF, TCP, PAY4), 667 IAVF_PTT(92, IP, IPV6, NOF, NONE, NONE, NOF, TCP, PAY4), [all …]
/Linux-v5.10/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`
/Linux-v5.10/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`
/Linux-v5.10/drivers/net/ethernet/wiznet/
D	Kconfig	`27 PHY and hardware TCP/IP stack, but this driver is limited to 28 the MAC and PHY functions only, onchip TCP/IP is unused. 40 PHY and hardware TCP/IP stack, but this driver is limited to 41 the MAC and PHY functions only, onchip TCP/IP is unused.`
/Linux-v5.10/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 …]
/Linux-v5.10/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`
/Linux-v5.10/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.`
/Linux-v5.10/drivers/nvme/target/
D	Kconfig	`80 tristate "NVMe over Fabrics TCP target support" 84 This enables the NVMe TCP target support, which allows exporting NVMe 85 devices over TCP.`

12 3 4 5 6