| /openbmc/linux/Documentation/networking/ |
| H A 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 …]
|
| H A 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 …]
|
| H A 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
|
| H A 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 …]
|
| H A 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.
|
| H A 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"
|
| H A 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
|
| /openbmc/linux/net/ipv4/ |
| H A 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;
384 bool "IP: ESP in TCP encapsulation (RFC 8229)"
391 TCP/IPv4 sockets.
428 Support for INET (TCP, DCCP, etc) socket monitoring interface used by
470 bool "TCP: advanced congestion control"
472 Support for selection of various TCP congestion control
486 BIC-TCP is a sender-side only change that ensures a linear RTT
[all …]
|
| /openbmc/openbmc-test-automation/security/ |
| H A D | test_bmc_network_security.robot | 148 Send Continuous TCP Connection Requests To Redfish Interface And Check Stability
149 [Documentation] Establish large number of TCP connections to Redfish port (443)
153 # Establish large number of TCP connections to Redfish interface.
154 ${connection_loss}= Establish TCP Connections And Get Connection Failures
161 # Check if TCP connections dropped.
166 Send Continuous TCP Connection Requests To IPMI Interface And Check Stability
167 [Documentation] Establish large number of TCP connections to IPMI interface
171 # Establish large number of TCP connections to IPMI interface.
172 ${connection_loss}= Establish TCP Connections And Get Connection Failures
178 # Check if TCP/Network connections dropped.
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/iptraf/ |
| H A D | iptraf-ng_1.2.1.bb | 6 data like TCP connection packet and byte counts, interface statistics \
7 and activity indicators, TCP/UDP traffic breakdowns, and LAN station \
9 which shows TCP flag information, packet and byte counts, ICMP \
11 interface statistics showing IP, TCP, UDP, ICMP, non-IP and other IP \
13 counts; a TCP and UDP service monitor showing counts of incoming and \
14 outgoing packets for common TCP and UDP application ports, a LAN \
16 about their activity; TCP, UDP and other protocol display filters so \
|
| /openbmc/linux/net/mptcp/ |
| H A 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"
|
| /openbmc/linux/drivers/infiniband/sw/siw/ |
| H A D | Kconfig | 2 tristate "Software RDMA over TCP/IP (iWARP) driver"
10 the Linux TCP/IP network stack. It enables a system with a
20 TCP/IP, the driver further interfaces with the Linux
21 in-kernel TCP socket layer.
|
| /openbmc/linux/net/dccp/ccids/ |
| H A 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
|
| /openbmc/linux/drivers/net/ethernet/intel/ice/ |
| H A D | ice_lan_tx_rx.h | 727 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 …]
|
| /openbmc/linux/net/rds/ |
| H A 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.
|
| /openbmc/linux/drivers/net/ethernet/intel/iavf/ |
| H A D | iavf_common.c | 546 IAVF_PTT(26, IP, IPV4, NOF, NONE, NONE, NOF, TCP, PAY4),
555 IAVF_PTT(33, IP, IPV4, NOF, IP_IP, IPV4, NOF, TCP, PAY4),
564 IAVF_PTT(40, IP, IPV4, NOF, IP_IP, IPV6, NOF, TCP, PAY4),
576 IAVF_PTT(48, IP, IPV4, NOF, IP_GRENAT, IPV4, NOF, TCP, PAY4),
585 IAVF_PTT(55, IP, IPV4, NOF, IP_GRENAT, IPV6, NOF, TCP, PAY4),
597 IAVF_PTT(63, IP, IPV4, NOF, IP_GRENAT_MAC, IPV4, NOF, TCP, PAY4),
606 IAVF_PTT(70, IP, IPV4, NOF, IP_GRENAT_MAC, IPV6, NOF, TCP, PAY4),
618 IAVF_PTT(78, IP, IPV4, NOF, IP_GRENAT_MAC_VLAN, IPV4, NOF, TCP, PAY4),
627 IAVF_PTT(85, IP, IPV4, NOF, IP_GRENAT_MAC_VLAN, IPV6, NOF, TCP, PAY4),
636 IAVF_PTT(92, IP, IPV6, NOF, NONE, NONE, NOF, TCP, PAY4),
[all …]
|
| H A D | iavf_adv_rss.c | 50 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()
|
| /openbmc/linux/tools/testing/selftests/bpf/prog_tests/ |
| H A D | cls_redirect.c | 172 TCP, enumerator
241 { TCP, ACCEPT, UNKNOWN_CONN, NO_HOPS, SYN },
242 { TCP, ACCEPT, UNKNOWN_CONN, NO_HOPS, ACK },
243 { TCP, FORWARD, UNKNOWN_CONN, ONE_HOP, ACK },
244 { TCP, ACCEPT, KNOWN_CONN, ONE_HOP, ACK },
335 case TCP: in build_input()
393 &servers[TCP][i], &conns[TCP][i], in test_cls_redirect_common()
394 &tuples[TCP][i]))) in test_cls_redirect_common()
|
| /openbmc/openbmc-test-automation/network/ |
| H A D | test_network_nping.robot | 41 [Documentation] Send TCP, UDP or ICMP packets to the target.
51 # by default it sends 100 TCP packets at 5 packets/second.
69 # SENT (0.0181s) TCP Source IP:37577 >
71 # SENT (0.2189s) TCP Source IP:37577 >
73 # RCVD (0.4120s) TCP Destination IP:80 >
|
| /openbmc/linux/Documentation/networking/device_drivers/ethernet/freescale/ |
| H A 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
|
| /openbmc/linux/Documentation/networking/device_drivers/ethernet/microsoft/ |
| H A 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
|
| /openbmc/openbmc/poky/meta/recipes-connectivity/slirp/ |
| H A D | libslirp_git.bb | 1 SUMMARY = "A general purpose TCP-IP emulator"
2 DESCRIPTION = "A general purpose TCP-IP emulator used by virtual machine hypervisors to provide vir…
|
| /openbmc/linux/drivers/net/ethernet/wiznet/ |
| H A 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.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-benchmark/dbench/ |
| H A D | dbench_4.0.bb | 1 SUMMARY = "The dbench (disk) and tbench (TCP) benchmarks"
3 SUMMARY:tbench = "TCP load benchmark"
|
| /openbmc/openbmc/poky/meta/recipes-core/netbase/ |
| H A D | netbase_6.4.bb | 1 SUMMARY = "Basic TCP/IP networking support"
2 DESCRIPTION = "This package provides the necessary infrastructure for basic TCP/IP based networking"
|