From mboxrd@z Thu Jan 1 00:00:00 1970 From: mans@mansr.com (=?iso-8859-1?Q?M=E5ns_Rullg=E5rd?=) Date: Thu, 03 Aug 2017 13:18:09 +0100 Subject: [RFC PATCH v2 0/2] nb8800 suspend/resume support In-Reply-To: <71dd7987-8c43-2548-5058-51a95658da71@free.fr> (Mason's message of "Wed, 2 Aug 2017 22:02:24 +0200") References: <33d1ab47-6098-5e3f-8a3c-f72626d07113@free.fr> <9e8e12b1-74e2-8323-ec16-eebda46b2a3d@free.fr> <6906dccf-bec9-0fc8-a34a-c39c05ada917@free.fr> <71dd7987-8c43-2548-5058-51a95658da71@free.fr> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Mason writes: > On 02/08/2017 19:31, Mason wrote: > >> # iperf3 -c 172.27.64.45 -u -b 950M >> Connecting to host 172.27.64.45, port 5201 >> [ 4] local 172.27.64.1 port 55533 connected to 172.27.64.45 port 5201 >> [ ID] Interval Transfer Bandwidth Total Datagrams >> [ 4] 0.00-1.00 sec 102 MBytes 858 Mbits/sec 13091 >> [ 4] 1.00-2.00 sec 114 MBytes 953 Mbits/sec 14541 > > 114 MB in 14541 packets => 7840 bytes per packet > Is iperf3 sending jumbo frames?? It's probably sending fragmented packets. -- M?ns Rullg?rd