Searched refs:traffic (Results 1 – 25 of 134) sorted by relevance
123456
| /Linux-v5.4/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
|
| /Linux-v5.4/Documentation/networking/device_drivers/freescale/ |
| 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 …]
|
| /Linux-v5.4/Documentation/networking/device_drivers/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 | 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 | 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 …]
|
| 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 | 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.
|
| /Linux-v5.4/Documentation/networking/dsa/ |
| D | sja1105.rst | 70 customizing the TPID by which VLAN traffic is identified as such. The switch
74 interfere with the reception and transmission of real 802.1Q-tagged traffic,
82 These are used to trap BPDUs and PTP traffic to the master netdevice, and are
86 The following traffic modes are supported over the switch netdevices:
92 | Regular traffic | Yes | Yes | No (use master) |
94 | Management traffic | Yes | Yes | Yes |
108 The hardware tags all traffic internally with a port-based VLAN (pvid), or it
117 bridge with ``vlan_filtering 0`` can be kept (accept all traffic, tagged or
125 ports are no longer available for standalone traffic termination.
131 management (no address learning and no flooding of unknown traffic) is not yet
[all …]
|
| 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 | 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
|
| /Linux-v5.4/net/bridge/ |
| 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-v5.4/drivers/staging/fsl-dpaa2/ethsw/ |
| D | TODO | 2 traffic to reach the CPU.
3 * Add ACL to redirect control traffic to CPU.
|
| /Linux-v5.4/net/dcb/ |
| D | Kconfig | 12 NICs and switches to support network traffic with differing
18 framework for assigning bandwidth guarantees to traffic classes.
|
| /Linux-v5.4/Documentation/networking/ |
| D | af_xdp.rst | 55 completed that traffic starts to flow.
79 traffic to user space through the XSK.
298 UMEMs. Say that you would like your UDP traffic from port 4242 to end
317 Q: I am not seeing any traffic on the socket. What am I doing wrong?
323 specify a specific queue id to bind to and it is only the traffic
326 traffic that is distributed to queues 1 through 7. If you are
327 lucky, you will see the traffic, but usually it will end up on one
331 traffic you want to the queue id you bound to. If you want to see
332 all the traffic, you can force the netdev to only have 1 queue, queue
337 If you want to only see part of the traffic, you can program the
[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 | 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
|
| /Linux-v5.4/net/mac80211/ |
| 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-v5.4/Documentation/networking/device_drivers/ti/ |
| D | 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:
|
| /Linux-v5.4/drivers/net/ethernet/neterion/vxge/ |
| D | Makefile | 8 vxge-objs := vxge-config.o vxge-traffic.o vxge-ethtool.o vxge-main.o
|
| /Linux-v5.4/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
|
| /Linux-v5.4/drivers/usb/mon/ |
| D | Kconfig | 9 If you select this option, a component which captures the USB traffic
|
| /Linux-v5.4/Documentation/networking/device_drivers/aquantia/ |
| D | atlantic.txt | 266 for traffic IPv4 or you can set 2 rules for traffic IPv6. Loc number traffic
270 Example filter for IPv6 filter traffic:
275 Example filter for IPv4 filter traffic:
281 If you set action -1, then all traffic corresponding to the filter will be discarded.
322 incorrect working of RSS for fragmented UDP traffic. To disable RSS for UDP the
|
| /Linux-v5.4/Documentation/networking/device_drivers/amazon/ |
| 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.
244 - The ENA device supports RSS that allows flexible Rx traffic
|
| /Linux-v5.4/Documentation/devicetree/bindings/fpga/ |
| D | altera-freeze-bridge.txt | 6 unfreeze/enable the bridges which allows traffic to pass through the
|
123456
