Home
last modified time | relevance | path

Searched refs:isolate (Results 1 – 24 of 24) sorted by relevance

/f-stack/dpdk/doc/guides/howto/
H A Ddebug_troubleshoot.rst18 In all the above cases, it is tedious to isolate, debug, and understand various
20 consolidate a few commonly seen issues for reference. Then, isolate to identify
243 on the objects, packets, lookup tables to isolate the issue.
305 * Use ``rte_thread_get_affinity`` to isolate functions running on the same
415 #. To isolate the possible packet corruption in the processing pipeline,
418 * First, isolate at NIC entry and exit.
424 * Second, isolate at pipeline entry and exit.
H A Dflow_bifurcation.rst68 testpmd> flow isolate 0 true
H A Dpvp_reference_benchmark.rst37 In this setup, we isolate 6 cores (from CPU2 to CPU7) on the same NUMA
/f-stack/dpdk/lib/librte_ethdev/
H A Drte_flow_driver.h96 int (*isolate) member
H A Drte_flow.c403 if (likely(!!ops->isolate)) { in rte_flow_isolate()
405 ret = ops->isolate(dev, set, error); in rte_flow_isolate()
/f-stack/dpdk/drivers/net/failsafe/
H A Dfailsafe_flow.c254 .isolate = fs_flow_isolate,
/f-stack/dpdk/drivers/net/bonding/
H A Drte_eth_bond_flow.c244 .isolate = bond_flow_isolate,
/f-stack/dpdk/drivers/net/bnxt/tf_ulp/
H A Dbnxt_ulp_flow.c428 .isolate = NULL
/f-stack/freebsd/contrib/octeon-sdk/
H A Dcvmx-mdio.h83 uint16_t isolate : 1; member
/f-stack/dpdk/doc/guides/linux_gsg/
H A Denable_func.rst146 it is possible to use the ``isolcpus`` Linux kernel parameter to isolate them from the general Linu…
/f-stack/dpdk/doc/guides/prog_guide/
H A Dlink_bonding_poll_mode_drv_lib.rst204 - Call to flow isolate for all slaves.
205 - Failure in flow isolation for existed slave rejects the isolate mode.
/f-stack/dpdk/drivers/net/octeontx2/
H A Dotx2_flow.c814 .isolate = otx2_flow_isolate,
/f-stack/dpdk/doc/guides/testpmd_app_ug/
H A Drun_app.rst420 * ``--flow-isolate-all``
H A Dtestpmd_funcs.rst1642 testpmd> set bypass mode (normal|bypass|isolate) (port_id)
1650 mode (normal|bypass|isolate) (port_id)
3308 flow isolate {port_id} {boolean}
4205 ``flow isolate`` can be used to tell the underlying PMD that ingress traffic
4210 flow isolate {port_id} {boolean}
4232 testpmd> flow isolate 0 true
4238 testpmd> flow isolate 0 false
/f-stack/dpdk/drivers/net/mlx4/
H A Dmlx4_flow.c1589 .isolate = mlx4_flow_isolate,
/f-stack/dpdk/drivers/net/cxgbe/
H A Dcxgbe_flow.c1452 .isolate = NULL,
/f-stack/dpdk/drivers/net/tap/
H A Dtap_flow.c215 .isolate = tap_flow_isolate,
/f-stack/dpdk/drivers/net/softnic/
H A Drte_eth_softnic_flow.c2287 .isolate = NULL,
/f-stack/dpdk/drivers/net/mvpp2/
H A Dmrvl_flow.c2792 .isolate = mrvl_flow_isolate
/f-stack/dpdk/drivers/net/sfc/
H A Dsfc_flow.c2744 .isolate = sfc_flow_isolate,
/f-stack/dpdk/drivers/net/hns3/
H A Dhns3_flow.c2026 .isolate = NULL,
/f-stack/freebsd/contrib/zstd/
H A DCONTRIBUTING.md277 isolate that snippit by moving it to its own function (this is usually not necessary but
/f-stack/dpdk/app/test-pmd/
H A Dcmdline_flow.c755 } isolate; /**< Isolated mode arguments. */ member
1977 .args = ARGS(ARGS_ENTRY(struct buffer, args.isolate.set),
7318 port_flow_isolate(in->port, in->args.isolate.set); in cmd_flow_parsed()
/f-stack/dpdk/drivers/net/mlx5/
H A Dmlx5_flow.c634 .isolate = mlx5_flow_isolate,