Home
last modified time | relevance | path

Searched refs:involved (Results 1 – 21 of 21) sorted by relevance

/f-stack/freebsd/contrib/zlib/doc/
H A Dtxtvsbin.txt80 Since there is no counting involved, other than simply observing the
83 (If counting were involved, it could be possible to obtain different
/f-stack/dpdk/doc/guides/rawdevs/
H A Ddpaa2_qdma.rst9 without CPU being involved in the actual DMA transaction. This is achieved
/f-stack/freebsd/contrib/device-tree/Bindings/memory-controllers/
H A Dnvidia,tegra186-mc.yaml54 The bulk of the work involved in controlling the external memory
/f-stack/dpdk/doc/guides/nics/
H A Dipn3ke.rst57 Users need to bind FPGA LineSidePort to FVL PF. So I40e PF name list should be involved in
H A Ddpaa2.rst97 A simple scenario is described illustrating the objects involved
299 The diagram below shows the dpaa2 drivers involved in a networking
H A Dena.rst42 are accessed only during driver initialization and are not involved
/f-stack/dpdk/doc/guides/prog_guide/
H A Dglossary.rst46 are the layers involved when forwarding packets. These layers must be
H A Dpacket_framework.rst324 In packet processing context, the sequence of operations involved in hash table operations is descr…
/f-stack/freebsd/contrib/device-tree/Bindings/powerpc/opal/
H A Dpower-mgt.txt18 - exit-latency: The latency involved in transitioning the state of the
/f-stack/dpdk/doc/guides/sample_app_ug/
H A Dl3_forward_access_ctrl.rst337 If it is, the application records the socket IDs of the CPU cores involved in the task.
342 involved in the task to reduce the time for remote memory access.
H A Dl2_forward_cat.rst207 COS 0 to all involved CPUs via ``pqos_l3ca_assoc_set(...)`` calls.
H A Dperformance_thread.rst390 not at all involved in the scheduling of L-threads.
1072 would otherwise been involved. It is a reasonable approach to evaluate
/f-stack/dpdk/doc/guides/contributing/
H A Dvulnerability.rst70 Area experts not members of the security team may be involved in the process.
H A Dpatches.rst594 ``Acked-by:`` is a record that the person named was not directly involved in
/f-stack/freebsd/contrib/device-tree/Bindings/arm/tegra/
H A Dnvidia,tegra20-pmc.yaml67 then fed into the ARM GIC. The PMC is not involved in the detection
/f-stack/app/redis-5.0.5/src/
H A Dredis-cli.c5240 list *involved = NULL; in clusterManagerCommandRebalance() local
5268 involved = listCreate(); in clusterManagerCommandRebalance()
5283 listAddNodeTail(involved, n); in clusterManagerCommandRebalance()
5301 listRewind(involved, &li); in clusterManagerCommandRebalance()
5333 listRewind(involved, &li); in clusterManagerCommandRebalance()
5417 if (involved != NULL) listRelease(involved); in clusterManagerCommandRebalance()
/f-stack/freebsd/contrib/device-tree/Bindings/thermal/
H A Dthermal.txt14 There are five types of nodes involved to describe thermal bindings:
/f-stack/freebsd/contrib/device-tree/Bindings/fpga/
H A Dfpga-region.txt330 Region, the parent's FPGA Manager is used. If FPGA Bridges need to be involved,
/f-stack/dpdk/doc/guides/rel_notes/
H A Drelease_18_05.rst291 without the CPU being involved in the actual DMA transaction.
/f-stack/app/redis-5.0.5/deps/jemalloc/
H A DChangeLog524 effort involved.
/f-stack/freebsd/contrib/dev/acpica/
H A Dchanges.txt18065 problem involved an adjustment of all reference counts involving