| /Documentation/networking/devlink/ |
| D | prestera.rst | 27 - Traps ARP broadcast packets (both requests/responses)
30 - Traps IS-IS packets
33 - Traps OSPF packets
36 - Traps IPv4 packets with broadcast DA Mac address
42 - Traps LACP packets
45 - Traps LLDP packets
48 - Traps multicast packets
51 - Traps VRRP packets
54 - Traps DHCP packets
57 - Traps (exception) packets that exceeded port's MTU
[all …]
|
| D | devlink-trap.rst | 11 as bridging and routing must also be able to send specific packets to the
16 Without processing such packets, the bridge module could never populate its
22 error datagram. Without letting the kernel route such packets itself, utilities
25 The fundamental ability of sending certain packets to the kernel for processing
32 supported packet traps with ``devlink`` and report trapped packets to
35 Upon receiving trapped packets, ``devlink`` will perform a per-trap packets and
91 * ``drop``: Trapped packets were dropped by the underlying device. Packets
94 * ``exception``: Trapped packets were not forwarded as intended by the
96 entry) and trapped to the control plane for resolution. Packets are
100 * ``control``: Trapped packets were trapped by the device because these are
[all …]
|
| /Documentation/networking/device_drivers/ethernet/mellanox/mlx5/ |
| D | counters.rst | 145 - The number of packets received on ring i.
153 - The number of packets transmitted on ring i.
173 - The number of TSO packets transmitted on ring i [#accel]_.
181 - The number of TSO packets which are indicated to be carry internal
191 - Number of received packets processed using hardware-accelerated GRO. The
192 number of hardware GRO offloaded packets received on ring i. Only true GRO
193 packets are counted: only packets that are in an SKB with a GRO count > 1.
199 packets are counted: only packets that are in an SKB with a GRO count > 1.
208 - Number of receive packets using hardware-accelerated GRO that have large
213 - Number of header only packets in header/data split mode [#accel]_.
[all …]
|
| /Documentation/netlink/specs/ |
| D | netdev.yaml | 68 HW timestamping egress packets is supported by the driver.
317 name: rx-packets
319 Number of wire packets successfully received and passed to the stack.
321 of the stack, so packets consumed by XDP are still counted here.
326 doc: Successfully received bytes, see `rx-packets`.
329 name: tx-packets
331 Number of wire packets successfully sent. Packet is considered to be
337 doc: Successfully sent bytes, see `tx-packets`.
349 Number of all packets which entered the device, but never left it,
350 including but not limited to: packets dropped due to lack of buffer
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-net-statistics | 14 Indicates the number of multicast packets received by this
31 Indicates the number of compressed packets received by this
40 Indicates the number of packets received with a CRC (FCS) error
49 Indicates the number of packets received by the network device
95 Indicates the number of received packets that have been missed
104 Indicates the number of received packets that were dropped on
112 Indicates the number of received packets that are oversized
122 Indicates the total number of good packets received by this
130 Indicates the number of packets that have been aborted
143 transmitted packets or all packets that have been queued for
[all …]
|
| /Documentation/networking/ |
| D | seg6-sysctl.rst | 12 Accept or drop SR-enabled IPv6 packets on this interface.
14 Relevant packets are those with SRH present and DA = local.
20 Define HMAC policy for ingress SR-enabled packets on this interface.
23 * 0 - Accept SR packets without HMAC, validate SR packets with HMAC
24 * 1 - Drop SR packets without HMAC, validate SR packets with HMAC
|
| D | nf_conntrack-sysctl.rst | 28 Verify checksum of incoming packets. Packets with bad checksums are
29 in INVALID state. If this is enabled, such packets will not be
54 purpose, the fragment handler will toss packets until
85 - 1 - log ICMP packets
86 - 6 - log TCP packets
87 - 17 - log UDP packets
88 - 33 - log DCCP packets
89 - 41 - log ICMPv6 packets
90 - 136 - log UDPLITE packets
91 - 255 - log packets of any protocol
[all …]
|
| D | scaling.rst | 28 (multi-queue). On reception, a NIC can send different packets to different
29 queues to distribute processing among CPUs. The NIC distributes packets by
31 of logical flows. Packets for each flow are steered to a separate receive
62 Some advanced NICs allow steering packets to queues based on
63 programmable filters. For example, webserver bound TCP port 80 packets
92 this to notify a CPU when new packets arrive on the given queue. The
198 RPS may enqueue packets for processing. For each received packet,
203 packets have been queued to their backlog queue. The IPI wakes backlog
204 processing on the remote CPU, and any queued packets are then processed
219 (the default), in which case packets are processed on the interrupting
[all …]
|
| D | tls-offload.rst | 25 on a packet by packet basis, provided the packets arrive in order.
47 Instead packets reach a device driver, the driver will mark the packets
56 :c:type:`struct sk_buff <sk_buff>`. The packets reach the TCP stack and
97 the received or transmitted packets. Driver uses the ``sk`` parameter
149 Record reassembly is not necessary for TLS offload. If the packets arrive
162 For segments passed in order, the driver marks the packets with
164 packets requiring HW offload, see the :ref:`5tuple_problems` section)
359 Packets may be redirected or rerouted by the stack to a different
381 packets should not be modified "in place". Splitting segments to handle partial
388 decryption and authentication errors, packets with errors must simply not
[all …]
|
| D | ppp_generic.rst | 79 packets.
153 transmit packets for the PPP unit (network interface device) plus a
154 queue of transmit packets for each attached channel. Normally the
156 exceptions are when pppd sends packets by writing to /dev/ppp, and
163 Transmit packets are dequeued from the PPP unit transmit queue and
166 point the packets can no longer be reordered, as the decompression
167 algorithms rely on receiving compressed packets in the same order that
189 layer will tend to fragment large packets across all the channels,
190 thus reducing latency, while under heavy load, packets will tend to be
281 be used for PPP negotiation but not for the transfer of data packets.
[all …]
|
| D | udplite.rst | 10 (video, VoIP) over wireless networks, as partly damaged packets can still be
81 all packets which have a coverage _less_ than this value. For example, if
83 packets with a minimum coverage of 20 are admitted::
135 partially covered packets are dropped and an error is logged.
140 All packets arriving with a coverage value less than the specified
154 is meaningless (as in TCP). Packets with a zero checksum field are
160 of UDP-Lite packets is determined by the size of the send buffer. The
168 split the payload into several individual packets, filling up the
173 UDP-Lite packet is split into several IP packets, of which only the
182 UDP-Lite will ship the 1536 bytes in two separate packets::
[all …]
|
| D | representors.rst | 27 When the system boots, and before any offload is configured, all packets from
69 fast-path rules in the virtual switch. Packets transmitted on the
70 representor netdevice should be delivered to the representee; packets
76 bridge) to forward packets between representees and the rest of the network.
82 on a VF representor applies in software to packets received on that representor
83 netdevice, while in hardware offload it would apply to packets transmitted by
131 translation between block DMA requests and network packets, so that only
132 network packets pass through the virtual port onto the switch. The network
186 Any TC rule on a representor applies (in software TC) to packets received by
189 hardware, applying it to packets transmitted by the representee.
[all …]
|
| D | ipvs-sysctl.rst | 73 If it is enabled, forward packets to the original destination
121 The drop_packet defense is designed to drop 1/rate packets
123 drop all the incoming packets.
157 packets when its destination server is not available. It may
190 If set, ipvs will set the ipvs_property on all packets which are of
193 packets that have been tunneled to the ipvs host (i.e. to prevent
201 for VS/NAT when the load balancer receives packets from real
208 By default, reject with FRAG_NEEDED all DF packets that exceed
210 the flag can be disabled to fragment such packets.
226 of incoming packets that a connection needs to receive before
[all …]
|
| D | napi.rst | 31 handler. The method will typically free Tx packets that have been
32 transmitted and process newly received packets.
63 called to process the events/packets. The method takes a ``budget``
65 packets but should only process up to ``budget`` number of
66 Rx packets. Rx processing is usually much more expensive.
69 packets driver can process in a single poll. Rx specific APIs like page
77 skb Tx completions and no Rx or XDP packets.
85 If event processing has been completed (all outstanding packets
189 the hardware interrupts as soon as all packets are processed.
200 Busy polling allows a user process to check for incoming packets before
[all …]
|
| D | mpls-sysctl.rst | 42 Default TTL value to use for MPLS packets where it cannot be
51 Control whether packets can be input on this interface.
53 If disabled, packets will be discarded without further
|
| /Documentation/networking/device_drivers/ethernet/altera/ |
| D | altera_tse.rst | 164 received. This count does not include any error packets such as CRC errors,
194 a count of the number of packets received containing errors that prevented the
198 is a count of the number of packets that could not be transmitted due to errors.
201 statistic is a count of the number of packets received that were not addressed
205 statistic is a count of the number of packets received that were addressed to
209 statistic is a count of the number of packets received that were addressed to
213 statistic is the number of outbound packets not transmitted even though an
218 statistic counts the number of packets transmitted that were not addressed to
222 statistic counts the number of packets transmitted that were addressed to a
226 statistic counts the number of packets transmitted that were addressed to a
[all …]
|
| /Documentation/admin-guide/blockdev/drbd/ |
| D | figures.rst | 5 Data flows that Relate some functions, and write packets
8 .. kernel-figure:: DRBD-8.3-data-packets.svg
9 :alt: DRBD-8.3-data-packets.svg
12 .. kernel-figure:: DRBD-data-packets.svg
13 :alt: DRBD-data-packets.svg
|
| /Documentation/admin-guide/ |
| D | dell_rbu.rst | 34 using the driver breaks the image in to packets of fixed sizes and the driver
36 maintains a link list of packets for reading them back.
60 of contiguous memory and the BIOS image is scattered in these packets.
63 changed to packets during the driver load time by specifying the load
68 In packet update mode the packet size has to be given before any packets can
74 packets of data arranged back to back. It can be done as follows:
75 The user creates packets header, gets the chunk of the BIOS image and
78 packet, the user needs to create more such packets out of the entire BIOS
79 image file and then arrange all these packets back to back in to one single
87 This method makes sure that all the packets get to the driver in a single operation.
|
| /Documentation/networking/device_drivers/ethernet/microsoft/ |
| D | netvsc.rst | 25 Hyper-V supports receive side scaling. For TCP & UDP, packets can
34 On Azure, fragmented UDP packets have high loss rate with L4
54 like packets and significantly reduces CPU usage under heavy Rx
85 Packets are received into a receive area which is created when device
87 contain one or more packets. The number of receive sections may be changed
90 There is a similar send buffer which is used to aggregate packets
92 bytes, each of section may contain one or more packets. Small
93 packets are usually transmitted via copy to the send buffer. However,
103 stage when packets arrive at a NIC card. The goal is to increase performance
|
| /Documentation/filesystems/nfs/ |
| D | knfsd-stats.rst | 48 packets-arrived
49 Counts how many NFS packets have arrived. More precisely, this
55 effects (such as Large Receive Offload) which can combine packets
85 to but less than the rate of change of the packets-arrived counter.
89 i.e. was not woken to handle any incoming network packets for
108 Note that incoming packets on NFS transports will be dealt with in
116 packets-deferred = packets-arrived - ( sockets-enqueued + threads-woken )
|
| /Documentation/networking/device_drivers/cellular/qualcomm/ |
| D | rmnet.rst | 20 packets with MAP headers to rmnet. Based on the multiplexer id, rmnet
44 packets are standard IP packets.
70 packets are standard IP packets.
123 packets are standard IP packets.
181 Aggregation is multiple MAP packets (can be data or command) delivered to
183 packets and either ACK the MAP command or deliver the IP packet to the
|
| /Documentation/translations/zh_CN/core-api/irq/ |
| D | irq-affinity.rst | 43 6029 packets transmitted, 6027 packets received, 0% packet loss
61 2779 packets transmitted, 2777 packets received, 0% packet loss
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | net_cls.rst | 6 tag network packets with a class identifier (classid).
9 different priorities to packets from different cgroups.
11 actions on such packets.
|
| /Documentation/driver-api/surface_aggregator/ |
| D | internal.rst | 103 Packets section in Packet Transport Layer
106 Packets are the fundamental transmission unit of the SSH protocol. They are
109 Packets to be transmitted by the SSAM core are represented via |ssh_packet|
110 (in contrast, packets received by the core do not have any specific
157 respective packets based on the packet type (major) and number of tries
160 All packets to be transmitted by the transport layer must be submitted to
161 this queue via |ssh_ptl_submit|. Note that this includes control packets
162 sent by the transport layer itself. Internally, data packets can be
163 re-submitted to this queue due to timeouts or NAK packets sent by the EC.
169 packet transport layer. It stores references to packets that have already
[all …]
|
| /Documentation/core-api/irq/ |
| D | irq-affinity.rst | 35 6029 packets transmitted, 6027 packets received, 0% packet loss
54 2779 packets transmitted, 2777 packets received, 0% packet loss
|