[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Mon, 10 Oct 2016 19:41:23 +0000
From: "Chopra, Manish" <Manish.Chopra@...ium.com>
To: Eric Dumazet <eric.dumazet@...il.com>,
Rick Jones <rick.jones2@....com>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"maorg@...lanox.com" <maorg@...lanox.com>,
"tom@...bertland.com" <tom@...bertland.com>
Subject: RE: Accelerated receive flow steering (aRFS) for UDP
> -----Original Message-----
> From: Eric Dumazet [mailto:eric.dumazet@...il.com]
> Sent: Monday, October 10, 2016 10:38 PM
> To: Rick Jones <rick.jones2@....com>
> Cc: Chopra, Manish <Manish.Chopra@...ium.com>; netdev@...r.kernel.org;
> maorg@...lanox.com; tom@...bertland.com
> Subject: Re: Accelerated receive flow steering (aRFS) for UDP
>
> On Mon, 2016-10-10 at 09:23 -0700, Rick Jones wrote:
> > 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.
>
> Indeed, it looks better, thanks !
>
Thanks Eric and Rick. With this, problem got resolved now.
I do see flows getting steered for UDP packets now :-)
Powered by blists - more mailing lists