| /dpdk/lib/timer/ |
| H A D | rte_timer.c | 670 __TIMER_STAT_ADD(priv_timer, manage, 1); in __rte_timer_manage() 817 __TIMER_STAT_ADD(data->priv_timer, manage, 1); in rte_timer_alt_manage() 1051 sum.manage += priv_timer[lcore_id].stats.manage; in __rte_timer_dump_stats() 1057 fprintf(f, " manage = %"PRIu64"\n", sum.manage); in __rte_timer_dump_stats()
|
| H A D | rte_timer.h | 83 uint64_t manage; /**< Number of calls to rte_timer_manage(). */ member
|
| /dpdk/doc/guides/compressdevs/ |
| H A D | octeontx.rst | 46 driver to manage configuration of ZIPVF device
|
| /dpdk/doc/guides/prog_guide/ |
| H A D | rte_security.rst | 137 E.g. in case of IPsec the device may internally manage anti-replay etc. 154 The underlying device will manage state information required for egress 210 In case of IPsec the device may internally manage anti-replay etc. 540 Sessions are used to manage protocol specific information as well as crypto parameters. 546 to create and manage two session mempools - one for session and other for session
|
| H A D | rawdev.rst | 23 way to manage such devices in a generic manner without expecting changes to
|
| H A D | traffic_metering_and_policing.rst | 60 * There is a meter policy API to manage pre-defined policies for meter.
|
| H A D | event_timer_adapter.rst | 88 how to create and configure an event timer adapter and use it to manage event 202 manage event timers with it.
|
| H A D | switch_representation.rst | 26 Without a standard software interface to manage traffic steering rules 373 these endpoints provides a standard interface to manage their 386 deemed flexible enough to manage representor traffic only with minor
|
| H A D | mempool_lib.rst | 102 Alternatively to the internal default per-lcore local cache, an application can create and manage e…
|
| H A D | vhost_lib.rst | 433 Vhost doesn't manage DMA devices and applications, like OVS, need to 434 manage and configure DMA devices. Applications need to tell vhost what
|
| H A D | gpudev.rst | 9 in order to manage the memory, synchronize operations, exchange info, etc..
|
| H A D | cryptodev_lib.rst | 497 processing of a packet flow. Sessions are used to manage information such as 722 ``struct rte_crypto_sym_vec`` to manage its data burst but with different 1037 It is the application's responsibility to create and manage the session mempools.
|
| H A D | link_bonding_poll_mode_drv_lib.rst | 344 and manage link bonding device from within any application. Link bonding
|
| /dpdk/doc/guides/nics/ |
| H A D | nfb.rst | 42 Kernel modules manage initialization of hardware, allocation and
|
| H A D | netvsc.rst | 38 If SR-IOV is enabled then the driver will transparently manage the interface,
|
| H A D | mlx4.rst | 173 manage actual hardware initialization and resources sharing with user
|
| H A D | dpaa2.rst | 237 Used by drivers to send commands to the MC to manage
|
| /dpdk/doc/guides/rel_notes/ |
| H A D | release_17_11.rst | 114 ``rte_cryptodev_pmd_destroy()`` for drivers to manage creation and 253 flow rules. It uses the ``librte_table`` API to manage the flow rules. 397 * **Removed deprecated functions to manage log level or type.**
|
| /dpdk/doc/guides/linux_gsg/ |
| H A D | linux_drivers.rst | 234 #. Start the DPDK application that will manage the PF device 241 #. Start the DPDK application that will manage the VF device
|
| H A D | sys_reqs.rst | 168 The tool ``dpdk-hugepages.py`` can be used to manage hugepages.
|
| /dpdk/doc/guides/eventdevs/ |
| H A D | cnxk.rst | 118 parameter disables NPA and uses software mempool to manage chunks
|
| /dpdk/doc/guides/sample_app_ug/ |
| H A D | l2_forward_crypto.rst | 61 * s: manage all ports from single core
|
| H A D | vm_power_management.rst | 45 The host application can manage power for an application by looking 302 It is possible to issue several commands from the CLI to manage VMs.
|
| H A D | kernel_nic_interface.rst | 216 Linux commands to manage the KNI interfaces as if they were any other
|
| /dpdk/doc/guides/platform/ |
| H A D | mlx5.rst | 118 that manage actual hardware initialization
|