On Tue, Jan 14, 2020 at 03:52:50PM -0500, Ryan Goodfellow wrote: > On Tue, Jan 14, 2020 at 10:59:19AM +0100, Magnus Karlsson wrote: > > > > Just sent out a patch on the mailing list. Would be great if you could > > try it out. > > Thanks for the quick turnaround. I gave this patch a go, both in the bpf-next > tree and manually applied to the 5.5.0-rc3 branch I've been working with up to > this point. It does allow for allocating more memory, however packet > forwarding no longer works. I did not see any complaints from dmesg, but here > is an example iperf3 session from a client that worked before. > > ry@xd2:~$ iperf3 -c 10.1.0.2 > Connecting to host 10.1.0.2, port 5201 > [ 5] local 10.1.0.1 port 53304 connected to 10.1.0.2 port 5201 > [ ID] Interval Transfer Bitrate Retr Cwnd > [ 5] 0.00-1.00 sec 5.91 MBytes 49.5 Mbits/sec 2 1.41 KBytes > [ 5] 1.00-2.00 sec 0.00 Bytes 0.00 bits/sec 1 1.41 KBytes > [ 5] 2.00-3.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes > [ 5] 3.00-4.00 sec 0.00 Bytes 0.00 bits/sec 1 1.41 KBytes > [ 5] 4.00-5.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes > [ 5] 5.00-6.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes > [ 5] 6.00-7.00 sec 0.00 Bytes 0.00 bits/sec 1 1.41 KBytes > [ 5] 7.00-8.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes > [ 5] 8.00-9.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes > ^C[ 5] 10.00-139.77 sec 0.00 Bytes 0.00 bits/sec 4 1.41 KBytes > - - - - - - - - - - - - - - - - - - - - - - - - - > [ ID] Interval Transfer Bitrate Retr > [ 5] 0.00-139.77 sec 5.91 MBytes 355 Kbits/sec 9 sender > [ 5] 0.00-139.77 sec 0.00 Bytes 0.00 bits/sec receiver > iperf3: interrupt - the client has terminated > > I'll continue to investigate and report back with anything that I find. Interestingly I found this behavior to exist in the bpf-next tree independent of the patch being present. I also gave the 5.5.0-rc6 branch a try (without the patch) and packets forward OK. -- ~ ry
|