| /dpdk/doc/guides/regexdevs/ |
| H A D | features_overview.rst | 18 PCRE back reference
19 Support PCRE back reference.
21 PCRE back tracking ctrl
22 Support PCRE back tracking ctrl.
|
| /dpdk/doc/guides/regexdevs/features/ |
| H A D | default.ini | 13 PCRE back reference =
14 PCRE back tracking ctrl =
|
| H A D | cn9k.ini | 7 PCRE back reference = Y
|
| /dpdk/doc/guides/sample_app_ug/ |
| H A D | bbdev_app.rst | 6 Loop-back Sample Application using Baseband Device (bbdev)
16 The Baseband device sample application performs a loop-back operation using a
21 packet is compared with the baseband operations output. Then it's looped back to
95 it will print the transmitted along with the looped-back traffic on Rx ports.
|
| H A D | server_node_efd.rst | 92 and the back-end node.
101 * ``-n NUM_NODES:`` Number of back-end nodes that will be used
104 The back-end node (node) has the following command line options::
164 The second process, the back-end node, receives the packets from the shared
|
| H A D | ethtool.rst | 84 application`_. Individual call-back functions handle the detail
|
| H A D | qos_scheduler.rst | 106 * C = RX write-back threshold (the default value is 4)
114 * C = TX write-back threshold (the default value is 0)
|
| H A D | multi_process.rst | 127 and frees the buffer space used by the messages back to the memory pool.
304 The routing used is very simple. All packets received on the first NIC port are transmitted back ou…
306 …iting the packets directly to the network ports; they are not transferred back via the server proc…
|
| /dpdk/doc/guides/prog_guide/ |
| H A D | kernel_nic_interface.rst | 92 The ``lo_mode_fifo`` loopback option will loop back ring enqueue/dequeue
99 The ``lo_mode_fifo_skb`` loopback option will loop back ring enqueue/dequeue
206 callback and locks it back after callback. Also enables asynchronous request to
345 The dequeued mbuf must be freed, so the same pointer is sent back in the free_q FIFO,
346 and next pointers must convert back to virtual address if exists before put in the free_q FIFO.
362 It then puts the mbuf back in the cache.
|
| H A D | poll_mode_drv.rst | 102 … to remove operations that would otherwise be unavoidable, such as ring index wrap back management.
208 …ds this threshold, the network adaptor should be checked to see if it has written back descriptors.
217 …In short, this parameter controls which transmit descriptors are written back to host memory by th…
220 …This ensures that at least 32 descriptors are used before the network adapter writes back the most…
222 …It is important to note that the TX Write-back threshold (TX wthresh) should be set to 0 when tx_r…
248 Many of the drivers do not release the mbuf back to the mempool, or local cache,
272 the application may want to reset back to an initial state
|
| H A D | efd_lib.rst | 17 use storage metadata tables to forward I/O requests to the correct back end
170 to the target back end server for processing. The system designer would
186 is the maximum number of flows served by each back end server of the X
197 rather distributing the flows to a target back end node based on the
|
| /dpdk/drivers/net/ice/ |
| H A D | ice_dcf_parent.c | 62 ice_flow_redirect((struct ice_adapter *)hw->back, &rd); in ice_dcf_update_vsi_ctx()
430 parent_hw->back = parent_adapter; in ice_dcf_init_parent_adapter()
|
| /dpdk/doc/guides/eventdevs/ |
| H A D | cnxk.rst | 107 Force Rx back pressure when same mempool is used across ethernet device
207 event device would cause back pressure to be asserted only on the first
|
| /dpdk/drivers/net/vmxnet3/ |
| H A D | vmxnet3_ethdev.h | 82 void *back; member
|
| /dpdk/drivers/net/e1000/base/ |
| H A D | e1000_vf.h | 232 void *back; member
|
| /dpdk/doc/guides/nics/ |
| H A D | virtio.rst | 21 standard qemu vhost back end and vhost kni back end.
37 vring, make them available to the device, and then notify the host back
52 the virtio PMD generates a warning and fall back to the hard-coded value.
92 This section demonstrates kni vhost back end example setup for Phy-VM Communication.
|
| H A D | pcap_ring.rst | 177 Read only incoming packets from a network interface and write them back to the same network interfa…
278 To create two pseudo-Ethernet ports where all traffic sent to a port is looped back
300 that is, traffic sent to port 0 is read back from port 1 and vice-versa,
|
| /dpdk/examples/ipsec-secgw/ |
| H A D | ep0.cfg | 5 # back-to-back that would forward traffic through an IPsec tunnel. This
|
| H A D | ep1.cfg | 5 # back-to-back that would forward traffic through an IPsec tunnel. This
|
| /dpdk/doc/guides/howto/ |
| H A D | debug_troubleshoot.rst | 218 not release MBUF back to mempool.
362 * Check for event stages if the events are looped back into the same queue.
455 is added in the same process. These can be invoked by timer call-back,
|
| /dpdk/doc/guides/contributing/ |
| H A D | abi_versioning.rst | 152 can still be mapped back to the public symbol name.
379 and differently named symbols. We've then mapped each of those back to the
385 To correct this, we can simply map a function of our choosing back to the public
388 map. So, back in the C file where, immediately after ``rte_acl_create_v22`` is
|
| /dpdk/doc/guides/linux_gsg/ |
| H A D | linux_eal_parameters.rst | 110 Free hugepages back to system exactly as they were originally allocated.
|
| /dpdk/doc/guides/rawdevs/ |
| H A D | ntb.rst | 78 reg00: base=0x000000000 ( 0MB), size= 2048MB, count=1: write-back
|
| /dpdk/doc/guides/testpmd_app_ug/ |
| H A D | run_app.rst | 243 In ``loop`` mode, ingress traffic is simply transmitted back on the same interface.
343 Set the write-back threshold register of RX rings to N, where N >= 0.
358 Set the write-back threshold register of TX rings to N, where N >= 0.
|
| /dpdk/doc/guides/rel_notes/ |
| H A D | release_20_05.rst | 199 back to fixed compression, the operation is now split into multiple smaller
203 code falls back to fixed compression as before.
231 thread(s) would receive events and submit them back to the event device
|