[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0b45793e-6172-9c07-5bdb-2dc99e58e375@intel.com>
Date: Tue, 10 Dec 2019 11:28:00 -0800
From: "Samudrala, Sridhar" <sridhar.samudrala@...el.com>
To: Björn Töpel <bjorn.topel@...il.com>,
netdev@...r.kernel.org, ast@...nel.org, daniel@...earbox.net
Cc: bpf@...r.kernel.org, magnus.karlsson@...il.com,
magnus.karlsson@...el.com, jonathan.lemon@...il.com,
ecree@...arflare.com, thoiland@...hat.com,
andrii.nakryiko@...il.com
Subject: Re: [PATCH bpf-next v3 0/6] Introduce the BPF dispatcher
On 12/9/2019 5:55 AM, Björn Töpel wrote:
> Overview
> ========
>
> This is the 4th iteration of the series that introduces the BPF
> dispatcher, which is a mechanism to avoid indirect calls.
Good to see the progress with getting a mechansism to avoid indirect calls
upstream.
[...]
> Performance
> ===========
>
> The tests were performed using the xdp_rxq_info sample program with
> the following command-line:
>
> 1. XDP_DRV:
> # xdp_rxq_info --dev eth0 --action XDP_DROP
> 2. XDP_SKB:
> # xdp_rxq_info --dev eth0 -S --action XDP_DROP
> 3. xdp-perf, from selftests/bpf:
> # test_progs -v -t xdp_perf
What is this test_progs? I don't see such ann app under selftests/bpf
> Run with mitigations=auto
> -------------------------
>
> Baseline:
> 1. 22.0 Mpps
> 2. 3.8 Mpps
> 3. 15 ns
>
> Dispatcher:
> 1. 29.4 Mpps (+34%)
> 2. 4.0 Mpps (+5%)
> 3. 5 ns (+66%)
>
> Dispatcher (full; walk all entries, and fallback):
> 1. 20.4 Mpps (-7%)
> 2. 3.8 Mpps
> 3. 18 ns (-20%)
Are these packets received on a single queue? Or multiple queues?
Do you see similar improvements even with xdpsock?
Thanks
Sridhar
Powered by blists - more mailing lists