Home
last modified time | relevance | path

Searched refs:IPv4 (Results 1 – 25 of 94) sorted by relevance

1234

/dpdk/doc/guides/prog_guide/
H A Dgeneric_receive_offload_lib.rst21 example, TCP/IPv4 GRO processes TCP/IPv4 packets.
31 6864 to process the IPv4 ID field.
33 Currently, the GRO library provides GRO supports for TCP/IPv4 and UDP/IPv4
35 inner TCP/IPv4 or UDP/IPv4 packet.
141 TCP/IPv4 GRO
161 - IPv4 ID. The IPv4 ID fields of the packets, whose DF bit is 0, should
168 VxLAN packets with an outer IPv4 header and inner TCP/IPv4 packet, is
180 - outer IPv4 ID. The IPv4 ID fields of the packets, whose DF bit in the
181 outer IPv4 header is 0, should be increased by 1.
185 - inner IPv4 ID. The IPv4 ID fields of the packets, whose DF bit in the
[all …]
H A Dgeneric_segmentation_offload_lib.rst44 #. Currently, the GSO library supports the following IPv4 packet types:
146 TCP/IPv4 GSO
148 TCP/IPv4 GSO supports segmentation of suitably large TCP/IPv4 packets, which
151 UDP/IPv4 GSO
153 UDP/IPv4 GSO supports segmentation of suitably large UDP/IPv4 packets, which
160 VXLAN IPv4 GSO
163 which contain an outer IPv4 header, inner TCP/IPv4 or UDP/IPv4 headers, and
166 GRE TCP/IPv4 GSO
169 an outer IPv4 header, inner TCP/IPv4 headers, and an optional VLAN tag.
198 wants to segment TCP/IPv4 packets, it should set gso_types to
[all …]
H A Dflow_classify_lib.rst10 The initial implementation supports counting of IPv4 5-tuple packets which match
276 The library currently supports three IPv4 5-tuple flow patterns, for UDP, TCP
281 /* Pattern for IPv4 5-tuple UDP filter */
289 /* Pattern for IPv4 5-tuple TCP filter */
297 /* Pattern for IPv4 5-tuple SCTP filter */
306 IPv4 5-tuple pattern, attributes and actions and returns the 5-tuple data in the
383 /** IPv4 5-tuple data */
411 /** count of packets that match IPv4 5tuple pattern */
413 /** IPv4 5tuple data */
H A Dpacket_classif_access_ctrl.rst78 For example, to define classification for the following IPv4 5-tuple structure:
104 /* next input field (IPv4 source address) - 4 consecutive bytes. */
113 /* next input field (IPv4 destination address) - 4 consecutive bytes. */
143 A typical example of such an IPv4 5-tuple rule is a follows:
249 /* next input field (IPv4 source address) - 4 consecutive bytes. */
258 /* next input field (IPv4 destination address) - 4 consecutive bytes. */
280 A typical example of such an IPv4 4-tuple rule is as follows:
409 The following example demonstrates IPv4, 5-tuple classification for rules defined above
443 /* destination IPv4 */
457 /* destination IPv4 */
[all …]
H A Dip_fragment_reassembly_lib.rst7 The IP Fragmentation and Reassembly Library implements IPv4 and IPv6 packet fragmentation and reass…
24 Note that for IPv4, header checksum is not recalculated and is set to zero.
78 #. Search the Fragment Table for entry with packet's <IPv4 Source Address, IPv4 Destination Addres…
/dpdk/examples/pipeline/examples/
H A Dvarbit.spec5 ; is Ethernet/IPv4/UDP, with the IPv4 header containing between 0 and 40 bytes of options. To locate
6 ; the start of the UDP header, the size of the IPv4 header needs to be detected first, which is done
7 ; by reading the first byte of the IPv4 header that carries the 4-bit Internet Header Length (IHL)
9 ; pointer within the input packet buffer. Once the size of the IPv4 header options is known for the
10 ; current packet, the IPv4 header is extracted by using the two-argument "extract" instruction. Then
71 // Extract the variable size IPv4 header with up to 10 options.
89 // Emit the Ethernet, IPv4 and UDP headers.
H A Dvxlan.spec86 // Ethernet (14) | IPv4 (total_len)
89 // Ethernet (14) | IPv4 (20) | UDP (8) | VXLAN (8) | Input frame | Ethernet FCS (4)
94 // Assumption: When read from the table, the outer IPv4 and UDP headers contain
97 // - The outer IPv4 header (20 bytes);
108 // Once the total length of the inner IPv4 packet (h.ipv4.total_len) is known,
109 // the outer IPv4 and UDP headers are updated as follows:
123 //Set the outer IPv4 header.
H A Dregisters.spec5 ; On every input packet (Ethernet/IPv4), the "pkt_counters" register at location indexed by
6 ; the IPv4 header "Source Address" field is incremented, while the same location in the
7 ; "byte_counters" array accumulates the value of the IPv4 header "Total Length" field.
H A Dmeter.spec5 ; Every input packet (Ethernet/IPv4) is metered by the meter at the location indexed by the IPv4
/dpdk/doc/guides/sample_app_ug/
H A Dipv4_multicast.rst4 IPv4 Multicast Sample Application
7 The IPv4 Multicast application is a simple example of packet processing
19 * The IPv4 Multicast sample application makes use of indirect buffers.
24 The lookup table is composed of pairs of destination IPv4 address (the FBK)
25 and a port mask associated with that IPv4 address.
31 If using non-consecutive ports, use the destination IPv4 address accordingly.
37 it looks only at the IPv4 destination address for any given packet.
64 NUMA support is not provided in the IPv4 Multicast sample application.
96 The IPv4 Multicast sample application uses three memory pools.
123 … the Ethernet* header is removed from the packet and the IPv4 address is extracted from the IPv4 h…
[all …]
H A Dtest_pipeline.rst108 …| | [destination IPv4 address, 4 bytes of…
131 …| | [destination IPv4 address, 12 bytes o…
154 …| | [destination IPv4 address, 28 bytes o…
161 …| 9 | lpm | Longest Prefix Match (LPM) IPv4 table. | In t…
182 … | At run time, core A is storing the IPv4 destination |
192 … | | IPv4 source = ANY, …
194 … | | IPv4 destination = 0.0.0…
207 … | | IPv4 source = ANY, …
209 … | | IPv4 destination = 0.128…
231 The profile for input traffic is TCP/IPv4 packets with:
H A Dip_reassembly.rst8 The application performs L3 forwarding with reassembly for fragmented IPv4 and IPv6 packets.
14 with reassembly for IPv4 and IPv6 fragmented packets.
17 it reassembles fragmented IPv4 and IPv6 packets before forwarding.
26 The Longest Prefix Match (LPM for IPv4, LPM6 for IPv6) table is used to store/lookup an outgoing po…
27 associated with that IPv4 address. Any unmatched packets are forwarded to the originating port.
119 For example, for the fragmented input IPv4 packet with destination address: 100.10.1.1,
120 a reassembled IPv4 packet be sent out from port #0 to the destination address 100.10.1.1
130 IPv4 Fragment Table Initialization
165 If the packet is an IPv4 or IPv6 fragment, then it calls rte_ipv4_reassemble_packet() for IPv4 pack…
H A Dip_frag.rst7 The IPv4 Fragmentation application is a simple example of packet processing
9 The application does L3 forwarding with IPv4 and IPv6 packet fragmentation.
28 The Longest Prefix Match (LPM for IPv4, LPM6 for IPv6) table is used to store/lookup an outgoing po…
116 For example, for the input IPv4 packet with destination address: 100.10.1.1 and packet length 9198 …
117 seven IPv4 packets will be sent out from port #0 to the destination address 100.10.1.1:
H A Dl3_forward_access_ctrl.rst34 Classification for both IPv4 and IPv6 packets is supported in this application.
41 The application implements packet classification for the IPv4/IPv6 5-tuple syntax specifically.
47 …: Each is either a 32-bit field (for IPv4), or a set of 4 32-bit fields (for IPv6) represented by …
115 * A typical IPv4 ACL rule line should have a format as shown below:
122 A typical IPv4 ACL rule
125 IPv4 addresses are specified in CIDR format as specified in RFC 4632.
206 Note that application maintains a separate AC contexts for IPv4 and IPv6 rules.
251 * --rule_ipv4 FILENAME: Specifies the IPv4 ACL and route rules file
294 * The --rule_ipv4 option specifies the reading of IPv4 rules sets from the rule_ipv4.db file.
325 For each supported AC rule format (IPv4 5-tuple, IPv6 6-tuple) application creates a separate conte…
[all …]
H A Dl3_forward.rst36 an LPM or FIB object is used to emulate the forwarding stage for IPv4 packets.
48 both IPv4 and IPv6.
49 LPM-based forwarding supports IPv4 only.
50 During the initialization phase route rules for IPv4 and IPv6 are read from rule files.
168 * The -rule_ipv4 option specifies the reading of IPv4 rules sets from the rule_ipv4.cfg file
259 * A typical IPv4 LPM/FIB rule line should have a format as shown below:
263 * A typical IPv4 EM rule line should have a format as shown below:
267 IPv4 addresses are specified in CIDR format as specified in RFC 4632.
329 The abridged code snippet below shows the FIB initialization for IPv4,
342 The l3fwd_simple_forward() function provides the basic functionality for both IPv4 and IPv6 packet …
[all …]
/dpdk/drivers/net/tap/
H A Dtap_bpf_program.c22 #define IPv4(a, b, c, d) ((__u32)(((a) & 0xff) << 24) | \ macro
160 .src_addr = IPv4(*(src_dst_addr + 0), in rss_l3_l4()
164 .dst_addr = IPv4(*(src_dst_addr + 4), in rss_l3_l4()
/dpdk/examples/ip_pipeline/examples/
H A Dflow_crypto.cli12 ; Input packet: Ethernet/IPv4
19 ; 3 IPv4 header 280 20
H A Dfirewall.cli16 ; Input packet: Ethernet/IPv4
23 ; 3 IPv4 header 270 20
H A Dflow.cli16 ; Input packet: Ethernet/IPv4
23 ; 3 IPv4 header 270 20
H A Droute.cli16 ; Input packet: Ethernet/IPv4
23 ; 3 IPv4 header 270 20
/dpdk/doc/api/
H A Ddoxy-api-index.md135 [LPM IPv4 route] (@ref rte_lpm.h),
137 [RIB IPv4] (@ref rte_rib.h),
139 [FIB IPv4] (@ref rte_fib.h),
177 [lpm IPv4] (@ref rte_table_lpm.h),
/dpdk/examples/l3fwd/
H A Dlpm_default_v4.cfg1 # Copy of hard-coded IPv4 FWD table for L3FWD LPM
H A Dem_default_v4.cfg1 #Copy of hard-coded IPv4 FWD table for L3FWD EM
/dpdk/drivers/net/ixgbe/
H A Dixgbe_ipsec.c161 } else if (ic_session->dst_ip.type == IPv4) in ixgbe_crypto_add_sa()
162 priv->rx_ip_tbl[ip_index].ip.type = IPv4; in ixgbe_crypto_add_sa()
169 if (priv->rx_ip_tbl[ip_index].ip.type == IPv4) { in ixgbe_crypto_add_sa()
702 ic_session->src_ip.type = IPv4; in ixgbe_crypto_add_ingress_sa_from_flow()
703 ic_session->dst_ip.type = IPv4; in ixgbe_crypto_add_ingress_sa_from_flow()
/dpdk/drivers/net/txgbe/
H A Dtxgbe_ipsec.c140 } else if (ic_session->dst_ip.type == IPv4) { in txgbe_crypto_add_sa()
141 priv->rx_ip_tbl[ip_index].ip.type = IPv4; in txgbe_crypto_add_sa()
148 if (priv->rx_ip_tbl[ip_index].ip.type == IPv4) { in txgbe_crypto_add_sa()
678 ic_session->src_ip.type = IPv4; in txgbe_crypto_add_ingress_sa_from_flow()
679 ic_session->dst_ip.type = IPv4; in txgbe_crypto_add_ingress_sa_from_flow()

1234