From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 354] net/tap can not get rx packet drop stats when packets be dropped in kernel (net/driver/tun.c)
Date: Wed, 16 Oct 2019 08:58:22 +0000 [thread overview]
Message-ID: <bug-354-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=354
Bug ID: 354
Summary: net/tap can not get rx packet drop stats when packets
be dropped in kernel (net/driver/tun.c)
Product: DPDK
Version: 18.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: donald_lee@trendmicro.com
Target Milestone: ---
Due to kernel tap/tun driver limitation, rte_eth_tap can not get the rx dropped
stats, so we have to compensate it by ourself.
$ ifconfig ethernet1
ethernet1 Link encap:Ethernet HWaddr 00:0d:3a:54:53:fb
UP BROADCAST RUNNING PROMISC MULTICAST MTU:9216 Metric:1
RX packets:2505026 errors:0 dropped:0 overruns:0 frame:0
TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1122805246 (1.0 GiB) TX bytes:98 (98.0 B)
$ ifconfig dtap0
dtap0 Link encap:Ethernet HWaddr 00:0d:3a:54:53:fb
inet6 addr: fe80::20d:3aff:fe54:53fb/64 Scope:Link
UP BROADCAST RUNNING PROMISC ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:1295156 errors:0 dropped:10830 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:1049937532 (1001.2 MiB)
$ ethtool -i ethernet1
driver: net_failsafe
version:
firmware-version:
expansion-rom-version:
bus-info: 0002:00:02.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no
$ ethtool -i dtap0
driver: tun
version: 1.6
firmware-version:
expansion-rom-version:
bus-info: tap
supports-statistics: no
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2019-10-16 8:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-354-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.