Searched full:flow (Results 1 – 25 of 146) sorted by relevance
123456
| /Documentation/networking/ |
| D | openvswitch.txt | 5 flow-level packet processing on selected network devices. It can be
7 VLAN processing, network access control, flow-based network control,
12 within a bridge). Each datapath also has associated with it a "flow
19 extracting its flow key and looking it up in the flow table. If there
20 is a matching flow, it executes the associated actions. If there is
22 its processing, userspace will likely set up a flow to handle further
26 Flow key compatibility
32 versions to parse additional protocols as part of the flow key. It
36 applications to work with any version of the flow key, past or future.
40 flow key that it parsed from the packet. Userspace then extracts its
[all …]
|
| D | secid.txt | 3 The secid member in the flow structure is used in LSMs (e.g. SELinux) to indicate
4 the label of the flow. This label of the flow is currently used in selecting
7 If this is an outbound flow, the label is derived from the socket, if any, or
8 the incoming packet this flow is being generated as a response to (e.g. tcp
13 If this is an inbound flow, the label is derived from the IPSec security
|
| D | scaling.rst | 19 - RFS: Receive Flow Steering
20 - Accelerated Receive Flow Steering
31 of logical flows. Packets for each flow are steered to a separate receive
131 flow hash over the packet’s addresses or ports (2-tuple or 4-tuple hash
133 associated flow of the packet. The hash is either provided by hardware
138 packet’s flow.
142 an index into the list is computed from the flow hash modulo the size
183 RPS Flow Limit
187 reordering. The trade-off to sending all packets from the same flow
189 In the extreme case a single flow dominates traffic. Especially on
[all …]
|
| D | nf_flowtable.txt | 10 Initial packets follow the classic forwarding path, once the flow enters the
12 in both directions), then you can decide to offload the flow to the flowtable
13 from the forward chain via the 'flow offload' action available in nftables.
26 Flowtables are populated via the 'flow offload' nftables action, so the user can
27 selectively specify what flows are placed into the flow table. Hence, packets
52 |-----| | 'flow offload' rule |
83 ip protocol tcp flow offload @f
95 The 'flow offload' action from the forward chain 'y' adds an entry to the
97 flow is offloaded, you will observe that the counter rule in the example above
|
| D | nf_conntrack-sysctl.txt | 7 Enable connection tracking flow accounting. 64-bit byte and packet
8 counters per flow are added.
27 Number of currently allocated flow entries.
154 Enable connection tracking flow timestamping.
|
| /Documentation/bpf/ |
| D | prog_flow_dissector.rst | 10 Flow dissector is a routine that parses metadata out of the packets. It's
11 used in the various places in the networking subsystem (RFS, flow hash, etc).
13 BPF flow dissector is an attempt to reimplement C-based flow dissector logic
20 BPF flow dissector programs operate on an ``__sk_buff``. However, only the
22 ``flow_keys`` is ``struct bpf_flow_keys`` and contains flow dissector input
31 Flow dissector BPF program should fill out the rest of the ``struct
41 In the VLAN-less case, this is what the initial state of the BPF flow
49 +-- flow dissector starts here
58 In case of VLAN, flow dissector can be called with the two different states.
67 +-- flow dissector starts here
[all …]
|
| /Documentation/core-api/ |
| D | genericirq.rst | 52 optimize the flow of the interrupt handling for each specific interrupt
58 the flow control in the super-handler. This leads to a mix of flow logic
62 have different flow handling.
64 A more natural abstraction is the clean separation of the 'irq flow' and
68 reveals that most of them can use a generic set of 'irq flow' methods
71 IRQ flow itself but not in the chip details - and thus provides a more
74 Each interrupt descriptor is assigned its own high-level flow handler,
76 flow handler implementation also makes it simple to provide
82 IRQ-flow implementation for 'level type' interrupts and add a
104 2. High-level IRQ flow handlers
[all …]
|
| /Documentation/devicetree/bindings/serial/ |
| D | milbeaut-uart.txt | 11 - auto-flow-control: flow control enable.
20 auto-flow-control;
|
| D | uniphier-uart.txt | 10 -auto-flow-control: enable automatic flow control support.
|
| D | st-asc.txt | 10 - st,hw-flow-ctrl bool flag to enable hardware flow control.
|
| D | st,stm32-usart.txt | 18 - st,hw-flow-ctrl: bool flag to enable hardware flow control.
44 st,hw-flow-ctrl;
|
| /Documentation/networking/device_drivers/intel/ |
| D | i40e.rst | 15 - Intel(R) Ethernet Flow Director
123 Intel(R) Ethernet Flow Director
125 The Intel Ethernet Flow Director performs the following tasks:
128 - Enables tight control on routing a flow in the platform.
129 - Matches flows and CPU cores for flow affinity.
130 - Supports multiple parameters for flexible flow classification and load
133 NOTE: The Linux i40e driver supports the following flow types: IPv4, TCPv4, and
134 UDPv4. For a given flow type, it supports valid combinations of IP addresses
141 and mask fields. Only L3 and L4 flow types are supported for user-defined
142 flexible filters. For a given flow type, you must clear all Intel Ethernet Flow
[all …]
|
| D | ixgbe.rst | 232 the DCB features (multiple traffic classes utilizing Priority Flow Control and
280 Flow Control
282 Ethernet Flow Control (IEEE 802.3x) can be configured with ethtool to enable
288 NOTE: You must have a flow control capable link partner.
290 Flow Control is enabled by default.
292 Use ethtool to change the flow control settings. To enable or disable Rx or
293 Tx Flow Control::
297 Note: This command only enables or disables Flow Control if auto-negotiation is
305 Note: Flow Control auto-negotiation is part of link auto-negotiation. Depending
308 NOTE: For 82598 backplane cards entering 1 gigabit mode, flow control default
[all …]
|
| D | fm10k.rst | 28 Flow Control
30 The Intel(R) Ethernet Switch Host Interface Driver does not support Flow
103 Retrieves the receive network flow classification configurations.
105 rx-flow-hash tcp4|udp4|ah4|esp4|sctp4|tcp6|udp6|ah6|esp6|sctp6
109 Configures the receive network flow classification.
111 rx-flow-hash tcp4|udp4|ah4|esp4|sctp4|tcp6|udp6|ah6|esp6|sctp6 m|v|t|s|d|f|n|r
|
| /Documentation/networking/device_drivers/mellanox/ |
| D | mlx5.rst | 42 | Enables Hardware-accelerated receive flow steering (arfs) support, and ntuple filtering.
48 | Enables ethtool receive network flow classification, which allows user defined
49 | flow rules to direct traffic into arbitrary rx queue via ethtool set/get_rxnfc API.
129 flow_steering_mode: Device flow steering mode
131 The flow steering mode parameter controls the flow steering mode of the driver.
133 1. 'dmfs' - Device managed flow steering.
134 2. 'smfs - Software/Driver managed flow steering.
145 - Set SMFS flow steering mode::
149 - Read device flow steering mode::
239 It follows fatal errors indications by CR-space dump and recover flow.
[all …]
|
| /Documentation/devicetree/bindings/hsi/ |
| D | client-devices.txt | 15 - hsi-flow: RX flow type ("synchronized" or "pipeline")
38 hsi-flow = "synchronized";
|
| /Documentation/devicetree/bindings/arm/tegra/ |
| D | nvidia,tegra20-flowctrl.txt | 1 NVIDIA Tegra Flow Controller
15 flow-controller@60007000 {
|
| /Documentation/networking/device_drivers/aquantia/ |
| D | atlantic.txt | 226 RX flow rules (ntuple filters)
237 To enable or disable the RX flow rules:
258 …ethtool -N <ethX> flow-type udp4 src-ip 10.0.0.1 dst-ip 10.0.0.2 src-port 2000 dst-port 2001 actio…
263 For "flow-type ip4|udp4|tcp4|sctp4|ip6|udp6|tcp6|sctp6" you must set the loc
265 For "flow-type ip4|udp4|tcp4|sctp4|ip6|udp6|tcp6|sctp6" you can set 8 rules
272 …sudo ethtool -N <ethX> flow-type tcp6 src-ip 2001:db8:0:f101::1 dst-ip 2001:db8:0:f101::2 action 1…
273 …sudo ethtool -N <ethX> flow-type ip6 src-ip 2001:db8:0:f101::2 dst-ip 2001:db8:0:f101::5 action -1…
277 …sudo ethtool -N <ethX> flow-type udp4 src-ip 10.0.0.4 dst-ip 10.0.0.7 src-port 2000 dst-port 2001 …
278 …sudo ethtool -N <ethX> flow-type tcp4 src-ip 10.0.0.3 dst-ip 10.0.0.9 src-port 2000 dst-port 2001 …
279 sudo ethtool -N <ethX> flow-type ip4 src-ip 10.0.0.6 dst-ip 10.0.0.4 loc 34
[all …]
|
| /Documentation/devicetree/bindings/dma/ |
| D | qcom_adm.txt | 8 denotes CRCI (client rate control interface) flow control assignment.
44 3. CRCI assignment, if applicable. If no CRCI flow control is required, use 0.
45 The CRCI is used for flow control. It identifies the peripheral device that
|
| /Documentation/networking/device_drivers/microsoft/ |
| D | netvsc.txt | 36 ethtool -N eth0 rx-flow-hash udp4 sdfn
38 ethtool -N eth0 rx-flow-hash udp4 sd
40 ethtool -n eth0 rx-flow-hash udp4
70 flow direction is desired, these should be applied directly to the
|
| /Documentation/networking/device_drivers/qualcomm/ |
| D | rmnet.txt | 34 or data packet. Control packet is used for transport level flow control. Data
58 Command 1 indicates disabling flow while 2 is enabling flow
|
| /Documentation/networking/device_drivers/freescale/ |
| D | dpaa.txt | 151 ethtool. Also, rx-flow-hash and rx-hashing was added. The addition of RSS
201 be processed by the same CPU. This ensures intra-flow order preservation
206 # ethtool -N fm1-mac9 rx-flow-hash tcp4 ""
208 To turn it back on, one needs to set rx-flow-hash for tcp4/6 or udp4/6:
210 # ethtool -N fm1-mac9 rx-flow-hash udp4 sfdn
214 going to control the rx-flow-hashing for all protocols on that interface.
230 Please note that Rx hashing depends upon the rx-flow-hashing being on
231 for that interface - turning off rx-flow-hashing will also disable the
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | cirrus,clps711x-intc.txt | 20 8: TC1OI TC1 under flow
21 9: TC2OI TC2 under flow
|
| /Documentation/gpu/ |
| D | komeda-kms.rst | 94 Single pipeline data flow
99 :caption: Single pipeline data flow
145 :caption: Slave pipeline enabled data flow
223 :caption: Layer (input) data flow
254 :caption: Writeback(output) data flow
270 :caption: Writeback(output) Split data flow
286 :caption: display output data flow
308 - Data flow controlling.
312 data flow control and all specific components are a subclass of this base
376 - `Single pipeline data flow`_
[all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | st,stm32-spdifrx.txt | 3 The SPDIFRX peripheral, is designed to receive an S/PDIF flow compliant with
12 - dmas: DMA specifiers for audio data DMA and iec control flow DMA
|
123456