Timestamp:
11/10/14 17:02:21 (6 years ago)
Author:
Shane Alcock <salcock@…>
Branches:
4.0.1-hotfixes, cachetimestamps, develop, dpdk-ndag, etsilive, libtrace4, master, ndag_format, pfring, rc-4.0.1, rc-4.0.2, rc-4.0.3, rc-4.0.4, ringdecrementfix, ringperformance, ringtimestampfixes
Children:
21f3226
Parents:
3c54095
Message:

Fix dodgy stream buffer flushing in DAG

Not sure what was going on with that flushing code, but I'm pretty sure
that wasn't going to work.

Ignore loss counters on the first packet observed on each interface.
Modern DAG interfaces treat any packets that appear while you're not
capturing as lost, so stopping and restarting a DAG capture will always
result in a non-zero loss counter. We tend to use the loss counter to
only indicate packets lost during active capture, so we need to compensate.

(No files)

Note: See TracChangeset for help on using the changeset viewer.