From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: "Samudrala\, Sridhar" <sridhar.samudrala@intel.com>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: "Karlsson, Magnus" <magnus.karlsson@intel.com>,
"Björn Töpel" <bjorn.topel@intel.com>,
Netdev <netdev@vger.kernel.org>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
intel-wired-lan <intel-wired-lan@lists.osuosl.org>,
"Fijalkowski, Maciej" <maciej.fijalkowski@intel.com>,
"Herbert, Tom" <tom.herbert@intel.com>
Subject: Re: FW: [PATCH bpf-next 2/4] xsk: allow AF_XDP sockets to receive packets directly from a queue
Date: Fri, 18 Oct 2019 21:22:52 +0200 [thread overview]
Message-ID: <87wod1dfjn.fsf@toke.dk> (raw)
In-Reply-To: <acf69635-5868-f876-f7da-08954d1f690e@intel.com>
"Samudrala, Sridhar" <sridhar.samudrala@intel.com> writes:
> Performance Results
> ===================
> Only 1 core is used in all these testcases as the app and the queue irq are pinned to the same core.
>
> ----------------------------------------------------------------------------------
> mitigations ON mitigations OFF
> Testcase ----------------------------------------------------------
> no patches with patches no patches with patches
> ----------------------------------------------------------------------------------
> AF_XDP default rxdrop X X Y Y
Is this really exactly the same with and without patches? You're adding
an extra check to xdp_do_redirect(); are you really saying that the
impact of that is zero?
> AF_XDP direct rxdrop N/A X+46% N/A Y+25%
> Kernel rxdrop X+61% X+61% Y+53% Y+53%
> ----------------------------------------------------------------------------------
>
> Here Y is pps with CPU security mitigations turned OFF and it is 26%
> better than X.
Any particular reason you're not sharing the values of X and Y?
-Toke
next prev parent reply other threads:[~2019-10-18 19:23 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 6:16 [PATCH bpf-next 0/4] Enable direct receive on AF_XDP sockets Sridhar Samudrala
2019-10-08 6:16 ` [PATCH bpf-next 1/4] bpf: introduce bpf_get_prog_id and bpf_set_prog_id helper functions Sridhar Samudrala
2019-10-08 6:16 ` [PATCH bpf-next 2/4] xsk: allow AF_XDP sockets to receive packets directly from a queue Sridhar Samudrala
2019-10-08 6:58 ` Toke Høiland-Jørgensen
2019-10-08 8:47 ` Björn Töpel
2019-10-08 8:48 ` Björn Töpel
2019-10-08 9:04 ` Toke Høiland-Jørgensen
2019-10-08 8:05 ` Björn Töpel
2019-10-09 16:32 ` Samudrala, Sridhar
2019-10-09 1:20 ` Alexei Starovoitov
[not found] ` <3ED8E928C4210A4289A677D2FEB48235140134CE@fmsmsx111.amr.corp.intel.com>
2019-10-09 16:53 ` FW: " Samudrala, Sridhar
2019-10-09 17:17 ` Alexei Starovoitov
2019-10-09 19:12 ` Samudrala, Sridhar
2019-10-10 1:06 ` Alexei Starovoitov
2019-10-18 18:40 ` Samudrala, Sridhar
2019-10-18 19:22 ` Toke Høiland-Jørgensen [this message]
2019-10-19 0:14 ` Alexei Starovoitov
2019-10-19 0:45 ` Samudrala, Sridhar
2019-10-19 2:25 ` Alexei Starovoitov
2019-10-20 10:14 ` Toke Høiland-Jørgensen
2019-10-20 17:12 ` [Intel-wired-lan] " Björn Töpel
2019-10-21 20:10 ` Samudrala, Sridhar
2019-10-21 22:34 ` Alexei Starovoitov
2019-10-22 19:06 ` Samudrala, Sridhar
2019-10-23 17:42 ` Alexei Starovoitov
2019-10-24 18:12 ` Samudrala, Sridhar
2019-10-25 7:42 ` Björn Töpel
2019-10-31 22:38 ` Samudrala, Sridhar
2019-10-31 23:15 ` Alexei Starovoitov
2019-11-01 0:21 ` Jakub Kicinski
2019-11-01 18:31 ` Samudrala, Sridhar
2019-11-04 2:08 ` dan
2019-10-25 9:07 ` Björn Töpel
2019-10-08 6:16 ` [PATCH bpf-next 3/4] libbpf: handle AF_XDP sockets created with XDP_DIRECT bind flag Sridhar Samudrala
2019-10-08 8:05 ` Björn Töpel
2019-10-08 6:16 ` [PATCH bpf-next 4/4] xdpsock: add an option to create AF_XDP sockets in XDP_DIRECT mode Sridhar Samudrala
2019-10-08 8:05 ` Björn Töpel
2019-10-08 8:05 ` [PATCH bpf-next 0/4] Enable direct receive on AF_XDP sockets Björn Töpel
2019-10-09 16:19 ` Samudrala, Sridhar
2019-10-09 0:49 ` Jakub Kicinski
2019-10-09 6:29 ` Samudrala, Sridhar
2019-10-09 16:53 ` Jakub Kicinski
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=87wod1dfjn.fsf@toke.dk \
--to=toke@redhat.com \
--cc=alexei.starovoitov@gmail.com \
--cc=bjorn.topel@intel.com \
--cc=bpf@vger.kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jakub.kicinski@netronome.com \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=sridhar.samudrala@intel.com \
--cc=tom.herbert@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).