| /linux/Documentation/misc-devices/ |
| H A D | dw-xdata-pcie.rst | 4 Driver for Synopsys DesignWare PCIe traffic generator (also known as xData) 22 The dw-xdata-pcie driver can be used to enable/disable PCIe traffic 33 Write TLPs traffic generation - Root Complex to Endpoint direction 36 Generate traffic:: 45 Stop traffic in any direction:: 49 Read TLPs traffic generation - Endpoint to Root Complex direction 52 Generate traffic:: 61 Stop traffic in any direction::
|
| /linux/Documentation/networking/device_drivers/ethernet/freescale/ |
| H A D | dpaa.rst | 159 different traffic flows received by one interface to be processed by different 162 The driver has support for multiple prioritized Tx traffic classes. Priorities 164 strict priority levels. Each traffic class contains NR_CPU TX queues. By 165 default, only one traffic class is enabled and the lowest priority Tx queues 166 are used. Higher priority traffic classes can be enabled with the mqprio 167 qdisc. For example, all four traffic classes are enabled on an interface with 168 the following command. Furthermore, skb priority levels are mapped to traffic 171 * priorities 0 to 3 - traffic class 0 (low priority) 172 * priorities 4 to 7 - traffic class 1 (medium-low priority) 173 * priorities 8 to 11 - traffic class 2 (medium-high priority) [all …]
|
| /linux/Documentation/admin-guide/cgroup-v1/ |
| H A D | net_prio.rst | 6 dynamically set the priority of network traffic generated by various 9 Nominally, an application would set the priority of its traffic via the 13 2) The priority of application traffic is often a site-specific administrative 17 the priority of egress traffic on a given interface. Network priority groups can 34 This file contains a map of the priorities assigned to traffic originating 42 This command would force any traffic originating from processes belonging to the 44 said traffic set to the value 5. The parent accounting group also has a 53 traffic to be steered to hardware/driver based traffic classes. These mappings
|
| /linux/Documentation/networking/ |
| H A D | tc-queue-filters.rst | 7 TC can be used for directing traffic to either a set of queues or 12 1) TC filter directing traffic to a set of queues is achieved 14 the priority maps to a traffic class (set of queues) when 17 2) TC filter directs traffic to a transmit queue with the action 25 1) TC flower filter directs incoming traffic to a set of queues using 27 hw_tc $TCID - Specify a hardware traffic class to pass matching 35 devices, TC filter directing traffic to a queue have higher
|
| H A D | bridge.rst | 74 * Blocking: The port is disabled for data traffic and only listens for 117 be in the forwarding state (used for data traffic) and which should be in 126 it to actively forward network traffic. 128 bridge will forward traffic towards the designated segment. Designated ports 192 to intelligently manage multicast traffic within a local area network (LAN). 198 switch optimizes the forwarding of multicast traffic. Instead of blindly 199 broadcasting the multicast traffic to all ports, it sends the multicast 200 traffic based on the destination MAC address only to ports which have 220 traffic forwarding is called the IGMP leave latency. A device configured 222 traffic if the last host to request to receive traffic from the device [all …]
|
| H A D | bareudp.rst | 31 This creates a bareudp tunnel device which tunnels L3 traffic with ethertype 32 0x8847 (MPLS traffic). The destination port of the UDP header will be set to 33 6635.The device will listen on UDP port 6635 to receive traffic.
|
| H A D | nexthop-group-resilient.rst | 33 previous and the new distribution, some traffic flows change the next hop 50 contains, and forwards traffic there. 71 traffic, and use those to satisfy the new next-hop distribution demands, 94 amount of time that a bucket must not be hit by traffic in order for it to 151 been hit by traffic. 155 as busy are treated as if traffic hit them. 251 only), each bucket will be considered idle when no traffic hits it for at
|
| H A D | switchdev.rst | 88 the physical port and provides a conduit for control traffic to/from the 147 traffic from a port in one namespace to another port in another namespace. 222 traffic. To enable VLAN support, turn on VLAN filtering:: 329 certain netdevs from flooding unicast traffic for which there is no FDB entry. 339 traffic groups only to the configured ports. 424 send and receive traffic to this network device and it is properly separated 477 - with VLAN filtering turned off, the bridge will process all ingress traffic 478 for the port, except for the traffic tagged with a VLAN ID destined for a 481 interfaces. Some approaches to ensure that the forwarding domain for traffic 485 configured to map all traffic, except the packets tagged with a VID [all …]
|
| /linux/Documentation/networking/device_drivers/ethernet/intel/ |
| H A D | e1000e.rst | 64 all traffic types, but lacking in small packet performance and latency. 69 it dynamically adjusts the InterruptThrottleRate value based on the traffic 70 that it receives. After determining the type of incoming traffic in the last 72 for that traffic. 74 The algorithm classifies the incoming traffic every interval into 76 adjusted to suit that traffic type the best. There are three classes defined: 77 "Bulk traffic", for large amounts of packets of normal size; "Low latency", 78 for small amounts of traffic and/or a significant percentage of small 80 minimal traffic. 84 However, this is generally not suitable for bulk throughput traffic due [all …]
|
| H A D | e1000.rst | 111 all traffic types,but lacking in small packet performance and latency. 116 it dynamically adjusts the InterruptThrottleRate value based on the traffic 117 that it receives. After determining the type of incoming traffic in the last 119 for that traffic. 121 The algorithm classifies the incoming traffic every interval into 123 adjusted to suit that traffic type the best. There are three classes defined: 124 "Bulk traffic", for large amounts of packets of normal size; "Low latency", 125 for small amounts of traffic and/or a significant percentage of small 127 minimal traffic. 130 for traffic that falls in class "Bulk traffic". If traffic falls in the "Low [all …]
|
| H A D | ixgbe.rst | 232 the DCB features (multiple traffic classes utilizing Priority Flow Control and 235 When DCB is enabled, network traffic is transmitted and received through 236 multiple traffic classes (packet buffers in the NIC). The traffic is associated 238 in the VLAN tag. When SR-IOV is not enabled, each traffic class is associated 240 pairs for a given traffic class depends on the hardware configuration. When 243 receive/transmit descriptor queue pairs. When multiple traffic classes are 245 each traffic class. When a single traffic class is configured in the hardware, 246 the pools contain multiple queue pairs from the single traffic class. 248 The number of VFs that can be allocated depends on the number of traffic 249 classes that can be enabled. The configurable number of traffic classes for [all …]
|
| H A D | iavf.rst | 121 allow L2 tunneling and the ability to segregate traffic within a particular 139 and allow Tx traffic to be rate limited per application. Follow the steps below 155 1. Create traffic classes (TCs). Maximum of 8 TCs can be created per interface. 209 for VXLAN traffic in non-tunnel mode, PCTYPE is identified as a VXLAN 212 - If a TC filter on a PF matches traffic over a VF (on the PF), that traffic 214 the VF. Such traffic will end up getting dropped higher up in the TCP/IP 216 - If traffic matches multiple TC filters that point to different TCs, that 217 traffic will be duplicated and sent to all matching TC queues. The hardware 236 You may not be able to pass traffic between a client system and a 251 Using four traffic classes fails [all …]
|
| H A D | ice.rst | 69 expected and can throttle traffic between the host and the virtual switch, 71 unintended traffic streams, configure all SR-IOV enabled ports for VLAN tagging 166 basic traffic and minimal functionality, such as updating the NVM or 245 NOTE: This driver allows you to filter traffic based on a user-defined flexible 254 Flow Director filters are used to direct traffic that matches specified 283 <queue> - the queue to direct traffic toward (-1 discards the 284 matched traffic) 313 To match TCP traffic sent from 192.168.0.1, port 5300, directed to 192.168.0.5, 500 2. Use netperf to route traffic from the client to CPU 4 on the server with 621 ingress traffic, use the following command:: [all …]
|
| /linux/tools/testing/selftests/drivers/net/hw/ |
| H A D | pp_alloc_fail.py | 81 traffic = None 83 traffic = GenerateTraffic(cfg) 127 if traffic: 128 traffic.stop()
|
| H A D | rss_input_xfrm.py | 13 def traffic(cfg, local_port, remote_port, ipver): function 61 If symmetric RSS hash is configured, send traffic twice, swapping the 62 src/dst UDP ports, and verify that the same queue is receiving the traffic 85 cpu1 = traffic(cfg, port1, port2, ipver) 86 cpu2 = traffic(cfg, port2, port1, ipver) 89 cpu1, cpu2, comment=f"Received traffic on different cpus with ports ({port1 = }, {port2 = }) while symmetric hash is configured") 97 raise KsftFailEx("Failed to run traffic") 100 comment=f"Received traffic on less than two cpus {cpus = }")
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-driver-xdata | 5 Description: Allows the user to enable the PCIe traffic generator which 7 Endpoint direction or to disable the PCIe traffic generator 30 Description: Allows the user to enable the PCIe traffic generator which 32 Complex direction or to disable the PCIe traffic generator
|
| H A D | sysfs-class-fc | 12 traffic based on the identifier. FC host and FC fabric 13 entities can utilize the application id and FC traffic 14 tag to identify traffic sources.
|
| /linux/net/bridge/ |
| H A D | Kconfig | 30 bridged ARP traffic in the arptables FORWARD chain. 44 forward multicast traffic based on IGMP/MLD traffic received from 58 receive and forward traffic based on VLAN information in the packet
|
| /linux/tools/testing/selftests/drivers/net/ |
| H A D | netpoll_basic.py | 362 traffic = None 365 traffic = GenerateTraffic(cfg) 368 if traffic: 369 traffic.stop()
|
| /linux/net/dcb/ |
| H A D | Kconfig | 12 NICs and switches to support network traffic with differing 18 framework for assigning bandwidth guarantees to traffic classes.
|
| /linux/Documentation/networking/dsa/ |
| H A D | b53.rst | 66 # tag traffic on CPU port 93 # tag traffic on ports 113 # tag traffic on CPU port 148 # tag traffic on CPU port 174 # tag traffic on ports
|
| H A D | configuration.rst | 38 to send or receive traffic. Prior to kernel v5.12, the state of the conduit 65 A user interface dedicated for upstream traffic 88 DSA switches. These switches are capable to tag incoming and outgoing traffic 176 # tag traffic on CPU port 204 # tag traffic on ports 221 # tag traffic on CPU port 246 # tag traffic on ports 260 # tag traffic on CPU port 287 # tag traffic on ports 376 statically assign the termination traffic associated with a certain user port [all …]
|
| H A D | sja1105.rst | 78 The hardware tags all traffic internally with a port-based VLAN (pvid), or it 87 bridge with ``vlan_filtering 0`` can be kept (accept all traffic, tagged or 102 The switch supports a variation of the enhancements for scheduled traffic 104 ensure deterministic latency for priority traffic that is sent in-band with its 109 would only be able to shape traffic originated from the CPU, but not 112 The device has 8 traffic classes, and maps incoming frames to one of them based 128 Management traffic (having DMAC 01-80-C2-xx-xx-xx or 01-19-1B-xx-xx-xx) is the 130 disregards any VLAN PCP bits even if present. The traffic class for management 131 traffic has a value of 7 (highest priority) at the moment, which is not 135 ``swp5``. The traffic class gate for management traffic (7) is open for 100 us, [all …]
|
| /linux/net/mac80211/ |
| H A D | led.c | 249 unsigned long traffic, delta; in tpt_trig_traffic() local 251 traffic = tpt_trig->tx_bytes + tpt_trig->rx_bytes; in tpt_trig_traffic() 253 delta = traffic - tpt_trig->prev_traffic; in tpt_trig_traffic() 254 tpt_trig->prev_traffic = traffic; in tpt_trig_traffic()
|
| /linux/drivers/net/ethernet/freescale/fman/ |
| H A D | Kconfig | 22 FMAN DMA read or writes under heavy traffic load may cause FMAN 40 stress with multiple ports injecting line-rate traffic.
|