Packets dropped

[ldhasty]

While using this version of the driver I noticed there was a high number of packets dropped using Fedora 29. I was transferring about 70 gig worth of data via SMB and noticed over 429k packets were dropped before I ended the transfer and reverted to the kernel's driver implementation. This is using kernel 5.0.5-200.fc29.x86_64 and an Asus XG-C100C(Atlantic 107). Reverting to the kernels implementation I lost about 1 MB/s in through put but there were no dropped packets. This card is currently connected at a 1Gbs link. I have hardware arriving that will enable the card to run at full speed. It is connected to a Cisco SG300 52-52 using Cat5E

[aenertia]

Interesting I noticed that on f29 to ubuntu bionic I was getting autoneg failures and when it did negotiate it would only do so at 100mb - forcing the speed to 10000 fixed when I upgraded the ubuntu side kernel to a mainline 4.20.17 kernel.

Previously ubuntu to ubuntu was working without issue. what firmware does ethtool report for you on the card?

[ldhasty]

driver: atlantic version: 2.0.4.0-kern firmware-version: 3.0.33 expansion-rom-version: bus-info: 0000:01:00.0 supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: yes supports-priv-flags: no

…

On Sun, Apr 7, 2019 at 5:43 AM Joel Wirāmu Pauling ***@***.***> wrote: Interesting I noticed that on f29 to ubuntu bionic I was getting autoneg failures and when it did negotiate it would only do so at 100mb - forcing the speed to 10000 fixed when I upgraded the ubuntu side kernel to a mainline 4.20.17 kernel. Previously ubuntu to ubuntu was working without issue. what firmware does ethtool report for you on the card? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#4 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHkxEbkbxhW3s5dYPeIZtn9FWbvLAxnIks5veb3RgaJpZM4cgWI2> .

[cail]

@ldhasty, how did you checked the number of drops?
Could you provide the following output before and after the transfer In good and bad cases:
ethtool -S enp1s0

[ldhasty]

@cail I used ifconfig here is the output
Stock Driver

enp1s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000
inet 192.168.1.2 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::5af8:ff3:8911:ef45 prefixlen 64 scopeid 0x20
ether 40:b0:76:58:43:89 txqueuelen 1000 (Ethernet)
RX packets 110330575 bytes 49335076640 (45.9 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 177051049 bytes 1546257089615 (1.4 TiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Latest Driver

enp1s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000
inet 192.168.1.2 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::5af8:ff3:8911:ef45 prefixlen 64 scopeid 0x20
ether 40:b0:76:58:43:89 txqueuelen 1000 (Ethernet)
RX packets 1277528 bytes 11439203693 (10.6 GiB)
RX errors 0 dropped 331707 overruns 0 frame 0
TX packets 331708 bytes 20262689 (19.3 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

From the ethtool using the latest driver

NIC statistics:
InPackets: 2532272
InUCast: 2530287
InMCast: 284
InBCast: 1701
InErrors: 0
OutPackets: 656988
OutUCast: 656816
OutMCast: 40
OutBCast: 132
InUCastOctets: 22762079250
OutUCastOctets: 45301027
InMCastOctets: 53912
OutMCastOctets: 5725
InBCastOctets: 110105
OutBCastOctets: 13098
InOctets: 22762243267
OutOctets: 45319850
InPacketsDma: 2532034
OutPacketsDma: 656988
InOctetsDma: 22683860954
OutOctetsDma: 38917463
InDroppedDma: 656988
Queue[0] InPackets: 1989
Queue[0] OutPackets: 105
Queue[0] Restarts: 0
Queue[0] InJumboPackets: 0
Queue[0] InLroPackets: 0
Queue[0] InErrors: 0
Queue[1] InPackets: 149
Queue[1] OutPackets: 911
Queue[1] Restarts: 0
Queue[1] InJumboPackets: 0
Queue[1] InLroPackets: 1
Queue[1] InErrors: 0
Queue[2] InPackets: 166
Queue[2] OutPackets: 207
Queue[2] Restarts: 0
Queue[2] InJumboPackets: 0
Queue[2] InLroPackets: 1
Queue[2] InErrors: 0
Queue[3] InPackets: 175
Queue[3] OutPackets: 227
Queue[3] Restarts: 0
Queue[3] InJumboPackets: 0
Queue[3] InLroPackets: 0
Queue[3] InErrors: 0
Queue[4] InPackets: 359
Queue[4] OutPackets: 107
Queue[4] Restarts: 0
Queue[4] InJumboPackets: 0
Queue[4] InLroPackets: 0
Queue[4] InErrors: 0
Queue[5] InPackets: 950
Queue[5] OutPackets: 654936
Queue[5] Restarts: 0
Queue[5] InJumboPackets: 1
Queue[5] InLroPackets: 0
Queue[5] InErrors: 0
Queue[6] InPackets: 1264795
Queue[6] OutPackets: 212
Queue[6] Restarts: 0
Queue[6] InJumboPackets: 40719
Queue[6] InLroPackets: 10679496
Queue[6] InErrors: 35
Queue[7] InPackets: 94
Queue[7] OutPackets: 269
Queue[7] Restarts: 0
Queue[7] InJumboPackets: 0
Queue[7] InLroPackets: 0
Queue[7] InErrors: 0

[cail]

in kernel driver did not reported "dropped" counter. Thats why you don't see it increasing.
I guess its always increasing, in both drivers.
You may check in kernel driver ethtool -S, line
InDroppedDma: 656988
will show you actual drops. Guess it'll be non zero.

Drops are inevitable on high rates, especially with udp-based protocols.