Menu
▾
▴
e1000-devel — Discussion of the Intel Ethernet out-of-tree drivers
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
(1) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
|
Feb
|
Mar
(1) |
Apr
(9) |
May
(3) |
Jun
|
Jul
(3) |
Aug
(6) |
Sep
|
Oct
(7) |
Nov
|
Dec
|
| 2004 |
Jan
|
Feb
(5) |
Mar
(10) |
Apr
(2) |
May
(22) |
Jun
(8) |
Jul
(4) |
Aug
(8) |
Sep
(3) |
Oct
|
Nov
(36) |
Dec
(52) |
| 2005 |
Jan
(9) |
Feb
(13) |
Mar
(9) |
Apr
|
May
(14) |
Jun
(5) |
Jul
(20) |
Aug
(31) |
Sep
(2) |
Oct
(3) |
Nov
(18) |
Dec
(18) |
| 2006 |
Jan
(36) |
Feb
(16) |
Mar
(76) |
Apr
(78) |
May
(32) |
Jun
(30) |
Jul
(67) |
Aug
(43) |
Sep
(54) |
Oct
(116) |
Nov
(223) |
Dec
(158) |
| 2007 |
Jan
(180) |
Feb
(71) |
Mar
(110) |
Apr
(114) |
May
(203) |
Jun
(100) |
Jul
(238) |
Aug
(191) |
Sep
(177) |
Oct
(171) |
Nov
(211) |
Dec
(159) |
| 2008 |
Jan
(227) |
Feb
(288) |
Mar
(197) |
Apr
(253) |
May
(132) |
Jun
(152) |
Jul
(109) |
Aug
(143) |
Sep
(157) |
Oct
(198) |
Nov
(121) |
Dec
(147) |
| 2009 |
Jan
(105) |
Feb
(61) |
Mar
(191) |
Apr
(161) |
May
(118) |
Jun
(172) |
Jul
(166) |
Aug
(67) |
Sep
(86) |
Oct
(79) |
Nov
(118) |
Dec
(181) |
| 2010 |
Jan
(136) |
Feb
(154) |
Mar
(92) |
Apr
(83) |
May
(101) |
Jun
(66) |
Jul
(118) |
Aug
(78) |
Sep
(134) |
Oct
(131) |
Nov
(132) |
Dec
(104) |
| 2011 |
Jan
(79) |
Feb
(104) |
Mar
(144) |
Apr
(145) |
May
(130) |
Jun
(169) |
Jul
(146) |
Aug
(76) |
Sep
(113) |
Oct
(82) |
Nov
(145) |
Dec
(122) |
| 2012 |
Jan
(132) |
Feb
(106) |
Mar
(145) |
Apr
(238) |
May
(140) |
Jun
(162) |
Jul
(166) |
Aug
(147) |
Sep
(80) |
Oct
(148) |
Nov
(192) |
Dec
(90) |
| 2013 |
Jan
(139) |
Feb
(162) |
Mar
(174) |
Apr
(81) |
May
(261) |
Jun
(301) |
Jul
(106) |
Aug
(175) |
Sep
(305) |
Oct
(222) |
Nov
(95) |
Dec
(120) |
| 2014 |
Jan
(196) |
Feb
(171) |
Mar
(146) |
Apr
(118) |
May
(127) |
Jun
(93) |
Jul
(175) |
Aug
(66) |
Sep
(85) |
Oct
(120) |
Nov
(81) |
Dec
(192) |
| 2015 |
Jan
(141) |
Feb
(133) |
Mar
(189) |
Apr
(126) |
May
(59) |
Jun
(117) |
Jul
(56) |
Aug
(97) |
Sep
(44) |
Oct
(48) |
Nov
(33) |
Dec
(87) |
| 2016 |
Jan
(37) |
Feb
(56) |
Mar
(72) |
Apr
(65) |
May
(66) |
Jun
(65) |
Jul
(98) |
Aug
(54) |
Sep
(84) |
Oct
(68) |
Nov
(69) |
Dec
(60) |
| 2017 |
Jan
(30) |
Feb
(38) |
Mar
(53) |
Apr
(6) |
May
(2) |
Jun
(5) |
Jul
(15) |
Aug
(15) |
Sep
(7) |
Oct
(18) |
Nov
(23) |
Dec
(6) |
| 2018 |
Jan
(39) |
Feb
(5) |
Mar
(34) |
Apr
(26) |
May
(27) |
Jun
(5) |
Jul
(12) |
Aug
(4) |
Sep
|
Oct
(4) |
Nov
(4) |
Dec
(4) |
| 2019 |
Jan
(7) |
Feb
(10) |
Mar
(21) |
Apr
(26) |
May
(4) |
Jun
(5) |
Jul
(11) |
Aug
(6) |
Sep
(7) |
Oct
(13) |
Nov
(3) |
Dec
(17) |
| 2020 |
Jan
|
Feb
(3) |
Mar
(3) |
Apr
(5) |
May
(2) |
Jun
(5) |
Jul
|
Aug
|
Sep
(6) |
Oct
(7) |
Nov
(2) |
Dec
(7) |
| 2021 |
Jan
(9) |
Feb
(10) |
Mar
(18) |
Apr
(1) |
May
(3) |
Jun
|
Jul
(16) |
Aug
(2) |
Sep
|
Oct
|
Nov
(9) |
Dec
(2) |
| 2022 |
Jan
(3) |
Feb
|
Mar
(9) |
Apr
(8) |
May
(5) |
Jun
(6) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
(7) |
Dec
(2) |
| 2023 |
Jan
(7) |
Feb
(2) |
Mar
(6) |
Apr
|
May
(4) |
Jun
(2) |
Jul
(4) |
Aug
(3) |
Sep
(4) |
Oct
(2) |
Nov
(4) |
Dec
(10) |
| 2024 |
Jan
(4) |
Feb
(2) |
Mar
(1) |
Apr
|
May
(1) |
Jun
(1) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
1
(1) |
2
(3) |
3
(3) |
4
(6) |
5
(1) |
6
(1) |
|
7
(2) |
8
(9) |
9
(1) |
10
|
11
|
12
|
13
(1) |
|
14
(1) |
15
(1) |
16
(3) |
17
(1) |
18
(1) |
19
|
20
|
|
21
|
22
(3) |
23
|
24
(1) |
25
(1) |
26
(5) |
27
|
|
28
|
29
(7) |
30
|
31
(2) |
|
|
|
|
From: Skidmore, D. C <don...@in...> - 2016-08-31 16:28:49
|
The error value of -19 means your EEPROM indicates you're NIC doesn't have support for your SFP+ module. So you're correct this isn't specifically a DPDK issue, the code that verifies this is shared both between the Linux driver as well as DPDK. There are two possible cases here 1) we recognize the module but it isn't supported or 2) we don't know what the module is. If it was the first case then for the out of tree linux driver you could use the module parameter "allow_unsupported_sfp" to get around this check. Of course turning on this option produces the following rather scary log message: "WARNING: Intel (R) Network Connections are quality tested using Intel (R) Ethernet Optics. Using untested modules is not supported and may cause unstable operation or damage to the module or the adapter. Intel Corporation is not responsible for any harm caused by using untested modules. Thanks, -Don Skidmore <don...@in...> > -----Original Message----- > From: Ajit Khaparde [mailto:aji...@br...] > Sent: Tuesday, August 30, 2016 7:22 PM > To: Alex Forster <al...@al...>; e10...@li... > Cc: de...@dp... > Subject: Re: [E1000-devel] [dpdk-dev] Unsupported SFP+ Module - Hardware > Initialization Failure -19 > > On Tue, Aug 30, 2016 at 11:02 AM, Alex Forster <al...@al...> > wrote: > > > Hi guys, > > > > I have a problem again that I had about a year ago[1]. My Finisar > > FTL410QE2C (multimode QSFP) transceivers aren’t working with my Intel > > X520-QDA1’s. I have 7 servers, each with two X520’s and two QSFP > > transceivers in them, totaling 14 NICs and transceivers, and all of > > them fail with the same error: Unsupported SFP+ Module / Hardware > > Initialization > > Failure: -19. > > > > This doesn’t appear to be specifically a DPDK issue, but rather an > > IXGBE issue, since (a) the stock Debian 8 IXGBE, (b) the latest out of > > tree IXGBE, and (c) DPDK’s copy of IXGBE all fail in this same way. > > I’m happy to take this to an IXGBE mailing list if somebody can point > > me to one, but just in case anyone here can help, here’s the info I’ve > > gathered– > > > > * The exact function where IXGBE bails is here, annotated with the > > values read from the transceiver’s EEPROMs: > > https://www.googledrive.com/ host/0B_-81lR_g8lyNDJ6QkkxS28yQzQ > > * I’ve modified DPDK’s copy of IXGBE to dump the whole EEPROM of these > > transceivers, which are here: https://gist.github.com/alexforster/ > > 5da30cd89d49877d5d6908e9628baee8 > > > > Here’s (I think) an important part: Last time I had this problem, I > > only had one server, and one of the two transceivers worked. I fixed > > the other transceiver in that server by replacing it with an identical > > model. Now, suddenly, neither of those transceivers (which have worked > > for ~11 months) are recognized. I don’t know how I could have done > > something that would have affected the EEPROM output, but I suspect I may > have. > > > > Anybody able to offer any advice? > > > > Alex Forster > > > > [1] http://dpdk.org/ml/archives/dev/2015-October/024973.html > > > Adding e10...@li... |
|
From: Ajit K. <aji...@br...> - 2016-08-31 02:52:29
|
On Tue, Aug 30, 2016 at 11:02 AM, Alex Forster <al...@al...> wrote: > Hi guys, > > I have a problem again that I had about a year ago[1]. My Finisar > FTL410QE2C (multimode QSFP) transceivers aren’t working with my Intel > X520-QDA1’s. I have 7 servers, each with two X520’s and two QSFP > transceivers in them, totaling 14 NICs and transceivers, and all of them > fail with the same error: Unsupported SFP+ Module / Hardware Initialization > Failure: -19. > > This doesn’t appear to be specifically a DPDK issue, but rather an IXGBE > issue, since (a) the stock Debian 8 IXGBE, (b) the latest out of tree > IXGBE, and (c) DPDK’s copy of IXGBE all fail in this same way. I’m happy to > take this to an IXGBE mailing list if somebody can point me to one, but > just in case anyone here can help, here’s the info I’ve gathered– > > * The exact function where IXGBE bails is here, annotated with the values > read from the transceiver’s EEPROMs: https://www.googledrive.com/ > host/0B_-81lR_g8lyNDJ6QkkxS28yQzQ > * I’ve modified DPDK’s copy of IXGBE to dump the whole EEPROM of these > transceivers, which are here: https://gist.github.com/alexforster/ > 5da30cd89d49877d5d6908e9628baee8 > > Here’s (I think) an important part: Last time I had this problem, I only > had one server, and one of the two transceivers worked. I fixed the other > transceiver in that server by replacing it with an identical model. Now, > suddenly, neither of those transceivers (which have worked for ~11 months) > are recognized. I don’t know how I could have done something that would > have affected the EEPROM output, but I suspect I may have. > > Anybody able to offer any advice? > > Alex Forster > > [1] http://dpdk.org/ml/archives/dev/2015-October/024973.html Adding e10...@li... |
|
From: Fujinaka, T. <tod...@in...> - 2016-08-29 22:12:21
|
You should contact SuperMicro for initial support. They have the answers for your hardware and will contact us if they need help. Todd Fujinaka Software Application Engineer Networking Division (ND) Intel Corporation tod...@in... (503) 712-4565 -----Original Message----- From: Sylvain Munaut [mailto:s.m...@wh...] Sent: Monday, August 29, 2016 12:56 PM To: e10...@li... Subject: [E1000-devel] Fwd: ixgbe: Can't get link / carrier on embedded NIC of a D-1518 CPU Hi, I'm having trouble getting a link up on a ixgbe card. The hardware is a SuperMicro SYS-5018D-FN8T ( https://www.supermicro.nl/products/system/1U/5018/SYS-5018D-FN8T.cfm ) It includes a Intel® Xeon® processor D-1518 with embedded 10G Intel NICs and cs4227 phys to SFP+ ports. The optics in it is an official Intel optics FTLX8571D3BCVIT1 but I tried with some direct attach cables and some active optical tables and other optics as well with the same results. I also tried several peers, including itself (i.e. that board has two ports so I tried connecting one to the other ...) I tried both latest stable 4.4.x and 4.8.0-rc4 kernels There is no errors, just the device stays at NO-CARRIER. Even loading the module with debug=16 doesn't show anything more. Any idea what I can try ? Seems, I'm not the only one ( https://sourceforge.net/p/e1000/mailman/message/35267502/ ). This seems pretty similar to me, however there doesn't seem to be a solution :( Cheers, Sylvain PS: Originally posted on netdev, but I was pointed privately to this list which is more appropriate. -------- Debug output : 8: eth6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000 link/ether 00:25:90:5d:f8:b2 brd ff:ff:ff:ff:ff:ff bash# ethtool eth6 Settings for eth6: Supported ports: [ FIBRE ] Supported link modes: 1000baseT/Full 10000baseT/Full Supported pause frame use: No Supports auto-negotiation: No Advertised link modes: 10000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: No Speed: Unknown! Duplex: Unknown! (255) Port: FIBRE PHYAD: 0 Transceiver: external Auto-negotiation: off Supports Wake-on: d Wake-on: d Current message level: 0x00007fff (32767) drv probe link timer ifdown ifup rx_err tx_err tx_queued intr tx_done rx_status pktdata hw wol Link detected: no bash# ethtool -m eth6 Identifier : 0x03 (SFP) Extended identifier : 0x04 (GBIC/SFP defined by 2-wire interface ID) Connector : 0x07 (LC) Transceiver codes : 0x10 0x00 0x00 0x01 0x00 0x00 0x00 0x00 Transceiver type : 10G Ethernet: 10G Base-SR Transceiver type : Ethernet: 1000BASE-SX Encoding : 0x06 (64B/66B) BR, Nominal : 10300MBd Rate identifier : 0x02 (8/4/2G Rx Rate_Select only) Length (SMF,km) : 0km Length (SMF) : 0m Length (50um) : 80m Length (62.5um) : 30m Length (Copper) : 0m Length (OM3) : 300m Laser wavelength : 850nm Vendor name : Intel Corp Vendor OUI : 00:1b:21 Vendor PN : FTLX8571D3BCVIT1 Vendor rev : A Optical diagnostics support : Yes Laser bias current : 21.410 mA Laser output power : 0.6035 mW / -2.19 dBm Receiver signal average optical power : 0.7226 mW / -1.41 dBm Module temperature : 41.82 degrees C / 107.27 degrees F Module voltage : 3.3114 V Alarm/warning flags implemented : Yes Laser bias current high alarm : Off Laser bias current low alarm : Off Laser bias current high warning : Off Laser bias current low warning : Off Laser output power high alarm : Off Laser output power low alarm : Off Laser output power high warning : Off Laser output power low warning : Off Module temperature high alarm : Off Module temperature low alarm : Off Module temperature high warning : Off Module temperature low warning : Off Module voltage high alarm : Off Module voltage low alarm : Off Module voltage high warning : Off Module voltage low warning : Off Laser rx power high alarm : Off Laser rx power low alarm : Off Laser rx power high warning : Off Laser rx power low warning : Off Laser bias current high alarm threshold : 13.200 mA Laser bias current low alarm threshold : 2.000 mA Laser bias current high warning threshold : 12.600 mA Laser bias current low warning threshold : 3.000 mA Laser output power high alarm threshold : 1.0000 mW / 0.00 dBm Laser output power low alarm threshold : 0.1585 mW / -8.00 dBm Laser output power high warning threshold : 0.7943 mW / -1.00 dBm Laser output power low warning threshold : 0.1995 mW / -7.00 dBm Module temperature high alarm threshold : 78.00 degrees C / 172.40 degrees F Module temperature low alarm threshold : -13.00 degrees C / 8.60 degrees F Module temperature high warning threshold : 73.00 degrees C / 163.40 degrees F Module temperature low warning threshold : -8.00 degrees C / 17.60 degrees F Module voltage high alarm threshold : 3.7000 V Module voltage low alarm threshold : 2.9000 V Module voltage high warning threshold : 3.6000 V Module voltage low warning threshold : 3.0000 V Laser rx power high alarm threshold : 1.0000 mW / 0.00 dBm Laser rx power low alarm threshold : 0.0100 mW / -20.00 dBm Laser rx power high warning threshold : 0.7943 mW / -1.00 dBm Laser rx power low warning threshold : 0.0158 mW / -18.01 dBm bash# dmesg | grep ixgbe [ 2.837788] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 4.4.0-k [ 2.837885] ixgbe: Copyright (c) 1999-2016 Intel Corporation. [ 3.516335] ixgbe 0000:04:00.0: Multiqueue Enabled: Rx Queue count = 8, Tx Queue count = 8 [ 3.648453] ixgbe 0000:04:00.0: MAC: 5, PHY: 18, SFP+: 5, PBA No: 020A00-000 [ 3.648532] ixgbe 0000:04:00.0: 00:25:90:5d:f8:b2 [ 3.836240] ixgbe 0000:04:00.0: Intel(R) 10 Gigabit Network Connection [ 5.606778] ixgbe 0000:04:00.1: Multiqueue Enabled: Rx Queue count = 8, Tx Queue count = 8 [ 5.738691] ixgbe 0000:04:00.1: MAC: 5, PHY: 0, PBA No: 020A00-000 [ 5.738779] ixgbe 0000:04:00.1: 00:25:90:5d:f8:b3 [ 6.052155] ixgbe 0000:04:00.1: Intel(R) 10 Gigabit Network Connection [ 91.585568] ixgbe 0000:04:00.0: registered PHC device on eth6 [ 91.700449] ixgbe 0000:04:00.0 eth6: detected SFP+: 5 ------------------------------------------------------------------------------ _______________________________________________ E1000-devel mailing list E10...@li... https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired |
|
From: Sylvain M. <s.m...@wh...> - 2016-08-29 20:17:58
|
Hi, I'm having trouble getting a link up on a ixgbe card. The hardware is a SuperMicro SYS-5018D-FN8T ( https://www.supermicro.nl/products/system/1U/5018/SYS-5018D-FN8T.cfm ) It includes a Intel® Xeon® processor D-1518 with embedded 10G Intel NICs and cs4227 phys to SFP+ ports. The optics in it is an official Intel optics FTLX8571D3BCVIT1 but I tried with some direct attach cables and some active optical tables and other optics as well with the same results. I also tried several peers, including itself (i.e. that board has two ports so I tried connecting one to the other ...) I tried both latest stable 4.4.x and 4.8.0-rc4 kernels There is no errors, just the device stays at NO-CARRIER. Even loading the module with debug=16 doesn't show anything more. Any idea what I can try ? Seems, I'm not the only one ( https://sourceforge.net/p/e1000/mailman/message/35267502/ ). This seems pretty similar to me, however there doesn't seem to be a solution :( Cheers, Sylvain PS: Originally posted on netdev, but I was pointed privately to this list which is more appropriate. -------- Debug output : 8: eth6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000 link/ether 00:25:90:5d:f8:b2 brd ff:ff:ff:ff:ff:ff bash# ethtool eth6 Settings for eth6: Supported ports: [ FIBRE ] Supported link modes: 1000baseT/Full 10000baseT/Full Supported pause frame use: No Supports auto-negotiation: No Advertised link modes: 10000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: No Speed: Unknown! Duplex: Unknown! (255) Port: FIBRE PHYAD: 0 Transceiver: external Auto-negotiation: off Supports Wake-on: d Wake-on: d Current message level: 0x00007fff (32767) drv probe link timer ifdown ifup rx_err tx_err tx_queued intr tx_done rx_status pktdata hw wol Link detected: no bash# ethtool -m eth6 Identifier : 0x03 (SFP) Extended identifier : 0x04 (GBIC/SFP defined by 2-wire interface ID) Connector : 0x07 (LC) Transceiver codes : 0x10 0x00 0x00 0x01 0x00 0x00 0x00 0x00 Transceiver type : 10G Ethernet: 10G Base-SR Transceiver type : Ethernet: 1000BASE-SX Encoding : 0x06 (64B/66B) BR, Nominal : 10300MBd Rate identifier : 0x02 (8/4/2G Rx Rate_Select only) Length (SMF,km) : 0km Length (SMF) : 0m Length (50um) : 80m Length (62.5um) : 30m Length (Copper) : 0m Length (OM3) : 300m Laser wavelength : 850nm Vendor name : Intel Corp Vendor OUI : 00:1b:21 Vendor PN : FTLX8571D3BCVIT1 Vendor rev : A Optical diagnostics support : Yes Laser bias current : 21.410 mA Laser output power : 0.6035 mW / -2.19 dBm Receiver signal average optical power : 0.7226 mW / -1.41 dBm Module temperature : 41.82 degrees C / 107.27 degrees F Module voltage : 3.3114 V Alarm/warning flags implemented : Yes Laser bias current high alarm : Off Laser bias current low alarm : Off Laser bias current high warning : Off Laser bias current low warning : Off Laser output power high alarm : Off Laser output power low alarm : Off Laser output power high warning : Off Laser output power low warning : Off Module temperature high alarm : Off Module temperature low alarm : Off Module temperature high warning : Off Module temperature low warning : Off Module voltage high alarm : Off Module voltage low alarm : Off Module voltage high warning : Off Module voltage low warning : Off Laser rx power high alarm : Off Laser rx power low alarm : Off Laser rx power high warning : Off Laser rx power low warning : Off Laser bias current high alarm threshold : 13.200 mA Laser bias current low alarm threshold : 2.000 mA Laser bias current high warning threshold : 12.600 mA Laser bias current low warning threshold : 3.000 mA Laser output power high alarm threshold : 1.0000 mW / 0.00 dBm Laser output power low alarm threshold : 0.1585 mW / -8.00 dBm Laser output power high warning threshold : 0.7943 mW / -1.00 dBm Laser output power low warning threshold : 0.1995 mW / -7.00 dBm Module temperature high alarm threshold : 78.00 degrees C / 172.40 degrees F Module temperature low alarm threshold : -13.00 degrees C / 8.60 degrees F Module temperature high warning threshold : 73.00 degrees C / 163.40 degrees F Module temperature low warning threshold : -8.00 degrees C / 17.60 degrees F Module voltage high alarm threshold : 3.7000 V Module voltage low alarm threshold : 2.9000 V Module voltage high warning threshold : 3.6000 V Module voltage low warning threshold : 3.0000 V Laser rx power high alarm threshold : 1.0000 mW / 0.00 dBm Laser rx power low alarm threshold : 0.0100 mW / -20.00 dBm Laser rx power high warning threshold : 0.7943 mW / -1.00 dBm Laser rx power low warning threshold : 0.0158 mW / -18.01 dBm bash# dmesg | grep ixgbe [ 2.837788] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 4.4.0-k [ 2.837885] ixgbe: Copyright (c) 1999-2016 Intel Corporation. [ 3.516335] ixgbe 0000:04:00.0: Multiqueue Enabled: Rx Queue count = 8, Tx Queue count = 8 [ 3.648453] ixgbe 0000:04:00.0: MAC: 5, PHY: 18, SFP+: 5, PBA No: 020A00-000 [ 3.648532] ixgbe 0000:04:00.0: 00:25:90:5d:f8:b2 [ 3.836240] ixgbe 0000:04:00.0: Intel(R) 10 Gigabit Network Connection [ 5.606778] ixgbe 0000:04:00.1: Multiqueue Enabled: Rx Queue count = 8, Tx Queue count = 8 [ 5.738691] ixgbe 0000:04:00.1: MAC: 5, PHY: 0, PBA No: 020A00-000 [ 5.738779] ixgbe 0000:04:00.1: 00:25:90:5d:f8:b3 [ 6.052155] ixgbe 0000:04:00.1: Intel(R) 10 Gigabit Network Connection [ 91.585568] ixgbe 0000:04:00.0: registered PHC device on eth6 [ 91.700449] ixgbe 0000:04:00.0 eth6: detected SFP+: 5 |
|
From: Tara <ta...@yo...> - 2016-08-29 14:43:36
|
August 26, 2016 We are trying to contact you regarding the amount Discharged on your Student Obligations. Your Forgiveness Reduction is Approved You will Cancel, Discharge and Reduce your current obligations. This program was put in to place to keep the individual working full time in the work place. A brief phone call will give you your REDUCTION AMOUNT. All individuals who have called have had their reduction approved Please call now 844-285-9572 Federal Forgiveness Program Hours of Operation: Mon-Fri : 9:00 am to 9:00 pm (all times Eastern) Looking forward to speaking with you briefly about the many options that are now available: 844-285-9572 Thank you for taking the time to read this, this is a simple letter giving the public information about the possibilities of reducing certain obligation. Apologies if you received this in error. Posta: <image> |
|
From: Lutz V. <lv...@5t...> - 2016-08-29 13:05:16
|
On 06/13/2016 07:40 PM, Lutz Vieweg wrote: > On 06/13/2016 04:46 AM, Wan ZongShun wrote: >> Firstly, I need to know if your ethernet card works well now or not >> after you set iommu=pt. > > Too early to tell - the NIC worked for the last 4 days now without > failing, however, that is only about the same time as it took after > the upgrade to linux-4.6.1 before the bug was encountered, first. I can now say that after using the option iommu=pt with linux-4.6.1, the machine ran for > 2 months without problems. For other reasons (btrfs-stuff) I had to upgrade the machine to linux-4.7.2 last week, and the "iommu=pt" option wasn't active after this upgrade. It only took 4 days until the "AMD-Vi: Event logged IO_PAGE_FAULT... ixgbe Detected Tx Unit Hang" issue occured again. So this evening, I'll reboot linux-4.7.2 with "iommu=pt" again, as that really seemed to help. Regards, Lutz Vieweg >> If your ethernet card with 64bit(not 32bit) DMA addressable cap, that >> is ok, you will not be impacted by bounce buffer. > >> But iommu=pt is a terrible option, that make all devices bypass the iommu. > > Why is that terrible? The documentation I found on what iommu=pt actually > means were pretty scarce, but I noticed how many places recommended to use > this option for 10G NICs. > >> If you want to get further help, Please try: >> >> (1)Please add 'amd_iommu_dump' option in your kernel boot option, and >> send your full kernel logs, lspci info, don't add iommu=pt. >> (2) Add amd_iommu=fullflush option to kernel boot option, just try it. > > Will try that when the NIC becomes unavailable again. > >>> One more thing I find curious, but this didn't change with "iommu=pt": >>>> >>>> [ 0.000000] AGP: Checking aperture... >>>> [ 0.000000] AGP: No AGP bridge found >>>> [ 0.000000] AGP: Node 0: aperture [bus addr 0x00000000-0x01ffffff] >>>> (32MB) >>>> [ 0.000000] AGP: Your BIOS doesn't leave an aperture memory hole >>>> [ 0.000000] AGP: Please enable the IOMMU option in the BIOS setup >>>> [ 0.000000] AGP: This costs you 64MB of RAM >>>> [ 0.000000] AGP: Mapping aperture over RAM [mem 0xcc000000-0xcfffffff] >>>> (65536KB) >>> >>> I checked and the IOMMU-option is definitely enabled in the BIOS setup. >>> So I assume right that these message are irrelevant (since AGP as a whole >>> is irrelevant on this server)? >> >> Please cat /proc/iomem, send the information. > > Here it is: >> 00000000-00000fff : reserved >> 00001000-00097bff : System RAM >> 00097c00-0009ffff : reserved >> 000a0000-000bffff : PCI Bus 0000:00 >> 000c0000-000c7fff : Video ROM >> 000ce800-000d43ff : Adapter ROM >> 000d4800-000d57ff : Adapter ROM >> 000e6000-000fffff : reserved >> 000f0000-000fffff : System ROM >> 00100000-d7e7ffff : System RAM >> 01000000-01688c05 : Kernel code >> 01688c06-01d4f53f : Kernel data >> 01eea000-02174fff : Kernel bss >> d7e80000-d7e8dfff : RAM buffer >> d7e8e000-d7e8ffff : reserved >> d7e90000-d7eb3fff : ACPI Tables >> d7eb4000-d7edffff : ACPI Non-volatile Storage >> d7ee0000-d7ffffff : reserved >> d9000000-daffffff : PCI Bus 0000:40 >> d9000000-d90003ff : IOAPIC 2 >> d9010000-d9013fff : amd_iommu >> db000000-dcffffff : PCI Bus 0000:00 >> db000000-dbffffff : PCI Bus 0000:01 >> db000000-dbffffff : 0000:01:04.0 >> db000000-dbffffff : mgadrmfb_vram >> dcd00000-dcffffff : PCI Bus 0000:04 >> dcdfc000-dcdfffff : 0000:04:00.0 >> dcdfc000-dcdfffff : ixgbe >> dce00000-dcffffff : 0000:04:00.0 >> dce00000-dcffffff : ixgbe >> dd000000-dfffffff : PCI Bus 0000:00 >> def00000-df7fffff : PCI Bus 0000:01 >> deffc000-deffffff : 0000:01:04.0 >> deffc000-deffffff : mgadrmfb_mmio >> df000000-df7fffff : 0000:01:04.0 >> dfaf6000-dfaf6fff : 0000:00:12.1 >> dfaf6000-dfaf6fff : ohci_hcd >> dfaf7000-dfaf7fff : 0000:00:12.0 >> dfaf7000-dfaf7fff : ohci_hcd >> dfaf8400-dfaf87ff : 0000:00:11.0 >> dfaf8400-dfaf87ff : ahci >> dfaf8800-dfaf88ff : 0000:00:12.2 >> dfaf8800-dfaf88ff : ehci_hcd >> dfaf8c00-dfaf8cff : 0000:00:13.2 >> dfaf8c00-dfaf8cff : ehci_hcd >> dfaf9000-dfaf9fff : 0000:00:13.1 >> dfaf9000-dfaf9fff : ohci_hcd >> dfafa000-dfafafff : 0000:00:13.0 >> dfafa000-dfafafff : ohci_hcd >> dfafb000-dfafbfff : 0000:00:14.5 >> dfafb000-dfafbfff : ohci_hcd >> dfb00000-dfbfffff : PCI Bus 0000:02 >> dfb1c000-dfb1ffff : 0000:02:00.1 >> dfb1c000-dfb1ffff : igb >> dfb20000-dfb3ffff : 0000:02:00.1 >> dfb40000-dfb5ffff : 0000:02:00.1 >> dfb40000-dfb5ffff : igb >> dfb60000-dfb7ffff : 0000:02:00.1 >> dfb60000-dfb7ffff : igb >> dfb9c000-dfb9ffff : 0000:02:00.0 >> dfb9c000-dfb9ffff : igb >> dfba0000-dfbbffff : 0000:02:00.0 >> dfbc0000-dfbdffff : 0000:02:00.0 >> dfbc0000-dfbdffff : igb >> dfbe0000-dfbfffff : 0000:02:00.0 >> dfbe0000-dfbfffff : igb >> dfc00000-dfcfffff : PCI Bus 0000:03 >> dfc3c000-dfc3ffff : 0000:03:00.0 >> dfc3c000-dfc3ffff : mpt2sas >> dfc40000-dfc7ffff : 0000:03:00.0 >> dfc40000-dfc7ffff : mpt2sas >> dfc80000-dfcfffff : 0000:03:00.0 >> dfd00000-dfdfffff : PCI Bus 0000:04 >> dfd80000-dfdfffff : 0000:04:00.0 >> dfe00000-dfffffff : PCI Bus 0000:05 >> dfeb0000-dfebffff : 0000:05:00.0 >> dfeb0000-dfebffff : mpt2sas >> dfec0000-dfefffff : 0000:05:00.0 >> dfec0000-dfefffff : mpt2sas >> dff00000-dfffffff : 0000:05:00.0 >> e0000000-efffffff : PCI MMCONFIG 0000 [bus 00-ff] >> e0000000-efffffff : reserved >> e0000000-efffffff : pnp 00:0a >> f6000000-f6003fff : amd_iommu >> fec00000-fec003ff : IOAPIC 0 >> fec10000-fec1001f : pnp 00:04 >> fec20000-fec203ff : IOAPIC 1 >> fed00000-fed003ff : HPET 2 >> fed00000-fed003ff : PNP0103:00 >> fed40000-fed44fff : PCI Bus 0000:00 >> fee00000-fee00fff : Local APIC >> fee00000-fee00fff : pnp 00:03 >> ffb80000-ffbfffff : pnp 00:04 >> ffe00000-ffffffff : reserved >> ffe50000-ffe5e05f : pnp 00:04 >> 100000000-2026ffffff : System RAM >> 2027000000-2027ffffff : RAM buffer > > Regards, > > Lutz Vieweg > |
|
From: Lutz V. <lv...@5t...> - 2016-08-29 13:00:19
|
On 06/13/2016 07:40 PM, Lutz Vieweg wrote: > On 06/13/2016 04:46 AM, Wan ZongShun wrote: >> Firstly, I need to know if your ethernet card works well now or not >> after you set iommu=pt. > > Too early to tell - the NIC worked for the last 4 days now without > failing, however, that is only about the same time as it took after > the upgrade to linux-4.6.1 before the bug was encountered, first. I can now say that after using the option iommu=pt with linux-4.6.1, the machine ran for > 2 months without problems. For other reasons (btrfs-stuff) I had to upgrade the machine to linux-4.7.2 last week, and the "iommu=pt" option wasn't active after this upgrade. It only took 4 days until the "AMD-Vi: Event logged IO_PAGE_FAULT... ixgbe Detected Tx Unit Hang" issue occured again. So this evening, I'll reboot linux-4.7.2 with "iommu=pt" again, as that really seemed to help. Regards, Lutz Vieweg >> If your ethernet card with 64bit(not 32bit) DMA addressable cap, that >> is ok, you will not be impacted by bounce buffer. > >> But iommu=pt is a terrible option, that make all devices bypass the iommu. > > Why is that terrible? The documentation I found on what iommu=pt actually > means were pretty scarce, but I noticed how many places recommended to use > this option for 10G NICs. > >> If you want to get further help, Please try: >> >> (1)Please add 'amd_iommu_dump' option in your kernel boot option, and >> send your full kernel logs, lspci info, don't add iommu=pt. >> (2) Add amd_iommu=fullflush option to kernel boot option, just try it. > > Will try that when the NIC becomes unavailable again. > >>> One more thing I find curious, but this didn't change with "iommu=pt": >>>> >>>> [ 0.000000] AGP: Checking aperture... >>>> [ 0.000000] AGP: No AGP bridge found >>>> [ 0.000000] AGP: Node 0: aperture [bus addr 0x00000000-0x01ffffff] >>>> (32MB) >>>> [ 0.000000] AGP: Your BIOS doesn't leave an aperture memory hole >>>> [ 0.000000] AGP: Please enable the IOMMU option in the BIOS setup >>>> [ 0.000000] AGP: This costs you 64MB of RAM >>>> [ 0.000000] AGP: Mapping aperture over RAM [mem 0xcc000000-0xcfffffff] >>>> (65536KB) >>> >>> I checked and the IOMMU-option is definitely enabled in the BIOS setup. >>> So I assume right that these message are irrelevant (since AGP as a whole >>> is irrelevant on this server)? >> >> Please cat /proc/iomem, send the information. > > Here it is: >> 00000000-00000fff : reserved >> 00001000-00097bff : System RAM >> 00097c00-0009ffff : reserved >> 000a0000-000bffff : PCI Bus 0000:00 >> 000c0000-000c7fff : Video ROM >> 000ce800-000d43ff : Adapter ROM >> 000d4800-000d57ff : Adapter ROM >> 000e6000-000fffff : reserved >> 000f0000-000fffff : System ROM >> 00100000-d7e7ffff : System RAM >> 01000000-01688c05 : Kernel code >> 01688c06-01d4f53f : Kernel data >> 01eea000-02174fff : Kernel bss >> d7e80000-d7e8dfff : RAM buffer >> d7e8e000-d7e8ffff : reserved >> d7e90000-d7eb3fff : ACPI Tables >> d7eb4000-d7edffff : ACPI Non-volatile Storage >> d7ee0000-d7ffffff : reserved >> d9000000-daffffff : PCI Bus 0000:40 >> d9000000-d90003ff : IOAPIC 2 >> d9010000-d9013fff : amd_iommu >> db000000-dcffffff : PCI Bus 0000:00 >> db000000-dbffffff : PCI Bus 0000:01 >> db000000-dbffffff : 0000:01:04.0 >> db000000-dbffffff : mgadrmfb_vram >> dcd00000-dcffffff : PCI Bus 0000:04 >> dcdfc000-dcdfffff : 0000:04:00.0 >> dcdfc000-dcdfffff : ixgbe >> dce00000-dcffffff : 0000:04:00.0 >> dce00000-dcffffff : ixgbe >> dd000000-dfffffff : PCI Bus 0000:00 >> def00000-df7fffff : PCI Bus 0000:01 >> deffc000-deffffff : 0000:01:04.0 >> deffc000-deffffff : mgadrmfb_mmio >> df000000-df7fffff : 0000:01:04.0 >> dfaf6000-dfaf6fff : 0000:00:12.1 >> dfaf6000-dfaf6fff : ohci_hcd >> dfaf7000-dfaf7fff : 0000:00:12.0 >> dfaf7000-dfaf7fff : ohci_hcd >> dfaf8400-dfaf87ff : 0000:00:11.0 >> dfaf8400-dfaf87ff : ahci >> dfaf8800-dfaf88ff : 0000:00:12.2 >> dfaf8800-dfaf88ff : ehci_hcd >> dfaf8c00-dfaf8cff : 0000:00:13.2 >> dfaf8c00-dfaf8cff : ehci_hcd >> dfaf9000-dfaf9fff : 0000:00:13.1 >> dfaf9000-dfaf9fff : ohci_hcd >> dfafa000-dfafafff : 0000:00:13.0 >> dfafa000-dfafafff : ohci_hcd >> dfafb000-dfafbfff : 0000:00:14.5 >> dfafb000-dfafbfff : ohci_hcd >> dfb00000-dfbfffff : PCI Bus 0000:02 >> dfb1c000-dfb1ffff : 0000:02:00.1 >> dfb1c000-dfb1ffff : igb >> dfb20000-dfb3ffff : 0000:02:00.1 >> dfb40000-dfb5ffff : 0000:02:00.1 >> dfb40000-dfb5ffff : igb >> dfb60000-dfb7ffff : 0000:02:00.1 >> dfb60000-dfb7ffff : igb >> dfb9c000-dfb9ffff : 0000:02:00.0 >> dfb9c000-dfb9ffff : igb >> dfba0000-dfbbffff : 0000:02:00.0 >> dfbc0000-dfbdffff : 0000:02:00.0 >> dfbc0000-dfbdffff : igb >> dfbe0000-dfbfffff : 0000:02:00.0 >> dfbe0000-dfbfffff : igb >> dfc00000-dfcfffff : PCI Bus 0000:03 >> dfc3c000-dfc3ffff : 0000:03:00.0 >> dfc3c000-dfc3ffff : mpt2sas >> dfc40000-dfc7ffff : 0000:03:00.0 >> dfc40000-dfc7ffff : mpt2sas >> dfc80000-dfcfffff : 0000:03:00.0 >> dfd00000-dfdfffff : PCI Bus 0000:04 >> dfd80000-dfdfffff : 0000:04:00.0 >> dfe00000-dfffffff : PCI Bus 0000:05 >> dfeb0000-dfebffff : 0000:05:00.0 >> dfeb0000-dfebffff : mpt2sas >> dfec0000-dfefffff : 0000:05:00.0 >> dfec0000-dfefffff : mpt2sas >> dff00000-dfffffff : 0000:05:00.0 >> e0000000-efffffff : PCI MMCONFIG 0000 [bus 00-ff] >> e0000000-efffffff : reserved >> e0000000-efffffff : pnp 00:0a >> f6000000-f6003fff : amd_iommu >> fec00000-fec003ff : IOAPIC 0 >> fec10000-fec1001f : pnp 00:04 >> fec20000-fec203ff : IOAPIC 1 >> fed00000-fed003ff : HPET 2 >> fed00000-fed003ff : PNP0103:00 >> fed40000-fed44fff : PCI Bus 0000:00 >> fee00000-fee00fff : Local APIC >> fee00000-fee00fff : pnp 00:03 >> ffb80000-ffbfffff : pnp 00:04 >> ffe00000-ffffffff : reserved >> ffe50000-ffe5e05f : pnp 00:04 >> 100000000-2026ffffff : System RAM >> 2027000000-2027ffffff : RAM buffer > > Regards, > > Lutz Vieweg > |
|
From: Lutz V. <lv...@5t...> - 2016-08-29 12:55:16
|
On 06/13/2016 07:40 PM, Lutz Vieweg wrote: > On 06/13/2016 04:46 AM, Wan ZongShun wrote: >> Firstly, I need to know if your ethernet card works well now or not >> after you set iommu=pt. > > Too early to tell - the NIC worked for the last 4 days now without > failing, however, that is only about the same time as it took after > the upgrade to linux-4.6.1 before the bug was encountered, first. I can now say that after using the option iommu=pt with linux-4.6.1, the machine ran for > 2 months without problems. For other reasons (btrfs-stuff) I had to upgrade the machine to linux-4.7.2 last week, and the "iommu=pt" option wasn't active after this upgrade. It only took 4 days until the "AMD-Vi: Event logged IO_PAGE_FAULT... ixgbe Detected Tx Unit Hang" issue occured again. So this evening, I'll reboot linux-4.7.2 with "iommu=pt" again, as that really seemed to help. Regards, Lutz Vieweg >> If your ethernet card with 64bit(not 32bit) DMA addressable cap, that >> is ok, you will not be impacted by bounce buffer. > >> But iommu=pt is a terrible option, that make all devices bypass the iommu. > > Why is that terrible? The documentation I found on what iommu=pt actually > means were pretty scarce, but I noticed how many places recommended to use > this option for 10G NICs. > >> If you want to get further help, Please try: >> >> (1)Please add 'amd_iommu_dump' option in your kernel boot option, and >> send your full kernel logs, lspci info, don't add iommu=pt. >> (2) Add amd_iommu=fullflush option to kernel boot option, just try it. > > Will try that when the NIC becomes unavailable again. > >>> One more thing I find curious, but this didn't change with "iommu=pt": >>>> >>>> [ 0.000000] AGP: Checking aperture... >>>> [ 0.000000] AGP: No AGP bridge found >>>> [ 0.000000] AGP: Node 0: aperture [bus addr 0x00000000-0x01ffffff] >>>> (32MB) >>>> [ 0.000000] AGP: Your BIOS doesn't leave an aperture memory hole >>>> [ 0.000000] AGP: Please enable the IOMMU option in the BIOS setup >>>> [ 0.000000] AGP: This costs you 64MB of RAM >>>> [ 0.000000] AGP: Mapping aperture over RAM [mem 0xcc000000-0xcfffffff] >>>> (65536KB) >>> >>> I checked and the IOMMU-option is definitely enabled in the BIOS setup. >>> So I assume right that these message are irrelevant (since AGP as a whole >>> is irrelevant on this server)? >> >> Please cat /proc/iomem, send the information. > > Here it is: >> 00000000-00000fff : reserved >> 00001000-00097bff : System RAM >> 00097c00-0009ffff : reserved >> 000a0000-000bffff : PCI Bus 0000:00 >> 000c0000-000c7fff : Video ROM >> 000ce800-000d43ff : Adapter ROM >> 000d4800-000d57ff : Adapter ROM >> 000e6000-000fffff : reserved >> 000f0000-000fffff : System ROM >> 00100000-d7e7ffff : System RAM >> 01000000-01688c05 : Kernel code >> 01688c06-01d4f53f : Kernel data >> 01eea000-02174fff : Kernel bss >> d7e80000-d7e8dfff : RAM buffer >> d7e8e000-d7e8ffff : reserved >> d7e90000-d7eb3fff : ACPI Tables >> d7eb4000-d7edffff : ACPI Non-volatile Storage >> d7ee0000-d7ffffff : reserved >> d9000000-daffffff : PCI Bus 0000:40 >> d9000000-d90003ff : IOAPIC 2 >> d9010000-d9013fff : amd_iommu >> db000000-dcffffff : PCI Bus 0000:00 >> db000000-dbffffff : PCI Bus 0000:01 >> db000000-dbffffff : 0000:01:04.0 >> db000000-dbffffff : mgadrmfb_vram >> dcd00000-dcffffff : PCI Bus 0000:04 >> dcdfc000-dcdfffff : 0000:04:00.0 >> dcdfc000-dcdfffff : ixgbe >> dce00000-dcffffff : 0000:04:00.0 >> dce00000-dcffffff : ixgbe >> dd000000-dfffffff : PCI Bus 0000:00 >> def00000-df7fffff : PCI Bus 0000:01 >> deffc000-deffffff : 0000:01:04.0 >> deffc000-deffffff : mgadrmfb_mmio >> df000000-df7fffff : 0000:01:04.0 >> dfaf6000-dfaf6fff : 0000:00:12.1 >> dfaf6000-dfaf6fff : ohci_hcd >> dfaf7000-dfaf7fff : 0000:00:12.0 >> dfaf7000-dfaf7fff : ohci_hcd >> dfaf8400-dfaf87ff : 0000:00:11.0 >> dfaf8400-dfaf87ff : ahci >> dfaf8800-dfaf88ff : 0000:00:12.2 >> dfaf8800-dfaf88ff : ehci_hcd >> dfaf8c00-dfaf8cff : 0000:00:13.2 >> dfaf8c00-dfaf8cff : ehci_hcd >> dfaf9000-dfaf9fff : 0000:00:13.1 >> dfaf9000-dfaf9fff : ohci_hcd >> dfafa000-dfafafff : 0000:00:13.0 >> dfafa000-dfafafff : ohci_hcd >> dfafb000-dfafbfff : 0000:00:14.5 >> dfafb000-dfafbfff : ohci_hcd >> dfb00000-dfbfffff : PCI Bus 0000:02 >> dfb1c000-dfb1ffff : 0000:02:00.1 >> dfb1c000-dfb1ffff : igb >> dfb20000-dfb3ffff : 0000:02:00.1 >> dfb40000-dfb5ffff : 0000:02:00.1 >> dfb40000-dfb5ffff : igb >> dfb60000-dfb7ffff : 0000:02:00.1 >> dfb60000-dfb7ffff : igb >> dfb9c000-dfb9ffff : 0000:02:00.0 >> dfb9c000-dfb9ffff : igb >> dfba0000-dfbbffff : 0000:02:00.0 >> dfbc0000-dfbdffff : 0000:02:00.0 >> dfbc0000-dfbdffff : igb >> dfbe0000-dfbfffff : 0000:02:00.0 >> dfbe0000-dfbfffff : igb >> dfc00000-dfcfffff : PCI Bus 0000:03 >> dfc3c000-dfc3ffff : 0000:03:00.0 >> dfc3c000-dfc3ffff : mpt2sas >> dfc40000-dfc7ffff : 0000:03:00.0 >> dfc40000-dfc7ffff : mpt2sas >> dfc80000-dfcfffff : 0000:03:00.0 >> dfd00000-dfdfffff : PCI Bus 0000:04 >> dfd80000-dfdfffff : 0000:04:00.0 >> dfe00000-dfffffff : PCI Bus 0000:05 >> dfeb0000-dfebffff : 0000:05:00.0 >> dfeb0000-dfebffff : mpt2sas >> dfec0000-dfefffff : 0000:05:00.0 >> dfec0000-dfefffff : mpt2sas >> dff00000-dfffffff : 0000:05:00.0 >> e0000000-efffffff : PCI MMCONFIG 0000 [bus 00-ff] >> e0000000-efffffff : reserved >> e0000000-efffffff : pnp 00:0a >> f6000000-f6003fff : amd_iommu >> fec00000-fec003ff : IOAPIC 0 >> fec10000-fec1001f : pnp 00:04 >> fec20000-fec203ff : IOAPIC 1 >> fed00000-fed003ff : HPET 2 >> fed00000-fed003ff : PNP0103:00 >> fed40000-fed44fff : PCI Bus 0000:00 >> fee00000-fee00fff : Local APIC >> fee00000-fee00fff : pnp 00:03 >> ffb80000-ffbfffff : pnp 00:04 >> ffe00000-ffffffff : reserved >> ffe50000-ffe5e05f : pnp 00:04 >> 100000000-2026ffffff : System RAM >> 2027000000-2027ffffff : RAM buffer > > Regards, > > Lutz Vieweg > |
|
From: Lutz V. <lv...@5t...> - 2016-08-29 12:35:16
|
On 06/13/2016 07:40 PM, Lutz Vieweg wrote: > On 06/13/2016 04:46 AM, Wan ZongShun wrote: >> Firstly, I need to know if your ethernet card works well now or not >> after you set iommu=pt. > > Too early to tell - the NIC worked for the last 4 days now without > failing, however, that is only about the same time as it took after > the upgrade to linux-4.6.1 before the bug was encountered, first. I can now say that after using the option iommu=pt with linux-4.6.1, the machine ran for > 2 months without problems. For other reasons (btrfs-stuff) I had to upgrade the machine to linux-4.7.2 last week, and the "iommu=pt" option wasn't active after this upgrade. It only took 4 days until the "AMD-Vi: Event logged IO_PAGE_FAULT... ixgbe Detected Tx Unit Hang" issue occured again. So this evening, I'll reboot linux-4.7.2 with "iommu=pt" again, as that really seemed to help. Regards, Lutz Vieweg >> If your ethernet card with 64bit(not 32bit) DMA addressable cap, that >> is ok, you will not be impacted by bounce buffer. > >> But iommu=pt is a terrible option, that make all devices bypass the iommu. > > Why is that terrible? The documentation I found on what iommu=pt actually > means were pretty scarce, but I noticed how many places recommended to use > this option for 10G NICs. > >> If you want to get further help, Please try: >> >> (1)Please add 'amd_iommu_dump' option in your kernel boot option, and >> send your full kernel logs, lspci info, don't add iommu=pt. >> (2) Add amd_iommu=fullflush option to kernel boot option, just try it. > > Will try that when the NIC becomes unavailable again. > >>> One more thing I find curious, but this didn't change with "iommu=pt": >>>> >>>> [ 0.000000] AGP: Checking aperture... >>>> [ 0.000000] AGP: No AGP bridge found >>>> [ 0.000000] AGP: Node 0: aperture [bus addr 0x00000000-0x01ffffff] >>>> (32MB) >>>> [ 0.000000] AGP: Your BIOS doesn't leave an aperture memory hole >>>> [ 0.000000] AGP: Please enable the IOMMU option in the BIOS setup >>>> [ 0.000000] AGP: This costs you 64MB of RAM >>>> [ 0.000000] AGP: Mapping aperture over RAM [mem 0xcc000000-0xcfffffff] >>>> (65536KB) >>> >>> I checked and the IOMMU-option is definitely enabled in the BIOS setup. >>> So I assume right that these message are irrelevant (since AGP as a whole >>> is irrelevant on this server)? >> >> Please cat /proc/iomem, send the information. > > Here it is: >> 00000000-00000fff : reserved >> 00001000-00097bff : System RAM >> 00097c00-0009ffff : reserved >> 000a0000-000bffff : PCI Bus 0000:00 >> 000c0000-000c7fff : Video ROM >> 000ce800-000d43ff : Adapter ROM >> 000d4800-000d57ff : Adapter ROM >> 000e6000-000fffff : reserved >> 000f0000-000fffff : System ROM >> 00100000-d7e7ffff : System RAM >> 01000000-01688c05 : Kernel code >> 01688c06-01d4f53f : Kernel data >> 01eea000-02174fff : Kernel bss >> d7e80000-d7e8dfff : RAM buffer >> d7e8e000-d7e8ffff : reserved >> d7e90000-d7eb3fff : ACPI Tables >> d7eb4000-d7edffff : ACPI Non-volatile Storage >> d7ee0000-d7ffffff : reserved >> d9000000-daffffff : PCI Bus 0000:40 >> d9000000-d90003ff : IOAPIC 2 >> d9010000-d9013fff : amd_iommu >> db000000-dcffffff : PCI Bus 0000:00 >> db000000-dbffffff : PCI Bus 0000:01 >> db000000-dbffffff : 0000:01:04.0 >> db000000-dbffffff : mgadrmfb_vram >> dcd00000-dcffffff : PCI Bus 0000:04 >> dcdfc000-dcdfffff : 0000:04:00.0 >> dcdfc000-dcdfffff : ixgbe >> dce00000-dcffffff : 0000:04:00.0 >> dce00000-dcffffff : ixgbe >> dd000000-dfffffff : PCI Bus 0000:00 >> def00000-df7fffff : PCI Bus 0000:01 >> deffc000-deffffff : 0000:01:04.0 >> deffc000-deffffff : mgadrmfb_mmio >> df000000-df7fffff : 0000:01:04.0 >> dfaf6000-dfaf6fff : 0000:00:12.1 >> dfaf6000-dfaf6fff : ohci_hcd >> dfaf7000-dfaf7fff : 0000:00:12.0 >> dfaf7000-dfaf7fff : ohci_hcd >> dfaf8400-dfaf87ff : 0000:00:11.0 >> dfaf8400-dfaf87ff : ahci >> dfaf8800-dfaf88ff : 0000:00:12.2 >> dfaf8800-dfaf88ff : ehci_hcd >> dfaf8c00-dfaf8cff : 0000:00:13.2 >> dfaf8c00-dfaf8cff : ehci_hcd >> dfaf9000-dfaf9fff : 0000:00:13.1 >> dfaf9000-dfaf9fff : ohci_hcd >> dfafa000-dfafafff : 0000:00:13.0 >> dfafa000-dfafafff : ohci_hcd >> dfafb000-dfafbfff : 0000:00:14.5 >> dfafb000-dfafbfff : ohci_hcd >> dfb00000-dfbfffff : PCI Bus 0000:02 >> dfb1c000-dfb1ffff : 0000:02:00.1 >> dfb1c000-dfb1ffff : igb >> dfb20000-dfb3ffff : 0000:02:00.1 >> dfb40000-dfb5ffff : 0000:02:00.1 >> dfb40000-dfb5ffff : igb >> dfb60000-dfb7ffff : 0000:02:00.1 >> dfb60000-dfb7ffff : igb >> dfb9c000-dfb9ffff : 0000:02:00.0 >> dfb9c000-dfb9ffff : igb >> dfba0000-dfbbffff : 0000:02:00.0 >> dfbc0000-dfbdffff : 0000:02:00.0 >> dfbc0000-dfbdffff : igb >> dfbe0000-dfbfffff : 0000:02:00.0 >> dfbe0000-dfbfffff : igb >> dfc00000-dfcfffff : PCI Bus 0000:03 >> dfc3c000-dfc3ffff : 0000:03:00.0 >> dfc3c000-dfc3ffff : mpt2sas >> dfc40000-dfc7ffff : 0000:03:00.0 >> dfc40000-dfc7ffff : mpt2sas >> dfc80000-dfcfffff : 0000:03:00.0 >> dfd00000-dfdfffff : PCI Bus 0000:04 >> dfd80000-dfdfffff : 0000:04:00.0 >> dfe00000-dfffffff : PCI Bus 0000:05 >> dfeb0000-dfebffff : 0000:05:00.0 >> dfeb0000-dfebffff : mpt2sas >> dfec0000-dfefffff : 0000:05:00.0 >> dfec0000-dfefffff : mpt2sas >> dff00000-dfffffff : 0000:05:00.0 >> e0000000-efffffff : PCI MMCONFIG 0000 [bus 00-ff] >> e0000000-efffffff : reserved >> e0000000-efffffff : pnp 00:0a >> f6000000-f6003fff : amd_iommu >> fec00000-fec003ff : IOAPIC 0 >> fec10000-fec1001f : pnp 00:04 >> fec20000-fec203ff : IOAPIC 1 >> fed00000-fed003ff : HPET 2 >> fed00000-fed003ff : PNP0103:00 >> fed40000-fed44fff : PCI Bus 0000:00 >> fee00000-fee00fff : Local APIC >> fee00000-fee00fff : pnp 00:03 >> ffb80000-ffbfffff : pnp 00:04 >> ffe00000-ffffffff : reserved >> ffe50000-ffe5e05f : pnp 00:04 >> 100000000-2026ffffff : System RAM >> 2027000000-2027ffffff : RAM buffer > > Regards, > > Lutz Vieweg > |
|
From: Alexander D. <ale...@gm...> - 2016-08-26 18:12:30
|
On Fri, Aug 26, 2016 at 7:45 AM, Auer, Jens <jen...@cg...> wrote: > Hi, > > how does Perfect Filter (PF) work? According to the Readme, > > > Perfect filter is an interface to load the filter table that funnels all flow > into queue_0 unless an alternative queue is specified using "action". In that > case, any flow that matches the filter criteria will be directed to the > appropriate queue. > > >From this, I would expect that the counters in the NIC count only traffic in queue 0 when receiving packets. > So I did a little experiment and captured the counters before and after sending some traffic with iperf. These are the counters before: > > rx_queue_0_packets 16039690804 > rx_queue_1_packets 395308116 > rx_queue_2_packets 84525446 > rx_queue_3_packets 107679699 > rx_queue_4_packets 27442172 > rx_queue_5_packets 38033947 > rx_queue_6_packets 17664248 > rx_queue_7_packets 13731407 > rx_queue_8_packets 1869081 > rx_queue_9_packets 1564940 > rx_queue_10_packets 5000550 > rx_queue_11_packets 5358344 > rx_queue_12_packets 5598815 > rx_queue_13_packets 5508204 > rx_queue_14_packets 2773449 > rx_queue_15_packets 2539626 > rx_queue_16_packets 30444701 > rx_queue_17_packets 1875836468 > rx_queue_18_packets 31240359 > rx_queue_19_packets 9905014 > rx_queue_20_packets 1947326460 > rx_queue_21_packets 44664553 > rx_queue_22_packets 4792314 > rx_queue_23_packets 43862206 > rx_queue_24_packets 141 > rx_queue_25_packets 97 > rx_queue_26_packets 73 > rx_queue_27_packets 176 > rx_queue_28_packets 158 > rx_queue_29_packets 191 > rx_queue_30_packets 93 > rx_queue_31_packets 318 > > And these are the counters after running iperf for 10s: > rx_queue_0_packets 16040037801 > rx_queue_1_packets 395655118 > rx_queue_2_packets 84872104 > rx_queue_3_packets 108026357 > rx_queue_4_packets 27442172 > rx_queue_5_packets 38033947 > rx_queue_6_packets 18011252 > rx_queue_7_packets 14079046 > rx_queue_8_packets 1869092 > rx_queue_9_packets 1738441 > rx_queue_10_packets 5347208 > rx_queue_11_packets 5531673 > rx_queue_12_packets 5598815 > rx_queue_13_packets 5508204 > rx_queue_14_packets 3120599 > rx_queue_15_packets 2886331 > rx_queue_16_packets 30444701 > rx_queue_17_packets 1875836468 > rx_queue_18_packets 31240359 > rx_queue_19_packets 9905014 > rx_queue_20_packets 1947326460 > rx_queue_21_packets 44664553 > rx_queue_22_packets 4792314 > rx_queue_23_packets 43862206 > rx_queue_24_packets 141 > rx_queue_25_packets 97 > rx_queue_26_packets 73 > rx_queue_27_packets 176 > rx_queue_28_packets 158 > rx_queue_29_packets 191 > rx_queue_30_packets 93 > rx_queue_31_packets 318 > > As you can see traffic is nicely distributed to several queues. I have no rules specified and nutple-filters=on for both servers. Is this RSS distributing the traffic to different queues? > > Best wishes, > Jens All turning on ntuple-filtering does is enable you to then populate the filter table the "ethtool -N <iface> flow-type" command. When it is enabled you default to RSS for any flows that don't match any of your rule criteria. If you specify a rule without specifying an action then it will route the packet to queue 0 as that is the default action. - Alex |
|
From: Skidmore, D. C <don...@in...> - 2016-08-26 17:14:24
|
Any packet that doesn't hit a perfect filter is then subject to the RSS hash. Since you don't have any perfect filters RSS is hashing everything. In fact this is a good way to turn on RSS only (i.e. turn on ntuple but don't make any filters.) Thanks, -Don Skidmore <don...@in...> > -----Original Message----- > From: Auer, Jens [mailto:jen...@cg...] > Sent: Friday, August 26, 2016 7:45 AM > To: e10...@li... > Subject: [E1000-devel] How does Perfect Filter work? > > Hi, > > how does Perfect Filter (PF) work? According to the Readme, > > > Perfect filter is an interface to load the filter table that funnels all flow into > queue_0 unless an alternative queue is specified using "action". In that case, > any flow that matches the filter criteria will be directed to the appropriate > queue. > > >From this, I would expect that the counters in the NIC count only traffic in > queue 0 when receiving packets. > So I did a little experiment and captured the counters before and after sending > some traffic with iperf. These are the counters before: > > rx_queue_0_packets 16039690804 > rx_queue_1_packets 395308116 > rx_queue_2_packets 84525446 > rx_queue_3_packets 107679699 > rx_queue_4_packets 27442172 > rx_queue_5_packets 38033947 > rx_queue_6_packets 17664248 > rx_queue_7_packets 13731407 > rx_queue_8_packets 1869081 > rx_queue_9_packets 1564940 > rx_queue_10_packets 5000550 > rx_queue_11_packets 5358344 > rx_queue_12_packets 5598815 > rx_queue_13_packets 5508204 > rx_queue_14_packets 2773449 > rx_queue_15_packets 2539626 > rx_queue_16_packets 30444701 > rx_queue_17_packets 1875836468 > rx_queue_18_packets 31240359 > rx_queue_19_packets 9905014 > rx_queue_20_packets 1947326460 > rx_queue_21_packets 44664553 > rx_queue_22_packets 4792314 > rx_queue_23_packets 43862206 > rx_queue_24_packets 141 > rx_queue_25_packets 97 > rx_queue_26_packets 73 > rx_queue_27_packets 176 > rx_queue_28_packets 158 > rx_queue_29_packets 191 > rx_queue_30_packets 93 > rx_queue_31_packets 318 > > And these are the counters after running iperf for 10s: > rx_queue_0_packets 16040037801 > rx_queue_1_packets 395655118 > rx_queue_2_packets 84872104 > rx_queue_3_packets 108026357 > rx_queue_4_packets 27442172 > rx_queue_5_packets 38033947 > rx_queue_6_packets 18011252 > rx_queue_7_packets 14079046 > rx_queue_8_packets 1869092 > rx_queue_9_packets 1738441 > rx_queue_10_packets 5347208 > rx_queue_11_packets 5531673 > rx_queue_12_packets 5598815 > rx_queue_13_packets 5508204 > rx_queue_14_packets 3120599 > rx_queue_15_packets 2886331 > rx_queue_16_packets 30444701 > rx_queue_17_packets 1875836468 > rx_queue_18_packets 31240359 > rx_queue_19_packets 9905014 > rx_queue_20_packets 1947326460 > rx_queue_21_packets 44664553 > rx_queue_22_packets 4792314 > rx_queue_23_packets 43862206 > rx_queue_24_packets 141 > rx_queue_25_packets 97 > rx_queue_26_packets 73 > rx_queue_27_packets 176 > rx_queue_28_packets 158 > rx_queue_29_packets 191 > rx_queue_30_packets 93 > rx_queue_31_packets 318 > > As you can see traffic is nicely distributed to several queues. I have no rules > specified and nutple-filters=on for both servers. Is this RSS distributing the > traffic to different queues? > > Best wishes, > Jens > > > -- > Jens Auer | CGI | Software-Engineer > CGI (Germany) GmbH & Co. KG > Rheinstraße 95 | 64295 Darmstadt | Germany > T: +49 6151 36860 154 > jen...@cg...<mailto:jen...@cg...> > Unsere Pflichtangaben gemäß § 35a GmbHG / §§ 161, 125a HGB finden Sie > unter de.cgi.com/pflichtangaben<http://de.cgi.com/pflichtangaben>. > > CONFIDENTIALITY NOTICE: Proprietary/Confidential information belonging to > CGI Group Inc. and its affiliates may be contained in this message. If you are > not a recipient indicated or intended in this message (or responsible for > delivery of this message to such person), or you think for any reason that this > message may have been addressed to you in error, you may not use or copy or > deliver this message to anyone else. In such case, you should destroy this > message and are asked to notify the sender by reply e-mail. |
|
From: Auer, J. <jen...@cg...> - 2016-08-26 16:19:51
|
Hi, how does Perfect Filter (PF) work? According to the Readme, Perfect filter is an interface to load the filter table that funnels all flow into queue_0 unless an alternative queue is specified using "action". In that case, any flow that matches the filter criteria will be directed to the appropriate queue. >From this, I would expect that the counters in the NIC count only traffic in queue 0 when receiving packets. So I did a little experiment and captured the counters before and after sending some traffic with iperf. These are the counters before: rx_queue_0_packets 16039690804 rx_queue_1_packets 395308116 rx_queue_2_packets 84525446 rx_queue_3_packets 107679699 rx_queue_4_packets 27442172 rx_queue_5_packets 38033947 rx_queue_6_packets 17664248 rx_queue_7_packets 13731407 rx_queue_8_packets 1869081 rx_queue_9_packets 1564940 rx_queue_10_packets 5000550 rx_queue_11_packets 5358344 rx_queue_12_packets 5598815 rx_queue_13_packets 5508204 rx_queue_14_packets 2773449 rx_queue_15_packets 2539626 rx_queue_16_packets 30444701 rx_queue_17_packets 1875836468 rx_queue_18_packets 31240359 rx_queue_19_packets 9905014 rx_queue_20_packets 1947326460 rx_queue_21_packets 44664553 rx_queue_22_packets 4792314 rx_queue_23_packets 43862206 rx_queue_24_packets 141 rx_queue_25_packets 97 rx_queue_26_packets 73 rx_queue_27_packets 176 rx_queue_28_packets 158 rx_queue_29_packets 191 rx_queue_30_packets 93 rx_queue_31_packets 318 And these are the counters after running iperf for 10s: rx_queue_0_packets 16040037801 rx_queue_1_packets 395655118 rx_queue_2_packets 84872104 rx_queue_3_packets 108026357 rx_queue_4_packets 27442172 rx_queue_5_packets 38033947 rx_queue_6_packets 18011252 rx_queue_7_packets 14079046 rx_queue_8_packets 1869092 rx_queue_9_packets 1738441 rx_queue_10_packets 5347208 rx_queue_11_packets 5531673 rx_queue_12_packets 5598815 rx_queue_13_packets 5508204 rx_queue_14_packets 3120599 rx_queue_15_packets 2886331 rx_queue_16_packets 30444701 rx_queue_17_packets 1875836468 rx_queue_18_packets 31240359 rx_queue_19_packets 9905014 rx_queue_20_packets 1947326460 rx_queue_21_packets 44664553 rx_queue_22_packets 4792314 rx_queue_23_packets 43862206 rx_queue_24_packets 141 rx_queue_25_packets 97 rx_queue_26_packets 73 rx_queue_27_packets 176 rx_queue_28_packets 158 rx_queue_29_packets 191 rx_queue_30_packets 93 rx_queue_31_packets 318 As you can see traffic is nicely distributed to several queues. I have no rules specified and nutple-filters=on for both servers. Is this RSS distributing the traffic to different queues? Best wishes, Jens -- Jens Auer | CGI | Software-Engineer CGI (Germany) GmbH & Co. KG Rheinstraße 95 | 64295 Darmstadt | Germany T: +49 6151 36860 154 jen...@cg...<mailto:jen...@cg...> Unsere Pflichtangaben gemäß § 35a GmbHG / §§ 161, 125a HGB finden Sie unter de.cgi.com/pflichtangaben<http://de.cgi.com/pflichtangaben>. CONFIDENTIALITY NOTICE: Proprietary/Confidential information belonging to CGI Group Inc. and its affiliates may be contained in this message. If you are not a recipient indicated or intended in this message (or responsible for delivery of this message to such person), or you think for any reason that this message may have been addressed to you in error, you may not use or copy or deliver this message to anyone else. In such case, you should destroy this message and are asked to notify the sender by reply e-mail. |
|
From: Alexander D. <ale...@gm...> - 2016-08-26 14:26:21
|
On Fri, Aug 26, 2016 at 3:18 AM, Auer, Jens <jen...@cg...> wrote: > Hi, > > we are experiencing packet reordering and thus bandwidth drops due to retransmissions on our servers. We are using RedHat 7.2 on HP Servers connected to a HP Aruba 1920 10GB switch. I can easily reproduce the issues by running iperf3 between the two servers: <snipping out test results> > In this test, I get some retransmissions every couple of seconds. We analyzed the retransmissions by capturing a sample with Wireshark and we can confirm that the retransmissions are fast retransmissions caused by reordering of the traffic at the receiving server only. > > I have found a description of problems caused by Flow Director and migrating processes from Fermilab (https://arxiv.org/pdf/1106.0443.pdf) together with a support case at RedHat (https://access.redhat.com/solutions/2403071). What is offical position concerning this issue? Is it considered as bug? > > The RedHat case recommends to either switch to Perfect Filtering or fix CPU assignment of processes. I have tried both solutions, but the first one still produces retransmissions even when pinning both iperf processes to a fixed CPU: <snipping out some more test results> > > Switching to Perfect Forwarding mode fixed the problems and iperf runs without retransmissions. Are there other factors that can cause retransmissions, e.g. irq balancing at the receiver? > > Best wishes, > Jens Hi Jens, The main cause of the reordering is likely the ATR feature on the adapter. What ATR does is try to redirect all Rx traffic for a given flow back to the same Tx queue that the flow was received on. When combined with XPS which aligns the Tx queue selection with the CPU that the transmitting application is scheduled on this can lead to reordering. The reordering is due to the fact that the scheduler will move flows back and forth between CPUs. This in turn can lead to reordering if either the scheduler moves the application between CPUs or the IRQ balancing moves the Rx queue to a new CPU which leads to possible bouncing if acknowledgements are generated by the stack on a different CPU from the transmissions. On additional cause for possible issues is if you are running flows with a high connection rate. The filter table used for ATR has a limited amount of space available and if the table overflows it will cause the contents to be flushed. This also can lead to reordering related to ATR. Hope this helps to clarify some of what is going on. - Alex |
|
From: Auer, J. <jen...@cg...> - 2016-08-26 10:51:43
|
Hi, we are experiencing packet reordering and thus bandwidth drops due to retransmissions on our servers. We are using RedHat 7.2 on HP Servers connected to a HP Aruba 1920 10GB switch. I can easily reproduce the issues by running iperf3 between the two servers: iperf3 -c 192.168.120.11 -p 12345 -b200m -P20 -t0 Connecting to host 192.168.120.11, port 12345 [ 4] local 192.168.120.10 port 59638 connected to 192.168.120.11 port 12345 [ 6] local 192.168.120.10 port 59640 connected to 192.168.120.11 port 12345 [ 8] local 192.168.120.10 port 59642 connected to 192.168.120.11 port 12345 [ 10] local 192.168.120.10 port 59644 connected to 192.168.120.11 port 12345 [ 12] local 192.168.120.10 port 59646 connected to 192.168.120.11 port 12345 [ 14] local 192.168.120.10 port 59648 connected to 192.168.120.11 port 12345 [ 16] local 192.168.120.10 port 59650 connected to 192.168.120.11 port 12345 [ 18] local 192.168.120.10 port 59652 connected to 192.168.120.11 port 12345 [ 20] local 192.168.120.10 port 59654 connected to 192.168.120.11 port 12345 [ 22] local 192.168.120.10 port 59656 connected to 192.168.120.11 port 12345 [ 24] local 192.168.120.10 port 59658 connected to 192.168.120.11 port 12345 [ 26] local 192.168.120.10 port 59660 connected to 192.168.120.11 port 12345 [ 28] local 192.168.120.10 port 59662 connected to 192.168.120.11 port 12345 [ 30] local 192.168.120.10 port 59664 connected to 192.168.120.11 port 12345 [ 32] local 192.168.120.10 port 59666 connected to 192.168.120.11 port 12345 [ 34] local 192.168.120.10 port 59668 connected to 192.168.120.11 port 12345 [ 36] local 192.168.120.10 port 59670 connected to 192.168.120.11 port 12345 [ 38] local 192.168.120.10 port 59672 connected to 192.168.120.11 port 12345 [ 40] local 192.168.120.10 port 59674 connected to 192.168.120.11 port 12345 [ 42] local 192.168.120.10 port 59676 connected to 192.168.120.11 port 12345 [ ID] Interval Transfer Bandwidth Retr Cwnd [ 4] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 2 225 KBytes [ 6] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 1 202 KBytes [ 8] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 8 225 KBytes [ 10] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 2 132 KBytes [ 12] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 2 133 KBytes [ 14] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 2 132 KBytes [ 16] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 12 165 KBytes [ 18] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 2 151 KBytes [ 20] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 1 150 KBytes [ 22] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 4 225 KBytes [ 24] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 5 143 KBytes [ 26] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 3 132 KBytes [ 28] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 3 126 KBytes [ 30] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 1 127 KBytes [ 32] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 6 136 KBytes [ 34] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 2 139 KBytes [ 36] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 1 154 KBytes [ 38] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 1 136 KBytes [ 40] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 2 122 KBytes [ 42] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 4 139 KBytes [SUM] 0.00-1.00 sec 438 MBytes 3.67 Gbits/sec 64 - - - - - - - - - - - - - - - - - - - - - - - - - [ 4] 1.00-2.00 sec 24.0 MBytes 201 Mbits/sec 0 255 KBytes [ 6] 1.00-2.00 sec 24.0 MBytes 201 Mbits/sec 0 243 KBytes [ 8] 1.00-2.00 sec 24.0 MBytes 201 Mbits/sec 0 256 KBytes [ 10] 1.00-2.00 sec 24.0 MBytes 201 Mbits/sec 0 191 KBytes [ 12] 1.00-2.00 sec 24.0 MBytes 201 Mbits/sec 0 192 KBytes [ 14] 1.00-2.00 sec 24.0 MBytes 201 Mbits/sec 0 192 KBytes [ 16] 1.00-2.00 sec 24.0 MBytes 201 Mbits/sec 0 216 KBytes [ 18] 1.00-2.00 sec 24.0 MBytes 201 Mbits/sec 0 208 KBytes [ 20] 1.00-2.00 sec 24.0 MBytes 201 Mbits/sec 0 205 KBytes [ 22] 1.00-2.00 sec 24.0 MBytes 201 Mbits/sec 0 259 KBytes [ 24] 1.00-2.00 sec 24.0 MBytes 201 Mbits/sec 0 202 KBytes [ 26] 1.00-2.00 sec 24.0 MBytes 201 Mbits/sec 0 198 KBytes [ 28] 1.00-2.00 sec 24.0 MBytes 201 Mbits/sec 0 191 KBytes [ 30] 1.00-2.00 sec 24.0 MBytes 201 Mbits/sec 0 192 KBytes [ 32] 1.00-2.00 sec 24.0 MBytes 201 Mbits/sec 0 201 KBytes [ 34] 1.00-2.00 sec 24.0 MBytes 201 Mbits/sec 0 198 KBytes [ 36] 1.00-2.00 sec 24.0 MBytes 201 Mbits/sec 0 211 KBytes [ 38] 1.00-2.00 sec 24.0 MBytes 201 Mbits/sec 0 198 KBytes [ 40] 1.00-2.00 sec 24.0 MBytes 201 Mbits/sec 0 194 KBytes [ 42] 1.00-2.00 sec 24.0 MBytes 201 Mbits/sec 0 198 KBytes [SUM] 1.00-2.00 sec 480 MBytes 4.03 Gbits/sec 0 - - - - - - - - - - - - - - - - - - - - - - - - - [ 4] 2.00-3.00 sec 23.8 MBytes 199 Mbits/sec 0 267 KBytes [ 6] 2.00-3.00 sec 23.8 MBytes 199 Mbits/sec 0 250 KBytes [ 8] 2.00-3.00 sec 23.8 MBytes 199 Mbits/sec 0 269 KBytes [ 10] 2.00-3.00 sec 23.8 MBytes 199 Mbits/sec 0 201 KBytes [ 12] 2.00-3.00 sec 23.8 MBytes 199 Mbits/sec 0 204 KBytes [ 14] 2.00-3.00 sec 23.8 MBytes 199 Mbits/sec 2 202 KBytes [ 16] 2.00-3.00 sec 23.8 MBytes 199 Mbits/sec 0 223 KBytes [ 18] 2.00-3.00 sec 23.8 MBytes 199 Mbits/sec 0 216 KBytes [ 20] 2.00-3.00 sec 23.8 MBytes 199 Mbits/sec 0 215 KBytes [ 22] 2.00-3.00 sec 23.8 MBytes 199 Mbits/sec 0 270 KBytes [ 24] 2.00-3.00 sec 23.8 MBytes 199 Mbits/sec 0 212 KBytes [ 26] 2.00-3.00 sec 23.8 MBytes 199 Mbits/sec 0 208 KBytes [ 28] 2.00-3.00 sec 23.8 MBytes 199 Mbits/sec 0 201 KBytes [ 30] 2.00-3.00 sec 23.8 MBytes 199 Mbits/sec 0 202 KBytes [ 32] 2.00-3.00 sec 23.8 MBytes 199 Mbits/sec 0 211 KBytes [ 34] 2.00-3.00 sec 23.8 MBytes 199 Mbits/sec 0 208 KBytes [ 36] 2.00-3.00 sec 23.8 MBytes 199 Mbits/sec 0 219 KBytes [ 38] 2.00-3.00 sec 23.8 MBytes 199 Mbits/sec 0 209 KBytes [ 40] 2.00-3.00 sec 23.8 MBytes 199 Mbits/sec 0 211 KBytes [ 42] 2.00-3.00 sec 23.8 MBytes 199 Mbits/sec 0 211 KBytes [SUM] 2.00-3.00 sec 475 MBytes 3.99 Gbits/sec 2 - - - - - - - - - - - - - - - - - - - - - - - - - [ 4] 3.00-4.00 sec 23.9 MBytes 200 Mbits/sec 5 205 KBytes [ 6] 3.00-4.00 sec 23.9 MBytes 200 Mbits/sec 0 260 KBytes [ 8] 3.00-4.00 sec 23.9 MBytes 200 Mbits/sec 0 276 KBytes [ 10] 3.00-4.00 sec 23.9 MBytes 200 Mbits/sec 0 221 KBytes [ 12] 3.00-4.00 sec 23.9 MBytes 200 Mbits/sec 0 225 KBytes [ 14] 3.00-4.00 sec 23.9 MBytes 200 Mbits/sec 0 221 KBytes [ 16] 3.00-4.00 sec 23.9 MBytes 200 Mbits/sec 0 243 KBytes [ 18] 3.00-4.00 sec 23.9 MBytes 200 Mbits/sec 0 230 KBytes [ 20] 3.00-4.00 sec 23.9 MBytes 200 Mbits/sec 0 229 KBytes [ 22] 3.00-4.00 sec 23.9 MBytes 200 Mbits/sec 0 281 KBytes [ 24] 3.00-4.00 sec 23.9 MBytes 200 Mbits/sec 0 233 KBytes [ 26] 3.00-4.00 sec 23.9 MBytes 200 Mbits/sec 0 226 KBytes [ 28] 3.00-4.00 sec 23.9 MBytes 200 Mbits/sec 0 222 KBytes [ 30] 3.00-4.00 sec 23.9 MBytes 200 Mbits/sec 0 218 KBytes [ 32] 3.00-4.00 sec 23.9 MBytes 200 Mbits/sec 0 232 KBytes [ 34] 3.00-4.00 sec 23.9 MBytes 200 Mbits/sec 0 229 KBytes [ 36] 3.00-4.00 sec 23.9 MBytes 200 Mbits/sec 0 239 KBytes [ 38] 3.00-4.00 sec 23.9 MBytes 200 Mbits/sec 0 229 KBytes [ 40] 3.00-4.00 sec 23.9 MBytes 200 Mbits/sec 0 226 KBytes [ 42] 3.00-4.00 sec 23.9 MBytes 200 Mbits/sec 0 225 KBytes [SUM] 3.00-4.00 sec 478 MBytes 4.00 Gbits/sec 5 - - - - - - - - - - - - - - - - - - - - - - - - - [ 4] 4.00-5.00 sec 23.8 MBytes 199 Mbits/sec 1 212 KBytes [ 6] 4.00-5.00 sec 23.8 MBytes 199 Mbits/sec 0 267 KBytes [ 8] 4.00-5.00 sec 23.8 MBytes 199 Mbits/sec 0 283 KBytes [ 10] 4.00-5.00 sec 23.8 MBytes 199 Mbits/sec 0 228 KBytes [ 12] 4.00-5.00 sec 23.8 MBytes 199 Mbits/sec 0 232 KBytes [ 14] 4.00-5.00 sec 23.8 MBytes 199 Mbits/sec 0 226 KBytes [ 16] 4.00-5.00 sec 23.8 MBytes 199 Mbits/sec 0 249 KBytes [ 18] 4.00-5.00 sec 23.8 MBytes 199 Mbits/sec 0 236 KBytes [ 20] 4.00-5.00 sec 23.8 MBytes 199 Mbits/sec 0 235 KBytes [ 22] 4.00-5.00 sec 23.8 MBytes 199 Mbits/sec 0 287 KBytes [ 24] 4.00-5.00 sec 23.8 MBytes 199 Mbits/sec 0 239 KBytes [ 26] 4.00-5.00 sec 23.8 MBytes 199 Mbits/sec 0 233 KBytes [ 28] 4.00-5.00 sec 23.8 MBytes 199 Mbits/sec 0 230 KBytes [ 30] 4.00-5.00 sec 23.8 MBytes 199 Mbits/sec 0 232 KBytes [ 32] 4.00-5.00 sec 23.8 MBytes 199 Mbits/sec 0 238 KBytes [ 34] 4.00-5.00 sec 23.8 MBytes 199 Mbits/sec 0 236 KBytes [ 36] 4.00-5.00 sec 23.8 MBytes 199 Mbits/sec 0 247 KBytes [ 38] 4.00-5.00 sec 23.8 MBytes 199 Mbits/sec 0 238 KBytes [ 40] 4.00-5.00 sec 23.8 MBytes 199 Mbits/sec 0 233 KBytes [ 42] 4.00-5.00 sec 23.8 MBytes 199 Mbits/sec 0 232 KBytes [SUM] 4.00-5.00 sec 475 MBytes 3.99 Gbits/sec 1 ^C- - - - - - - - - - - - - - - - - - - - - - - - - [ 4] 5.00-5.32 sec 9.50 MBytes 251 Mbits/sec 0 212 KBytes [ 6] 5.00-5.32 sec 9.50 MBytes 251 Mbits/sec 0 267 KBytes [ 8] 5.00-5.32 sec 9.50 MBytes 251 Mbits/sec 0 283 KBytes [ 10] 5.00-5.32 sec 9.50 MBytes 251 Mbits/sec 0 228 KBytes [ 12] 5.00-5.32 sec 9.50 MBytes 251 Mbits/sec 0 232 KBytes [ 14] 5.00-5.32 sec 9.50 MBytes 251 Mbits/sec 0 226 KBytes [ 16] 5.00-5.32 sec 9.50 MBytes 251 Mbits/sec 0 249 KBytes [ 18] 5.00-5.32 sec 9.50 MBytes 251 Mbits/sec 0 236 KBytes [ 20] 5.00-5.32 sec 9.50 MBytes 251 Mbits/sec 0 235 KBytes [ 22] 5.00-5.32 sec 9.50 MBytes 251 Mbits/sec 0 287 KBytes [ 24] 5.00-5.32 sec 9.50 MBytes 251 Mbits/sec 0 239 KBytes [ 26] 5.00-5.32 sec 9.50 MBytes 251 Mbits/sec 0 233 KBytes [ 28] 5.00-5.32 sec 9.50 MBytes 251 Mbits/sec 0 230 KBytes [ 30] 5.00-5.32 sec 9.50 MBytes 251 Mbits/sec 0 232 KBytes [ 32] 5.00-5.32 sec 9.50 MBytes 251 Mbits/sec 0 238 KBytes [ 34] 5.00-5.32 sec 9.50 MBytes 251 Mbits/sec 0 236 KBytes [ 36] 5.00-5.32 sec 9.50 MBytes 251 Mbits/sec 0 247 KBytes [ 38] 5.00-5.32 sec 9.50 MBytes 251 Mbits/sec 0 238 KBytes [ 40] 5.00-5.32 sec 9.50 MBytes 251 Mbits/sec 0 233 KBytes [ 42] 5.00-5.32 sec 9.50 MBytes 251 Mbits/sec 0 232 KBytes [SUM] 5.00-5.32 sec 190 MBytes 5.02 Gbits/sec 0 - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 8 sender [ 4] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 6] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 1 sender [ 6] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 8] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 8 sender [ 8] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 10] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 2 sender [ 10] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 12] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 2 sender [ 12] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 14] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 4 sender [ 14] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 16] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 12 sender [ 16] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 18] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 2 sender [ 18] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 20] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 1 sender [ 20] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 22] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 4 sender [ 22] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 24] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 5 sender [ 24] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 26] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 3 sender [ 26] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 28] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 3 sender [ 28] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 30] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 1 sender [ 30] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 32] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 6 sender [ 32] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 34] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 2 sender [ 34] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 36] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 1 sender [ 36] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 38] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 1 sender [ 38] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 40] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 2 sender [ 40] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 42] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 4 sender [ 42] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [SUM] 0.00-5.32 sec 2.48 GBytes 4.00 Gbits/sec 72 sender [SUM] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver iperf3: interrupt - the client has terminated In this test, I get some retransmissions every couple of seconds. We analyzed the retransmissions by capturing a sample with Wireshark and we can confirm that the retransmissions are fast retransmissions caused by reordering of the traffic at the receiving server only. I have found a description of problems caused by Flow Director and migrating processes from Fermilab (https://arxiv.org/pdf/1106.0443.pdf) together with a support case at RedHat (https://access.redhat.com/solutions/2403071). What is offical position concerning this issue? Is it considered as bug? The RedHat case recommends to either switch to Perfect Filtering or fix CPU assignment of processes. I have tried both solutions, but the first one still produces retransmissions even when pinning both iperf processes to a fixed CPU: taskset 0x1 iperf3 -s -p 12345 ----------------------------------------------------------- Server listening on 12345 ----------------------------------------------------------- Accepted connection from 192.168.120.10, port 59720 [ 5] local 192.168.120.11 port 12345 connected to 192.168.120.10 port 59722 [ 7] local 192.168.120.11 port 12345 connected to 192.168.120.10 port 59724 [ 9] local 192.168.120.11 port 12345 connected to 192.168.120.10 port 59726 [ 11] local 192.168.120.11 port 12345 connected to 192.168.120.10 port 59728 [ 13] local 192.168.120.11 port 12345 connected to 192.168.120.10 port 59730 [ 15] local 192.168.120.11 port 12345 connected to 192.168.120.10 port 59732 [ 17] local 192.168.120.11 port 12345 connected to 192.168.120.10 port 59734 [ 19] local 192.168.120.11 port 12345 connected to 192.168.120.10 port 59736 [ 21] local 192.168.120.11 port 12345 connected to 192.168.120.10 port 59738 [ 23] local 192.168.120.11 port 12345 connected to 192.168.120.10 port 59740 [ 25] local 192.168.120.11 port 12345 connected to 192.168.120.10 port 59742 [ 27] local 192.168.120.11 port 12345 connected to 192.168.120.10 port 59744 [ 29] local 192.168.120.11 port 12345 connected to 192.168.120.10 port 59746 [ 31] local 192.168.120.11 port 12345 connected to 192.168.120.10 port 59748 [ 33] local 192.168.120.11 port 12345 connected to 192.168.120.10 port 59750 [ 35] local 192.168.120.11 port 12345 connected to 192.168.120.10 port 59752 [ 37] local 192.168.120.11 port 12345 connected to 192.168.120.10 port 59754 [ 39] local 192.168.120.11 port 12345 connected to 192.168.120.10 port 59756 [ 41] local 192.168.120.11 port 12345 connected to 192.168.120.10 port 59758 [ 43] local 192.168.120.11 port 12345 connected to 192.168.120.10 port 59760 [ ID] Interval Transfer Bandwidth [ 5] 0.00-1.00 sec 21.8 MBytes 182 Mbits/sec [ 7] 0.00-1.00 sec 21.8 MBytes 182 Mbits/sec [ 9] 0.00-1.00 sec 21.8 MBytes 182 Mbits/sec [ 11] 0.00-1.00 sec 21.8 MBytes 182 Mbits/sec [ 13] 0.00-1.00 sec 21.8 MBytes 182 Mbits/sec [ 15] 0.00-1.00 sec 21.8 MBytes 182 Mbits/sec [ 17] 0.00-1.00 sec 21.8 MBytes 182 Mbits/sec [ 19] 0.00-1.00 sec 21.8 MBytes 182 Mbits/sec [ 21] 0.00-1.00 sec 21.8 MBytes 182 Mbits/sec [ 23] 0.00-1.00 sec 21.8 MBytes 182 Mbits/sec [ 25] 0.00-1.00 sec 21.8 MBytes 182 Mbits/sec [ 27] 0.00-1.00 sec 21.8 MBytes 182 Mbits/sec [ 29] 0.00-1.00 sec 21.8 MBytes 182 Mbits/sec [ 31] 0.00-1.00 sec 21.8 MBytes 182 Mbits/sec [ 33] 0.00-1.00 sec 21.8 MBytes 182 Mbits/sec [ 35] 0.00-1.00 sec 21.8 MBytes 182 Mbits/sec [ 37] 0.00-1.00 sec 21.8 MBytes 182 Mbits/sec [ 39] 0.00-1.00 sec 21.8 MBytes 182 Mbits/sec [ 41] 0.00-1.00 sec 21.8 MBytes 182 Mbits/sec [ 43] 0.00-1.00 sec 21.8 MBytes 182 Mbits/sec [SUM] 0.00-1.00 sec 435 MBytes 3.65 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ 5] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec [ 7] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec [ 9] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec [ 11] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec [ 13] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec [ 15] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec [ 17] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec [ 19] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec [ 21] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec [ 23] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec [ 25] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec [ 27] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec [ 29] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec [ 31] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec [ 33] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec [ 35] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec [ 37] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec [ 39] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec [ 41] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec [ 43] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec [SUM] 1.00-2.00 sec 478 MBytes 4.01 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ 5] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec [ 7] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec [ 9] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec [ 11] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec [ 13] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec [ 15] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec [ 17] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec [ 19] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec [ 21] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec [ 23] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec [ 25] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec [ 27] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec [ 29] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec [ 31] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec [ 33] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec [ 35] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec [ 37] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec [ 39] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec [ 41] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec [ 43] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec [SUM] 2.00-3.00 sec 478 MBytes 4.01 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ 5] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec [ 7] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec [ 9] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec [ 11] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec [ 13] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec [ 15] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec [ 17] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec [ 19] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec [ 21] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec [ 23] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec [ 25] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec [ 27] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec [ 29] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec [ 31] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec [ 33] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec [ 35] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec [ 37] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec [ 39] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec [ 41] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec [ 43] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec [SUM] 3.00-4.00 sec 475 MBytes 3.98 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ 5] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 7] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 9] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 11] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 13] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 15] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 17] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 19] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 21] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 23] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 25] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 27] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 29] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 31] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 33] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 35] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 37] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 39] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 41] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 43] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [SUM] 4.00-5.00 sec 478 MBytes 4.01 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ 5] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 7] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 9] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 11] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 13] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 15] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 17] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 19] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 21] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 23] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 25] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 27] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 29] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 31] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 33] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 35] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 37] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 39] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 41] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [ 43] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec [SUM] 4.00-5.00 sec 478 MBytes 4.01 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth [ 5] 0.00-5.00 sec 0.00 Bytes 0.00 bits/sec sender [ 5] 0.00-5.00 sec 125 MBytes 210 Mbits/sec receiver [ 7] 0.00-5.00 sec 0.00 Bytes 0.00 bits/sec sender [ 7] 0.00-5.00 sec 125 MBytes 210 Mbits/sec receiver [ 9] 0.00-5.00 sec 0.00 Bytes 0.00 bits/sec sender [ 9] 0.00-5.00 sec 125 MBytes 210 Mbits/sec receiver [ 11] 0.00-5.00 sec 0.00 Bytes 0.00 bits/sec sender [ 11] 0.00-5.00 sec 125 MBytes 210 Mbits/sec receiver [ 13] 0.00-5.00 sec 0.00 Bytes 0.00 bits/sec sender [ 13] 0.00-5.00 sec 125 MBytes 210 Mbits/sec receiver [ 15] 0.00-5.00 sec 0.00 Bytes 0.00 bits/sec sender [ 15] 0.00-5.00 sec 125 MBytes 210 Mbits/sec receiver [ 17] 0.00-5.00 sec 0.00 Bytes 0.00 bits/sec sender [ 17] 0.00-5.00 sec 125 MBytes 210 Mbits/sec receiver [ 19] 0.00-5.00 sec 0.00 Bytes 0.00 bits/sec sender [ 19] 0.00-5.00 sec 125 MBytes 210 Mbits/sec receiver [ 21] 0.00-5.00 sec 0.00 Bytes 0.00 bits/sec sender [ 21] 0.00-5.00 sec 125 MBytes 210 Mbits/sec receiver [ 23] 0.00-5.00 sec 0.00 Bytes 0.00 bits/sec sender [ 23] 0.00-5.00 sec 125 MBytes 210 Mbits/sec receiver [ 25] 0.00-5.00 sec 0.00 Bytes 0.00 bits/sec sender [ 25] 0.00-5.00 sec 125 MBytes 210 Mbits/sec receiver [ 27] 0.00-5.00 sec 0.00 Bytes 0.00 bits/sec sender [ 27] 0.00-5.00 sec 125 MBytes 210 Mbits/sec receiver [ 29] 0.00-5.00 sec 0.00 Bytes 0.00 bits/sec sender [ 29] 0.00-5.00 sec 125 MBytes 210 Mbits/sec receiver [ 31] 0.00-5.00 sec 0.00 Bytes 0.00 bits/sec sender [ 31] 0.00-5.00 sec 125 MBytes 210 Mbits/sec receiver [ 33] 0.00-5.00 sec 0.00 Bytes 0.00 bits/sec sender [ 33] 0.00-5.00 sec 125 MBytes 210 Mbits/sec receiver [ 35] 0.00-5.00 sec 0.00 Bytes 0.00 bits/sec sender [ 35] 0.00-5.00 sec 125 MBytes 210 Mbits/sec receiver [ 37] 0.00-5.00 sec 0.00 Bytes 0.00 bits/sec sender [ 37] 0.00-5.00 sec 125 MBytes 210 Mbits/sec receiver [ 39] 0.00-5.00 sec 0.00 Bytes 0.00 bits/sec sender [ 39] 0.00-5.00 sec 125 MBytes 210 Mbits/sec receiver [ 41] 0.00-5.00 sec 0.00 Bytes 0.00 bits/sec sender [ 41] 0.00-5.00 sec 125 MBytes 210 Mbits/sec receiver [ 43] 0.00-5.00 sec 0.00 Bytes 0.00 bits/sec sender [ 43] 0.00-5.00 sec 125 MBytes 210 Mbits/sec receiver [SUM] 0.00-5.00 sec 0.00 Bytes 0.00 bits/sec sender [SUM] 0.00-5.00 sec 2.45 GBytes 4.20 Gbits/sec receiver iperf3: the client has terminated taskset 0x1 iperf3 -c 192.168.120.11 -p 12345 -b200m -P20 -t0 Connecting to host 192.168.120.11, port 12345 [ 4] local 192.168.120.10 port 59722 connected to 192.168.120.11 port 12345 [ 6] local 192.168.120.10 port 59724 connected to 192.168.120.11 port 12345 [ 8] local 192.168.120.10 port 59726 connected to 192.168.120.11 port 12345 [ 10] local 192.168.120.10 port 59728 connected to 192.168.120.11 port 12345 [ 12] local 192.168.120.10 port 59730 connected to 192.168.120.11 port 12345 [ 14] local 192.168.120.10 port 59732 connected to 192.168.120.11 port 12345 [ 16] local 192.168.120.10 port 59734 connected to 192.168.120.11 port 12345 [ 18] local 192.168.120.10 port 59736 connected to 192.168.120.11 port 12345 [ 20] local 192.168.120.10 port 59738 connected to 192.168.120.11 port 12345 [ 22] local 192.168.120.10 port 59740 connected to 192.168.120.11 port 12345 [ 24] local 192.168.120.10 port 59742 connected to 192.168.120.11 port 12345 [ 26] local 192.168.120.10 port 59744 connected to 192.168.120.11 port 12345 [ 28] local 192.168.120.10 port 59746 connected to 192.168.120.11 port 12345 [ 30] local 192.168.120.10 port 59748 connected to 192.168.120.11 port 12345 [ 32] local 192.168.120.10 port 59750 connected to 192.168.120.11 port 12345 [ 34] local 192.168.120.10 port 59752 connected to 192.168.120.11 port 12345 [ 36] local 192.168.120.10 port 59754 connected to 192.168.120.11 port 12345 [ 38] local 192.168.120.10 port 59756 connected to 192.168.120.11 port 12345 [ 40] local 192.168.120.10 port 59758 connected to 192.168.120.11 port 12345 [ 42] local 192.168.120.10 port 59760 connected to 192.168.120.11 port 12345 [ ID] Interval Transfer Bandwidth Retr Cwnd [ 4] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 7 189 KBytes [ 6] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 7 122 KBytes [ 8] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 1 134 KBytes [ 10] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 0 158 KBytes [ 12] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 2 130 KBytes [ 14] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 1 168 KBytes [ 16] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 5 133 KBytes [ 18] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 0 181 KBytes [ 20] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 1 132 KBytes [ 22] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 5 129 KBytes [ 24] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 4 132 KBytes [ 26] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 4 133 KBytes [ 28] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 2 127 KBytes [ 30] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 0 173 KBytes [ 32] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 9 132 KBytes [ 34] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 3 130 KBytes [ 36] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 4 136 KBytes [ 38] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 1 130 KBytes [ 40] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 0 168 KBytes [ 42] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec 6 127 KBytes [SUM] 0.00-1.00 sec 438 MBytes 3.67 Gbits/sec 62 - - - - - - - - - - - - - - - - - - - - - - - - - [ 4] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec 0 189 KBytes [ 6] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec 0 130 KBytes [ 8] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec 0 134 KBytes [ 10] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec 0 158 KBytes [ 12] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec 0 134 KBytes [ 14] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec 0 168 KBytes [ 16] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec 3 148 KBytes [ 18] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec 0 191 KBytes [ 20] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec 0 141 KBytes [ 22] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec 0 143 KBytes [ 24] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec 0 134 KBytes [ 26] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec 0 139 KBytes [ 28] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec 0 129 KBytes [ 30] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec 1 173 KBytes [ 32] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec 0 133 KBytes [ 34] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec 0 141 KBytes [ 36] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec 0 137 KBytes [ 38] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec 0 141 KBytes [ 40] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec 0 168 KBytes [ 42] 1.00-2.00 sec 23.9 MBytes 200 Mbits/sec 0 133 KBytes [SUM] 1.00-2.00 sec 478 MBytes 4.01 Gbits/sec 4 - - - - - - - - - - - - - - - - - - - - - - - - - [ 4] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec 0 189 KBytes [ 6] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec 0 130 KBytes [ 8] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec 0 134 KBytes [ 10] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec 0 158 KBytes [ 12] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec 0 134 KBytes [ 14] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec 0 168 KBytes [ 16] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec 0 151 KBytes [ 18] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec 0 211 KBytes [ 20] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec 0 157 KBytes [ 22] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec 0 157 KBytes [ 24] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec 0 137 KBytes [ 26] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec 0 147 KBytes [ 28] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec 4 129 KBytes [ 30] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec 0 173 KBytes [ 32] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec 0 133 KBytes [ 34] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec 0 143 KBytes [ 36] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec 0 137 KBytes [ 38] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec 0 144 KBytes [ 40] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec 0 168 KBytes [ 42] 2.00-3.00 sec 23.9 MBytes 200 Mbits/sec 0 136 KBytes [SUM] 2.00-3.00 sec 478 MBytes 4.01 Gbits/sec 4 - - - - - - - - - - - - - - - - - - - - - - - - - [ 4] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec 0 189 KBytes [ 6] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec 0 130 KBytes [ 8] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec 0 134 KBytes [ 10] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec 0 158 KBytes [ 12] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec 0 134 KBytes [ 14] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec 0 168 KBytes [ 16] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec 1 156 KBytes [ 18] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec 2 223 KBytes [ 20] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec 0 163 KBytes [ 22] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec 0 165 KBytes [ 24] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec 0 139 KBytes [ 26] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec 0 154 KBytes [ 28] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec 0 130 KBytes [ 30] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec 0 173 KBytes [ 32] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec 0 134 KBytes [ 34] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec 0 150 KBytes [ 36] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec 0 137 KBytes [ 38] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec 0 151 KBytes [ 40] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec 0 168 KBytes [ 42] 3.00-4.00 sec 23.8 MBytes 199 Mbits/sec 0 146 KBytes [SUM] 3.00-4.00 sec 475 MBytes 3.98 Gbits/sec 3 - - - - - - - - - - - - - - - - - - - - - - - - - [ 4] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec 0 189 KBytes [ 6] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec 0 130 KBytes [ 8] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec 0 134 KBytes [ 10] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec 1 158 KBytes [ 12] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec 0 134 KBytes [ 14] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec 0 168 KBytes [ 16] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec 1 161 KBytes [ 18] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec 0 223 KBytes [ 20] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec 0 174 KBytes [ 22] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec 0 175 KBytes [ 24] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec 0 139 KBytes [ 26] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec 0 154 KBytes [ 28] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec 0 132 KBytes [ 30] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec 0 173 KBytes [ 32] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec 0 134 KBytes [ 34] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec 0 150 KBytes [ 36] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec 0 137 KBytes [ 38] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec 0 151 KBytes [ 40] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec 0 168 KBytes [ 42] 4.00-5.00 sec 23.9 MBytes 200 Mbits/sec 0 146 KBytes [SUM] 4.00-5.00 sec 478 MBytes 4.01 Gbits/sec 2 ^C- - - - - - - - - - - - - - - - - - - - - - - - - [ 4] 5.00-5.32 sec 9.38 MBytes 248 Mbits/sec 0 189 KBytes [ 6] 5.00-5.32 sec 9.38 MBytes 248 Mbits/sec 0 130 KBytes [ 8] 5.00-5.32 sec 9.38 MBytes 248 Mbits/sec 0 134 KBytes [ 10] 5.00-5.32 sec 9.38 MBytes 248 Mbits/sec 0 158 KBytes [ 12] 5.00-5.32 sec 9.38 MBytes 248 Mbits/sec 0 140 KBytes [ 14] 5.00-5.32 sec 9.38 MBytes 248 Mbits/sec 0 168 KBytes [ 16] 5.00-5.32 sec 9.38 MBytes 248 Mbits/sec 0 164 KBytes [ 18] 5.00-5.32 sec 9.38 MBytes 248 Mbits/sec 0 223 KBytes [ 20] 5.00-5.32 sec 9.38 MBytes 248 Mbits/sec 0 174 KBytes [ 22] 5.00-5.32 sec 9.38 MBytes 248 Mbits/sec 0 175 KBytes [ 24] 5.00-5.32 sec 9.38 MBytes 248 Mbits/sec 0 139 KBytes [ 26] 5.00-5.32 sec 9.38 MBytes 248 Mbits/sec 0 154 KBytes [ 28] 5.00-5.32 sec 9.38 MBytes 248 Mbits/sec 0 132 KBytes [ 30] 5.00-5.32 sec 9.38 MBytes 248 Mbits/sec 0 173 KBytes [ 32] 5.00-5.32 sec 9.38 MBytes 248 Mbits/sec 0 134 KBytes [ 34] 5.00-5.32 sec 9.38 MBytes 248 Mbits/sec 0 150 KBytes [ 36] 5.00-5.32 sec 9.38 MBytes 248 Mbits/sec 0 137 KBytes [ 38] 5.00-5.32 sec 9.38 MBytes 248 Mbits/sec 0 151 KBytes [ 40] 5.00-5.32 sec 9.38 MBytes 248 Mbits/sec 0 168 KBytes [ 42] 5.00-5.32 sec 9.38 MBytes 248 Mbits/sec 0 146 KBytes [SUM] 5.00-5.32 sec 188 MBytes 4.96 Gbits/sec 0 - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 7 sender [ 4] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 6] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 7 sender [ 6] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 8] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 1 sender [ 8] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 10] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 1 sender [ 10] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 12] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 2 sender [ 12] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 14] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 1 sender [ 14] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 16] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 10 sender [ 16] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 18] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 2 sender [ 18] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 20] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 1 sender [ 20] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 22] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 5 sender [ 22] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 24] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 4 sender [ 24] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 26] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 4 sender [ 26] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 28] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 6 sender [ 28] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 30] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 1 sender [ 30] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 32] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 9 sender [ 32] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 34] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 3 sender [ 34] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 36] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 4 sender [ 36] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 38] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 1 sender [ 38] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 40] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 0 sender [ 40] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [ 42] 0.00-5.32 sec 127 MBytes 200 Mbits/sec 6 sender [ 42] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver [SUM] 0.00-5.32 sec 2.47 GBytes 3.99 Gbits/sec 75 sender [SUM] 0.00-5.32 sec 0.00 Bytes 0.00 bits/sec receiver iperf3: interrupt - the client has terminated Switching to Perfect Forwarding mode fixed the problems and iperf runs without retransmissions. Are there other factors that can cause retransmissions, e.g. irq balancing at the receiver? Best wishes, Jens -- Jens Auer | CGI | Software-Engineer CGI (Germany) GmbH & Co. KG Rheinstraße 95 | 64295 Darmstadt | Germany T: +49 6151 36860 154 jen...@cg...<mailto:jen...@cg...> Unsere Pflichtangaben gemäß § 35a GmbHG / §§ 161, 125a HGB finden Sie unter de.cgi.com/pflichtangaben<http://de.cgi.com/pflichtangaben>. CONFIDENTIALITY NOTICE: Proprietary/Confidential information belonging to CGI Group Inc. and its affiliates may be contained in this message. If you are not a recipient indicated or intended in this message (or responsible for delivery of this message to such person), or you think for any reason that this message may have been addressed to you in error, you may not use or copy or deliver this message to anyone else. In such case, you should destroy this message and are asked to notify the sender by reply e-mail. |
|
From: Newsletter <akt...@lc...> - 2016-08-25 07:43:17
|
Hallo! Wir freuen uns, dass du dich für unseren kostenlosen Newsletter entschieden hast. Ab deiner Eintragung bekommst du von uns regelmäßig, komplett kostenfrei, alle aktuellen News zu dem von dir gewählten Thema auf deine E-Mailadresse zugestellt. Schließe deine Eintragung ab indem du auf den untenstehenden Link klickst: http://rdr.lcp-prios.com/c/b431c69117cdee2fc838ad982000be669b7f5cb081e7bc4af9114e14add988668597a4ef4a7e69605ded80b76fd1ffb4?sToken=listcompanion Du hast deine Meinung geändert oder dich nicht selbst für unseren Dienst eingetragen? Kein Thema, in dem Fall brauchst du nichts weiter zu tun. Du erhältst von uns keine weiteren E-Mails. Dein Team von ListCompanion |
|
From: Passafaro - S. em A. <orc...@pa...> - 2016-08-24 14:19:22
|
Reservatórios Metálicos para Água, Combustível e Produtos Químicos
Solicite um Orçamento - Qualidade e Preço CompetitivoMONTAGEM IN LOCO COM AGILIDADE NA ENTREGA!
Ligue Grátis - 0800.052.1004 - orc...@pa...
RESERVATÓRIOS PARA ÁGUA
Reservatório com
Montagem no Local
Reservatório Modelo Tubular
Reservatório Modelo
Taça Coluna Cheia
Cisterna Metálica
Subterrânea para Tráfego
Cilindrico Vertical de
Fundo Cônico
Reservatório Modelo
Taça Coluna Seca
RESERVATÓRIOS PARA COMBUSTÍVEL
Tanque Aereo Horizontal
Tanque Jaquetado para Posto de Combustível
Módulo de Abastecimento para Frota de Veículos
ECONOMIZE DINHEIRO
Tendo seu Próprio Módulo de Abastecimento para Frota
TANQUES PARA POSTOS DE COMBUSTÍVEIS
CONHEÇA A PASSAFARO
WWW.PASSAFARO.COM.BR
Se você não deseja mais receber nossos e-mails, cancele sua inscrição através do link %{link} |
|
From: Fujinaka, T. <tod...@in...> - 2016-08-22 17:30:23
|
Forgot to reply back to the mailing list. Todd Fujinaka Software Application Engineer Networking Division (ND) Intel Corporation tod...@in... (503) 712-4565 -----Original Message----- From: Fujinaka, Todd Sent: Monday, August 22, 2016 9:03 AM To: Hasan Jamal <hj...@co...> Subject: RE: [E1000-devel] Ethernet driver 154b That's the basic device ID for a device with an unprogrammed NVM. You should contact whoever you purchased the device from for the proper tools and support. Todd Fujinaka Software Application Engineer Networking Division (ND) Intel Corporation tod...@in... (503) 712-4565 -----Original Message----- From: Hasan Jamal [mailto:hj...@co...] Sent: Monday, August 22, 2016 7:48 AM To: e10...@li... Subject: [E1000-devel] Ethernet driver 154b I'm wondering whether anyone could point to the right driver for the following Ethernet controller: Intel Corporation Device 154b (rev 01) Thanks, Hasan |
|
From: Camila C. <cam...@wo...> - 2016-08-22 16:49:45
|
Hello there, Might want to know whether you are keen on obtaining Nuxeo Red Herring Business Contacts for your marketing effort. Data Fields: Name, Title, Email, Phone Numbers, Company Name, and Company Details like Physical Address, Web Address, Revenue Size, Employee Size and industry. Specialties: Cost reduction, Benchmarking, Supplier management, Audits, Supplier consolidation, Tender services, Staff training, CSR reviews and many more... Please review and let me know your thoughts. Last Verification Date: 07/28/2016. Regards, Camila Carroll Sales Executive |
|
From: Hasan J. <hj...@co...> - 2016-08-22 14:48:33
|
I'm wondering whether anyone could point to the right driver for the following Ethernet controller: Intel Corporation Device 154b (rev 01) Thanks, Hasan |
|
From: Hartman, A. <Ala...@nc...> - 2016-08-18 15:05:08
|
Hello, I've been able to build the e1000e driver (version 3.3.5) that hopefully will work on my I219-LM motherboard. When I proceed to do the modprobe e1000e, I do not get any error messages from the modprobe command. However, dmesg contains the following: e1000e: Intel(r) PRO/1000 Network Driver - 3.3.5 e1000e: Copyright(c) 1999 2016 Intel Corporation. e1000e: 0000:00:1f:6 setting latency timer to 64 e1000e: probe of 0000:00:1f:6 failed with error -5 My Lan chip has vid/pid of 8086:15b7 and works fine under Windows. I was hoping for some sort of error information to help look for issue, but I can't seem to get any. Trying to add the "debug=xx" on the modprobe line doesn't get anything output. I'm assuming that this is a pretty beginner's type of error, but I'm unsure where to begin. Any beginning advice for debug? Thanks, Alan |
|
From: Vincent Li <vin...@gm...> - 2016-08-17 19:49:34
|
Hi Sorry if this is wrong list and please suggest proper list if you know :) I am running ixgbe SR-IOV in ubuntu 14.04.1 KVM server, pf is p2p1 and vf 0,1 assigned to guest with interface eth1 and ip 10.6.6.99. from another machine with ip 10.6.6.1, ping the guest ip and tcpdump on both p2p1 and guest eth1 interface, p2p1 only shows arp request, no arp reply and icmp packet, is this normal? how do I run tcpdump on KVM server to see all the packet between client and guest ? ---client 10.6.6.1 # ping 10.6.6.99 PING 10.6.6.99 (10.6.6.99) 56(84) bytes of data. 64 bytes from 10.6.6.99: icmp_seq=1 ttl=255 time=3.73 ms 64 bytes from 10.6.6.99: icmp_seq=2 ttl=255 time=1.75 ms 64 bytes from 10.6.6.99: icmp_seq=3 ttl=255 time=1.56 ms ----KVM server: (missing arp reply and icmp) # tcpdump -nn -i p2p1 host 10.6.6.99 and "icmp or arp" tcpdump: WARNING: p2p1: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on p2p1, link-type EN10MB (Ethernet), capture size 65535 bytes 12:31:31.490147 ARP, Request who-has 10.6.6.99 tell 10.6.6.1, length 46 ----guest 10.6.6.99 # tcpdump -nn -i eth1 host 10.6.6.99 and "icmp or arp" tcpdump: WARNING: eth1: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes 12:31:29.907498 ARP, Request who-has 10.6.6.99 tell 10.6.6.1, length 46 12:31:29.907854 ARP, Reply 10.6.6.99 is-at e6:83:ea:29:00:94, length 46 12:31:29.908379 IP 10.6.6.1 > 10.6.6.99: ICMP echo request, id 40201, seq 1, length 64 12:31:29.909708 IP 10.6.6.99 > 10.6.6.1: ICMP echo reply, id 40201, seq 1, length 64 12:31:30.907321 IP 10.6.6.1 > 10.6.6.99: ICMP echo request, id 40201, seq 2, length 64 12:31:30.908596 IP 10.6.6.99 > 10.6.6.1: ICMP echo reply, id 40201, seq 2, length 64 12:31:31.908118 IP 10.6.6.1 > 10.6.6.99: ICMP echo request, id 40201, seq 3, length 64 12:31:31.909225 IP 10.6.6.99 > 10.6.6.1: ICMP echo reply, id 40201, seq 3, length 64 |
|
From: Skidmore, D. C <don...@in...> - 2016-08-16 18:13:39
|
Hey Kevin, All I meant in the post you reference bellow is that ixgbe (not the driver that supports Fortville) does NOT support a zero init mode for unknown PHYs. I mention the reason for this in the post as well. We have never support such a mode and to my knowledge Fortville's driver doesn't either. However I don't work directly with that driver so will let others on the list more knowledgeable that I correct me if I'm wrong about that. :) Thanks, -Don Skidmore <don...@in...> > -----Original Message----- > From: Kevin Wilson [mailto:wk...@gm...] > Sent: Tuesday, August 16, 2016 10:39 AM > To: e10...@li... > Subject: [E1000-devel] Initializing Fortville nic in zero init mode > > Hi all, > > I had encountered in several places the "term zero" init in context of nics. > > Also in this mailing list I found this thread, in which the answer from Donald > Skidmore mentions zero init: > https://sourceforge.net/p/e1000/mailman/message/34745380/ > > My question is: I have an XL710 nic (Fortville). In practical terms, how do I > initialize the adapter in zero init mode ? > > and what does zero init mode means, in context of Network Interface Cards ? > > Regards, > Kevin > > ------------------------------------------------------------------------------ > _______________________________________________ > E1000-devel mailing list > E10...@li... > https://lists.sourceforge.net/lists/listinfo/e1000-devel > To learn more about Intel® Ethernet, visit > http://communities.intel.com/community/wired |
|
From: Fujinaka, T. <tod...@in...> - 2016-08-16 17:58:15
|
"Zero init mode" refers to a setting in an internal tool we have that is only released under NDA. If you have an FAE, please contact them for more information instead of the public mailing list. Otherwise, "zero init mode" shouldn't mean anything special and you're just quoting Don out of context. Todd Fujinaka Software Application Engineer Networking Division (ND) Intel Corporation tod...@in... (503) 712-4565 -----Original Message----- From: Kevin Wilson [mailto:wk...@gm...] Sent: Tuesday, August 16, 2016 10:39 AM To: e10...@li... Subject: [E1000-devel] Initializing Fortville nic in zero init mode Hi all, I had encountered in several places the "term zero" init in context of nics. Also in this mailing list I found this thread, in which the answer from Donald Skidmore mentions zero init: https://sourceforge.net/p/e1000/mailman/message/34745380/ My question is: I have an XL710 nic (Fortville). In practical terms, how do I initialize the adapter in zero init mode ? and what does zero init mode means, in context of Network Interface Cards ? Regards, Kevin ------------------------------------------------------------------------------ _______________________________________________ E1000-devel mailing list E10...@li... https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired |
|
From: Kevin W. <wk...@gm...> - 2016-08-16 17:39:37
|
Hi all, I had encountered in several places the "term zero" init in context of nics. Also in this mailing list I found this thread, in which the answer from Donald Skidmore mentions zero init: https://sourceforge.net/p/e1000/mailman/message/34745380/ My question is: I have an XL710 nic (Fortville). In practical terms, how do I initialize the adapter in zero init mode ? and what does zero init mode means, in context of Network Interface Cards ? Regards, Kevin |
|
From: gaven <gav...@xi...> - 2016-08-15 09:32:51
|
你好，Dear valued clients,我们是一家专业从事人造饰品的生产厂家，有生产外贸饰品十多年的经验，Our company is specialized in designing and manufacturing fashion jewelries and have more than ten years of experience in international trade. 公司位于落于中国浙江省义乌市稠州经济开发区，公司现有员工40个,生产基地员工近百人， Company is located in the fall in China zhejiang yiwu thick state economic development zone, the company existing staff 30, production staff of 120 people, 我厂主要以手工类饰品，环保合金类饰品为主，主要以欧美市场为主，Our factory mainly produce hand-made and pewter jewelry and current target market are Europe and America.附件是我们生产过的一些款式图片，请参考。The attachment includes some of the styles we have produced.如有需要，我们可以不间断提供一系列其它款式给您选择，For innovation purposes, we can provide newly designed series of other styles and products for you to broaden your product types . 也可根据客人要求来样品制,或根据客人设计图纸安排出样，We are more than happy to create samples according to the requirements of your designs. 同时也可帮您代为采购一系列其它产品，如箱包，围巾，帽子,杂货.......等等,In addition, We can also assist our clients in their process of procurement to help them make the optimal purchase decisions based on our 17 years of manufacturing and sales experience. The product scale is sufficient enough for our clients to refer to, such as bags, scarves, hats, groceries, and so on. Product information and related market positioning could be sent as you required. 希望来电来人来厂参观.期待与您的合作.We sincerely welcome your calls and visits and look forward to cooperating with you in the near future. 祝好！Best regards,旭红饰品 Xu red act the role ofing is tastedQQ: 354228523 or 798996345Gaven 15858933387 yoyo 18867967715 E-mail:.gav...@xi... yoy...@xi... |
3 messages has been excluded from this view by a project administrator.
