netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: "Björn Töpel" <bjorn.topel@gmail.com>
Cc: netdev@vger.kernel.org, bpf@vger.kernel.org,
	bjorn.topel@intel.com, magnus.karlsson@intel.com, ast@kernel.org,
	daniel@iogearbox.net, maciej.fijalkowski@intel.com,
	sridhar.samudrala@intel.com, jesse.brandeburg@intel.com,
	qi.z.zhang@intel.com, edumazet@google.com,
	jonathan.lemon@gmail.com, maximmi@nvidia.com
Subject: Re: [PATCH bpf-next v3 00/10] Introduce preferred busy-polling
Date: Mon, 23 Nov 2020 16:14:12 -0800	[thread overview]
Message-ID: <20201123161412.363bfb30@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <20201119083024.119566-1-bjorn.topel@gmail.com>

On Thu, 19 Nov 2020 09:30:14 +0100 Björn Töpel wrote:
> Performance netperf UDP_RR:
> 
> Note that netperf UDP_RR is not a heavy traffic tests, and preferred
> busy-polling is not typically something we want to use here.
> 
>   $ echo 20 | sudo tee /proc/sys/net/core/busy_read
>   $ netperf -H 192.168.1.1 -l 30 -t UDP_RR -v 2 -- \
>       -o min_latency,mean_latency,max_latency,stddev_latency,transaction_rate
> 
> busy-polling blocking sockets:            12,13.33,224,0.63,74731.177
> 
> I hacked netperf to use non-blocking sockets and re-ran:
> 
> busy-polling non-blocking sockets:        12,13.46,218,0.72,73991.172
> prefer busy-polling non-blocking sockets: 12,13.62,221,0.59,73138.448
> 
> Using the preferred busy-polling mode does not impact performance.
> 
> The above tests was done for the 'ice' driver.

Any interest in this work form ADQ folks? I recall they were using
memcache with busy polling for their tests, it'd cool to see how much
this helps memcache on P99+ latency!

      parent reply	other threads:[~2020-11-24  0:14 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-19  8:30 [PATCH bpf-next v3 00/10] Introduce preferred busy-polling Björn Töpel
2020-11-19  8:30 ` [PATCH bpf-next v3 01/10] net: introduce " Björn Töpel
2020-11-24  0:04   ` Jakub Kicinski
2020-11-24  7:58     ` Björn Töpel
2020-11-24  0:11   ` Jakub Kicinski
2020-11-24  8:47     ` Björn Töpel
2020-11-24 16:21   ` Jakub Kicinski
2020-11-19  8:30 ` [PATCH bpf-next v3 02/10] net: add SO_BUSY_POLL_BUDGET socket option Björn Töpel
2020-11-24 16:21   ` Jakub Kicinski
2020-11-19  8:30 ` [PATCH bpf-next v3 03/10] xsk: add support for recvmsg() Björn Töpel
2020-11-25  6:55   ` Magnus Karlsson
2020-11-19  8:30 ` [PATCH bpf-next v3 04/10] xsk: check need wakeup flag in sendmsg() Björn Töpel
2020-11-25  7:16   ` Magnus Karlsson
2020-11-19  8:30 ` [PATCH bpf-next v3 05/10] xsk: add busy-poll support for {recv,send}msg() Björn Töpel
2020-11-25  7:58   ` Magnus Karlsson
2020-11-19  8:30 ` [PATCH bpf-next v3 06/10] xsk: propagate napi_id to XDP socket Rx path Björn Töpel
2020-11-25 14:47   ` Magnus Karlsson
2020-11-25 21:14   ` Michael S. Tsirkin
2021-09-29 18:33   ` kernel test robot
2021-09-30  6:04     ` Magnus Karlsson
2021-10-02  2:07       ` [kbuild-all] " Philip Li
2021-11-05 20:17   ` kernel test robot
2020-11-19  8:30 ` [PATCH bpf-next v3 07/10] samples/bpf: use recvfrom() in xdpsock/rxdrop Björn Töpel
2020-11-25  7:59   ` Magnus Karlsson
2020-11-19  8:30 ` [PATCH bpf-next v3 08/10] samples/bpf: use recvfrom() in xdpsock/l2fwd Björn Töpel
2020-11-25  8:00   ` Magnus Karlsson
2020-11-19  8:30 ` [PATCH bpf-next v3 09/10] samples/bpf: add busy-poll support to xdpsock Björn Töpel
2020-11-25  8:19   ` Magnus Karlsson
2020-11-19  8:30 ` [PATCH bpf-next v3 10/10] samples/bpf: add option to set the busy-poll budget Björn Töpel
2020-11-25  8:23   ` Magnus Karlsson
2020-11-23 13:31 ` [PATCH bpf-next v3 00/10] Introduce preferred busy-polling Björn Töpel
2020-11-23 23:54   ` Jakub Kicinski
2020-11-24  0:14 ` Jakub Kicinski [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=20201123161412.363bfb30@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
    --to=kuba@kernel.org \
    --cc=ast@kernel.org \
    --cc=bjorn.topel@gmail.com \
    --cc=bjorn.topel@intel.com \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=edumazet@google.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=jonathan.lemon@gmail.com \
    --cc=maciej.fijalkowski@intel.com \
    --cc=magnus.karlsson@intel.com \
    --cc=maximmi@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=qi.z.zhang@intel.com \
    --cc=sridhar.samudrala@intel.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).