Searched full:flow (Results 1 – 25 of 216) sorted by relevance
123456789
| /Documentation/networking/ |
| D | openvswitch.rst | 8 flow-level packet processing on selected network devices. It can be
10 VLAN processing, network access control, flow-based network control,
15 within a bridge). Each datapath also has associated with it a "flow
22 extracting its flow key and looking it up in the flow table. If there
23 is a matching flow, it executes the associated actions. If there is
25 its processing, userspace will likely set up a flow to handle further
29 Flow key compatibility
35 versions to parse additional protocols as part of the flow key. It
39 applications to work with any version of the flow key, past or future.
43 flow key that it parsed from the packet. Userspace then extracts its
[all …]
|
| D | secid.rst | 9 The secid member in the flow structure is used in LSMs (e.g. SELinux) to indicate
10 the label of the flow. This label of the flow is currently used in selecting
13 If this is an outbound flow, the label is derived from the socket, if any, or
14 the incoming packet this flow is being generated as a response to (e.g. tcp
19 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
51 both directions of the flow to land on the same Rx queue (and CPU). The
143 RX flow hash indirection table for eth0 with 13 RX ring(s):
149 RX flow hash indirection table for eth0 with 13 RX ring(s):
157 # ethtool -N eth0 flow-type tcp6 dst-port 22 context 1
188 flow hash over the packet’s addresses or ports (2-tuple or 4-tuple hash
190 associated flow of the packet. The hash is either provided by hardware
195 packet’s flow.
[all …]
|
| D | nf_flowtable.rst | 15 Once the first packet of the flow successfully goes through the IP forwarding
16 path, from the second packet on, you might decide to offload the flow to the
18 action that allows you to specify when to add a flow to the flowtable.
32 The 'flow add' action allows you to populate the flowtable, the user selectively
60 |-----| | 'flow offload' rule |
78 release the flow gracefully. Packets that exceed the MTU are also passed up to
93 ip protocol tcp flow add @f
105 The 'flow offload' action from the forward chain 'y' adds an entry to the
107 flow is offloaded, you will observe that the counter rule in the example above
200 a chance to offload the flow to the network device.
[all …]
|
| D | nf_conntrack-sysctl.rst | 14 Enable connection tracking flow accounting. 64-bit byte and packet
15 counters per flow are added.
33 Number of currently allocated flow entries.
164 Enable connection tracking flow timestamping.
224 TCP connections may be offloaded from nf conntrack to nf flow table.
231 UDP connections may be offloaded from nf conntrack to nf flow table.
|
| D | iso15765-2.rst | 59 Flow Control (FC) frame, which provides the maximum supported size of a macro
64 confirmation from the receiver which should then send another Flow Control
201 * ``CAN_ISOTP_CF_BROADCAST``: use 1-to-N transmission without flow control
205 * ``CAN_ISOTP_DYN_FC_PARMS``: enable dynamic update of flow control
223 Flow Control options
226 Flow Control (FC) options can be passed using the ``CAN_ISOTP_RECV_FC`` optname
244 * ``bs``: blocksize provided in flow control frames.
246 * ``stmin``: minimum separation time provided in flow control frames; can
253 * ``wftmax``: maximum number of wait frames provided in flow control frames.
291 flow control frames:
[all …]
|
| D | devmem.rst | 32 The flow involving host copies is suboptimal, especially for bulk data transfers,
79 Header split, flow steering, & RSS are required features for devmem TCP.
84 Flow steering & RSS are used to ensure that only flows targeting devmem land on
87 Enable header split & flow steering::
93 # enable flow steering
141 The socket must be flow steered to the dmabuf bound RX queue::
143 ethtool -N eth1 flow-type tcp4 ... queue 15
|
| /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/hwmon/ |
| D | aquacomputer_d5next.rst | 14 * Aquacomputer High Flow Next sensor
19 * Aquacomputer High Flow USB flow meter
20 * Aquacomputer MPS Flow devices
31 virtual temperature sensors, as well as two flow sensors. The fans expose their
48 The Octo exposes four physical and sixteen virtual temperature sensors, a flow sensor
50 and current. Flow sensor pulses are also available.
52 The Quadro exposes four physical and sixteen virtual temperature sensors, a flow
54 voltage and current. Flow sensor pulses are also available.
59 The High Flow Next exposes +5V voltages, water quality, conductivity and flow readings.
65 filled with coolant. Pump RPM and flow can be set to enhance on-device calculations,
[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/netlink/specs/ |
| D | ovs_flow.yaml | 9 OVS flow configuration over generic netlink.
25 name: ovs-flow-stats
297 the fields in a flow will be used as part of the hash. Each datapath is free to use its
360 doc: Flow is in the reply direction.
376 name: flow-attrs
377 enum-name: ovs-flow-attr
378 name-prefix: ovs-flow-attr-
385 Nested attributes specifying the flow key. Always present in
401 struct: ovs-flow-stats
403 Statistics for this flow. Present in notifications if the stats would
[all …]
|
| /Documentation/devicetree/bindings/serial/ |
| D | st,stm32-uart.yaml | 34 st,hw-flow-ctrl:
35 description: enable hardware flow control (deprecated)
51 # or 'st,hw-flow-ctrl' (deprecated) for making use of any gpio pins for flow
55 # 'st,hw-flow-ctrl' (deprecated) properties cannot co-exist in a design.
85 - st,hw-flow-ctrl
|
| D | milbeaut-uart.txt | 11 - auto-flow-control: flow control enable.
20 auto-flow-control;
|
| D | socionext,uniphier-uart.yaml | 28 auto-flow-control:
29 description: enable automatic flow control support.
|
| D | st,asc.yaml | 28 st,hw-flow-ctrl:
29 description: When set, enable hardware flow control.
|
| /Documentation/networking/device_drivers/ethernet/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 | ice.rst | 67 Software-generated layer two frames, like IEEE 802.3x (link flow control), IEEE
68 802.1Qbb (priority based flow-control), and others of this type, are not
190 Intel(R) Ethernet Flow Director
192 The Intel Ethernet Flow Director performs the following tasks:
195 - Enables tight control on routing a flow in the platform
196 - Matches flows and CPU cores for flow affinity
198 NOTE: This driver supports the following flow types:
209 Each flow type supports valid combinations of IP addresses (source or
216 L3 and L4 flow types are supported for user-defined flexible filters. For a
217 given flow type, you must clear all Intel Ethernet Flow Director filters before
[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/devicetree/bindings/hsi/ |
| D | client-devices.txt | 15 - hsi-flow: RX flow type ("synchronized" or "pipeline")
38 hsi-flow = "synchronized";
|
| /Documentation/networking/devlink/ |
| D | mlx5.rst | 49 - Controls the flow steering mode of the driver
51 * ``dmfs`` Device managed flow steering. In DMFS mode, the HW
53 * ``smfs`` Software managed flow steering. In SMFS mode, the HW
224 It follows fatal errors indications by CR-space dump and recover flow.
227 The recover function runs recover flow which reloads the driver and triggers fw
234 - Run fw recover flow manually::
271 number of packets that completed RX flow
272 steering but were discarded due to a mismatch in flow table.
275 failure (at any point in steering flow).
278 failure (at any point in steering flow owned by the VNIC, including the FDB
|
| /Documentation/networking/device_drivers/ethernet/aquantia/ |
| D | atlantic.rst | 256 RX flow rules (ntuple filters)
269 To enable or disable the RX flow rules::
292 …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…
297 For ``flow-type ip4|udp4|tcp4|sctp4|ip6|udp6|tcp6|sctp6`` you must set the loc
299 For ``flow-type ip4|udp4|tcp4|sctp4|ip6|udp6|tcp6|sctp6`` you can set 8 rules
306 …sudo ethtool -N <ethX> flow-type tcp6 src-ip 2001:db8:0:f101::1 dst-ip 2001:db8:0:f101::2 action 1…
307 …sudo ethtool -N <ethX> flow-type ip6 src-ip 2001:db8:0:f101::2 dst-ip 2001:db8:0:f101::5 action -1…
311 …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 …
312 …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 …
313 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/net/nfc/ |
| D | marvell,nci.yaml | 54 flow-control:
74 flow-control: false
90 flow-control: false
168 flow-control;
|
| /Documentation/devicetree/bindings/soc/tegra/ |
| D | nvidia,tegra20-flowctrl.yaml | 7 title: NVIDIA Tegra Flow Controller
38 flow-controller@60007000 {
|
| /Documentation/devicetree/bindings/crypto/ |
| D | amlogic,gxl-crypto.yaml | 22 - description: Interrupt for flow 0
23 - description: Interrupt for flow 1
|
123456789