Searched refs:traffic (Results 1 – 25 of 124) sorted by relevance
12345
| /Linux-v4.19/Documentation/cgroup-v1/ |
| D | net_prio.txt | 5 dynamically set the priority of network traffic generated by various
8 Nominally, an application would set the priority of its traffic via the
12 2) The priority of application traffic is often a site-specific administrative
16 the priority of egress traffic on a given interface. Network priority groups can
32 This file contains a map of the priorities assigned to traffic originating from
40 This command would force any traffic originating from processes belonging to the
42 said traffic set to the value 5. The parent accounting group also has a
51 traffic to be steered to hardware/driver based traffic classes. These mappings
|
| /Linux-v4.19/Documentation/networking/ |
| D | dpaa.txt | 153 different traffic flows received by one interface to be processed by different
156 The driver has support for multiple prioritized Tx traffic classes. Priorities
158 strict priority levels. Each traffic class contains NR_CPU TX queues. By
159 default, only one traffic class is enabled and the lowest priority Tx queues
160 are used. Higher priority traffic classes can be enabled with the mqprio
161 qdisc. For example, all four traffic classes are enabled on an interface with
162 the following command. Furthermore, skb priority levels are mapped to traffic
165 * priorities 0 to 3 - traffic class 0 (low priority)
166 * priorities 4 to 7 - traffic class 1 (medium-low priority)
167 * priorities 8 to 11 - traffic class 2 (medium-high priority)
[all …]
|
| D | e1000e.txt | 66 all traffic types, but lacking in small packet performance and latency.
71 it dynamically adjusts the InterruptThrottleRate value based on the traffic
72 that it receives. After determining the type of incoming traffic in the last
74 for that traffic.
76 The algorithm classifies the incoming traffic every interval into
78 adjusted to suit that traffic type the best. There are three classes defined:
79 "Bulk traffic", for large amounts of packets of normal size; "Low latency",
80 for small amounts of traffic and/or a significant percentage of small
82 minimal traffic.
85 for traffic that falls in class "Bulk traffic". If traffic falls in the "Low
[all …]
|
| D | e1000.rst | 109 all traffic types,but lacking in small packet performance and latency.
114 it dynamically adjusts the InterruptThrottleRate value based on the traffic
115 that it receives. After determining the type of incoming traffic in the last
117 for that traffic.
119 The algorithm classifies the incoming traffic every interval into
121 adjusted to suit that traffic type the best. There are three classes defined:
122 "Bulk traffic", for large amounts of packets of normal size; "Low latency",
123 for small amounts of traffic and/or a significant percentage of small
125 minimal traffic.
128 for traffic that falls in class "Bulk traffic". If traffic falls in the "Low
[all …]
|
| D | bonding.txt | 278 traffic recently (the precise criteria depends upon the
279 bonding mode, and the state of the slave). Regular traffic is
311 non-ARP traffic should be filtered (disregarded) for link
351 is receiving the appropriate ARP traffic.
370 target fail (but not the switch itself), the probe traffic
386 determining if a slave has received traffic for link availability
390 levels of third party broadcast traffic would fool the standard
392 filtering can resolve this, as only ARP traffic is considered for
457 often takes place for any traffic, not just ARP
458 traffic, if the switch snoops incoming traffic to
[all …]
|
| D | ti-cpsw.txt | 66 tc - traffic class
176 // Map skb->priority to traffic class:
178 // Map traffic class to transmit queue:
184 // As two interface sharing same set of tx queues, assign all traffic
186 // with traffic from interface Eth0, so use separate txq to send
398 // Map skb->priority to traffic class for Eth0:
400 // Map traffic class to transmit queue:
450 // Map skb->priority to traffic class for Eth1:
452 // Map traffic class to transmit queue:
|
| D | tproxy.txt | 52 2. Redirecting traffic
55 Transparent proxying often involves "intercepting" traffic on a router. This is
100 the HTTP listener you redirect traffic to with the TPROXY iptables
|
| D | ena.txt | 20 ENA devices enable high speed and low overhead network traffic
102 Notification Suspend traffic
103 Notification Resume traffic
188 according to the traffic nature.
190 By default ENA driver applies adaptive coalescing on Rx traffic and
191 conventional coalescing on Tx traffic.
241 - The ENA device supports RSS that allows flexible Rx traffic
|
| D | spider_net.txt | 45 flowing RX traffic, every descr behind it should be marked "full",
53 and advance the tail pointer. Thus, when there is flowing RX traffic,
55 all of those behind it should be "not-in-use". When RX traffic is not
61 When traffic is flowing, then the head pointer will be pointing at
66 is flowing RX traffic, everything in front of the head pointer should
68 RX traffic is flowing, then the head pointer can catch up to the tail
|
| /Linux-v4.19/net/bridge/ |
| D | Kconfig | 29 bridged ARP traffic in the arptables FORWARD chain.
43 forward multicast traffic based on IGMP/MLD traffic received from
57 receive and forward traffic based on VLAN information in the packet
|
| /Linux-v4.19/drivers/staging/fsl-dpaa2/ethsw/ |
| D | TODO | 2 traffic to reach the CPU.
3 * Add ACL to redirect control traffic to CPU.
|
| /Linux-v4.19/net/dcb/ |
| D | Kconfig | 11 NICs and switches to support network traffic with differing
17 framework for assigning bandwidth guarantees to traffic classes.
|
| /Linux-v4.19/net/mac80211/ |
| D | led.c | 252 unsigned long traffic, delta; in tpt_trig_traffic() local
254 traffic = tpt_trig->tx_bytes + tpt_trig->rx_bytes; in tpt_trig_traffic()
256 delta = traffic - tpt_trig->prev_traffic; in tpt_trig_traffic()
257 tpt_trig->prev_traffic = traffic; in tpt_trig_traffic()
|
| /Linux-v4.19/drivers/net/ethernet/neterion/vxge/ |
| D | Makefile | 7 vxge-objs := vxge-config.o vxge-traffic.o vxge-ethtool.o vxge-main.o
|
| /Linux-v4.19/Documentation/ABI/testing/ |
| D | sysfs-class-net-mesh | 13 Indicates whether the data traffic going from a
22 Indicates whether the data traffic going through the
39 Indicates whether the data traffic going through the
|
| /Linux-v4.19/drivers/usb/mon/ |
| D | Kconfig | 8 If you select this option, a component which captures the USB traffic
|
| /Linux-v4.19/drivers/staging/fsl-dpaa2/ethernet/ |
| D | ethernet-driver.rst | 106 frames, but must be affine to the CPUs for the purpose of traffic distribution.
120 DPCONs are used to distribute ingress traffic to different CPUs via the cores'
181 traffic based on a 5-tuple key: src IP, dst IP, IP proto, L4 src port,
|
| /Linux-v4.19/Documentation/devicetree/bindings/fpga/ |
| D | altera-freeze-bridge.txt | 6 unfreeze/enable the bridges which allows traffic to pass through the
|
| D | xilinx-pr-decoupler.txt | 7 couple / enable the bridges which allows traffic to pass through the
|
| /Linux-v4.19/net/ |
| D | Kconfig | 127 bothersome to set up; it inspects the network traffic much more
140 forwards the traffic to the intended outside destination, but
143 replies, the Linux box will silently forward the traffic to the
153 box can transparently forward the traffic to a local server,
158 the bridged traffic. For filtering on the lower network and Ethernet
190 ARP resp. IP traffic. If you want a bridging firewall, you probably
320 generate the vast majority of load, drop their traffic earlier to
|
| /Linux-v4.19/Documentation/aoe/ |
| D | aoe.txt | 47 limit ATA over Ethernet traffic to eth2 and eth4. AoE traffic from
107 AoE traffic to the network interfaces in the given
|
| /Linux-v4.19/Documentation/media/uapi/dvb/ |
| D | net-add-if.rst | 36 contains a TCP/IP traffic, the type of encapsulation to be used (MPE or
|
| /Linux-v4.19/samples/bpf/ |
| D | tcp_bpf.readme | 20 If using netperf/netserver to create traffic, you need to run them under the
|
| /Linux-v4.19/Documentation/devicetree/bindings/devfreq/event/ |
| D | exynos-nocp.txt | 9 or as traffic debug or statistic collectors. Exynos542x bus has multiple
|
| /Linux-v4.19/Documentation/devicetree/bindings/iio/gyroscope/ |
| D | invensense,mpu3050.txt | 19 incoming I2C bus, alternatively drive traffic to a slave device (usually
|
12345
