From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-d.ads.isi.edu ([128.9.180.199]:60945 "EHLO mail-d.ads.isi.edu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728844AbgAOBll (ORCPT ); Tue, 14 Jan 2020 20:41:41 -0500 Date: Tue, 14 Jan 2020 20:41:37 -0500 From: Ryan Goodfellow Subject: Re: zero-copy between interfaces Message-ID: <20200115014137.GA105434@smtp.ads.isi.edu> References: <14f9e1bf5c3a41dbaec53f83cb5f0564@isi.edu> <20200113151159.GB68570@smtp.ads.isi.edu> <20200114205250.GA85903@smtp.ads.isi.edu> MIME-Version: 1.0 In-Reply-To: <20200114205250.GA85903@smtp.ads.isi.edu> Sender: xdp-newbies-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline To: Magnus Karlsson Cc: "xdp-newbies@vger.kernel.org" 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: > >=20 > > Just sent out a patch on the mailing list. Would be great if you could > > try it out. >=20 > 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=20 > this point. It does allow for allocating more memory, however packet=20 > forwarding no longer works. I did not see any complaints from dmesg, but = here=20 > is an example iperf3 session from a client that worked before. >=20 > 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 sen= der > [ 5] 0.00-139.77 sec 0.00 Bytes 0.00 bits/sec recei= ver > iperf3: interrupt - the client has terminated >=20 > 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 independe= nt of the patch being present. I also gave the 5.5.0-rc6 branch a try (without the patch) and packets forw= ard OK. --=20 ~ ry