From: Andrii Nakryiko <andrii.nakryiko@gmail.com>
To: Alexei Starovoitov <ast@kernel.org>
Cc: davem@davemloft.net, Daniel Borkmann <daniel@iogearbox.net>,
Networking <netdev@vger.kernel.org>,
bpf@vger.kernel.org, Kernel Team <kernel-team@fb.com>
Subject: Re: [PATCH v2 bpf-next 0/3] bpf: optimize explored_states
Date: Tue, 21 May 2019 22:54:12 -0700 [thread overview]
Message-ID: <CAEf4BzbZyTiF8KZBdPS0pxfCHfTEZSjgDLFDywR7yi5=M_86wQ@mail.gmail.com> (raw)
In-Reply-To: <20190522031707.2834254-1-ast@kernel.org>
On Tue, May 21, 2019 at 8:17 PM Alexei Starovoitov <ast@kernel.org> wrote:
>
> Convert explored_states array into hash table and use simple hash to
> reduce verifier peak memory consumption for programs with bpf2bpf calls.
> More details in patch 3.
>
> v1->v2: fixed Jakub's small nit in patch 1
>
> Alexei Starovoitov (3):
> bpf: cleanup explored_states
> bpf: split explored_states
> bpf: convert explored_states to hash table
>
> include/linux/bpf_verifier.h | 2 +
> kernel/bpf/verifier.c | 77 ++++++++++++++++++++++--------------
> 2 files changed, 50 insertions(+), 29 deletions(-)
>
> --
> 2.20.0
>
For the series:
Acked-by: Andrii Nakryiko <andriin@fb.com>
next prev parent reply other threads:[~2019-05-22 5:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 3:17 [PATCH v2 bpf-next 0/3] bpf: optimize explored_states Alexei Starovoitov
2019-05-22 3:17 ` [PATCH v2 bpf-next 1/3] bpf: cleanup explored_states Alexei Starovoitov
2019-05-22 3:17 ` [PATCH v2 bpf-next 2/3] bpf: split explored_states Alexei Starovoitov
2019-05-22 3:17 ` [PATCH v2 bpf-next 3/3] bpf: convert explored_states to hash table Alexei Starovoitov
2019-05-22 5:54 ` Andrii Nakryiko [this message]
2019-05-24 8:05 ` [PATCH v2 bpf-next 0/3] bpf: optimize explored_states Daniel Borkmann
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='CAEf4BzbZyTiF8KZBdPS0pxfCHfTEZSjgDLFDywR7yi5=M_86wQ@mail.gmail.com' \
--to=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=kernel-team@fb.com \
--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 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).