From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rick Jones Subject: Re: Accelerated receive flow steering (aRFS) for UDP Date: Mon, 10 Oct 2016 09:23:16 -0700 Message-ID: <844f9891-3b30-e5fa-720e-d20e4ea5d751@hpe.com> References: <1475883496.28155.270.camel@edumazet-glaptop3.roam.corp.google.com> <1476033293.28155.273.camel@edumazet-glaptop3.roam.corp.google.com> <1476052402.28155.277.camel@edumazet-glaptop3.roam.corp.google.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: "netdev@vger.kernel.org" , "maorg@mellanox.com" , "tom@herbertland.com" To: Eric Dumazet , "Chopra, Manish" Return-path: Received: from g2t2352.austin.hpe.com ([15.233.44.25]:58789 "EHLO g2t2352.austin.hpe.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752586AbcJJQXS (ORCPT ); Mon, 10 Oct 2016 12:23:18 -0400 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On 10/10/2016 09:08 AM, Rick Jones wrote: > On 10/09/2016 03:33 PM, Eric Dumazet wrote: >> OK, I am adding/CC Rick Jones, netperf author, since it seems a netperf >> bug, not a kernel one. >> >> I believe I already mentioned fact that "UDP_STREAM -- -N" was not doing >> a connect() on the receiver side. > > I can confirm that the receive side of the netperf omni path isn't > trying to connect UDP datagrams. I will see what I can put together. I've put something together and pushed it to the netperf top of trunk. It seems to have been successful on a quick loopback UDP_STREAM test. happy benchmarking, rick jones