From: Rick Jones <rick.jones2@hpe.com>
To: Eric Dumazet <eric.dumazet@gmail.com>,
"Chopra, Manish" <Manish.Chopra@cavium.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"maorg@mellanox.com" <maorg@mellanox.com>,
"tom@herbertland.com" <tom@herbertland.com>
Subject: Re: Accelerated receive flow steering (aRFS) for UDP
Date: Mon, 10 Oct 2016 09:23:16 -0700 [thread overview]
Message-ID: <844f9891-3b30-e5fa-720e-d20e4ea5d751@hpe.com> (raw)
In-Reply-To: <ed0f723c-5e66-6d23-086d-71744570700a@hpe.com>
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
next prev parent reply other threads:[~2016-10-10 16:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 22:55 Accelerated receive flow steering (aRFS) for UDP Chopra, Manish
2016-10-07 23:38 ` Eric Dumazet
2016-10-08 12:25 ` Chopra, Manish
2016-10-09 17:14 ` Eric Dumazet
2016-10-09 19:48 ` Chopra, Manish
2016-10-09 22:33 ` Eric Dumazet
2016-10-10 16:08 ` Rick Jones
2016-10-10 16:23 ` Rick Jones [this message]
2016-10-10 17:08 ` Eric Dumazet
2016-10-10 19:41 ` Chopra, Manish
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=844f9891-3b30-e5fa-720e-d20e4ea5d751@hpe.com \
--to=rick.jones2@hpe.com \
--cc=Manish.Chopra@cavium.com \
--cc=eric.dumazet@gmail.com \
--cc=maorg@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=tom@herbertland.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).