Searched refs:traces (Results 1 – 5 of 5) 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
7 Exchanging packet traces becomes more and more critical every day.
99 meson -Denable_trace_fp=true tracebuild # build with fast path traces
112 void *traces; member503 config.traces = rte_zmalloc_socket(name, sz, RTE_CACHE_LINE_SIZE, in tracef_init()505 if (config.traces == NULL) in tracef_init()515 v = config.traces; in tracef_init()516 w = config.traces; in tracef_init()866 v = config.traces; in search_ip5tuples_once()
674 pmd.qat exposes both sets of traces.