ring_{rx,tx}: verbose: output version and v3 specific info

Kevin says:

  With netsniff-ng 0.5.8-rc2+, when I run the below packet capture
  session, the output seems to imply that 64K of memory is being
  allocated per frame, which does not look like what I want since my
  interface MTU is only 1500.  This appears to be severely limiting
  the number of frames I can fit into my packet capture ring.

As TPACKET_V3 is used in capturing to pcap files, frames are written
continuously to the ring, thus the above will give a wrong impression
to the user. Therefore, output such information in verbose mode
differently when TPACKET_V3 is being used, as it works block-wise.

Reported-by: Kevin Branch <branchnetconsulting@gmail.com>
Signed-off-by: Daniel Borkmann <dborkman@redhat.com>

0 files changed, 0 insertions, 0 deletions