Searched full:packets (Results 1 – 25 of 200) sorted by relevance
12345678
| /Documentation/networking/devlink/ |
| 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/ |
| 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 | 29 Verify checksum of incoming packets. Packets with bad checksums are
30 in INVALID state. If this is enabled, such packets will not be
52 purpose, the fragment handler will toss packets until
92 - 1 - log ICMP packets
93 - 6 - log TCP packets
94 - 17 - log UDP packets
95 - 33 - log DCCP packets
96 - 41 - log ICMPv6 packets
97 - 136 - log UDPLITE packets
98 - 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
47 Some advanced NICs allow steering packets to queues based on
48 programmable filters. For example, webserver bound TCP port 80 packets
77 this to notify a CPU when new packets arrive on the given queue. The
141 RPS may enqueue packets for processing. For each received packet,
146 packets have been queued to their backlog queue. The IPI wakes backlog
147 processing on the remote CPU, and any queued packets are then processed
162 (the default), in which case packets are processed on the interrupting
[all …]
|
| D | nf_flowtable.rst | 13 Initial packets follow the classic forwarding path, once the flow enters the
18 Packets that find an entry in the flowtable (ie. flowtable hit) are sent to the
20 path (the visible effect is that you do not see these packets from any of the
30 selectively specify what flows are placed into the flow table. Hence, packets
31 follow the classic forwarding path unless the user explicitly instruct packets
69 The flowtable entry also stores the NAT configuration, so all packets are
70 mangled according to the NAT policy that matches the initial packets that went
89 counter packets 0 bytes 0
103 does not get updated for the packets that are being forwarded through the
|
| 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 | 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.
137 packets when its destination server is not available. It may
170 If set, ipvs will set the ipvs_property on all packets which are of
173 packets that have been tunneled to the ipvs host (i.e. to prevent
181 for VS/NAT when the load balancer receives packets from real
188 By default, reject with FRAG_NEEDED all DF packets that exceed
190 the flag can be disabled to fragment such packets.
206 of incoming packets that a connection needs to receive before
[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 | 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
|
| D | phonet.rst | 16 Phonet packets can be exchanged through various hardware connections
26 Packets format
29 Phonet packets have a common header as follows::
65 Linux Phonet network interfaces support a dedicated link layer packets
67 only send and receive Phonet packets.
73 Note that Phonet interfaces are not allowed to re-order packets, so
99 2^10 object IDs available, and can send and receive packets with any
141 The Phonet Pipe protocol is a simple sequenced packets protocol
|
| D | snmp_counter.rst | 9 All layer 4 packets and ICMP packets will change these counters, but
10 these counters won't be changed by layer 2 packets (such as STP) or
11 ARP packets.
19 The number of packets received by the IP layer. It gets increasing at the
32 The number of packets delivers to the upper layer protocols. E.g. TCP, UDP,
35 socket, all valid IP packets will be delivered.
43 The number of packets sent via IP layer, for both single cast and
44 multicast packets, and would always be updated together with
57 They indicate the number of four kinds of ECN IP packets, please refer
62 These 4 counters calculate how many packets received per ECN
[all …]
|
| D | tcp-thin.rst | 25 In order to reduce application-layer latency when packets are lost,
35 of packets in flight. If there are less than 4 packets in flight,
|
| /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/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/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/ |
| 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 for sending.
92 contain one or more packets. The send buffer is an optimization, the driver
93 will use slower method to handle very large packets or if the send buffer
99 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
43 packets are standard IP packets.
79 Aggregation is multiple MAP packets (can be data or command) delivered to
81 packets and either ACK the MAP command or deliver the IP packet to the
|
| /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/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
|
| /Documentation/devicetree/bindings/net/ |
| D | marvell-armada-370-neta.txt | 28 - bm,pool-long: ID of a pool, that will accept all packets of a size
33 packets of a size lower than given threshold. If not set, the port
34 will use a single 'long' pool for all packets, as defined above.
|
| /Documentation/devicetree/bindings/devfreq/event/ |
| D | exynos-nocp.txt | 5 NoC provides the primitive values to get the performance data. The packets
8 capture packets with header or data on the data request response network,
|
| /Documentation/driver-api/media/drivers/ |
| D | vidtv.rst | 109 How often to send SI packets. Default: 40ms.
112 How often to send PCR packets. Default: 40ms.
115 Attempt to maintain this bit rate by inserting TS null packets, if
140 Code to work with MPEG TS packets, such as TS headers, adaptation
141 fields, PCR packets and NULL packets.
144 This is the PSI generator. PSI packets contain general information
170 packets. These can then be fed into a TS multiplexer and eventually
207 loop to produce TS packets.
208 These packets may be interleaved by the muxer and then delivered
222 #. Inserting PSI and/or PCR packets, if needed.
[all …]
|
12345678