All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: Edward Cree <ecree@solarflare.com>,
	davem@davemloft.net,
	Alexei Starovoitov <alexei.starovoitov@gmail.com>,
	Alexei Starovoitov <ast@fb.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	iovisor-dev <iovisor-dev@lists.iovisor.org>
Subject: Re: [PATCH v3 net-next] bpf/verifier: track liveness for pruning
Date: Wed, 16 Aug 2017 00:12:58 +0200	[thread overview]
Message-ID: <599371EA.20605@iogearbox.net> (raw)
In-Reply-To: <f40d3d54-c88a-7348-99ca-66db8075a8d5@solarflare.com>

On 08/15/2017 09:34 PM, Edward Cree wrote:
> State of a register doesn't matter if it wasn't read in reaching an exit;
>   a write screens off all reads downstream of it from all explored_states
>   upstream of it.
> This allows us to prune many more branches; here are some processed insn
>   counts for some Cilium programs:
> Program                  before  after
> bpf_lb_opt_-DLB_L3.o       6515   3361
> bpf_lb_opt_-DLB_L4.o       8976   5176
> bpf_lb_opt_-DUNKNOWN.o     2960   1137
> bpf_lxc_opt_-DDROP_ALL.o  95412  48537
> bpf_lxc_opt_-DUNKNOWN.o  141706  78718
> bpf_netdev.o              24251  17995
> bpf_overlay.o             10999   9385
>
> The runtime is also improved; here are 'time' results in ms:
> Program                  before  after
> bpf_lb_opt_-DLB_L3.o         24      6
> bpf_lb_opt_-DLB_L4.o         26     11
> bpf_lb_opt_-DUNKNOWN.o       11      2
> bpf_lxc_opt_-DDROP_ALL.o   1288    139
> bpf_lxc_opt_-DUNKNOWN.o    1768    234
> bpf_netdev.o                 62     31
> bpf_overlay.o                15     13
>
> Signed-off-by: Edward Cree <ecree@solarflare.com>

Acked-by: Daniel Borkmann <daniel@iogearbox.net>

  reply	other threads:[~2017-08-15 22:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-15 19:34 [PATCH v3 net-next] bpf/verifier: track liveness for pruning Edward Cree
2017-08-15 19:34 ` Edward Cree via iovisor-dev
2017-08-15 22:12 ` Daniel Borkmann [this message]
2017-08-15 23:32   ` David Miller
2017-08-18  3:21 ` Alexei Starovoitov
2017-08-18  3:21   ` Alexei Starovoitov via iovisor-dev
2017-08-18 14:16   ` Edward Cree
2017-08-18 14:16     ` Edward Cree via iovisor-dev
2017-08-18 23:37     ` Alexei Starovoitov
2017-08-18 23:37       ` Alexei Starovoitov via iovisor-dev
2017-08-21 18:36       ` Edward Cree
2017-08-21 18:36         ` Edward Cree via iovisor-dev
2017-08-21 20:27         ` Daniel Borkmann
2017-08-21 20:27           ` Daniel Borkmann via iovisor-dev
2017-08-21 20:44           ` Edward Cree
2017-08-21 20:44             ` Edward Cree via iovisor-dev
2017-08-21 21:00             ` Daniel Borkmann
2017-08-21 21:23               ` Alexei Starovoitov
2017-08-21 21:23                 ` Alexei Starovoitov via iovisor-dev
2017-08-21 20:24     ` Edward Cree
2017-08-21 21:18       ` Alexei Starovoitov
2017-08-21 21:18         ` Alexei Starovoitov via iovisor-dev

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=599371EA.20605@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=alexei.starovoitov@gmail.com \
    --cc=ast@fb.com \
    --cc=davem@davemloft.net \
    --cc=ecree@solarflare.com \
    --cc=iovisor-dev@lists.iovisor.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.