From: Lukas Erlacher <erlacher@in.tum.de>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: No SO_BUSY_POLL for UDP?
Date: Wed, 18 Mar 2015 00:51:40 +0100 [thread overview]
Message-ID: <5508BE0C.7060103@in.tum.de> (raw)
In-Reply-To: <1426634401.11398.245.camel@edumazet-glaptop2.roam.corp.google.com>
On 03/18/2015 12:20 AM, Eric Dumazet wrote:
>
> busypoll should be available on _connected_ UDP sockets. Otherwise, we
> would have to look all RX queues of the NIC, not a single one.
>
> Try netperf -t UDP_RR -- -N -n
>
> -n Use the connected socket for UDP locally
> -N Use the connected socket for UDP remotely
>
> (Although I believe netserver->netperf is ignoring the -N option, that
> is a netperf bug)
>
> check with ss -a|grep udp
>
Thank you very much, I was missing that bit of info. With connected
sockets, busy polling works perfectly.
Best,
Lukas Erlacher
prev parent reply other threads:[~2015-03-17 23:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 22:26 No SO_BUSY_POLL for UDP? Lukas Erlacher
2015-03-17 23:20 ` Eric Dumazet
2015-03-17 23:51 ` Lukas Erlacher [this message]
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=5508BE0C.7060103@in.tum.de \
--to=erlacher@in.tum.de \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
/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).