From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: Magnus Karlsson <magnus.karlsson@gmail.com>
Cc: "Alexei Starovoitov" <alexei.starovoitov@gmail.com>,
"Magnus Karlsson" <magnus.karlsson@intel.com>,
"Björn Töpel" <bjorn.topel@intel.com>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Network Development" <netdev@vger.kernel.org>,
bpf@vger.kernel.org, "Jonathan Lemon" <bsd@fb.com>,
"Maciej Fijalkowski" <maciejromanfijalkowski@gmail.com>,
"Samudrala, Sridhar" <sridhar.samudrala@intel.com>
Subject: Re: [RFC bpf-next 0/7] busy poll support for AF_XDP sockets
Date: Fri, 17 May 2019 11:20:03 -0700 [thread overview]
Message-ID: <20190517112003.02b130b2@cakuba.netronome.com> (raw)
In-Reply-To: <CAJ8uoz1i72MOk711wLX18zmgo9JS+ztzSYAx0YS0VKxkbvod-w@mail.gmail.com>
On Thu, 16 May 2019 14:37:51 +0200, Magnus Karlsson wrote:
> Applications
> method cores irqs txpush rxdrop l2fwd
> ---------------------------------------------------------------
> r-t-c 2 y 35.9 11.2 8.6
> poll 2 y 34.2 9.4 8.3
> r-t-c 1 y 18.1 N/A 6.2
> poll 1 y 14.6 8.4 5.9
> busypoll 2 y 31.9 10.5 7.9
> busypoll 1 y 21.5 8.7 6.2
> busypoll 1 n 22.0 10.3 7.3
Thanks for the numbers! One question that keeps coming to my mind
is how do the cases compare on zero drop performance?
When I was experimenting with AF_XDP it seemed to be slightly more
prone to dropping packets than expected. I wonder if you're seeing
a similar thing (well drops or back pressure to the traffic generator)?
Perhaps the single core busy poll would make a difference there?
next prev parent reply other threads:[~2019-05-17 18:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 8:39 [RFC bpf-next 0/7] busy poll support for AF_XDP sockets Magnus Karlsson
2019-05-02 8:39 ` [RFC bpf-next 1/7] net: fs: make busy poll budget configurable in napi_busy_loop Magnus Karlsson
2019-05-02 8:39 ` [RFC bpf-next 2/7] net: i40e: ixgbe: tun: veth: virtio-net: centralize xdp_rxq_info and add napi id Magnus Karlsson
2019-05-02 8:39 ` [RFC bpf-next 4/7] netdevice: introduce busy-poll setsockopt for AF_XDP Magnus Karlsson
2019-05-03 0:13 ` Samudrala, Sridhar
2019-05-03 6:35 ` Magnus Karlsson
2019-05-02 8:39 ` [RFC bpf-next 5/7] net: add busy-poll support for XDP sockets Magnus Karlsson
2019-05-03 0:23 ` Samudrala, Sridhar
2019-05-02 8:39 ` [RFC bpf-next 6/7] libbpf: add busy-poll support to " Magnus Karlsson
2019-05-02 8:39 ` [RFC bpf-next 7/7] samples/bpf: add busy-poll support to xdpsock sample Magnus Karlsson
2019-05-24 2:51 ` Ye Xiaolong
2019-05-27 6:58 ` Magnus Karlsson
2019-05-06 16:31 ` [RFC bpf-next 0/7] busy poll support for AF_XDP sockets Alexei Starovoitov
2019-05-07 11:51 ` Magnus Karlsson
2019-05-07 18:24 ` Alexei Starovoitov
2019-05-08 12:10 ` Magnus Karlsson
2019-05-16 12:37 ` Magnus Karlsson
2019-05-16 23:50 ` Samudrala, Sridhar
2019-05-17 7:50 ` Magnus Karlsson
2019-05-17 18:20 ` Jakub Kicinski [this message]
2019-05-18 8:49 ` Magnus Karlsson
2019-05-13 20:42 ` Jonathan Lemon
2019-05-13 23:30 ` Samudrala, Sridhar
2019-05-14 7:53 ` Björn Töpel
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=20190517112003.02b130b2@cakuba.netronome.com \
--to=jakub.kicinski@netronome.com \
--cc=alexei.starovoitov@gmail.com \
--cc=bjorn.topel@intel.com \
--cc=bpf@vger.kernel.org \
--cc=bsd@fb.com \
--cc=daniel@iogearbox.net \
--cc=maciejromanfijalkowski@gmail.com \
--cc=magnus.karlsson@gmail.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--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).