Searched full:traffic (Results 1 – 25 of 121) sorted by relevance
12345
| /Documentation/admin-guide/cgroup-v1/ |
| 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
|
| D | net_cls.rst | 8 The Traffic Controller (tc) can be used to assign
38 - creating traffic class 10:1::
|
| /Documentation/networking/device_drivers/ethernet/freescale/ |
| 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 …]
|
| /Documentation/networking/device_drivers/ethernet/intel/ |
| 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 …]
|
| 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 …]
|
| D | iavf.rst | 107 - 1 Traffic Class (TC), TC0
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
234 Traffic Is Not Being Passed Between VM and Client
[all …]
|
| 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 …]
|
| D | i40e.rst | 103 ingress traffic, use the following command::
121 this example is that the VF will get all traffic that is tagged with VLAN 100.
139 NOTE: The Linux i40e driver allows you to filter traffic based on a
187 Sideband Perfect Filters are used to direct traffic that matches specified
199 <queue> - the queue to direct traffic towards (-1 discards matching traffic)
212 The following example matches TCP traffic sent from 192.168.0.1, port 5300,
278 To create filters that direct traffic to a specific Virtual Function, use the
285 specifies to direct traffic to Virtual Function 7 (8 minus 1) into queue 2 of
289 route traffic that otherwise would not have been sent to the specified Virtual
353 Retrieves the hash options for the specified network traffic type.
[all …]
|
| D | ixgb.rst | 144 efficiency if properly tuned for specific network traffic. Increasing
146 decreasing the throughput of TCP traffic. If the system is reporting
157 efficiency if properly tuned for specific network traffic. Increasing
159 decreasing the throughput of TCP traffic. If this value is set too high,
293 Resolving Slow UDP Traffic
295 If your server does not seem to be able to receive UDP traffic as fast as it
296 can receive TCP traffic, it could be because Linux, by default, does not set
431 will respond to IP traffic for any IP address assigned to the system.
432 This results in unbalanced receive traffic.
|
| D | fm10k.rst | 92 shown that by coalescing Rx traffic into larger chunks of data, CPU
106 Retrieves the hash options for the specified network traffic type.
112 Configures the hash options for the specified network traffic type.
|
| /Documentation/networking/dsa/ |
| D | configuration.rst | 55 A slave interface dedicated for upstream traffic
78 DSA switches. These switches are capable to tag incoming and outgoing traffic
170 # tag traffic on CPU port
197 # tag traffic on ports
216 # tag traffic on CPU port
240 # tag traffic on ports
256 # tag traffic on CPU port
282 # tag traffic on ports
|
| D | sja1105.rst | 66 Traffic support
72 These are used to trap BPDUs and PTP traffic to the master netdevice, and are
78 format based on VLANs), general-purpose traffic termination through the network
89 other than STP, PTP etc) traffic termination is not possible through the
100 To summarize, in each mode, the following types of traffic are supported over
107 | traffic | | (use master) | |
110 | traffic | | | |
269 The hardware tags all traffic internally with a port-based VLAN (pvid), or it
278 bridge with ``vlan_filtering 0`` can be kept (accept all traffic, tagged or
286 ports are no longer available for standalone traffic termination.
[all …]
|
| 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
|
| /Documentation/networking/ |
| D | bareudp.rst | 30 This creates a bareudp tunnel device which tunnels L3 traffic with ethertype
31 0x8847 (MPLS traffic). The destination port of the UDP header will be set to
32 6635.The device will listen on UDP port 6635 to receive traffic.
|
| D | bonding.rst | 287 traffic recently (the precise criteria depends upon the
288 bonding mode, and the state of the slave). Regular traffic is
320 non-ARP traffic should be filtered (disregarded) for link
360 is receiving the appropriate ARP traffic.
379 target fail (but not the switch itself), the probe traffic
395 determining if a slave has received traffic for link availability
399 levels of third party broadcast traffic would fool the standard
401 filtering can resolve this, as only ARP traffic is considered for
466 often takes place for any traffic, not just ARP
467 traffic, if the switch snoops incoming traffic to
[all …]
|
| D | af_xdp.rst | 55 completed that traffic starts to flow.
79 traffic to user space through the XSK.
318 built in one in libbpf that will route the traffic for you.
398 both, you will be able to both receive and send traffic from your
549 you would like your UDP traffic from port 4242 to end up in queue 16,
572 Q: I am not seeing any traffic on the socket. What am I doing wrong?
578 specify a specific queue id to bind to and it is only the traffic
581 traffic that is distributed to queues 1 through 7. If you are
582 lucky, you will see the traffic, but usually it will end up on one
586 traffic you want to the queue id you bound to. If you want to see
[all …]
|
| D | tproxy.rst | 55 2. Redirecting traffic
58 Transparent proxying often involves "intercepting" traffic on a router. This is
105 the HTTP listener you redirect traffic to with the TPROXY iptables
|
| /Documentation/networking/devlink/ |
| D | sja1105.rst | 27 - Can terminate untagged traffic over switch net
30 - Can terminate VLAN-tagged traffic over switch net
|
| /Documentation/ABI/obsolete/ |
| D | sysfs-class-net-mesh | 15 Indicates whether the data traffic going from a
24 Indicates whether the data traffic going through the
41 Indicates whether the data traffic going through the
|
| /Documentation/networking/device_drivers/ethernet/toshiba/ |
| D | spider_net.rst | 47 flowing RX traffic, every descr behind it should be marked "full",
55 and advance the tail pointer. Thus, when there is flowing RX traffic,
57 all of those behind it should be "not-in-use". When RX traffic is not
63 When traffic is flowing, then the head pointer will be pointing at
68 is flowing RX traffic, everything in front of the head pointer should
70 RX traffic is flowing, then the head pointer can catch up to the tail
|
| /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
|
| /Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-fm-rx.rst | 57 If set, then a traffic announcement is in progress.
60 If set, then the tuned programme carries traffic announcements.
|
| /Documentation/admin-guide/aoe/ |
| D | aoe.rst | 52 limit ATA over Ethernet traffic to eth2 and eth4. AoE traffic from
113 AoE traffic to the network interfaces in the given
|
| /Documentation/devicetree/bindings/devfreq/event/ |
| D | exynos-nocp.txt | 9 or as traffic debug or statistic collectors. Exynos542x bus has multiple
|
12345