Searched refs:traces (Results 1 – 14 of 14) sorted by relevance
161 ``$HOME/dpdk-traces/rte-yyyy-mm-dd-[AP]M-hh-mm-ss/``.174 There are many tools you can use to read DPDK traces:182 any type of logs or traces, including DPDK traces.192 ``babeltrace`` finds all traces recursively within the given path and prints208 ``Tracecompass`` is another tool to view/analyze the DPDK traces which gives232 - View the traces with babeltrace viewer::234 babeltrace $HOME/dpdk-traces/rte-yyyy-mm-dd-[AP]M-hh-mm-ss/239 As DPDK trace library is designed to generate traces that uses ``Common Trace
110 void *traces; member486 config.traces = rte_zmalloc_socket(name, sz, RTE_CACHE_LINE_SIZE, in tracef_init()488 if (config.traces == NULL) in tracef_init()498 v = config.traces; in tracef_init()499 w = config.traces; in tracef_init()833 v = config.traces; in search_ip5tuples_once()
118 /* RGMII delays added via PCB traces */
233 * Set a 100ms delay to account for PMIC ramp time and board traces.
362 * ramp time and board traces.
368 * Set a 100ms delay to account for PMIC ramp time and board traces.
417 * ramp time and board traces.
414 * ramp time and board traces.
48 the fixed-link, or by PCB serpentine traces on the board.
191 functionalty to trigger event notifications and debug traces.
108 * Stack traces which may be logged to `dmesg`.
665 pmd.qat exposes both sets of traces.
65 list *traces; /* Messages about Redis commands executed since last stop.*/ member
18571 Added optional thread ID output for debug traces, to simplify