diff options
author | Daniel Borkmann <dborkman@redhat.com> | 2013-06-25 12:30:58 +0200 |
---|---|---|
committer | Daniel Borkmann <dborkman@redhat.com> | 2013-06-25 12:30:58 +0200 |
commit | 278f62a9da99dcca7a7b95f34635b0fcd1a88185 (patch) | |
tree | 071023d829cf078c7446fe23049a7cab299de628 /ring_rx.h | |
parent | ea14716362e78d109490df9f345488d1c9a4a6c9 (diff) |
netsniff-ng: tpacketv3: 'fix' packet accounting output
In netsniff-ng, we use tpacketv3 for capturing-only mode. The issue
observed lately is that when using f.e. -n10 or capturing a pcap and
then quitting, the pcap or actually seen number of packets are less
than what the statistics tell us from getsockopt(2).
This is due to the fact that tpacketv3 divides its ring buffer into
blocks of frames. Meaning, while we are traversing block n, the kernel
already fills up block n+1 and following if new packets arrive. While
doing so, it increments packet counters. Thus, when we ^C, we haven't
seen those blocks, so the stats tell us mostly a slightly higher
result. Fix this by adjusting socket stats printing to this fact.
Signed-off-by: Daniel Borkmann <dborkman@redhat.com>
Diffstat (limited to 'ring_rx.h')
-rw-r--r-- | ring_rx.h | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -19,7 +19,7 @@ extern void alloc_rx_ring_frames(int sock, struct ring *ring); extern void bind_rx_ring(int sock, struct ring *ring, int ifindex); extern void setup_rx_ring_layout(int sock, struct ring *ring, unsigned int size, bool jumbo_support, bool v3); -extern void sock_rx_net_stats(int sock); +extern void sock_rx_net_stats(int sock, unsigned long seen); static inline int user_may_pull_from_rx(struct tpacket2_hdr *hdr) { |