Changes between Version 16 and Version 17 of SupportedTraceFormats


Ignore:
Timestamp:
08/02/13 17:43:38 (7 years ago)
Author:
rjs51
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SupportedTraceFormats

    v16 v17  
    77|| Native Linux interface || int:<interface> || Yes || Yes || Only available on Linux ||
    88|| Native Linux interface (ring buffers) || ring:<interface> || Yes || Yes || Only available on Linux -- requires Libtrace 3.0.16 or later ||
     9|| Intel Data Plane Development Kit (DPDK) || dpdk:<PCI address> || Yes || Yes || Only available on Linux -- experimental (requires additional setup) ||
    910|| Native BSD interface || bpf:<interface> || Yes || No || Only available on BSD or Mac OS X ||
    1011|| TSH trace file || tsh:<filename> || Yes || No || ||
     
    5152 * Supports all the same features as int:
    5253
     54=== Intel Data Plane Development Kit (dpdk:) - This format is currently experimental ===
     55 * Better performance than int: and ring: under the correct conditions.
     56 * Binds to a single CPU core and polls on a buffer, this means waiting for a packet uses 100% CPU on that bound core.
     57 * You can only use a single instance of the dpdk: format at a given time - that is you can listen to a single interface or write to a single interface but not both.
     58
    5359=== RT protocol ===
    5460 * libtrace does not (yet?) support RT output.