| /f-stack/dpdk/doc/guides/sample_app_ug/ |
| H A D | intro.rst | 36 enabled cores. This application doesn't do any packet forwarding but it is a
41 basic packet forwarding with DPDK. This allows you to test if your network
44 * :doc:`Network Layer 2 forwarding<l2_forward_real_virtual>`: The Network Layer 2
45 forwarding, or ``l2fwd`` application does forwarding based on Ethernet MAC
48 * :doc:`Network Layer 2 forwarding<l2_forward_event>`: The Network Layer 2
49 forwarding, or ``l2fwd-event`` application does forwarding based on Ethernet MAC
53 * :doc:`Network Layer 3 forwarding<l3_forward>`: The Network Layer3
54 forwarding, or ``l3fwd`` application does forwarding based on Internet
57 * :doc:`Network Layer 3 forwarding Graph<l3_forward_graph>`: The Network Layer3
58 forwarding Graph, or ``l3fwd_graph`` application does forwarding based on IPv4
[all …]
|
| H A D | ntb.rst | 11 This sample supports 4 types of packet forwarding mode.
53 Set the packet forwarding mode as ``file-trans``, ``txonly``,
88 file-trans forwarding mode first.
92 * ``set fwd file-trans/rxonly/txonly/iofwd``: Set packet forwarding
|
| H A D | l3_forward.rst | 9 The application performs L3 forwarding.
15 to implement packet forwarding using poll or event mode PMDs for packet I/O.
19 packet can be Rx/Tx from/to eventdev instead of port directly and forwarding
33 When the selected lookup method is LPM based, an LPM object is used to emulate the forwarding stage…
40 In the sample application, hash-based forwarding supports IPv4 and IPv6. LPM-based forwarding suppo…
296 For each input packet, the packet forwarding operation is done by the l3fwd_simple_forward()
298 …simple_forward() function provides the basic functionality for both IPv4 and IPv6 packet forwarding
300 and the packet forwarding decision (that is, the identification of the output interface for the pac…
369 For each input packet, the packet forwarding operation is done by the l3fwd_simple_forward() functi…
370 but the packet forwarding decision (that is, the identification of the output interface for the pac…
[all …]
|
| H A D | l3_forward_graph.rst | 8 using the DPDK Graph framework. The application performs L3 forwarding using
16 implement packet forwarding.
21 Run-time path is main thing that differs from L3 forwarding sample application.
22 Difference is that forwarding logic starting from Rx, followed by LPM lookup,
33 In the sample application, only IPv4 forwarding is supported as of now.
77 To enable L3 forwarding between two ports, assuming that both ports are in the same socket, using t…
266 lock-less mechanisms(RCU, etc) to add run-time forwarding data like route and
267 rewrite data, forwarding data is added before packet processing loop is
300 forwarding data is updated with nodes, worker lcores will be launched with graph
|
| H A D | ip_frag.rst | 9 The application does L3 forwarding with IPv4 and IPv6 packet fragmentation.
22 * The second difference is that the forwarding decision is taken
33 Before forwarding, the input IP packet is fragmented to fit into the "standard" Ethernet* v2 MTU (1…
47 For each input packet, the packet forwarding decision
|
| H A D | skeleton.rst | 8 forwarding application.
10 It is intended as a demonstration of the basic components of a DPDK forwarding
11 application. For more detailed implementations see the L2 and L3 forwarding
211 printf("\nCore %u forwarding packets. [Ctrl+C to quit]\n",
289 The forwarding loop can be interrupted and the application closed using
|
| H A D | ip_reassembly.rst | 8 The application performs L3 forwarding with reassembly for fragmented IPv4 and IPv6 packets.
13 The application demonstrates the use of the DPDK libraries to implement packet forwarding
17 it reassembles fragmented IPv4 and IPv6 packets before forwarding.
22 * The first difference is that the forwarding decision is taken based on information read from th…
195 For each input packet, the packet forwarding operation is done by the l3fwd_simple_forward() functi…
200 Then l3fwd_simple_forward() continues with the code for the packet forwarding decision
|
| H A D | l3_forward_access_ctrl.rst | 16 and packet L3 forwarding.
19 * Route information rules, which are used for L3 forwarding
29 For example, the original L3 forwarding application uses either LPM or
30 an exact match algorithm to perform forwarding port lookup,
85 …It can be the forwarding port number if the rule is a route table entry or it can be a pointer to …
138 that indicates the forwarding port number.
269 To enable L3 forwarding between two ports, assuming that both ports are in the same socket, using t…
307 The following sections describe aspects that are specific to L3 forwarding with access control.
319 while route rules save the forwarding port number.
|
| H A D | rxtx_callbacks.rst | 7 The RX/TX Callbacks sample application is a packet forwarding application that
49 The ``rxtx_callbacks`` application is mainly a simple forwarding application
51 details of the forwarding part of the application.
|
| H A D | l2_forward_cat.rst | 8 a forwarding application. It has been extended to make use of CAT via extended
11 It is intended as a demonstration of the basic components of a DPDK forwarding
13 For more detailed implementations see the L2 and L3 forwarding
|
| H A D | keep_alive.rst | 36 of the L2 forwarding application.
123 the same paths as the L2 forwarding application. The only
|
| H A D | ipv4_multicast.rst | 14 The application demonstrates the use of zero-copy buffers for packet forwarding.
21 * The forwarding decision is taken based on information read from the input packet's IPv4 header.
142 All forwarding is done inside the mcast_forward() function.
180 This is done to determine which forwarding algorithm to use.
|
| H A D | vhost.rst | 22 default forwarding mode (io forward), those packets will be put into
83 Then start testpmd for packet forwarding testing.
121 - 2 means hardware mode packet forwarding between guests, it allows packets
|
| H A D | flow_classify.rst | 8 of a forwarding application.
10 It is intended as a demonstration of the basic components of a DPDK forwarding
443 printf("\nCore %u forwarding packets. \n",
543 The forwarding loop can be interrupted and the application closed using
|
| /f-stack/dpdk/doc/guides/testpmd_app_ug/ |
| H A D | run_app.rst | 36 immediately enters forwarding mode.
44 Start forwarding on initialization.
48 Start forwarding, after sending a burst of packets first.
61 Set the number of forwarding cores,
67 Set the number of forwarding ports,
82 Set the forwarding ports based on the user input used by the packet forwarding test.
241 Set the forwarding mode where ``mode`` is one of the following::
382 and ``flowgen`` forwarding modes.
476 for buffering packets. Only available with the noisy forwarding mode.
482 Only available with the noisy forwarding mode. The default value is 0.
[all …]
|
| H A D | intro.rst | 9 The ``testpmd`` application can be used to test the DPDK in a packet forwarding mode
|
| H A D | testpmd_funcs.rst | 282 * ``cores``: List of forwarding cores.
284 * ``fwd``: Packet forwarding configuration.
301 nb forwarding cores=2 - nb forwarding ports=1
311 Set the packet forwarding mode::
329 * ``macswap``: MAC swap forwarding mode.
361 Set rxonly packet forwarding mode
397 Clear the forwarding engines statistics::
714 Set the forwarding cores hexadecimal mask::
727 Set the forwarding ports hexadecimal mask::
869 Set the list of forwarding cores::
[all …]
|
| /f-stack/app/nginx-1.16.1/conf/ |
| H A D | f-stack.conf | 164 net.inet6.ip6.forwarding=0
190 net.inet.ip.forwarding=0
|
| /f-stack/dpdk/doc/guides/nics/ |
| H A D | kni.rst | 10 any forwarding application can use PMD interface for KNI.
41 When testpmd forwarding starts, any packets sent to ``kni0`` interface
143 * Start forwarding with tx_first:
149 * Quit and check forwarding stats:
|
| H A D | szedata2.rst | 138 Start automatic packet forwarding
139 io packet forwarding - CRC stripping disabled - packets/burst=32
140 nb forwarding cores=2 - nb forwarding ports=1
|
| H A D | nfb.rst | 141 Start automatic packet forwarding
142 io packet forwarding - CRC stripping disabled - packets/burst=32
143 nb forwarding cores=2 - nb forwarding ports=1
|
| H A D | octeontx2.rst | 85 No commandline core given, start packet forwarding
86 …io packet forwarding - ports=1 - cores=1 - streams=1 - NUMA support enabled, MP allocation mode: n…
90 io packet forwarding packets/burst=32
91 nb forwarding cores=1 - nb forwarding ports=1
|
| H A D | softnic.rst | 131 Set softnic packet forwarding mode
161 * Start forwarding
166 …softnic packet forwarding - ports=1 - cores=1 - streams=1 - NUMA support enabled, MP over anonymou…
170 softnic packet forwarding packets/burst=32
171 nb forwarding cores=1 - nb forwarding ports=1
|
| H A D | pfe.rst | 31 PFE is a hardware programmable packet forwarding engine to provide
80 to send and receive packets through packet forwarding engine. Both network
|
| /f-stack/freebsd/netipsec/ |
| H A D | ipsec_output.c | 296 ipsec4_common_output(struct mbuf *m, struct inpcb *inp, int forwarding) in ipsec4_common_output() argument
302 sp = ipsec4_checkpolicy(m, inp, &error, !forwarding); in ipsec4_common_output()
320 if (!forwarding) { in ipsec4_common_output()
611 ipsec6_common_output(struct mbuf *m, struct inpcb *inp, int forwarding) in ipsec6_common_output() argument
617 sp = ipsec6_checkpolicy(m, inp, &error, !forwarding); in ipsec6_common_output()
627 if (!forwarding) { in ipsec6_common_output()
|