Home
last modified time | relevance | path

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

123456

/linux-5.19.10/Documentation/networking/
Dkcm.rst8 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 …]
Dsnmp_counter.rst32 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 …]
Dproc_net_tcp.rst10 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
Dtls-offload.rst10 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 …]
Dstrparser.rst21 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.
Ddctcp.rst4 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"
Dsegmentation-offloads.rst15 * 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
Dip-sysctl.rst40 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).
298 TCP variables
304 See also tcp_max_syn_backlog for additional tuning for TCP sockets.
337 Enable TCP auto corking :
364 TCP SYN and SYNACK messages usually advertise an ADVMSS option,
383 Allows TCP to send "duplicate" SACKs.
398 Control use of Explicit Congestion Notification (ECN) by TCP.
399 ECN is used only when both ends of the TCP connection indicate
[all …]
/linux-5.19.10/net/ipv4/
DKconfig269 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;
384 bool "IP: ESP in TCP encapsulation (RFC 8229)"
391 TCP/IPv4 sockets.
418 Support for INET (TCP, DCCP, etc) socket monitoring interface used by
460 bool "TCP: advanced congestion control"
462 Support for selection of various TCP congestion control
476 BIC-TCP is a sender-side only change that ensures a linear RTT
[all …]
/linux-5.19.10/net/mptcp/
DKconfig3 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-5.19.10/drivers/infiniband/sw/siw/
DKconfig2 tristate "Software RDMA over TCP/IP (iWARP) driver"
7 the Linux TCP/IP network stack. It enables a system with a
17 TCP/IP, the driver further interfaces with the Linux
18 in-kernel TCP socket layer.
/linux-5.19.10/net/dccp/ccids/
DKconfig15 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-5.19.10/net/rds/
DKconfig8 sequenced delivery of datagrams over Infiniband or TCP.
18 tristate "RDS over TCP"
22 Allow RDS to use TCP as a transport.
/linux-5.19.10/drivers/net/ethernet/intel/ice/
Dice_lan_tx_rx.h727 ICE_PTT(26, IP, IPV4, NOF, NONE, NONE, NOF, TCP, PAY4),
736 ICE_PTT(33, IP, IPV4, NOF, IP_IP, IPV4, NOF, TCP, PAY4),
745 ICE_PTT(40, IP, IPV4, NOF, IP_IP, IPV6, NOF, TCP, PAY4),
757 ICE_PTT(48, IP, IPV4, NOF, IP_GRENAT, IPV4, NOF, TCP, PAY4),
766 ICE_PTT(55, IP, IPV4, NOF, IP_GRENAT, IPV6, NOF, TCP, PAY4),
778 ICE_PTT(63, IP, IPV4, NOF, IP_GRENAT_MAC, IPV4, NOF, TCP, PAY4),
787 ICE_PTT(70, IP, IPV4, NOF, IP_GRENAT_MAC, IPV6, NOF, TCP, PAY4),
799 ICE_PTT(78, IP, IPV4, NOF, IP_GRENAT_MAC_VLAN, IPV4, NOF, TCP, PAY4),
808 ICE_PTT(85, IP, IPV4, NOF, IP_GRENAT_MAC_VLAN, IPV6, NOF, TCP, PAY4),
817 ICE_PTT(92, IP, IPV6, NOF, NONE, NONE, NOF, TCP, PAY4),
[all …]
/linux-5.19.10/tools/testing/selftests/bpf/prog_tests/
Dcls_redirect.c171 TCP, enumerator
240 { TCP, ACCEPT, UNKNOWN_CONN, NO_HOPS, SYN },
241 { TCP, ACCEPT, UNKNOWN_CONN, NO_HOPS, ACK },
242 { TCP, FORWARD, UNKNOWN_CONN, ONE_HOP, ACK },
243 { TCP, ACCEPT, KNOWN_CONN, ONE_HOP, ACK },
334 case TCP: in build_input()
392 &servers[TCP][i], &conns[TCP][i], in test_cls_redirect_common()
393 &tuples[TCP][i]))) in test_cls_redirect_common()
/linux-5.19.10/drivers/net/ethernet/intel/iavf/
Diavf_common.c576 IAVF_PTT(26, IP, IPV4, NOF, NONE, NONE, NOF, TCP, PAY4),
585 IAVF_PTT(33, IP, IPV4, NOF, IP_IP, IPV4, NOF, TCP, PAY4),
594 IAVF_PTT(40, IP, IPV4, NOF, IP_IP, IPV6, NOF, TCP, PAY4),
606 IAVF_PTT(48, IP, IPV4, NOF, IP_GRENAT, IPV4, NOF, TCP, PAY4),
615 IAVF_PTT(55, IP, IPV4, NOF, IP_GRENAT, IPV6, NOF, TCP, PAY4),
627 IAVF_PTT(63, IP, IPV4, NOF, IP_GRENAT_MAC, IPV4, NOF, TCP, PAY4),
636 IAVF_PTT(70, IP, IPV4, NOF, IP_GRENAT_MAC, IPV6, NOF, TCP, PAY4),
648 IAVF_PTT(78, IP, IPV4, NOF, IP_GRENAT_MAC_VLAN, IPV4, NOF, TCP, PAY4),
657 IAVF_PTT(85, IP, IPV4, NOF, IP_GRENAT_MAC_VLAN, IPV6, NOF, TCP, PAY4),
666 IAVF_PTT(92, IP, IPV6, NOF, NONE, NONE, NOF, TCP, PAY4),
[all …]
Diavf_adv_rss.c50 VIRTCHNL_SET_PROTO_HDR_TYPE(hdr, TCP); in iavf_fill_adv_rss_tcp_hdr()
53 VIRTCHNL_ADD_PROTO_HDR_FIELD_BIT(hdr, TCP, SRC_PORT); in iavf_fill_adv_rss_tcp_hdr()
56 VIRTCHNL_ADD_PROTO_HDR_FIELD_BIT(hdr, TCP, DST_PORT); in iavf_fill_adv_rss_tcp_hdr()
/linux-5.19.10/Documentation/networking/device_drivers/ethernet/freescale/
Dgianfar.rst15 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-5.19.10/Documentation/networking/device_drivers/ethernet/microsoft/
Dnetvsc.rst20 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-5.19.10/drivers/net/ethernet/wiznet/
DKconfig27 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-5.19.10/Documentation/networking/device_drivers/ethernet/chelsio/
Dcxgb.rst77 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-5.19.10/drivers/nvme/target/
DKconfig78 tristate "NVMe over Fabrics TCP target support"
82 This enables the NVMe TCP target support, which allows exporting NVMe
83 devices over TCP.
/linux-5.19.10/Documentation/scsi/
Dcxgb3i.rst34 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-5.19.10/tools/testing/selftests/netfilter/
Dnf_nat_edemux.sh79 ip netns exec $ns2 socat -t 10 - TCP:192.168.1.1:5201 > /dev/null &
86 echo test | ip netns exec $ns2 socat -t 3 -u STDIN TCP:10.96.0.1:443 >/dev/null
/linux-5.19.10/Documentation/admin-guide/blockdev/
Dnbd.rst2 Network Block Device (TCP version)
11 request over TCP to the server, which will reply with the data read.

123456